Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Investigating the new Spatial Types in SQL Server 2008 - Part 1 Expand / Collapse
Author
Message
Posted Wednesday, November 19, 2008 12:27 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, February 10, 2014 10:30 AM
Points: 4, Visits: 63
Comments posted to this topic are about the item Investigating the new Spatial Types in SQL Server 2008 - Part 1
Post #604927
Posted Wednesday, November 19, 2008 12:47 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Thursday, July 17, 2014 10:36 PM
Points: 5,303, Visits: 1,378
Good one. It will be a good series.


Post #604930
Posted Wednesday, November 19, 2008 12:56 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, May 17, 2013 12:43 AM
Points: 3, Visits: 57
Good intro.

Looking forward to some real world TSQL examples.
Post #604932
Posted Wednesday, November 19, 2008 6:27 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, May 1, 2012 10:31 AM
Points: 17, Visits: 105
Nice article - you seem to have laid out a good foundation of topics to cover. There are just a couple of points I wanted to add:

The SQL Server-native geography and geometry datatypes are NOT stored using Well-Known Binary format. WKB is administered by the OGC, just like WKT and GML are. Internally, SQL Server uses a custom binary format.

Although the WKT representation of a geometry/geography instance may be defined using a z coordinate (representing the elevation/depth of a point), none of the inbuilt methods actually perform any operations using this coordinate, so it's for storage only. All operations take place on the (flat) 2-dimensional plane of the geometry datatype, or the (curved) ellipsoidal surface of the geography datatype.

You say that geographic coordinates of latitude/longitude are most common, but that depends a lot on the sort of data you want to use - for instance, here in the UK most data uses the GB national grid system (and many other European countries use their own national grid), and most of the detailed spatial information for the US is provided at state-level using the relevant state plane coordinate system (such as from http://www.mass.gov/mgis/database.htm). If you want to use this sort of data, you need the geometry datatype, not geography.

Other than that - good stuff! I look forward to the rest of the series.

For anybody interested in finding out more about spatial in SQL Server 2008, check out:
"Beginning Spatial with SQL Server 2008" (Apress)
http://www.apress.com/book/view/9781430218296
Post #605085
Posted Wednesday, November 19, 2008 10:53 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, March 7, 2011 9:43 AM
Points: 2, Visits: 5
Well done.

Although here in the latter part of my career I am firmly positioned in the small business development world, your enticing introduction to this series of articles immediately took me back to my previous "sub-career" as an analyst and department manager in the defense systems simulation arena. How we could have used OO and spatial databases in those days!

Looking forward to more...
Post #605295
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse