Okay, sure thing!

It's okay, hahaha. I've changed it back to "East Galleria Drive." By the way, does your Tesla router still tell you to make that three-point turn?

Hello, why did you change the name of one segment of East Galleria Drive to West Galleria Drive? OpenWeb (https://maps.clarkcountynv.gov/openweb), Clark County's GIS, says it's East all the way to Lake Las Vegas Parkway.

I think I found what happened. First, I verified the street names and changed them accordingly. Second, I found a "U-turn only" relation comprising the way intersecting Lake Las Vegas Parkway and the westernmost node of said way. I'll use street-level imagery to fix it.

What "next" intersection? What street were you driving from? What's the name of the street of the "next" intersection? What direction were you driving along (north, south, west, east, etc.)? Also, a street changing its name just before reaching its terminus (endpoint) is very rare and impractical. Can you please provide more details? Thanks.

Okay. Well, what parts of the Nellis AFB should actually be classified as Nellis Air Force Base? The base itself or the complex around it? It turns out that the latter is much larger than what is currently shown.

Why did you create another node for the Nellis Air Force Base CDP? There are now two landuse objects that refer to the base in OSM: The military base itself and the complex containing it.

No, I'll admit it: I don't know why they haven't been removed. I didn't explain this earlier, but I didn't remove ALL directional prefixes, just the mismatched ones. Why weren't they removed anyway?

Okay, I've since downgraded it (and portions of Hughes Park Drive) back to primary. Thanks!

Which website did you use? If any object in your view belongs to a relation, you can select an object (like a tram stop), scroll down to the "Relations" section, and type the route's name or ref.

Hello, can you please add the tram stop "A" to the appropriate tram relation? I don't see any around the area. Thanks.

Hm, alright then. I'll go change it back. My reasoning for it being trunk are as follows:
* Residents of Blue Diamond can use SR 159 to get to the west-central portions of the valley quickly. The next-fastest route would be SR 160, then either Durango or I-15 to CC 215.
* Residents of the valley who want to visit Red Rock Canyon basically have to use this road eventually, since it's literally the only road connecting it to Red Rock.

Alright then, thanks for the information!

Hello, why did you delete the node for the Las Vegas Paiute Tribe headquarters? I have a feeling that this change will cause it to no longer appear.

According to streetlevel imagery, not all street signs in the area display directional prefixes. Therefore, adding them would be a violation of the "on-the-ground" rule. This doesn't even count the fact that some streets' directional prefixes are "mismatched" (i.e., "North Main Street" without "South Main Street"). However, because these are still important for addresses, I've preserved them in `name:full` and `name:prefix`, in line with what Utah does.

Hello, please do not use abbreviations in names. Also, please don't put "BLDG#" in the name. I suggest using the tags building=apartments, operator=Mountain GateTrails Apartments, and either ref=(building number) or addr:unit=(building number). Thank you.

Okay, thanks!

Just as an FYI: You don't need footway:surface on footways. That tag would come in play in this scenario:
* You map a traffic road and notice that it has sidewalks made of concrete. You would tag the traffic road with `sidewalk=both` and `footway:surface=concrete`.
For the footways themselves, `surface=concrete` should be good enough.

Oh, okay then. Could you please edit the tags to match what you said? I wouldn't know how to map something entirely underground (or covered), hahaha.

Hello, what was your reasoning for changing `highway=footway` to `highway=path`? This looks a lot like a sidewalk, except for the part at the eastern end (the one with the fixme). What _does_ it lead to, anyway?