OpenStreetMap logo OpenStreetMap

Changeset When Comment
153051575 over 1 year ago

There was a bridge wrongly mapped on a gravel road, and two bridges were missed on a parallel railway line. I also mapped in the drainage ditches to be more explicit to prevent this from happening again.

153045227 over 1 year ago

On second thought, this is Crystal City. Working on an update

153045311 over 1 year ago

Looks like this originated from TIGER

153012783 over 1 year ago

^ because it was named "MO 291" to be clear; it runs parallel to the real 291.

153012783 over 1 year ago

Also, I pulled the name from way/66098137 and left it unnamed. It's an outer road, likely state-maintained, but I did not research the appropriate name/desg.

153012783 over 1 year ago

AIUI name tags on ways for Missouri state routes are only warranted for natural language names, not systematic ones better suited for ref tags and route relations.

148783969 over 1 year ago

Hi. This reclassification left out a small piece of MO 163 (way/536809831).

152827383 over 1 year ago

I just went ahead and modeled the buildings and driveway in the area so that it doesn't get moved back onto U.S. 50.

152802862 over 1 year ago

See note/4293101

152707595 over 1 year ago

This also fixed a stretch of WW near Coffman being tagged mistakenly as W.

152705387 over 1 year ago

Concurrency fixed in #152706294.

MoDOT's official travelway definitions are wrong, as they claim K ends at N rather than running concurrently with it to the west some distance.

You can clearly see the route marker for K here in Streetside: https://www.bing.com/maps?cp=37.214245%7E-89.541025&lvl=21.6&pi=-3.8&style=x&dir=130.5

152705387 over 1 year ago

I am aware of the concurrency issue in Scott City between K and N, and I'm researching the correct alignments now.

152703001 over 1 year ago

To be more specific, K was ref'd to the southern border of Clever, but both Streetside-captured signage and official open data from MoDOT indicate K snakes through the town to hit MO 14.

152697154 over 1 year ago

Either way, I removed oneway=no since that's the default, and there's no reasonable expectation of it to be oneway to justify being explicit afaict. I won't die on that hill, though, so feel free to add it back if you wish.

Also following recent OSMUS consensus of removing names like "State Route C" when they duplicate the ref tag and take shapeshifting forms "State Highway...", "State Route...", etc.

152697154 over 1 year ago

Streetside is available on 52. I wonder if maybe a stitching error lead to C being read as CC by the last editor 3 years ago?

152654922 over 1 year ago

Proof at https://www.bing.com/maps?cp=38.366703%7E-90.629484&lvl=22.0&pi=4.8&style=x&dir=60.5

152614326 over 1 year ago

For High Hill, I made sure Route F connected as specified by the relevant MoDOT travelways because Booneslick Road is not state-maintained. I have seen errors in the travelway defs for interstate interchange connection before, e.g. another Route F over in Wright City where the travelway says it goes to I-70 but the signs clearly state where maintenance ends. MoDOT would generally want a fully state-maintained connection to the interstate, though, unless posted otherwise, so I followed the travelways here in connecting F through.

152566709 over 1 year ago

This also corrected an instance where Elm Street was called "Elms Street". This was from TIGER originally.

152519926 over 1 year ago

I left the classification alone at tertiary. Feel free to downgrade if you feel it's needed.

152519926 over 1 year ago

Looking back at TIGER suggests that maybe development in this area was associated with dropping Route P? I didn't dig too much into the details because I'm completely certain it doesn't exist now.