Differences between revisions 2 and 3
⇤ ← Revision 2 as of 2014-04-01 21:20:39 →
Size: 918
Editor: scot
Comment:
← Revision 3 as of 2014-04-01 21:21:15 → ⇥
Size: 901
Editor: scot
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
Chris Dant did a nice job of presenting this chapter. Note the following problems: Chris Dant did a nice job of presenting this chapter.
Line 5: Line 5:
 1. Problems with KML export: I haven't solved the problem yet, but it appears that the re-projection is not correct. If you run the following query you will notice 2 things. 1) The visualization is a solid rectangle encompassing the world. 2) Not all polygons are valid and if you retrieve only the ones that are invalid, they look ok in the visualization. Very odd. '''Problems:'''

Problems with KML export: I haven't solved the problem yet, but it appears that the re-projection is not correct. If you run the following query you will notice 2 things. 1) The visualization is a solid rectangle encompassing the world. 2) Not all polygons are valid and if you retrieve only the ones that are invalid, they look ok in the visualization. Very odd.
Line 17: Line 19:
 2. Visual Studio 2013 doesn't have any Business Intelligence templates yet so the SSIS package is not something that we did. Further it appears to be quite SQL Server Version specific. Visual Studio 2013 doesn't have any Business Intelligence templates yet so the SSIS package is not something that we did. Further it appears to be quite SQL Server Version specific.

Importing Spatial Data

Chris Dant did a nice job of presenting this chapter.

Problems:

Problems with KML export: I haven't solved the problem yet, but it appears that the re-projection is not correct. If you run the following query you will notice 2 things. 1) The visualization is a solid rectangle encompassing the world. 2) Not all polygons are valid and if you retrieve only the ones that are invalid, they look ok in the visualization. Very odd. 

SELECT *, geog4326.STIsValid() as geog4326 
FROM precincts_reprojected

--Also try this one:

SELECT *, geog4326.IsValidDetailed() as geog4326 
FROM precincts_reprojected
WHERE NOT (geog4326.IsValidDetailed() LIKE '24400%')

Visual Studio 2013 doesn't have any Business Intelligence templates yet so the SSIS package is not something that we did. Further it appears to be quite SQL Server Version specific.

GeographicInformationSystems/ImportingSpatialData (last edited 2014-04-01 21:21:48 by scot)