GDAL 1.9 Brings Esri FGDB and Google Fusion Tables Support

Good news for users of GDAL/OGR:

The GDAL/OGR team is pleased to announce the release of GDAL/OGR 1.9.0.
This is a major new release including the following major new features:

* New GDAL drivers: ACE2, CTG, E00GRID, ECRGTOC, GRASSASCIIGrid,
GTA, NGSGEOID, SNODAS, WebP, ZMap
* New OGR drivers: ARCGEN, CouchDB, DWG, EDIGEO, ESRI FileGDB, Geomedia,
Google Fusion Tables, IDRISI, MDB, SEGUKOOA, SEGY, SVG, XLS
* Significantly improved drivers: NetCDF
* Encoding support for shapefile/dbf (#882)
* RFC 35: Delete, reorder and alter field definitions of OGR layers
* RFC 37: Add mechanism to provide user data to CPLErrorHandler (#4295)
* gdalsrsinfo: new supported utility to report SRS in various form
(supercedes testepsg)

Some nice new formats in there.  How does it all work?  Paolo Corti takes a look and says, “Brilliant!”.

Frank Warmerdam Goes to Google — Google Unimpressed with our Niche Awesomeness

Late yesterday morning I saw something on Facebook that caught my eye.  Frank Warmerdam posted that he was moving to California and join Google[ref]We learn this stuff on Facebook these days apparently.[/ref]. He later blogged about it and it’s now all over the internets.

Today I accepted a job with Google as a GIS Data Engineer. I will be based in Mountain View California at head office, and involved in various sorts of geodata processing though I don’t really know the details of my responsibilities yet.

Mr. Warmerdam Goes to Google -- Click for full size goodness!

Frank says he was looking for a change[ref]I can’t tell you how many people I’ve talked to in the past month that are saying the same thing, clearly our niche is stale[/ref] and the awesome of Google was too much for him to turn down.  You really need to read Frank’s post.  Google had no idea what they were interviewing even though they are a huge user of GDAL.  It looks like eventually smart people at Google came forward to attest to Frank’s history and he was hired as a non-entry level tech.  Here is one of our best and brightest and Google just looked at him as a number[ref]Wake up call people![/ref].

Google does make use of GDAL/OGR for some internal data processing and in products like Google Earth Professional. My original hope had been that my job would at least partly be in support of GDAL and possibly other open source technologies within Google. While things are still a bit vague that does not seem to be immediately the case though I’m optimistic such opportunities might arise in the future. But I think this usage does mean that work on GDAL is a reasonable thing to spend 20% time on.

I always assumed Esri would eventually hire Frank to work on their raster conversion stuff as they already pay him, but it appears that Frank is moving on to better things.  Clearly he’s not giving up on GDAL/OGR, but his focus could be elsewhere.  Say’s Frank:

Writing file translators for 20 years can in some ways become a rut!

Best of luck Frank, we all appreciate your hard work every time we open any geospatial application since your hard work is in the core of everything we do.  And Google?  They’ve got top men working on just about anything.  Wow!

 

More Command Line GIS Goodness

I’ve been talking quite a bit about using ArcPy and Python as a means to go back to using the command line for GIS analysis. You get such a better understanding as to what you are doing with the geospatial analysis functions when you type them in manually rather than using a wizard.

There are other ways to do this though. Darren Cope has a short blog post on using OGR for clipping GIS data files. Simple and sweet!

It’s just that easy, and best of all it just works when all other methods fail!

That’s just it though, command line usually works when GUI’s fail.  The logical outcome is stop using the darn GUI!

GDAL/OGR 1.7.0 Released

Good news from the gdal-announce email list:

The GDAL/OGR Project is pleased to announce the release of GDAL/OGR 1.7.0.

Yep, you can stop there and get your GDAL/OGR on.  Or maybe you want to know what is new, copied directly from Frank’s email:

  • New Raster Drivers: BAG, EPSILON, Northwood/VerticalMapper, R, Rasterlite, SAGA GIS Binary, SRP (USRP/ASRP), EarthWatch .TIL, WKT Raster
  • GDAL PCIDSK driver using the new PCIDSK SDK by default
  • New Vector drivers : DXF, GeoRSS, GTM, PCIDSK and VFK
  • New utilities: gdaldem, gdalbuildvrt now compiled by default
  • Add support for Python 3.X. Compatibility with Python 2.X preserved
  • Remove old-generation Python bindings.
  • Significantly improved raster drivers: GeoRaster, GeoTIFF, HFA, JPEG2000 JasPer, JPEG2000 Kakadu, NITF
  • Significantly improved vector drivers: CSV, KML, SQLite/SpataiLite, VRT

I did a little highlighting up there to list what I think is noteworthy at least for me. You can either build it yourself or keep an eye out for an update of FWTools.

 

The Leningrad Cowboys will play us off, have a great weekend folks!

GeoServer 1.7.2 continues improvements to Cartography

As with GeoServer 1.7.1, the latest release improves some cartographic rendering capabilities of the Open Source server product. 1.7.2 brings wrapped labels and hatching to render some impressive maps. Other new additions include HTML image mapping, OGR extension to output WFS as any supported OGR output formats (I get chills thinking of the possibilities), and improvements to GeoExt Styler. If that still doesn’t get you interested, this little tidbit at the end of the post should catch your eye:

Stay tuned for the 1.7.3 release, slated for release in the next month, which will include improvements to Geo Search, and the official release of the REST configuration API.

Using OGR to Visualize Data

The biggest excuse I hear time and time again for not using open source geospatial tools is that they are too confusing to use. Take GDAL/OGR for example, the webpage probably scares off most users because of the lack of examples of how to use both toolsets. But the tools themselves are so easy to use this shouldn’t scare anyone off. In fact, if you’ve used ArcInfo to convert a coverage to a shapefile in your past, you have all the skills needed to use both GDAL and OGR.

That said Tom Kralidis has a great example of using OGR to convert a Microsoft Excel file to KML. GDAL/OGR is integral to so many GIS applications (even ESRI uses it) that any GIS professional should have at least a basic understanding to how it works. Look at Tom’s example, download FWTools and get cracking on using GDAL/OGR.


Fans of the Waffle House wait for open source geospatial tool users to create GeoRSS feed of store locations

The Holy Grail

This is clear to me:

FeatureServer + ArcSDE Data Store = Holy Grail

Being able to store data in ArcSDE, but still access it freely across any and all platforms. ArcGIS clients can hit ArcSDE and everyone else can enjoy data served by FeatureServer. But deep down this is even bigger than FeatureServer because really what I’m talking about is GDAL/OGR ArcSDE Vector Write Support. That opens up loads of open source projects to ArcSDE users and gives them the best of all worlds. ArcGIS Desktop/Server users can continue using ArcSDE they way they always have and open source solutions can come right in the front door and coexist with existing workflows. The benefit will be realized by users who will be able to get products that work best for them.

If I have to sell Amway door to door, I will get this project funded.


The gatekeeper will no longer be able to stop users from writing to ArcSDE from OGR.