Geography is one of the spatial data types introduced in SQL Server 2008. One of the characteristic of the geography data type is that it can accommodate any supported geometry based on any supported spatial reference system in the same field. So if the data that is stored in a column of geography data type is not standardized, it can be a very tedious and resource intensive task to figure out the geometry and spatial reference system associated with each value. To deal with this issue, we need to standardize the data stored in a field of that has the geography data type and in this tip we will look at how to deal with this issue.
In Part IV of the Geo-Spatial series, an interactive dashboard is developed to present and interact with the data.
Part III of our spatial data series, continues building a demo spatial data app and uses Reports Builder for detailed visual mapping.
Continuing from Part I of the Spatial Data series we model an in-memory/persistent data repository for storing geocoded data and plot the data.
The institution I work with has decided to migrate their database system to SQL Server 2008. One of the applications uses geospatial data, which consists of millions of rows. I understand that their are indexes that can be used for geospatial data, but have not worked with them. What's the scoop on them?
The company I work for has migrated to SQL Server 2008 and we're ready to start planning for the use of geospatial data. One of the applications we want to use geospatial data in will assist order fulfillers in efficiently picking stock for orders. Our warehouse is fairly large, which geospatial data type should we use?