SQL Server 2008 Spatial: Lack of Arc support...

While I have been unable to find any direct information from the Microsoft website regarding a lack of support for arc segments in the new SQL Server 2008 Spatial, I did find a few posts on the Microsoft Tech Forums, and one specifically from Isaac Kunen stating that arcs are not supported, and are a high priority item for the next release.

Personnaly, I think this a deal-breaker for many organizations, and I believe it would be in Microsoft's best interest to address this shortcoming sooner, rather than later.

Here ia another great comparison document that cross compares SQL Server 2008 Spatial, PostgreSQL/PostGIS 1.3-1.4, MySQL 5-6

Take Care,
Warren
AU in 60 days

Comments

Anonymous said…
I believe that it also requires valid geometry; spatial queries (including basic BBOX requests) were throwing exceptions when encountering invalid geometries when I was testing with the RCs.

This can be a problem; as far as I know Map doesn't have any way of testing for OGC validity. Inserting one invalid feature can really mess up, for instance, a MapGuide map where every request includes an envelopeintersects call.

Ideally, SQL Server would include a "loose compliance" mode.
October 8, 2008 at 11:40 PM
Warren J. Medernach, BGIS, GISP said…
Thanks for the additional info Jason! Great stuff!

So there's obviously some holes yet to be addressed, as we might expect in a first release.
October 9, 2008 at 12:44 PM
Post a Comment

Popular posts from this blog

ArcGIS: Packaging error - General function failure

Image
Whoa... 2 posts within 2 months...  I'm on a roll baby...   :-) In today's episode I want to document what I've discovered with the following lovely error when attempting to create a Map Package: I've had this very insightful (hint:sarcasm) message box pop-up a number of times when trying to create a Map Package.  After much copying/pasting, renaming, re-connecting data sources I finally figured out what the problem was in this particular instance. This particular map had some DWG files connected to the map, and some of these DWG names contained a special character "#", and also contained extra 'dots' in the name to delimit a date.  For example: Name#-2013.04.09.dwg In my testing and trials, removing the '#' symbol did not resolve the issue, and it wasn't until I removed the extra 'dots' in the name that I was finally able to successfully generate the package.  Further testing revealed that the '#' symbol
Read more

More ArcGIS Woes with 'Special' Characters...

Image
It's no secret that I've griped and complained about many of ArcGIS's quirks that seem stuck or rooted in the 80's ...  One would think I wouldn't be surprised anymore when I come across such silly issues... But I am. The latest 'undocumented feature' I've discovered is that the Field Calculator will fail if there is forward slash ( '\' ) in the Layer name. ArcGIS 11 can't come soon enough.
Read more

ArcGIS Collector: Update Error Code 1006

Image
Alright, this is the second time this happened to me, and I neglected to document it the first time, so I had to search again to find the answer, so I will document it here, and now. Here goes... If you happen to come across ArcGIS Collector throwing an error when updating a feature, and the error states something along the lines of: Invalid untrusted Html content detected in field: Have no fear, there is a simple fix.  Well, that is, it's a simple fix if this is 'local' map, not accessible to the general public.  That's only because ESRI doesn't actually 'recommend' this fix. So what is 'this fix' I speak of? A little more background... If you have any fields that contain HTML content, there is a chance that Collector could see that as malicious content, and it will block it.  You can see a list of allowable HTML tags in Collector a this link . In my instance, I am running some database triggers to populate and update a URL field, where
Read more