OpenStreetMap logo OpenStreetMap

Changeset When Comment
89998359

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

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

81600509

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

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

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

Sure, what's the changeset number?

89887974

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

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

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

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

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!

89887974

Generally speaking where I downgraded it, I did so because it doesn't qualify as a motorway, because of intervening or terminating at-grade intersections, or it was an iffy call and it's better to go with the lower value to avoid level creep on edge cases.

Could you be more specific?

76162979

Sorry, US 54.

76162979

Feeling like US 50 is a little overrated as a trunk; that value tends to be used as an indication that something's almost but not quite a motorway, not a two lane federal highway. Compare US 69 in Oklahoma.

76176002

Feeling like US 50 is a little overrated as a trunk; that value tends to be used as an indication that something's almost but not quite a motorway, not a two lane federal highway. Compare US 69 in Oklahoma.

59418875

This should probably get punted to talk-us, not the wiki.

59418875

So that'd be ref=NF 1828-118, and noname=yes, with no name.

The US tagging page is not correct or consistent in this case.

59418875

Yeah, that's wrong. This is more applicable to the situation.

osm.wiki/Names#Name_is_the_name_only

59418875

Well, that would be ref=NF 44, not name=Forest Road 44. Refs are not names.

I can also confirm that Camp Baldwin, which is within the national forest on 44, from survey, is 76201 Dufur Valley Road.

59418875

name=Dufur Valley Road is correct. The ref=* value should not be in name or alt_name at all.