James Fee GIS Blog

8 Comments

1. Tim Maddle says:

   March 1, 2008 at 9:48 am

   Thanks for pointing out this blog. I’m just about to install the new CTP to see if it can handle buffering large polygons a bit better. Given that SQL Server 2008 is still in CTP status, will it actually make its debut in 2009?
2. Ed Katibah says:

   March 1, 2008 at 2:16 pm

   While we are making no promises, things are on target to ship SQL Server 2008 in Q3 of 2008.

   On the issue of “…buffering large polygons a bit better…”, let me know what problems you’ve been having. We are actively fixing any bugs or misbehavior we can find.
3. Tim Maddle says:

   March 2, 2008 at 8:56 am

   @Ed,
   My problem was that when I tried to buffer a particular large, complex polygon, SQL Server would start grabbing a lot of memory (hundreds of megabytes) and I would always have to stop the SQL Server process before the buffering could complete. PostGIS seems to handle the process a lot better, buffering the polygon in a few seconds. I’m instaling the new CTP now. Once done, I’ll try the buffer again and see if I get the same result. If so, I’ll zip the shapefile that I imported into SQL Server and indicate the polygon that’s giving me problems.
4. Abe says:

   March 3, 2008 at 8:55 pm

   @Ed

   I vote to rename your blog to “Spatial Ed.” Come on, it’s too good to pass up!
5. Ed Katibah says:

   March 3, 2008 at 10:16 pm

   @Tim,
   When you are ready, let me know (ed.katibah at microsoft.com) and I’ll set up a site to drop the shapefile off.

   @Abe,
   I’ll consider it…
6. Ed Katibah says:

   March 5, 2008 at 10:04 pm

   @Abe
   It is as you have wished…
7. Abe says:

   March 5, 2008 at 11:10 pm

   
8. Tim Maddle says:

   March 6, 2008 at 6:05 pm

   I emailed Ed my problem shapefile. Ed ran a buffer on the problem polygon and the process seems to be much improved. Thanks, Ed.