Maintenance facilities don't really count as true at-grade intersections (or at least ones significant enough to affect road classification) since the driveways are inaccessible to the general public. These ramps could definitely be motorway links.

+1 to stubs themselves not being an issue in their own right, as rather they are more a symptom of greater problematic classification criteria or careless editing. I should specify that these road classification stubs are usually an issue since they typically will stem from physical-construction based classification, route designations, an accidental or incomplete edit, etc. As I have explained before though, there will be instances where because of physical geography or road conditions, a road should not be classified any higher past a certain point and a stub-ended route is justified.

Just like with the primary stretch of Lamoille Highway ending at a central location in Spring Creek where the traffic splits off onto other lower-tier major roads, this logic can be used with a secondary road ending at a split with tertiary roads. Some of it goes straight into the small community of Lamoille, while some goes south into the Ruby Mountain Wilderness Area. Neither of these destinations in their own merits may be worth 'linking' with a secondary route, but considering traffic heading to both of these destinations (and anywhere else beyond) is forced onto a single highway makes that highway that much more important.

On its own, Spring Creek probably wouldn't need to be linked by a primary route, especially if it was more adjacent and well-connected to Elko, but Lamoille Highway itself is the only route linking this some 15k population and a handful of commercial/industrial areas here to Elko, and thus it sees an AADT of about 14k-16k.

What's the reason for this one little section being tagged as a motorway? It's only a quarter mile between the frontage road access and the exit ramps.

This would be a rare primary-stub exception like Pyramid Way in Spanish Springs or Lake Mead Parkway in Henderson created by a busy, high-capacity road leading to a populous suburban area with not much beyond that other than low-traffic two-lane highway serving mostly recreational traffic.

The primary route here would be better linking Spring Creek rather than looping back to Idaho Street since the bulk of traffic on both 5th and 12th Streets would be heading towards the Lamoille Highway/Spring Creek rather than following a route like this.

If possible, if you would like a complete relation here, using proposed ways following the rough path of the future roadway would be more ideal. Though, keep in mind that mapping future features isn't always necessary as the data is rarely used and is subject to change.

West Virginia's State Route 121 only consists of the opened Coalfields Expressway segment so far. I would only add fut_ref=US 121 to any open segments of the Coalfields Expressway that are slated to be signed as U.S. Route 121, as well as any other proposed/under construction segments of the route.

As for the duplicate relations, that new State Route 121 relation might've been created erroneously on my part. The actual SR 121 is in Wythe County. The only official designation here is State Route 460.

I wouldn't add future highway designations to dirt roads/paths like these. This implies the exact roads here will be part of the route when in reality they're likely to be graded/blasted out of existence when Route 121 is built. Same for Route 16 through McDowell County since a new expressway is supposed to bypass the existing road.

Please do not use future highway designations in the ref=* key, instead use future_ref=*, likewise it should not be applied to proposed segments of Interstates like I 11. There are some signs posted for 121 along the new Coalfields Expressway, but VDOT does have a track record for not getting signage right, and the current LRS Route Overlap does not recognize Route 121 as an official highway yet.

Bend Parkway should not be tagged as highway=motorway since it has at-grade intersections, crosswalks, and bike lanes, which would disqualify it from being a motorway by OSM's standards.

McCarran Blvd does form a ring road around Reno, but it's a little too urbanized to serve as a true city-bypassing beltway like the 215 does around Vegas. It mostly links other major local highways like Pyramid Way, Sun Valley Blvd, and Virginia Street to each other rather than providing a bypass to through traffic, despite its expressway-like construction (which is just a more common theme for the major roads around Reno than elsewhere than in the Las Vegas Valley).

Veterans Pkwy is a good call though. I think I upgraded this one to trunk a couple years ago but in retrospect this is another road just like McCarran Blvd, that being a highway that looks like it could be a bypass but it mostly serves local, suburban traffic.

Suitland Parkway shouldn't have any motorway sections, just because it jump between grade-separation and at-grade intersections very frequently. It also has a speed limit of 45 mph, which may be fine for a section of a greater motorway or connection between motorways (even some Interstates have 45mph sections), but on its own it's a relatively low speed limit.

Another thing for motorways is that each section tagged as motorway should be treated as its own freeway. That way, you will get more consistent results, and each section of motorway between the trunk segments is in reality just a very short standalone motorway, which is discouraged on OSM. Particularly the section under the Anacostia Freeway is very much not its own freeway, as the speed limit is 30 and it has sidewalks.

MassCartog, the editor who created this changeset either is someone who has the exact same mannerisms of this one editor, or, is this particular user who has been blocked from OSM countless times in the past on various other accounts, primarily making edits in Florida and Maine, originally editing as edops and now more recently as 44mpr (@44mpr). They don't respond to changeset comments and make massive undiscussed edits to place classifications (changing a lot of cities to towns and vice versa) as well as changing the classification of roads all over, both often with no justification in their changeset comments, usually relying on vague comments like "fixed road" and "minor fix". A few times they have gone out and made the same changes after their previous account was banned and will probably revert anything you fix until they are blocked again. If this is that user and not just someone else who coincidentally has the same mannerisms of them, and Philadelphia is an are you specialize in mapping around, checking in on their edits every now and then might be good.

I don't want to outright accuse this editor of being the ban evader considering it's possible that they aren't. In which case—philpennmap it would likely be in your best interest to not use the exact same vague changeset comments as that user, not make the exact same controversial edits as them without (at least providing justifications if you don't discuss them first), and to read comments from other users.

However, if I have more proof that this is a sockpuppet account and/or more damaging edits are made, I will send a quick DWG email.

That makes sense to me. Like I've said before, it'd best to wait and see how developed this area gets to get a full understanding of how these roads are used to get the best idea of how they should be classified.

I would say the last two changes make sense.

As for Sky Vista, I don't believe it's that much of a primary road, at least for the time being. One issue with it is that it's not that much of a through route, as evidenced by the intersection with Charleston Blvd which restricts EB Charleston traffic from turning left onto Sky Vista. It's good to remember that the most major roadways you're going to see serving one particular section of a city will be secondary, as primary roads will typically have some sort of function providing through access for traffic that isn't immediately local (unless we're talking about a road serving an area large and developed enough it could be a city in its own right like Anthem).

I wouldn't worry too much about classification 'stubs' for under-construction roads since they aren't routable, and it is often the only way to tag the future classification of the completed road when the road is being built in segments.

The road alignments here prior to your changeset were up-to-date. The new alignments are more visible in the Esri imagery which is dated Feb 22, 2025.

The correct tag for any sort of community within a larger community would be neighborhood, quarter, or suburb. "Community" is also a very vague word and thus would not make a good tag in OSM. You could essentially say that it already does exist in the form of most place=* tags, be it a neighborhood, hamlet, village, city, suburb, etc. Also worth noting that Wikipedia descriptions don't match 1:1 with OSMs definitions, and the word "community" is used in the context of Sumnerlin being a master-planned community rather than the word alone being used to indicate what specific type of populated place it is.

Summerlin South is technically separate from Summerlin proper as it is a CDP in unincorporated Clark County, while the original Summerlin development is inside of the Las Vegas city limits. Even if Summerlin encompassed areas outside of the city limits, it should not be tagged as a town as it is not a entirely separate from Las Vegas as an unincorporated community or a separate legal entity.