AIUI name tags on ways for Missouri state routes are only warranted for natural language names, not systematic ones better suited for ref tags and route relations.

Hi. This reclassification left out a small piece of MO 163 (way/536809831).

I just went ahead and modeled the buildings and driveway in the area so that it doesn't get moved back onto U.S. 50.

See note/4293101

This also fixed a stretch of WW near Coffman being tagged mistakenly as W.

Concurrency fixed in #152706294.

MoDOT's official travelway definitions are wrong, as they claim K ends at N rather than running concurrently with it to the west some distance.

You can clearly see the route marker for K here in Streetside: https://www.bing.com/maps?cp=37.214245%7E-89.541025&lvl=21.6&pi=-3.8&style=x&dir=130.5

I am aware of the concurrency issue in Scott City between K and N, and I'm researching the correct alignments now.

To be more specific, K was ref'd to the southern border of Clever, but both Streetside-captured signage and official open data from MoDOT indicate K snakes through the town to hit MO 14.

Either way, I removed oneway=no since that's the default, and there's no reasonable expectation of it to be oneway to justify being explicit afaict. I won't die on that hill, though, so feel free to add it back if you wish.

Also following recent OSMUS consensus of removing names like "State Route C" when they duplicate the ref tag and take shapeshifting forms "State Highway...", "State Route...", etc.

Streetside is available on 52. I wonder if maybe a stitching error lead to C being read as CC by the last editor 3 years ago?

Proof at https://www.bing.com/maps?cp=38.366703%7E-90.629484&lvl=22.0&pi=4.8&style=x&dir=60.5

For High Hill, I made sure Route F connected as specified by the relevant MoDOT travelways because Booneslick Road is not state-maintained. I have seen errors in the travelway defs for interstate interchange connection before, e.g. another Route F over in Wright City where the travelway says it goes to I-70 but the signs clearly state where maintenance ends. MoDOT would generally want a fully state-maintained connection to the interstate, though, unless posted otherwise, so I followed the travelways here in connecting F through.

This also corrected an instance where Elm Street was called "Elms Street". This was from TIGER originally.

I left the classification alone at tertiary. Feel free to downgrade if you feel it's needed.

Looking back at TIGER suggests that maybe development in this area was associated with dropping Route P? I didn't dig too much into the details because I'm completely certain it doesn't exist now.

This changeset also upgraded way #1286318982 from tertiary_link to tertiary. Yes, it's technically a connector road, but it's functionally an extension of KK in my opinion. There's not even a stop sign for traffic on KK or this connector.

Imagery is not updated yet. The parking lot is gone. Please don't re-add it.

Looks like it was set to asphalt without checking the entire stretch for pavement. Part of it is indeed asphalt (part closer to US 183)

Thanks for catching this even after I closed the note. I only checked the intersection to the east before closing it. Missed the other half of N just to the west

Even if "registered" didn't mean incorporated, it still doesn't meet verifiability requirements IMO