Try TIGER new roads based on TIGER 2018 layer data

[mvexel]

The TIGER 2018 overlay for JOSM / iD identifies potentially missing roads in red.

It would be neat if we can try a MapRoulette challenge based on these missing roads.

@iandees maintains the code that produces this layer, perhaps he can advise.

[iandees]

🤔 I've thought a bit about how to do this systematically, but it's tough! As you can see on the TIGER 2018 map of CONUS there is a lot of red (roads where OSM and TIGER don't match).

Some thoughts:

• I didn't filter out any TIGER data and compared it with all OSM tiles that had a highway tag of any kind. Maybe we could only compare some of the TIGER roads with some of the OSM highway tags?
• I don't do anything to keep track of when TIGER is wrong and OSM has been corrected.

We could cluster the unmatched roads into bins the size of a block or three and build MapRoulette tasks on areas that have an abnormally high length of unmatched road?

[bikeoid]

When there's new construction, I try to leave a clue to following mappers by placing a trace of highway:demolished=yes over the old highway on the imagery. But for example, we are updating a local county using official county data. Every road will be inspected and synchronized to county data and tiger:reviewed is removed. Many roads are being moved / removed compared with original TIGER. It would be great if there was a way to keep those old roads from 're-sprouting'. https://tasks.openstreetmap.us/project/76