Places aren't classified based on their legal statuses but rather their size and regional prominence. Parker has nearly 60k population in 2020 with that figure rapidly increasing, plus a lot of surrounding development outside city limits within Parker's ZIP codes.

Just because a roadway is 'approved'—which in this situation means the right-of-way has been acquired and is an official proposed roadway—does not necessarily mean that it should be mapped. As I stated in my last comment, this road doesn't exist and isn't even currently under-construction. OSM's primary rule is to map what's on the ground, meaning only objects that currently exist in the real world should be mapped, no matter how useful it may be to a select few users to map it before it exist. You mapped this road as an open, completed roadway that OSM data users could be routed down, when in reality, there is no road here, just a field.

Sorry for the late response. Technically, there are no true ramps here, since the carriageways of 93 Business merge directly with I 11 rather than downsize into one-lane slip roads and/or drop the highway designation. It is a fairly common phenomenon for freeways to simply merge directly into each other at Y-junctions (for example, I 15 and 40 in Barstow, CA, or I 15 and I 215 in Salt Lake City, UT) and for these linking roadways to be tagged as motorways rather than motorway links.

Hello, please do not map roads that do not exist or are not built yet. Imagery from October 16 2025 does not show any evidence of a road here.

Hello. When mapping roads, please remember to use the fully-expanded prefixes and suffixes of the street's name rather than one in abbreviated form for consistency with OpenStreetMap's naming format. For example, use 'North' rather than 'N', and 'Lane' and 'Road' instead of 'Ln' and 'Rd'.

Additionally, roads should be tagged based on their real-world usage, consistent with the tags of other nearby roads. In this case, these roads should be tagged as highway=residential rather than highway=primary, which would imply these roads are a major highway rather than a simply residential street.

Thanks!

Hello—what is "Jax's Dead Spot"? This doesn't appear to be an actual town or populated place of any sort. If this is just a made-up location, please note that fictional mapping is considered disruptive and could result in getting you blocked from editing the site. It is important not to treat OpenStreetMap as a space for personal projects but as a collaborative mapping project. Additionally, a lot of the other things you've edited thus far appear to be incorrect—particularly changing nearly every populated place in the Jacksonville metro area to a 'city' and some seemingly random non-freeway roadways, like Zoo Parkway and Emerson Street, to motorways. Note that the city tag should only applied to a significant populated place of regional prominence with a large population, like Jacksonville, St. Augustine, Gainesville, etc. As for the motorway tag, this should only be used on freeways such as I 95, 295, or the First Coast Expressway.

While the NHS designation is definitely criteria for classifying a road as primary or higher, this might be a rare exception, as the NHS-designated segment of Casino Drive is only a spur leading to some casinos rather than a major transport hub like an airport or seaport. In fact, I'm not even sure why the FHWA designated this as an NHS route, but I guess it might have to do with some planned development around Laughlin that was scrapped or postponed indefinitely (which there is plenty examples of in the area) or maybe the generating station. But on its own merits, Casino Drive isn't used as a through route as much as Bruce Woodbury is, and Thomas Edison Drive has a quite low AADT.

My bad—meant to say un-numbered, like other arterial roads such as Hualapai and Durango, rather than unsigned implying it does have a road number. Could be like Summerlin Parkway someday though, in that it would receive a state route number if it ever becomes a freeway like Summerlin Pkwy did. For the meantime it's maintained by the city.

That's true about Hollywood Blvd. I think the new road will do just fine but future-proofing roads when you can is always good. Nevada seems to be on a streak of building important connections like these as 35 mph arterial roads rather than 45-55 mph highways like one would expect (Silver Copper Crossing in Laughlin for example). In an ideal scenario in my opinion, there'd be a Sheep Mountain Parkway-like roadway being built instead of the Wiesner/Hollywood connection to take future higher-speed through traffic off the local roads. Since there's no beltway here, all traffic to Sunrise Manor is forced along Nellis, including quite a bit of truck traffic going to the Pabco facilities, but a project like this would almost certainly face more opposition than one like Sheep Mountain Pkwy since this is a more well-established area and not one that's actively sprawling outward like Skye Canyon.

I would probably keep these terminal roads down at secondary just because they are important roads but not important through routes/arterials like Russell or Paradise Road, and only serve airport traffic.

On another note, I recommend avoiding tagging roads like this one (way/204632888) as links. 'Link' is a very ambiguous term as it could be interpreted as anything in the scop of roads, but in OSM, this refers to almost exclusively unnamed roadways such as exit ramps, right and left turn slip lanes, and median breaks that focus on providing U-turns. This sort of road I linked is better tagged as a service or unclassified road.

Sheep Mountain Pkwy was originally proposed as a freeway that would run from the 215 north to 95 and then heading east over to I 15 north of the Beltway. While the lengthy segment that would run from 95 to I 15 has almost certainly been scrapped—considering this proposal predates the foundation of the Tule Springs National Monument established in 2014 (the parkway would been routed through this land)—full-freeway plans seem to be on the table still for the 215 to 95 segment. ROW acquisition and environmental assessments are happening around this area for a freeway to actually be built here.

That said, it could still be decades before any work on a freeway comes to fruition, considering there's still a lot of federal land to acquire and then the Paiute Reservation overlapping with where its northern interchange with 95 would be. For the meantime, Sheep Mountain Parkway will be a two-lane limited-access unsigned highway that bypasses the Skye Canyon area, running from Kyle Canyon Road down to somewhere near the Beltway.

Searching Sheep Mountain Parkway on Google and going to images should yield some old proposal maps of this highway. The ideas, even taking into consideration potential northward development into where the Tule Springs Monument is, are very unrealistic. I'm actually surprised they are still deciding to build a sort of bypass here of all places considering there isn't a whole lot of room for massive development in the Kyle Canyon area that would require such a project, especially when the eastern valley/Sunrise Manor area could really use one.

Just like city limits, all land claimed by the base is officially part of and should be tagged as part of the base even if undeveloped, just like how Fort Bragg, Quantico, and A. P. Hill are mapped. Note, annexes like the Nellis Small Arms Range may be better mapped separate from the base proper.

It's a limited-access highway, meaning it has no driveway access points, and most side-street intersections are RCUTs and RIROs. It's also a higher-speed, higher-capacity route for through traffic unlike a standard arterial road like Government Way.

The CDP is a separate, ungoverned entity from the air force base that is only a populated area of a base rather than the entirety of it.

Roads are classified based on their connectivity rather than their designation, especially since highway designations are often arbitrary in the scope of navigation and tend to reflect which entity maintains the road more than anything (particularly in more urbanized areas). This particular unsigned stretch completes part of the most direct route from West Chester and Pottstown towards Allentown.

Primary would be the ideal tag in a scenario in which you'd want to link a significant area (like Summerlin or Red Rock Canyon) within a population center (like Las Vegas). If 159 served to link longer-distance traffic to, from, or around Vegas, trunk would be the best tag, but functionally it is mostly a local highway.

I don't think Red Rock Canyon Road should be trunk since it functions more as a scenic bypass rather than long-distance travel/commuter route (or a component of such a route) like 160 and 146 do. Primary reflects its importance as a high-traffic route that links these very touristy parks to the city while also implying that it's not really a crucial route logistically like highway=trunk would imply.

The headquarters isn't a village, despite it being entirely separate from the City of Las Vegas, since it isn't its own community or jurisdiction. The Las Vegas Indian Colony is one entity which includes the main area with the headquarters north of Downtown plus Snow Mountain by NW Las Vegas.

Updated it. Since there doesn't seem to be any sort of a tunnel here, it's all a matter of removing the tunnel tag and adjusting the way to match the real-world alignment.

Path is a more ambiguous tag than footway=sidewalk is. Sidewalks are exclusively footways right along the side of a road, while a path or footway without specific tags varies in its purposes. Looking at aerial imagery again, specifically comparing the Bing Aerial to ESRI Clarity, this doesn't seem to actually lead anywhere, and it's rather an old alignment of a footway or authorized vehicle accessway that used to directly connect to the sidewalk along Las Vegas Blvd but now dead-ends at a retaining wall.

The whole road is closed as of now. Some paving work is complete but it remains accessible only to construction traffic.