You can be more than one kind of geek at the same time, I guess. First and foremost, I am a map geek. This started when I got my first atlas for my 6th birthday. Then came computers, with the arrival of the Commodore 64 I shared with my brothers. Shortly after that came trains. I still have a few thousand slides of stations, trains and railyards in my basement. Also, German and Dutch timetables dating back to 1985.
One of my later railway photos. Berlin Lehrter Stadtbahnhof, summer 1996. This was demolished not too long after to make room for Berlin HBf. Source: Flickr
Roads are a more recent object of geekery for me. Before I moved to the United States, I didn’t drive much. As I started driving (and mapping) more in my new home country, I also started to become more interested in the rich history of the vast road network in the United States. And I am not the only one! It doesn’t take much online searching to find sites like AARoads and CrossCountryRoads containing 1000s of freeway driving images and videos, as well as Facebook groups dedicated to the celebration of U.S. freeways present and past. (I especially enjoy Freeway Jim for its mix of history and current content. And for Utahns, this Flickr account is pretty cool too.)
I thought it might be interesting to start tapping into this road geek community to help us improve OSM. Even in a well mapped state like Utah cough, most freeway exits still don’t have any signpost information except for a
ref. To give you an idea: of 1654 total
motorway_link ways, only 193 have a
destination tag. Even accepting that probably half of these ways are onramps, that’s still a big data gap! And one that sites like AAroads and CrossCountryRoads fill perfectly, with images like this one:
(If you’re interested, here is the Overpass query for the
motorway_link ways with
After some email exchanges between various US community members and the maintainers of AARoads and CrossCountryRoads, we now have permission to use the images and videos on these sites for mapping. Yay! (I created a wiki page for CrossCountryRoads.com. There is none for AAroads yet, as far as I know.)
I thought I’d try it out myself and share my experiences.
First I pick a region I want to improve. CrossCountryRoads.com has a list of all the Interstates it has coverage for, sorted by state. No Utah, unfortunately :( Let’s pick I-68 Westbound in West Virginia. I see a neatly organized list of images, mostly covering exits. Excellent!
Next, I load all
motorway_link ways as well as all
motorway_junction nodes for West Virginia into JOSM. (Perhaps overkill, but I am not an Overpass expert..).
The result looks a little bit like one of those flight tracking web sites :)
The first exit is to the WV Welcome center and a rest area.
I zoom / pan to where I-68 enters West Virginia from Maryland and quickly find the exit, and add the
I also check the
motorway_junction node for any irregularities (such as deprecated
exit_to tags and missing / wrong
I will delete this
exit_to tag. Does anyone know if
noref is a thing?
With the edits done, I upload the changeset. Be sure to attribute the source - in this case CrossCountryRoads:
Then I move on to the next exit and map some more!