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.

Bounding box is large due to very long power line.

Large bbox due to state route relation.

This was previously ref'd as Z, but open MoDOT data and Bing StreetSide disagreed. I have corrected this.

Presumably, before the J-turn was installed the stretch named "State Hwy O" was part of the route, but now MoDOT specifically excludes it.

See this sign assembly: <https://www.bing.com/maps?cp=37.315993%7E-93.331&lvl=18.7&pi=-0.5&style=x&dir=213>. It says "State Hwy O" is the next left but shows the O shield as the next right.

Kime*

I don't know the specific history of the Routes O/13 intersection, but it looks like the J-turn is a recent addition. I un-abbreviated stuff in the vicinity as well that got mistakenly abbreviated at some point.

I also aligned the western terminus of O along Klime and North Main as signed by MoDOT (https://www.bing.com/maps?cp=37.305434%7E-93.42792&lvl=20.3&pi=-3.6&style=x&dir=94.6).

Also also, there is a small segment of county-maintained road literally named "State Hwy O" without any MoDOT route shields. This is, at present, not technically part of Route O according to MoDOT data and Bing StreetSide signage.

Bounding box is large because I touched the MO13 relation.

wow, double correction: it's route M and U.S. 60