I wrote up how to build a US Census Tract database earlier. However, we all know that data without a way of showing it on a map, is a little sad. So I wrote up the process I used to make it all available on a Google Map. The process involves the use of PostGIS, Mapnik, Node.js and just a smidge of magic. Its a longer post, so i lumped it in with my tutorials. You can go check it out here.

When talking with clients there is always a turning point in my mind where their request turns from being a "Google Map" to being a "web mapping application". It is usually where data is being filtered, updataed, or when 'users' are mentioned. This a pivotal point where the project both gets more interesting, a lot more complex, and likely more expensive for the client. in this post I will take apart what a web mapping aplicatiuon actually looks like and outline some high level application considerations.

This article shows how you (yes, you!) can build your very own US Census Tracts PostGIS database. I had looked over the interwebs for some time under the false assumption that someone, somewhere would have already done this, but it seems not. So this article documents my process. I am running a mac, so some things could be done faster / smarter using other technology refinements, but I have tried to keep things pretty generic for 'nix users. Windows people; you will find this process is pretty simple, I am sure you can replicate it using what you have available.

I remember in a previous job, I had to travel 2000kms on two flights to spend three nights in our Alberta head office to, in the end, act as a translator between a forester and a GIS resource. Although there was an ethnic difference, it was clear that the information gap was caused by the differences between those who could speak GIS and those who could not.