Optimum settings for MS SQL Spatial Database writer.
Our workflows creates a MS SQL Spatial database. However we are getting a significant amount of Linestring type entities when we open the same database in Postgis. What are the optimum defaults in the sql spatial writer which could avoid the problem. Are there any other steps we could add to our shape file preparation workflow which could also assist with the issue?
Userlevel 4
+13
- Contributor
- 3725 replies
-
11 November 2015
Could you provide a few more details as to what the expected result is in MS SQL and what the overall workflow is? Sounds like you're going Shape->MSSQL and then as a parallel exercise Shape->PostGIS? And getting different results?
Reply
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.