BostonGIS Blog

We've made our first huge milestone. With much of Steve Woodbridge's help and patience as well as support from pgRouting Windows campaign sponsors, we have windows PostgreSQL 9.2 binaries for the pgRouting 1.07 development branch for both PostgreSQL 32-bit and 64-bit. You can download these from: Winnie's 9.2 windows downloads. Details on how to install are described on Windows download page at bottom. Please give these a try to see if they work okay for you. These binaries will work for PostGIS 2+ releases as well as the experimental PostGIS 2.1 builds and upcoming PostGIS 2.1 release.

We are still missing payments from some pgRouting sponsors. So if you haven't sent us payment yet, please do so. If you weren't on the initial campaign and would still like to give, you can still contact us at lr at pcorp dot us to make payment arrangements. If you want to contribute, we ask you do $100 USD or more since smaller amounts are too much bookkeeping. Any additional money's will go toward work on pgRouting 2.0 (not just Windows but general support of the rewrite) and future buildbot upgrades.

Steve is now pushing further forward with upcoming pgRouting 2.0, so the pgRouting code base will soon be a bit volatile and unstable. We are still in middle of setting up the buildbot to automate the future builds and then come PostGIS 2.1, you can expect to see pgRouting included in the PostgreSQL 9.2+ PostGIS 2.1 application stack builder packages.

We have a confession to make. We're not GIS analysts; we just play one at parties. Truth is the bread and butter of our business involves pretty boring stuff like e-Commerce, pricing (venture capital, private equity, travel, pension management), project management, work force management and all that other stuff that would bore a real GIS analyst to tears. Somehow we've got a lot of pictures to deal with particularly with project management and e-commerce work. So I was elated when Bborie checked in this new function ST_FromGDALRaster. With this function you can do all resizing and other manipulations right in the database with standard type images like PNGs, bitmaps and anything else users will throw at you.

As mentioned before, we like keeping our work related pictures in the database, but every once in a while, we'd like to manipulate them and it would be nice not to have to keep many sizes of one image in the database. Having to drag them out of the database to do stuff with them is kind of a pain or to keep extra sizes is also a pain. We'd like to keep the original format we were given intact, but all other custom sizes people ask for do on the fly.

For these operations, I'm using:

Using the buildbot builds generated by Winnie PostGIS buildbot.

The Boston OSGeo Code Sprint ended today. Overall I think it was a great success just in terms of what was accomplished and the fact that it was the very first conference we had ever set up. We were all nerves so couldn't enjoy it as much as we wanted to. It was also the first conference we were able to sorta attend all days for.

Paul already gave a great cap on what was going on in the PostGIS and MapServer camps. I still felt like there was way too much coding going on and would be nice to have a bit more talking and a bit less typing.

I want to thank EnterpriseDb for being a Gold Sponsor and it would have been nice if they gave a talk. Maybe I can drag them in some other day. Rich Grady, of AppGeo gave a wonderful and humorous talk about the metamophisis AppGeo is going thru coming from a predominantly ESRI shop, now focused on the prize of finding the best solutions to solve spatial IT problems; which surprisingly does not always involve ESRI and is more and more requiring Open Source GIS technologies. They did show off their ESRI medals of honor and how well they kept papers from flying around.

For those who contributed to our pgRouting campaign, a BIG THANKS. We'll be circling back later this week or early next to try to finish collecting and charging credit cards. If you already wrote us asking, but how do I pay? and we haven't responded with details, don't worry about it. We'll get to you next week. More concerned about those who haven't contacted us.