OpenStreetMap logo OpenStreetMap

Changeset When Comment
145095890 about 2 years ago

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.

144986198 about 2 years ago

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.

144981758 about 2 years ago

Large bbox due to sparse changeset

144979479 about 2 years ago

And stop/yield signs

144948539 about 2 years ago

Missing source: TIGER called it "Spur EE"

144945555 about 2 years ago

This is essentially a continuation of changeset/144945397.

144945397 about 2 years ago

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

144923202 about 2 years ago

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

144923202 about 2 years ago

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

144923202 about 2 years ago

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

144920895 about 2 years ago

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.

144887758 about 2 years ago

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.

144887758 about 2 years ago

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.

142712571 about 2 years ago

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

142712571 about 2 years ago

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.

144811475 about 2 years ago

And I added some stop signs.

144811475 about 2 years ago

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

144811475 about 2 years ago

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

144810990 about 2 years ago

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

144810990 about 2 years ago

These tags are frequently incorrect about MO state route alignments.