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.

And I added some stop signs.

This changeset addresses notes 4016496, 4016494, 4016499, and 4016495.

Also slightly extended Portage Open Bay since it didn't quite go under the bridge.

I also did generic cleanup stuff like move name_1 to alt_name, and I fixed a ref tag that missed a concurrency.

These tags are frequently incorrect about MO state route alignments.

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