OpenGeo Suite – A Milestone

On May 28th OpenGeo announced the release of the OpenGeo Suite. They also describe their open pricing structure for support of the suite.

This announcement represents a milestone for open-source geospatial software. If you are of a technical nature and are expecting a detailed discussion of the technical advantages of the OpenGeo Suite, you should probably stop reading now. The OpenGeo Suite is a milestone because it establishes a fair pricing model that addresses what, in my opinion, has been the primary barrier to the adoption of open-source GIS in many enterprises: risk. Continue reading “OpenGeo Suite – A Milestone”

Bringing It All Together…

These are pretty fun times to be working in GIS. There’s an explosion of new technologies across the whole spectrum and integration possibilities are seemingly boundless. Back when I got started, ESRI and Intergaph were duking it out and others, like MapInfo, were out there on the periphery also. GRASS was flying the OS banner and there were a few good free tools, such as the various ones put out by Sol Katz at the BLM.

Everything quieted down for a few years but there’s been a flowering of new technologies (well-documented elsewhere) over the last couple of years in both the commercial and open-source communities. I am particularly impressed with the pace at which the open-source community has ramped up with tools of strong quality and capability. In addition, the back-and-forth between Google and Microsoft has put better tools in the hands of the average consumer. That doesn’t come without drawbacks, but I see it as a net positive.

What I find interesting about all of this activity is that it demonstrates that the closed/commerical/competitive approach can bear fruit and so can the open-source/free/collaborative approach. Where you fall in the spectrum between the two is totally up to you but no one can offer up any concrete evidence that one is vastly superior to the other at this point. In addition, it’s becoming increasingly clear that they don’t have to be mutually exclusive.

When you throw in OGC standards and well as de facto standards such as KML, it becomes quite possible to stitch together technologies of various parentage effectively. I offer up the following as a concrete example:

This screenshot depicts a map (no, it’s not pretty but blame that on me) that was assembled using several technologies. The application is obviously ArcMap. Working from the bottom up, the layers are:

  • Counties – US Counties residing in ArcSDE and SQL Server
  • State Boundaries – US States loaded directly from a local install of PostGIS using the zigGIS connector
  • Major Water – A shapefile on the local hard drive
  • Hospitals – A WFS layer being served from my GeoServer instance and loaded into ArcMap with the help of the free CarbonArc Lite extension from the Carbon Project. Behind Geoserver, the data sits in PostGIS.

So we have commercially licensed software (ArcMap, ArcSDE, SQL Server), freeware (CarbonArc Lite) and open-source software (zigGIS, PostGIS, GeoServer, PostgreSQL) working together to make this product. All are good tools that, working together, bolster each others’ shortcomings. This kind of thing demostrates the “best-of-breed” (hate that term) concept very well.

A few months back, Paolo posted about mixing commercial and open-source tools. I think this will eventually be the prevalent means of doing business.

My Little Open-Source Stack

It’s been a while since I’ve posted and things have been busy. Soccer season has ended, the kids have finished school and I’ve finished up at my client site and moved back to the office. Among the many things I’ve been working on, I’ve started building an open-source GIS stack. It’s not entirely open-source since it’s installed on a Windows server but the purists will have to get over that.

So far, I’ve got PostgreSQL/PostGIS and GeoServer 1.5.1 installed. I’ve got GeoServer running as a Windows service and I’ve loaded a couple of data sets into PostGIS, serving one out through GeoServer for now. I’ve been able to successfully connect to the WMS and WFS remotely using uDig as a client. KML seems to work fine for the sample data sets that install with GeoServer but my test layer doesn’t work correctly. That’s not as much of an issue for us right now because we’ll probably focus on World Wind for the spinny globe component. Basically, I’m at the infrastructure-building stage. My next step is to set up SharpMap and start writing some apps.

The only hiccup I’ve had so far dealt with getting GeoServer to run as a service. Every time I logged out, the service would stop (not a great feature in a service). It turns out that I had the DLL and JARs for the Java Service Wrapper in the wrong place. Now it works fine.

So far, I’m impressed with how smoothly it’s going. We’ll see how long that keeps up once I start slinging code. 😉

The road less traveled…