Slashgeo Log In
Microsoft SQL Server Spatial Plans
posted by Satri
on Wednesday April 12, @10:11AM
Permalink
Trackback URI
Slashdotthis
Diggthis
Del.icio.us
from the follow-the-floc-but-only-after-a-while dept.
from the follow-the-floc-but-only-after-a-while dept.
All Points Blog links to an CRN article about Microsoft SQL Server plans in an interview with VP Flessner. From the article: ""You will see an investment in spatial indexing, geometry libraries. I want to do a good job supporting ESRI and other geo-spatial guys and make a good library available so if you can't afford those packages do good spatial analysis with out them," Flessner said. [...] When will that happen? The next four to six years, although he'd like to get more done "sooner rather than later.""
Related Stories
Geographic Data Support in Next Microsoft SQL Server 1 comment
[+]
The Memory Leak blog informs us about geodata support for the upcoming Microsoft SQL Server expected in 2008. All Points Blog adds more details and links. From APB: "Spatial will be supported in the next release of SQL Server (code named Katmai) as system data types.
Katmai is scheduled to ship in 2008 and will most likely be called SQL Server 2008.
Katmai spatial will support two models: a “Flat Earth” planar data type and a “Round Earth” geodetic data type.
The Flat Earth data type (GEOMETRY) will support the Open Geospatial Consortium (OGC) Simple Features for SQL Specification with support for approximately 70 spatial methods/functions.
There will be spatial indexes for both planar and geodetic data types."
Technology: Spherical Indexing Schemes and PostGIS
[+]
The Lin.ear th.inking blog ran an entry last month on spherical indexing schemes for PostGIS. Thought not exhaustive, the entry is still interesting and reminds us how spatial indexes are important to efficiently analyze huge spatial databases. From the entry: "Handling geodetic data in a correct and efficient way presents quite a few challenges. A major one is: how can geodetic geometry be spatially indexed? Conventional spatial indexes (such as 2D R-trees) all rely on geometry being embedded in a planar space. They don't handle data which can "wrap around", as can occur in a spherical space." See below for other (rare) stories related to spatial indexes.
Technology: Safe Software's FME to Support SQL Server 2008
[+]
Safe Software writes "“Safe Software continues to extend the power of our leading FME platform to address the broad spectrum of spatial ETL challenges that IT and GIS Professionals face,” says Don Murray, President of Safe Software. “We are committed to helping Microsoft SQL Server customers realize the benefits of tapping into their spatial and non-spatial data assets and are pleased to enhance FME to support SQL Server 2008.”" I deleted the rest of the press release, head here if you want it all. See also related stories below.
Several Software Announces Support for SQL Server 2008 5 comments
[+]
All Points Blog did what I was going to do, to point out the several announcements for support of Microsoft SQL Server 2008, which includes new spatial capabilities. Here are the full press releases: Safe, Manifold, SpatialPoint, AWhere). In addition, there's MapDotNet Server 6.5 which will also support the new SQL Server. See also related stories below.
Virtual Earth support for SQL Server 2008
[+]
Flat Out GIS has an article about this speculation. Here is there summary : "I’m comparing Google Maps versus Virtual Earth right now, and one of the deciding factors is spatial data support. With the upcoming release of SQL Server 2008 spatial support, will VE be able to read these new WKB and WKT types natively? I saw a news release from Microsoft indicating several partners have developed this capability for their products, but was looking for information on whether or not it will become part of the VE api. It would be a plus if VE could read SQL Server geometry and render them automatically without additional coding."
To get the link to the actual microsoft release, head on over to Flat Out GIS.
To get the link to the actual microsoft release, head on over to Flat Out GIS.
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.




