Today was the last day of the Boston OSGeo code sprint we hosted. Several OSGeo project tribes were represented.
PostGIS had a big showing with core PostGIS developers and related working on PostGIS core, PostGIS 3D, PostGIS raster, pgRouting, geocoding, and point clouds.
Leo and I with lots of help from Steve Woodbridge, spent a good chunk of time working out kinks of PostGIS pgRouting packaging for Windows and address normalizer replacement for the one packaged with tiger geocoder.
A special shout-out thanks to all the Code Sprint sponsors:
We have all the setup executables for PostgreSQL 8.4-9.2 32-bit and
PostgreSQL 9.1-9.2 x64-bit for PostGIS 2.0.3. We'll have the 9.0x64-bit
ones up shortly but do have the binaries.
We are planning to release these to stackbuilder sometime next week, but
would like some feedback first with any issues people run into.
One person already reported a serious bug in our original packaging which we
fixed. If you already installed 2.0.3 the x64-bit version or any of the 9.2
versions (both x32 and x64) that was not marked as -2.zip, -2.exe, you'll
want to reinstall. The 8.4-9.1 32-bits were not affected so just have a -1.
Should I install using PostGIS extension? is an FAQ that comes up quite a bit in PostGIS circles and unfortunately askers get mixed answers.
In How to upgrade your database to PostGIS 2.0
we covered WHY you should use extensions. In this article I'll use my Lincoln-Douglas debate skills to argue why you shouldn't.
Keep in mind that I put a great deal of effort in fitting PostGIS extensions
into the existing PostGIS build structure and I eat my own dogfood, so I might be a little biased and a poor defender of the counter argument.