[OSM-talk] TIGER cleannup

[Andrew MacKinnon]

> 1) Don't ever update.  Let the OSMers do the updates.  Even the new
> census data at Lava Beds National Monument has errors in it (incorrect
> road names, foot trails marked as residential, old non-existent trails
> in data, missing trails, etc.)  In Chico, the new super-accurate data
> doesn't render or record freeway interchanges correctly.

Nice sounding, but unrealistic. The US is a huge country. Undoubtedly
we will miss parts of it, and thus we will want to be able to update
OpenStreetMap using the most recent TIGER data. Thus, we will have to
use #2 or #3 to supplement our manual map-gathering expeditions.

> 2) Update everything that's not marked as "reviewed".  This seems like
> it would have hellish merge implications that I'm not sure are readily
> surmountable.  Plus I forget to mark stuff as reviewed half the time anyway.

What about updating everything that was uploaded by user DaveHansen
according to the history, and not updated since? This would be much
more accurate than using the tiger.reviewed tag. Perhaps the update
tool should also avoid adding TIGER data in areas where non-TIGER data
has been added, to avoid messing those areas up.

> 3) Interactive regional updates... that is, maybe you get a chunk of new
> data, you download the OSM data, you run the as-yet-unwritten Magical
> Munger Program, and load the result back into JOSM.  Then you massage
> the data, verify it, and upload it.