The Future I 11 Corridor signs aren't official highway shields or designations, just signs promoting the upcoming project. Only designations like US 93 and I 40 should be signed.

What is your reason for re-adding the 'I 11 Future' designation to this corridor? This is not a valid ref key value as the road is not officially designated or signed as such, nor would this be useful for navigation since I 11 does not yet exist here. fut_ref=* serves this purpose.

Which OSM Wiki article did you refer to? Generally the white 'end freeway' signs (which I believe are California exclusive) are the only ones followed as official freeway termini on OSM that I know of, as white road signs indicate a set-in-stone rule while yellow signs (aka advisory signs) provide warnings to drivers about what is coming up ahead.

The county's GIS (Geographical Information System) would be the Clark County OpenWeb. Most counties in the US will have their own equivalent to this (for example, here is Nye County's: https://portico.mygisonline.com/html5/?viewer=nyenv), and as far as I know, it is free to use as a source for mapping on OSM as it is government-provided. 99 times out of 100 these maps will be more reliable than Google Maps or any other copyrighted map as the latter will often add fake street/place names to catch users redistributing the data without a license. Unfortunately, when it comes to street view as a source, the biggest three options we could use as mappers on OSM are the two provided in the iD Editor (Mapillary and Bing Streetside) and viewing it in person. Luckily, street view is only important for more meticulous things, and road names can usually easily be obtained through county GIS maps.

Route 564 ends right at the Beltway and the Beltway starts right at the convergence of the I 11 ramps. The 'freeway ends' sign as a yellow advisory sign implies that the freeway is about to end rather than a marker that the freeway has ended at that precise location.

I have informed you before to please not use Google Maps for mapping in OpenStreetMap. OSM as a free open-source project cannot use this data due to legal restrictions. Please see here: osm.wiki/Google

As for the road's name, the county's GIS shows that the road's official name is E. North Belt Road and that the businesses along it are addressed to the road. It is likely that at the time of the image capture you viewed was before the official name change or before the signs were updated. The on-the-ground rule typically applies but should be taken with a grain of salt in the prospect of road signs as they can be outdated or outright incorrect occasionally.

Hello, I downgraded this section of Route 50 to trunk for reasons whammo suggested. It has tight ramps, a relatively low speed limit, low/narrow medians, sidewalks separated by a curb and grass, and level crossings on the ramps adjacent to the main carriageways. While it is common for some freeways to have one or two of these characteristics, all of them in one road can indicate that it is more of an arterial road that is controlled by ramps (rather than a freeway), which is a good candidate for highway=trunk/primary/etc. and expressway=yes tagging.

Generally, not every development, such as Summerlin West, will be reached by a primary route, especially if it is primarily residential zoning and is located in a corner of the valley, thus introducing geographical circumstances for why a major intra-city arterial road does not pass through, meaning these roads will see mostly local traffic rather than though traffic on a road like Cheyenne or Charleston.

These prefixes should not be assumed and should be added only if they're signed or officially documented in some other way like in the county GIS. Directional prefixes are not arbitrary and are part of the addresses of properties located along the road. Allison is correct that it is West Galleria up to Russell Road—CC OpenWeb shows the road is named as such and shows that buildings like the middle school, rec center, and LDS church are addressed to West Galleria despite the road physically being north-south west of Whitney Ranch Drive.

Hello, where did you source these directional prefixes from, particularly 'Southwest Galleria Drive'?

Hello, Lake Mead Boulevard west of Rampart most likely does not meet the criteria for primary. It sees considerably lower traffic than roads like Rampart and Cheyenne (less than 10k vs. over 20k on the other two roads) as well as less commercial development and poorer access to other neighborhoods outside of the Summerlin development, especially west of the Beltway where there is very little current development or major roadways to connect to.

Generally roads like these will have disproportionately higher traffic just as long as there is something like a major supermarket or truck stop along it (especially adjacent to highways in rural areas), though functionally the roads remain the same, particularly since this is just one property driving up the traffic vs. a large transportation facility such as an airport or seaport.

An example of this I've noticed is the road leading up to the Buc-ee's in Florence, SC. Based on AADT alone, it could probably be a tertiary or secondary road, but it is functionally a dead-end street that has a bustling travel center located along it.

I think something like a Walmart could be a great case for bumping a road up from residential/unclassified to tertiary, granted it's not just a short little stub or dead-end road of some sort, but primary usually indicates the road is a more trans-regional highway like 14A or a major arterial like the business loop.

Hello, please use more descriptive changeset comments by briefly explaining what edits you've made so that it is clearer to other users what you have added or modified. Many thanks!

I don't believe primary is the best classification for roadways leading to a supermarket. The roads themselves aren't significant on their own merits, as they link no major population centers, transportation hubs, or other highways as the tag is intended to represent. A rural Walmart itself can be regionally significant, but only in its own niche as a private business that just so happens to be located along that road, and not like a typical primary road destination such as a town or an airport is.

Airport Bypass is not the official name of this road, but rather just a description of its role through the airport. Its official name is Paradise Road after it passes through the interchange, according to signs posted on the side of the overpass visible from Flight Path Ave and the sign at the intersection with Russell Road.

Technically, these road segments are not ramps but are rather part of the mainline Desert Inn Road before it splits off into the Wilbur Clark D.I. Road/Desert Inn Expressway. They have sidewalks, driveway access, and are signed as Desert Inn Road, serving more as frontage roads rather than solely as ramps/slip lanes.

Hello, do you you have a source for MDT's classification of the Kalispell Bypass as a motorway?

Technically, this should be trunk, as it lacks any sort of median in the center for the majority of its route—it's just been incorrectly mapped as divided.

I realized I confused the highway=busway tag with the deprecated service=busway tag and concluded that being the reason for the lack of rendering/routing in OSMCarto, and also further connected the dots with some other busways I've seen being tagged with the highway=service + bus=designated scheme, so I switched them to the one I'm more used to seeing and under the belief that it was the replacement for the deprecated tag. Turns out the other tagging scheme for busways is plain incorrect too, so I've restored the traditional busway tags here.

Technically it wouldn't since it only connects to another primary (or greater classification) road at one end and a secondary at the other, making it an inaccessible stub in the realm of road classification. If Main Street/Fairview were primary too, this little segment of Chinden should be primary since it'd connect the two routes.

Please do not use Google content as a source. osm.wiki/Google