OpenStreetMap logo OpenStreetMap

Changeset When Comment
91915070 about 5 years ago

This changeset has been reverted fully or in part by changeset/92115889 where the changeset comment is: Please go to https://opengeofiction.net/ to create fictional geodata.

84206271 about 5 years ago

Hey, are these train relations for a passenger route? If not, these shouldn't be train relations.

88045920 over 5 years ago

When working with alignment, please be mindful of the placement=* tags as this indicates which lane the line runs down or between.

39843086 over 5 years ago

What's this - ??K stuff about? I don't understand what you're intending with that.

87776466 over 5 years ago

Right? Depressing.

90215737 over 5 years ago

In this case I was working on making sure OR 213 had a complete, contiguous relation.

90215737 over 5 years ago

names are not refs and don't qualify for the name tag.

https://help.openstreetmap.org/questions/63501/highway-naming-conventions
osm.wiki/Names#Name_is_the_name_only

89998359 over 5 years ago

I honestly don't think length comes into play here since it terminates with intersections on either end. If there was one more grade separated change, I think we'd be on the same page for this one.

Yeah, Rand McNally switched to using OSM 5-10 years ago instead of doing their own cartography. Probably the best source for printed OpenStreetMap in the US since then.

That said, I'd generally recommend avoiding making mapping decisions in OSM based off commercial maps due to copyright issues.

89998359 over 5 years ago

Doublechecked the name, looks like it got renamed in 2017 by the Kansas legislature. I'm disinclined to remove name=* on this for that reason.

89998359 over 5 years ago

Checking Rand McNally is just a feedback loop, their source is OpenStreetmap.

alt_name isn't compatible with noname=yes.

I don't see the characteristics you describe out of line with highway=trunk *especially* given the arbitrary cut to motorway at the locations you gave...there's not a reason to step up for one exit with intersections on either end.

89998359 over 5 years ago

On this motorway portion, you think a proposed=motorway, highway=trunk would be a good compromise?

81600509 over 5 years ago

Nice little tip, when something is tagged highway=construction, construction=residential, you can just change construction=residential to highway=residential and it will overwrite the highway=construction value and remove the construction=residential value.

89887974 over 5 years ago

You're talking about the ones just west of Wichita in 90043845, right? I saw those, they make coherent sense, I just think motorway isn't the right level for something with intersections, and jumping back and forth for short distances takes away from clarity instead of improving it.

I live down in Tulsa but 50, 54 and 400 are my favorites for getting up to Colorado when I go to/from there ~2 times a year. I make it up to Wichita, Sedan and Independence more regularly.

89887974 over 5 years ago

I think they'll eventually finish it as a freeway but this feels a lot too mixed to not call it an expressway and just tag as trunk still. Once everything's grade-seperated between Garden Plain and Maize Road, I'd be comfortable calling it a motorway to Northeast 40th Street, and something lower than that from that exit west to where it transitions to single carriageway.

Some other similar roads I can think of offhand would be the Milwaukie Expressway and Sunrise Expressway in Oregon, US 75 in Oklahoma north of Tulsa.

89887974 over 5 years ago

Sure, what's the changeset number?

89887974 over 5 years ago

Like, they're aware that it's not there yet, but they're futureproofing themselves a little to buy what they got a couple extra decades.

89887974 over 5 years ago

That'd be about right for KDOT, no? Seems 50, 54 and 400 seem to have been renovated with aspirations of bigger plans later, particularly at major interchanges. Which is a big contributor towards me really wanting to err on the lower side of the edge cases.

89887974 over 5 years ago

Good catch, I believe the bing imagery to be accurate based on my last drive through the Cannonball Stageline. I believe what we're seeing with the bridge may have been previously assumed based on the temporary diversion and gapped earthworks that may have been present shortly after the current configuration opened.

89887974 over 5 years ago

Sure, let's see if we can come to a compromise on this.

My biggest concerns is that going too high tends to give more credit to a road that it effectively operates as. We're in a big, barely connected part of the world after all.

89887974 over 5 years ago

OK, so we are talking about the Cannonball Stageline. Motorways don't have intersections. The section you're referring to has 2 at-grade intersections and 1 interchange at Cunningham. I think we can agree where it goes to single carriageway on the west end is definitely a primary.

Freeways are purely all of dual carriageway, grade separated and limited access and map to motorway cleanly.

Trunk maps to the various flavors of expressway and other quasi-freeway things that are close but not quite a freeway. The presence of the grade separated ramp doesn't automatically make it a freeway; expressways can and do contain grade separated ramps quite commonly. The segment you're referring to ends at a single-carriageway primary on the west and the east, with several at-grade intersections and one grade-separated junction.

While it's clearly obviously that KDOT has plans to make the whole Cannonball Stageline a freeway at some point years or decades down the road, I think it's an equally aspirational stretch to call that a freeway. proposed=motorway does make sense, though!