For future reference, roads should not be classified solely based on their width, especially if it's a very short segment of a street like this that just so happens to be very wide. This street segment would still serve as a residential road in this case.

Please do not change the surface of an under-construction roadway to anything other than its typical surface unless it has officially been permanently changed to that surface. access=no with surface=sand would imply that it is a road with a sand surface that is inaccessible for any reason while highway=construction implies the road is not open due to long-term road work and may be unpaved due to the construction.

Please avoid using Google Maps data as a source for mapping, as Google's Terms of Use prohibit users from using this data to produce other content: osm.wiki/Google

I would recommend that, if reliant on third-party websites for mapping, using government-provided GIS services like the Clark County OpenWeb, which is also more accurate than Google since copyrighted maps tend to add subtle quirks to catch users who copy data from the map: https://en.wikipedia.org/wiki/Trap_street

Nevada state traffic data can be found here: https://geohub-ndot.hub.arcgis.com/maps/85d32ba5e82d44988bdd16943be5f14a/explore

I will note that AADT should not be 100% relied on for classifying roads, and that connectivity with destinations and other major roadways, physical characteristics, etc. may end up playing a role in the classification judgement. For example, a relatively minor road or segment of a road in a commercial area may see more traffic than a some segments along a major arterial that spans the metro and has multiple connections with other major highways, or a major highway that heads out of town to other communities may see just as much traffic as a collector roads through residential areas. AADT is, however, still a good tool for determining how these roads are used to get places.

I didn't downgrade all of the primary section of Warm Springs to secondary, just the section east of Las Vegas Blvd that abruptly terminated just before Lindell Road. This section of West Warm Springs sees far less traffic and adjacent development compared to East Warm Springs, which also has an Interstate connection.

Please do not tag roads based on their classification. A state route number is merely a number in the grand scheme of things and only reflects who maintains the road as opposed to its role in the road network. Bonanza Road has less traffic than Washington Avenue and lacks a direct I 15 connection unlike Washington does. Casino Center Boulevard is not as important of a Downtown link as Las Vegas Boulevard is and sees far less traffic as well.

Hello. 'CC 215' is the official designation for the Beltway, as it is referred to as the 'Clark County 215' rather than 'County Road 215'. Please do not make edits like these for the sake of rendering on third-party programs.

Hello—please do not add city labels for metro areas. The Las Vegas Valley is only a region, not a proper city, and the current Las Vegas city node already represents the core city that the metro area is sprawling off of.

Hello. Why were these unpopulated places changed back to hamlets?

Trunk roads are not classified based on their physical construction but rather their role in the highway network. In an urban scenario like DC, these are the most important highways that links commuters and trucks in and out of the city. See for example, Routes 1, 29, and 50 through DC, which serve as major arteries that link the city center to other major highways leading out of the city. Pennsylvania Avenue is also designated as a truck route in both DC and Maryland, and then becomes a freeway like Branch Ave does, linking the city to other major exurban communities.

Hello. What is the reason for downgrading this section of Pennsylvania Ave to primary? The road serves as a major commuter route in and out of DC and downgrading this trunk section breaks the connectivity with the rest of Pennsylvania Avenue and creates a dead-end trunk route on Branch Avenue as well.

Hello, why was the Powhite Parkway extension tagged as under-constructon? Proposed highway would be the correct classification since this project is still under study and has not yet broken ground.

The frontage road serves as an alternate route from the International Center and links to I 80. If it were to continue to another minor road without providing a secondary access point to the Interstate then I wouldn't have considered upgrading it to tertiary.

Upland Blvd. is a prime example of a tertiary road in which it is not a high-capacity arterial like Alta but it sees more traffic than a typical residential street. It is wider and and has lane markings, which are often signs that a street serves as a collector road. Compare that to Evergreen Ave, which is narrow, lacks lane markings, and has many speed bumps to discourage higher-speed through traffic (though some tertiary roads will have speed bumps here and there). This is an indication that Evergreen is intended to be a local neighborhood street that consequentially sees more through traffic due to it making a beeline through multiple neighborhoods and major streets.

Additional context can be found here: highway=tertiary

Hello, I have reverted this changeset in which you changed Route 29 to a motorway. This is incorrect, as the motorway tag is used for fully-controlled access highways. Whereas the Culpeper bypass is a controlled-access freeway, the rest of Route 29 which you retagged as a motorway has many at-grade intersections with other roads and driveways including traffic signals, and therefore should not be tagged as a motorway and should remain a trunk road.

Hello. Do you have an explanation for why these correctly-tagged parking aisles were retagged to regular service roads?

Looks like DWG might be taking care of it. osm.org/user_blocks/17388

I've reverted this changeset to restore the relation. I would've manually restored the city label like I did here (changeset/163537635) but I was unable to find the node in this one.

I will say from experience that it is very easy to accidentally break a relation with good faith edits, and that unless you are 100% certain that you know what you're adjusting or fixing in the relation, it is best to leave them as-is.

relation/170116 still exists, the boundaries have just been swapped with the city label role and the node itself was either moved or deleted, so the city label does not appear on the map.

Every complete city relation will have two components:

- a boundary or a series of connected ways forming a boundary that renders on the map

- a node that shows the city's name on the map

In your changeset, converting the city into an area broke the rendering of the city on the map. Zooming into the valley, you would only see North Las Vegas and Henderson while the name 'Las Vegas' no longer shows on the map and can only be found by other users by searching.

For example, you now have done the same thing for Henderson, which removes the name 'Henderson' from the map. Another editor has left a comment regarding that here: changeset/163465103

Now regarding placing a new Las Vegas city node instead of reverting it to restore the old one, re-mapping is highly discouraged since it does not have the same stored history as the object it is intending to replace. I've found the node that was converted from the city node to a random node in the boundary: node/31551114/history

So, it wasn't exactly deleted upon finding it, but it is now essentially hidden and its historic data cannot be accessed without digging through changesets or guessing which node along the boundary is the one you're looking for.

I have restored the original Las Vegas city node (changeset/163537635) but am not able to delete the new redundant city area polygon that was created in your changeset.

Hello, I had to revert this changeset because it appears some of the edits you made in it broke the Desert National Wildlife Refuge and Tule Springs Fossil Beds relations. I will recommend that it may be better to publish any unrelated edits you make in separate changesets so that smaller innocuous edits—such as the ones you make around the city published under this changeset—just so that the good edits you make won't have to be undone just because of one or a few erroneous ones that need to be reverted. For example, if you were to add businesses or edit buildings near the airport, it would be safer to publish those edits before or after you make edits in the vicinity of the DNWR.