Some of these segment had directional prefixes, too, but that's not something MoDOT does afaik.

Sorry, that should read "primary_link" rather than "tertiary_link".

(I would actually be in favor of using tertiary for numbered county roads, too, but that's another topic.)

The highway=unclassified tag is used for roads/routes that are too minor for systematic designation, and they are usually (not required to be) maintained by local government.

SSRs, on the other hand, are designated, signed with letters, and maintained by the state DOT.

No other objects or tags were touched in order to make this a clean revert if needed.

No other objects or tags were touched.

Edit: No it's not.

See changeset/145394324.

In this location, a single-letter (or even a double-letter) supplemental route would not be used for the purpose. If anything, an unsigned spur of 179 would be used.

On June 15, 2023, I added ref and relation for a supposed MO P in Wooldridge apparently based on Bing StreetSide. I can't verify that now, and I do not remember why I added it.

Also, being a designated county road might make it unclassified rather than track? Something for the future

to the east, not north*

It runs parallel to HH to the north, so HH does actually need to be adjusted still.

Typo: Route*

I write that a lot when I type fast.

I'm no longer un-naming singly-designated segments of highway, so I change the name of those ways from "MO 30" to "State Highway 30".

Turns out GPS validated Bing imagery, and the bridges were actually just wrong.

I also used GPS data on this one to verify the bridge since it was offset a bit.

This is in St. Clair County, Missouri.

I also added a missing concurrency between Y and 23.

I also reworked an intersection just north of Missouri State Fair, and I added footways in the process.

I also added a missing concurrency between D and Y just south of Whiteman Air Force Base.