This mainly had to do with name concurrencies among supplemental state routes east of Kansas City, Missouri, but there were some buildings in here too that were given the same treatment.

*County)"

I feel like "Missouri Route AX (Macon County" is better placed in the description tag than the name tag. Both are meant for end-user consumption, as opposed to note for other mappers, but people don't expect the name to contain the parent county or city.

I also opted for one relation per route rather than my previous experiment of one per direction, as that's not necessary for these simple routes.

I also bumped CR 249 to tertiary because its functional class shouldn't change just because state maintenance ends and the surface changes to unpaved.

A segment of CR 322 had a tiger:name_base tag claiming to be part of J which was clearly false. I also added surface tags.

Bbox is large because I touched multiple route relations (each very tiny) throughout the state in addition. Specifically, I removed the "is_in:state=MO" tag from them which I added about six months ago and which I now realize is redundant and fragile.

Large bbox due to sparse changeset

And stop/yield signs

Missing source: TIGER called it "Spur EE"

This is essentially a continuation of changeset/144945397.

Bbox is large b/c added layer=5 to power line

I shortened FF on its eastern terminus because it does not reach MO 15/22. State maintenance ends at South Elmwood Drive. You can see this on Bing StreetSide here: https://www.bing.com/maps?cp=39.170717%7E-91.906309&lvl=22.0&pi=-2.8&style=x&dir=275.3

Affected routes are D (new relation), E (no relation), FF (existing relation), and M (new relation).

This one had a large bounding box due to power lines and waterways.

AE did not go south through Lake Mykee Town. That was a TIGER error. Instead, it jogs east to US 54 where it hits TT.

I should also note that the turn-by-turn directions take a day or so to update, so they'll keep saying to use the center crossing until tomorrow.

The "slippy map" on openstreetmap.org? It's probably your browser cache. Try a hard refresh (CTRL+F5 for most browsers on Windows).

Alternatively, click the Layers button on the right (the stack of paper icon) and tick "Map Data" which updates faster.

I am going to finish the job here with replacing W with N and NN.

Hi there, my name's Tyler. I have been working on Missouri's state routes recently and stumbled across this issue today.

First off, thank you for finding this problem. You are absolutely correct in that W does not exist here. Instead, N runs from 32 down to 21, and NN spurs off eastwardly to 21's cousin, 221.

Unfortunately, though, your edit tagged this entire segment as a bridge. A very long bridge, indeed :)

We also have a pretty strict convention throughout OSM to expand abbreviations. So "Hwy NN" should really be "Highway NN". Actually it should be "State Highway NN" in my opinion, but that's another topic. Exceptions are when the abbreviation is part of a last name, brand name, etc. I know it looks weird on the officially-rendered map, but we don't tag for the renderer.

We also have a convention to prefix the ref tag with "MO". So ref=NN should really be ref="MO NN".

P.S. The lettered routes around here are state-maintained. If you see "County Highway X" somewhere, it's a misnomer. Most of them used to be county roads until the 50s when MoDOT took them over to expand the state network.