Also, I made a typo in the comment: SSRs should just be SRs. This covers more than just supplemental routes.

There was also an instance where the name tag on an SSR used a semicolon delimiter...so I removed that.

Continued in changeset #155350752

Also, I saw one instance of justification for some of these redundant way-names as making the road match with addr:street on nearby buildings. This is tricky, as it runs into the same issue I outlined two comments up: our road network is highly decentralized in the US, and many entities cooperate with loose terminology. When a county applies physical addresses to land parcels, it may do so with the form "Hwy 67" instead of "Lindbergh Boulevard", but that IMHO does not justify renaming the road to a variant of the former.

^ Even that has exceptions, though, such as "Business 13" in Branson West.

This is done in an effort to help normalize nomenclature across the Missouri state highway system. As it currently stands, ways can use any number of name strings from "Route X" to "State Road X" to "Highway X" to the most common, and most TIGERish, "State Highway X".

It's important to recognize that, when a MoDOT sign indicates a road is named "Route X" or "Hwy X", that's not the canonical name string. That's a systematic designation of the road segment as belonging to the X route in the broader state route system.

Additionally, I removed a few "is_in" tags containing strings of the format "{countyname}, MO" and some ZIP codes (?) in both postal_code and addr:postcode tags

Each route connects to both directions of US 65, so there is a slight overlap in the middle.

I also added lane counts, turn restrictions, and service roads; and I smoothed some ways out.

I also smoothed out ways, adjusted lane counts, and added some smaller roads like driveways and service roads.

I also added stop signs, a yield sign, and smoothed out the ways.

There was a road segment previously mapped as a secondary_link road which is actually a proper designated route segment (MO 49). If you're just looking at designations, then the intersection looks like a Y. The road segment that closes the triangle is actually an undesignated connector segment inline with MO 49 to the south and MO 21/72 to the north.

MO 5, MO 87, and MO 240 are all concurrent for a stretch south of Glasgow. That concurrency runs westward, and MO 240 continues over the Glasgow Bridge into the next county. MO 5 makes a northward turn into Glasgow at an intersection near a rail crossing, and MO 87 terminates at that intersection. MO 240 Business starts at that intersection and runs concurrently with MO 5 beneath the railroad into Glasgow. The bit underneath the railroad is what I modified here.

To clarify, F and ZZ are partially concurrent at their shared I-44 interchange.

This only impacts the westbound travelway of I-72 which previously terminated at the exit ramp. Signage on the ground and open govt. data both suggested otherwise. I added a few more ways to the relation and updated the ref tag on those ways to carry I-72 a little further west on the westbound lanes.

Note #4376852

Hi, thanks for working on the roads in this area.

OpenStreetMap has a convention, though, to un-abbreviate names of things. Here's the wiki page about this: osm.wiki/Abbreviations

Street suffixes like "Dr" and "St" should become "Drive" and "Street", respectively. "Hwy" should become "Highway", and directional affixes like "SW" should become "Southwest", too, around here.

This applies to other things, too: even the name of St. Louis becomes "Saint Louis" in OSM.

A common exception to this is when things are named after people, as people's names are generally kept as-is (e.g. "Dr. Edward A. Babler Memorial State Park"). Other exceptions exist, too. Always look around the local area to see how similar things are already mapped before making changes so that OSM stays consistent.

Again, thanks for this changeset, as it did fix multiple road names that were wrong.

The original area was conflated with the colon-delimited name "Cuivre River State Park: Northwoods Wild Area". This changeset removes the nature reserve tagging from the way in favor of a proper boundary relation for the wild area.

The state park boundary relation should also incorporate this closed way, but these boundaries should be verified first.

This improves semantics without affecting rendering at all

This improves semantics without affecting Carto rendering at all