0 out of 1 rated this helpful - Rate this topic

Designing and Implementing Spatial Storage (Database Engine)

SQL Server 2008 R2

Spatial data represents information about the physical location and shape of geometric objects. These objects can be point locations or more complex objects such as countries, roads, or lakes.

SQL Server supports two spatial data types: the geometry data type and the geography data type. Both data types are implemented as .NET common language runtime (CLR) data types in SQL Server.

The geometry Data Type

The geometry data type (planar) supported by SQL Server conforms to the Open Geospatial Consortium (OGC) Simple Features for SQL Specification version 1.1.0.

For more information on OGC specifications, see the following:

SQL Server supports a subset of the existing GML 3.1 standard which is defined in the following schema: http://schemas.microsoft.com/sqlserver/profiles/gml/SpatialGML.xsd.

The geography Data Type

The geography data type (geodetic) stores ellipsoidal (round-earth) data, such as GPS latitude and longitude coordinates.

In This Section

Working with Spatial Data (Database Engine): Contains information about the types of spatial data in SQL Server Database Engine, how to create spatial data instances, how to query and retrieve properties and other information about spatial instances, and how to modify and create new spatial instances from existing ones.
Working with Spatial Indexes (Database Engine): Contains an introduction to spatial indexing in the SQL Server Database Engine and provides information about creating, altering, and dropping a spatial index.

Concepts

Getting Started with the geometry Data Type

Getting Started with the geography Data Type

Other Resources

Working with Spatial Indexes (Database Engine)

Did you find this helpful? Yes No

Not accurate

Not enough depth

Need more code examples

(1500 characters remaining)

Community Additions

ADD