This also fixes the concurrency between Route A and Route B which ignored A entirely.

Regarding the concurrency, it does not span the two counties. It is entirely within Harrison County, but Route M is a long east-west route that spans the two.

Also fixed a TIGER error on nearby YY.

I verified all north/south roles in the relation.

This looks like an editing mistake where someone forgot to deselect a node when merging? Hard to say

The one number I corrected was on way #18627830. It had "name_2" tag claiming it was a continuation of PCR 616. I verified on Bing StreetSide (which remarkably has coverage here) that it's actually PCR 622.

Notice: The accuracy of these expanded names is 100% dependent on the accuracy of the original Pcr-initialism names. I did not reference any sources beyond imagery (to correct one incorrect road, which I'll mention next) to verify numbering.

I chose to use the "PCR X" form as the ref value for the ways. I think CR is more common nationwide, but PCR is more locally-appropriate. This is easy enough to change in the future. Similarly, I believe this is only an incremental improvement.

I should note that I couldn't determine whether PCR expands to "Perry County Road" or "Perry County Route", but picking one was a better thing than leaving abbreviations in the database.

Most of these roads had names of the format "Pcr X" where X is an integer. The "cr" letters were lowercase. These were carried over from the TIGER import.

This only affected U.S. Route 61 in Missouri.

Please let me know if this changed something wrongly. I am very confident it was only an improvement, as there were many gaps and a mix of forward/backward and north/south roles (I changed everything over to the latter).

This northbound piece of North Truman Boulevard was only in US 67 relation, but the opposing way was correctly in both US 67 and US 61 relations.

No sources cited because this is just in OSM.

Make that "six", and include O and M.

I also added is_in:county tags to relations for all four mentioned supplemental route relations.

Bounding box is large because I added layer=4 and layer=5 tags on two power lines crossing roads I touched.

Specifically added missing water bodies, smoothed some roads, added a tower crane, and added missing power towers (some of which were incorrectly tagged as poles and the rest untagged altogether).

Source: Bing Aerial Imagery; Esri Clarity; Bing StreetSide; MoDOT travelway definitions (via MSDIS Open Data Portal)

I also added some stop signs, and I smoothed some roads.

Bounding box is large because I unglued some power lines which have been glued since TIGER.