Some names need to be verified.

Route E does not continue to MO 164. That is DD, and I'll get to that later tonight.

This changeset also touched up some ways in the relation for A which was added in my previous changeset.

^ However, MO B is signed on either end of the concurrency, and there is a well-established convention that letters aren't reused that closely together (exceptions exist, but this isn't one of them imho).

There is an unsigned concurrency of MO B on MO 162. MoDOT acknowledges this in their TMS open data set, but signs on the ground just recognize MO 162.

Also YY in Hornersville

Bounding box is large due to power lines.

The relation for B already existed but was incomplete, so I finished it out.

I also tweaked some power line details which expanded the bounding box.

Also "County Road [A-Z][A-Z]?" is not a correct format for supplemental route names at all. These used to be county roads, but they were taken over by MoDOT/MHTC (i.e. they are state maintained nowadays).

Also impacted Mercer County.

Layer added in 138826330.

This changeset corrects placement of ref tag in changeset/138826184.

This changeset was corrected in 138826264.

Bridge ref number comes from MoDOT

Addresses note/3791543

Also Source: Bing for redrawing the footprints

Also excluded are Route 64A and Route 64B which are considered related routes of Route 64. I treated them like special routes.

I used Notepad++ macros to convert the resulting CSV into JavaScript function calls which I pasted into the Scripting console in JOSM.

I then, of course, manually verified. But I wanted the extra layer.