OpenStreetMap logo OpenStreetMap

Changeset When Comment
57923383 over 7 years ago

Please avoid attaching areas to road centerlines

57990274 over 7 years ago

This changeset has been reverted fully or in part by changeset/57990388 where the changeset comment is: Reverting my own terribly vetted changeset.

57843955 over 7 years ago

This changeset had them as nodes rather than outlines.

57878090 over 7 years ago

addr:full or addr:postal might work better than name for the rural route box number.
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/57878090

57872601 over 7 years ago

US 54 is already the ref, and there is a proper name on this already.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.mapbox.com/changesets/57872601

57861827 over 7 years ago

Where the state and the local jurisdictions have two names for the same road, please move the state name to the reg_name=* key.
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/57861827

57843955 over 7 years ago

This is a rather peculiar way to map houses

57843682 over 7 years ago

The county road number can be moved to the ref tag when adding the name.
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/57843682

57843578 over 7 years ago

maxspeed:type=* is a little unusual in the US at this point, source:maxspeed=* has generally won out.
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.mapbox.com/changesets/57843578

57819641 over 7 years ago

Your neighborhood spans two continents?
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/57819641

57817107 over 7 years ago

Be sure to knock out source:maxspeed if you're changing to a more specific limit.
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/57817107

57785660 over 7 years ago

Is this actually a park, or some kind of commons?
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/57785660

57782595 over 7 years ago

Might doublecheck those speed limits.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.mapbox.com/changesets/57782595

57754161 over 7 years ago

I 35 probably should be a trunk north of the MN 194 interchange and south of Loop 20 as well. The segment between those two interchanges would be a motorway. MO 13 has no such major interchanges. It's pretty much the same character as long stretches of US 75 in Oklahoma.

57754161 over 7 years ago

Sorry, intersections even at the end (and going to single carriageway also counts) still counts as an intersection and disqualifies it as a motorway. It wasn't vandalism to change it to trunk, and the government classification doesn't count.

57754161 over 7 years ago

It has an at grade intersection, though. Walmart Avenue.

Looking through the wiki, it appears that some pages have been gamed a bit away from where things have largely settled in regards to how trunk is typically used in the United States, and various pages aren't in agreement on this anymore. In practice, anything that hits Interstate standards or close to it, and doesn't go to single carriageway at either end, would be a motorway. Less than that but otherwise, would be a trunk.

I honestly can't tell anything about MO13 that's different than MO 10 except they slapped down a dozen or so kilometers of a second carriageway with plans to expand later as funding becomes more available.

57754161 over 7 years ago

What AASHTO or MODOT consider it is not the determining factor for OpenStreetMap when it comes to the highway=* tag. Right now, I don't believe this is a clear enough case of motorway to justify the tag. Eliminate the intersection, slap on a continuously flowing interchange at MO 10 and don't drop to single carriageway at the south end, and yeah, that's a motorway. It's got the future potential to be motorway, but for now it really looks like more of a trunk.

37678382 over 7 years ago

Or, for that matter, Portland International Airport's Airport Way.

37678382 over 7 years ago

With this ending on a surface route, I'd be more inclined to call this segment a "trunk", as it's really just a built up limited access part of Airport Road and less a proper freeway in it's own sense. Particularly with the lack of runout room before 59th Street. Kind of a similar situation as with the Gilcrease Expressway or LL Tisdale Parkway in Tulsa or the Milwaukie Expressway in Oregon.

57754161 over 7 years ago

Generally speaking, changeset comments are the best way to contact someone regarding a specific change, plus keeps the whole thing out in the light for others to pick up on.

My concerns with this is that OpenStreetMap isn't the AASHTO, and with this transitioning cleanly into surface roadways on either ends, this acts more like a grade separated portion of Spartan Drive south of MO 10 (and especially with it discontinuing quickly after US 24), or a first phase of upgrading the route to a freeway later. Once they upgrade the MO 13/10 interchange and extend the MO 13 interchange, yeah, motorway it then. You say it has no intersections, yet right there, you have one at Walmart Avenue.

Trunk fills that nice grey area that things like MO 10 itself, the section of MO 13 that is the subject of this changeset, and other "freeway like, but not quite all the way there" objects.