How on Earth are we going to add addressing in to OpenStreetMap?

Today OSM is a great display map. It’s routable too if you squint. But it’s essentially not geocodable, you can’t turn an address in to a location.

If we fix that then there’s really not a whole lot of point to ever using a proprietary map ever again.

Here in the United States there are essentially two readily available sources. TIGER data has address ranges between intersections and counties (all 3,000 odd of them) have parcel data.

TIGER is public domain but it’s kind of crappy. There is a problem importing it because automatically taking TIGER ranges and putting them in our map is non-trivial. In lots of places new roads have been added, old ones deleted and so on. So, getting an address range in TIGER and then figuring out where to put it in OSM isn’t always easy.

Parcel data is much better but it’s all over the place. There are companies which will aggregate it together for you and sell it to you, but that’s millions of dollars of cost. And, they have no incentive to make it all available.

And it’s even worse in Europe. And even more worserer in Japan where addresses are assigned according to the age of the house and the block they are on, which may as well be random().

So what the hell are we going to do?

I say import the TIGER ranges and slap them on top of the map. They won’t impact the rendering. It will be kind of painful to go and fix all those ranges but it’s much better than what we have today (which is nothing).

All the other solutions are basically horrible. We could crowd-source it but that might take 100 years. We could try and raise the money to purchase the data. We could go visit all 3,000 counties. None of these is palatable.

So, let’s just import what we have available and make the most of it. It worked for the road network, it can work for addressing.