The ref tag correctly marked this as MO H, but there's no reason to keep wrong import data around

...but the name bled over a few more ways than it should've. Maybe TIGER did some imprecise map matching or other processing that messed these up, or maybe their data source just wasn't that great at the time.

A very frequent error I see in the tags I remove is what I call "tiger contamination" where the way inherits a name like "State Highway X" while X actually terminated at a state route or a township or two over.

Most of the ways targeted have been unpaved rural roads and/or right-angle connector roads linking winding state routes to grid-like county roads.

This changeset specifically targeted unclassified highways. I have done similar changesets for tracks and service roads in the recent past.

I am in the process of manually correcting concurrencies on Missouri state routes, so I am running a lot of Overpass Turbo queries to find anomalies. Frequently, however, my queries are being cluttered by long-redundant, and often incorrect, tiger:name_base=* tags and their ilk.

I targeted ways that my Overpass query picked up as "possibly state routes" based on regexing the keys

To clarify, this changeset targets, e.g., private driveways with tiger:name_base="State Highway A" due to imprecision from original TIGER import

Bbox is large because many tiny changes around the state

It's part of broader cleanup I'm doing to prevent future mistakes with naming and ref-ing roads near SSRs because TIGER was incredibly imprecise with them.

The bounding box on this one is large because it makes a bunch of tiny edits throughout the state.

The only state route in Schell City is AA.

C never ran concurrently with M at all, and neither touched Schell City.

NOTE: Bing Aerial is way outdated here!

Also added Duck Creek culvert under AX.

I have since stopped doing this because it's not necessary. Apologies for the spam.

Among that fixed being the concurrency with T in Koeltztown

I modifed the ref tags to indicate the concurrency between A and J.

I am manually combing through an Overpass Turbo query looking for discrepancies between way names and ref tags, and this singular way was identified as Route E for some tigery reason.

There were two concurrencies to keep track of on this long route, E/H and A/E.