ArcGIS 10 Service Pack 2 Is Available

Esri announced late today that Service Pack 2 for ArcGIS 10 is available. It looks like a fairly sizable list of issues was addressed with this service pack.

Who knows, we could be witnessing history as this could potentially be the last service pack to address ArcIMS. (Well, I can dream, can’t I?)

Anyway, if you’re among those who like to wait until the second service pack before doing an Esri upgrade, you can now start putting 9.3 out to pasture. Live it up!

Out to pasture

Using ArcSDE 9.3 with PostgreSQL, Part 3.5

I thought I was done with the series a while back but I’ve been getting a steady stream of questions through other channels so I thought I’d wrap up a lot of the common stuff in another post. Most of the inquiries come from people trying to integrate ArcSDE for PostgreSQL with open-source tools in one way or another. Here are a few notes: Continue reading “Using ArcSDE 9.3 with PostgreSQL, Part 3.5”

SQL Server SIG at the UC

My blogging has been slower this time around because I’ve been doing a lot of booth duty. This is my thrid conference this year and some of our other staff are getting to go to the sessions. I did, however, go to the SQL Server SIG a little while ago.

Ed Katibah had a few tricks up his sleeve. First off, he dropped the news that, as of 11:00am, SQL Server 2008 is now in RTM. Very soon, the final version will be in our hands. That’s great news to everyone who has been working with the CTPs and RCs.

Ed had few other nuggets. He described the stress-testing that SQL 2008 has undergone. In short, there has been about 375,000 hours of stress testing run against SQL 2008 so we should be able to expect it to be solid. Additionally, Microsoft has already been running on SQL 2008 for “a few months.” To me, this is all great news that makes me feel even more confident about the product (which already had my confidence). When I first installed the November CTP, I felt that much of the platform was already production-ready but more testing and use can’t have hurt.

Ed went on to describe the two spatial types and reationale for doing that. That discussion is well documented and I fall in the “it’s a good thing category” mainly because of previous work with applications that had over-the-horizon requirements.

Ed gave props to Paul Ramsey during his talk when explaining the XY switching debate. It was great to see that kind of respect on display.

Some nuts and bolts: SQL 2008 limits spatial objects to about 250 million vertices. This greatly exceeds Ed’s largest test case, which is a high-res vector data set of the world’s oceans. Polygons are limited to about 65,000 holes. I think those limits leave a lot of wiggle room. He also discussed the significance of coordinate ordering for the geography data type. Basically, it’s counter-clockwise for outer rings and clockwise for inner rings. This is consistent with implementations in Informix, DB2 and Oracle (those are what he mentioned). He did mention that this was an industry consensus but there was no official specification on this matter. Ed also mentioned it may be a topic of future discussion for OGC.

Ed also demonstrated the spatial results window in the SQL management Studio. This is a really nice tool that lets you visualize the results of your spatial SQL inside the management studio. As a developer, that will be a huge help because I won’t have to do a test run to see if I got the query right. Ed just saved me a bunch of time!

Ed went on to announce a companion CodePlex site for SQL Server 2008 spatial tools: There are already some tools that Isaac has posted but Ed said that other tools will include shapefile and KML converters. The site will also be open to contribs from the community. All of the tools currently there were developed using the Builder API and full source code is available so they serve has great examples of working with the Builder API.

All in all, it was a great talk. Ed’s one of the nicest guys ever and he is having a lot of fun with ArcSDE on SQL Server 2008.

A Good PostGIS Overview…

Steven Citron-Pousty gave a talk on PostGIS and has helpfully posted his slides here. It’s a good introductory overview and provides some good examples of basic spatial SQL in PostGIS.

With ArcGIS Server now supporting PostgreSQL as a back end RDBMS and also supporting the use of PostGIS geometries, a lot of new users may be migrating to the PostgreSQL platform. This presentation is a good overview for anyone picking it up for the first time. Thanks, @TheSteve0!

ArcSDE Geocoding Services Deprecated at 9.3

This isn’t a huge surprise but this announcement made it official a couple of days ago.

Basically, you’ll need to use ArcGIS Server’s server-side geocoding because the next release of ArcSDE won’t include it. The PDF attached to the announcement gives more detail. I know we had moved away from ArcSDE geocoding some time ago because it didn’t hold up to the load we were putting on it. We used Oracle Spatial instead.

But, if you’ve got any apps that are still using ArcSDE for geocoding, now’s the time the transition.

Using ArcSDE 9.3 with PostgreSQL, Part 2

In my previous post, I discussed some approaches to configuring PostgreSQL databases and accessing the data in them with ArcSDE 9.3. For this post, I will describe some of my ongoing experiences with getting data into ArcSDE 9.3.

There are two main ways that I am investigating of loading/making available your spatial data in ArcSDE 9.3 for PostgreSQL. The first is the traditional method of importing a feature class via ArcCatalog. (You can also create data in this manner but I haven’t played with that yet.) The second is to register an existing PostGIS table as a layer using the “sdelayer -o register” command-line tool. I will discuss this latter option first. Continue reading “Using ArcSDE 9.3 with PostgreSQL, Part 2”

Using ArcSDE 9.3 with PostgreSQL, Part 1

First part in a series documenting my experiences with PostgreSQL and ArcSDE 9.3.

This post may cover some similar ground to that which Dave has been treading but I’m just trying to document my experiences as they occur.

By virtue of my association with zigGIS, I’ve been involved with using PostgreSQL and PostGIS in the ArcGIS envrionment for some time now. One of the primary sources of excitement about 9.3 for me was that ArcSDE would finally support PostgreSQL as an RDBMS platform. ArcSDE has always been positioned as an enterprise platform and has, therefore, been rather expensive. This expense has been compounded by the need to also separately license an RDBMS platform such as Oracle, SQL Server or DB2 in addition to ArcSDE. PostgreSQL helps alleviate some of that cost while also providing very advanced capability. Continue reading “Using ArcSDE 9.3 with PostgreSQL, Part 1”