When I lived in this area here and to my current understanding this is a heavy traffic route, especially compared to 156 and 158. Not only does it connect the Mt. Charleston village, it serves nearly all traffic heading from Las Vegas to the MCWA and all its ski resorts and summer homes. It's no US 95 but it's an important route. It serves the same exact purpose and gets the same level of traffic that 159 does however this does not loop around back into the city.

No problem, happy mapping!

My bad, I was unaware of the discussion/consensus, and usually these types of roads are tagged as motorway in my region and in other parts of the US I edit in. I've reverted my changeset.

Hello, dufekin. I took a look at you edits, and I want to ask to please not tag primary Virginia state routes to secondary. The secondary tag is for secondary state routes and unsigned major roads. If you believe a road that is tagged as trunk is not an expressway, consider tagging it to primary instead, because it is still a major route, or more preferred, discuss it on Slack.

That doesn't look like the case though since just above this location is TX 152 tagged as primary, and exploring the rest of Texas many of the other main state highways are primary and Farm-to-Market roads (which are usually secondary or minor roads) are secondary.

If it is a secondary route, shouldn't it use secondary tags then, or at least from where it was tagged as trunk to the next highway ramp?

Trunk roads aren't exclusively just for expressways. Their US definition is for such, but they can be used on 4-lane, undivided roads (at least in just small sections like in this case) since traffic that is using the trunk road is forced to take these roads to continue along it. If these primary roads were standalone or much longer than what they are actually, it would be most logical to have them be primary roads, but since they are short segments that make up the expressway route, it makes most sense to tag them as expressway/trunk.

Hello, this small portion of VA 7 does not meet requirements for motorway tags, as it is accessed directly by roads without grade separation so I retagged it to trunk, and "road class" does not provide enough details for why my edit here was reverted.

Lee Highway has full freeway-to-freeway access from I-66 and sufficient interchanges while a portion PWP is planned to become a motorway when the Clover Hill and Dumfries Road interchanges are constructed.

The examples that you provided are of motorway intersecting instances, nothing containing two other road classes converging or splitting. I believe a motorway spurring off or merging into another is perfectly fine when it is, for example, four lanes splitting into a pair of two-lane carriageways, although it technically doesn't abide with wiki's explanation on how to correctly tag these instances, and the wiki is the general global acceptance.

Now if it's two trunk carriageways connecting two the motorway, one connecting to the eastbound and another with a flyover connecting to the westbound lane, that would technically imply there is some sort of at-grade intersection formed when those two ways meet (since the motorway and trunk road are two different classifications of road), therefore breaking the motorway's purpose of being only accessed via ramps/links. It makes more sense just to tag these ramps as links since they are most definitely links and not expressway carriageways.

Almost every single other one ramp + one flyover interchange configuration in the US is mapped with the two ramps tagged as links for the major road (motorway in this case) the other road (trunk road in this case) is spurring off of from Y-junction to the point where the two ramps converge to form a central median.

I only did this because this is how I've seen it been done before, and it's how I've been doing it since I've started mapping.

Trunk roads should never directly intersect with motorways because any road shouldn't directly intersect with motorways (unless it's a service road) without motorway links. It technically breaks the definition of a motorway which should only be accessed by links and not directly by other major roads. It's seen with really every other interchange in the state of Utah, the US, and the world. Here are some references: osm.wiki/File:OpenStreetMap_Highway_links_table_between_different_highway_types..png highway=motorway

I upgraded this portion of highway to trunk because (like I stated in my changeset comment) that it's a continuation of the Reno Highway/US 50 ALT, with 40-60 mph speed limit and sufficient lanes. What further differentiates this portion of highway from Williams Street, a regular primary road, is that even though there are still driveways on both carriageways accessible via the center turn lane, there are far less of them than on Williams Street. Reno Highway also lacks the sidewalks and crosswalks which Williams Street has.

One other reason for this edit was that trunk roads, as seen in almost everywhere else in the US, don't usually become primary roads until reaching the city or other motorway or trunk road it leads to, unless it the expressway-like portion is heavily interrupted and becomes something like a 35 mph 2 lane road.

Also, btwhite92, as you mentioned, had contacted me referring to me upgrading other similarly-structured parts of US 50 (center turn lane/lack of median, driveway access) to trunk, saying: "I am willing to leave the changes you recently made on US 50 (primary->trunk) since 'trunk' classification in particular is unsettled and recently came up again on talk-us without consensus. Nevada's multi-lane highways with occasional divided carriageways and sporadic access control are a pretty grey zone."

And I can explain the other edits; I separated the road because most of the route was separated by an unusable rough asphalt median rather than a turn lane, and this median was also going to become a wall as the segment from I-15 to Southern Parkway was going to be upgraded to a freeway with interchanges, overpasses/underpasses, and frontage roads as part of a Zion-bound traffic improvement project, which is currently in environmental study: https://www.thespectrum.com/story/news/2020/02/25/utah-road-sr-9-needs-improvements-udot-zion-national-park/4858022002/

I'm pretty sure I added correct speed limit and lane info, as I traveled along street view reading all of the speed limit signs along the route, which is what I do for every road-editing project I make, but if I didn't, these are all just minor errors that I would have corrected in a revision with remapping the Coral Canyon interchange.

As for Southern Parkway, I could find no sources stating that the road was complete or that a junction existed right there, all I could find were articles about how the Sand Hollow interchange was complete, nothing about a junction with West 3000 South or State Street.

Hey, apparently I somehow forgot to re-map the exits at Coral Canyon Boulevard. It appears I saved my changes before finishing completely since I went straight to work on the I-15 interchange instead of working on the Coral Canyon one then moving onto a whole other area. This was just a mistake by me and I meant good intentions when editing here and if the edits were un-reverted I could finish where I left off. I also had trouble saving some additional edits (such as mapping the proposed interchanges and frontage roads) because you reverted my edits. Apologies for any interferences and I'd like to fix this if I can since I spent hours mapping it.

Roads can be tagged as trunk regardless of whether it has a median as long as it is a major route (or primary road) with 4 lanes or sufficient separation from other roads as well as a 40+ mph speed limit, this is stated on the wiki and is used in most other US states. Roads are also usually mapped as one tag until it reaches the next major town or intersection rather than at the end of the median or speed limit change.

Sorry for the incomplete changeset comment, didn't know there was a limit.

I'm confused as to why the tagging of this road as a trunk road would be incorrect. It's a wide, high-speed, and somewhat-divided highway. It has a lot in common with other trunk roads in Nevada feature and driving experience-wise and meets all requirements listed on the article for this tag on the OSM Wiki.

I upgraded Boulder Highway and Boulder City Parkway to trunk roads because they are major and widened highways with a speed limit above 40 mph, similar to with how Saint Rose Parkway and Lake Mead Parkway were mapped.

I upgraded NV 169 to a primary because it is the main thoroughfare through Moapa Valley and the general area and acts as the main road through the Lake Mead National Recreation Area and is a link to a couple small settlements within the area.

I upgraded NV 147 because it is a continuation of Lake Mead Boulevard, a major thoroughfare in the Las Vegas Metro, and connects the valley to NV 169. Similarly, I also did the same for NV 564 because it is a continuation of a trunk road (Lake Mead Parkway) and connects NV 169 to Henderson and Boulder City.

Finally, I upgraded Nevada Way since it is the main street through (and the only major road to connect to) Downtown Boulder City.

I do believe it would be considered a motorway since it has a sufficient amount of interchanges, with Rancho Drive and Highland Drive, along with an eastbound entrance from Wynn Boulevard. Not to mention it has multiple basic grade separations over the Cima Subdivison and Sammy Davis Drive and then a tunnel under Las Vegas Boulevard.