The U.S. has binders full of TIGER deserts. Let me explain. Back in 2007, we imported TIGER/Line data from the U.S. Census into OpenStreetMap. TIGER/Line was and is pretty crappy geodata, never meant to make pretty maps with, let alone do frivolous things like routing. But we did it anyway, because it gave us more … Continue reading Binders Full Of TIGER Deserts
I had what I thought was a pretty straightforward use case for OpenStreetMap data: I want all bridges in the US that are mapped in OpenStreetMap in a PostGIS database. There are about 125,000 of them - for now loosely defined as 'ways that have the 'bridge' tag'. So on the scale of OpenStreetMap data … Continue reading A self-updating OpenStreetMap database of US bridges – a step-by-step guide.
Looks can be deceiving - we all know that. Did you know it also applies to maps? To OpenStreetMap? Let me give you an example. Head over to osm.org and zoom in to an area outside the major metros in the United States. What you're likely to see is an OK looking map. It may … Continue reading The State Of The OpenStreetMap Road Network In The US
OpenStreetMap represents a lot of data. If you want to import the entire planet into a PostGIS database using osmosis, you need at least 300GB of hard disk space and, depending on how much you spent on fast processors and (more importantly) memory, a lot of patience. Chances are that you are interested in only … Continue reading Tutorial: Creating buffered country POLYs for OpenStreetMap data processing