How were you able to edit it when I can't? It's not like there's anything I can do to edit it again since this one relation is so big.

I didn't get a chance to add a description, so I'll do it now: I added "Home Depot" as the operator.

Hello, what was the point of that? Having a node and a building represent the same thing makes the map look cluttered; it also violates the "one element, one feature" rule.

No, this was not an automated edit at all. I made sure to check the highways before publishing them, since some values of road=* were typos (e.g., road=unclasified). Also, the fact that a road is unpaved doesn't inherently mean it can't be a secondary road (I just read the article for track roads on the wiki). Any locals who know the classification of these highways are free at any time to correct the classification. I changed most of them to highway=road because I could not determine their classification by looking at their tags (i.e., road=rural road). Also, marking them with highway=road alerts QA tools to (hopefully) alert users about what happened.

There were ~400 objects (IIRC), so I really only checked one (a random junction in California).

Thanks for adding names to these roads! They've been missing for a long time.

It's not just me. Many other people have been doing that over the past few years. In fact, I think that adding boundary=administrative on ways because it appears on a particular renderer (Freemap Slovakia, in this case) is "tagging for the renderer" and should be avoided. Instead, the OSM Wiki suggests opening a bug report on the renderer to fix that instead.

If there is, in fact, a sign indicating its name, I couldn't find it, and it's definitely not along the main highway. Is it buried on some random intersection hidden from Street View?

Well, Russia also held a "referendum" in those four oblasts (I put it in quotes because the international community views them as illegitimate). Also, just to clarify, Russia actually 𝘢𝘯𝘯𝘦𝘹𝘦𝘥 them, not just occupied them because they're at war. In the case of the latter, I couldn't find any `military=danger_area` polygon or something similar covering those four oblasts (or Kursk or Crimea) like there is in Gaza. I read that Ukraine did manage to recapture one of the four oblast's capital cities, though.
"[The four oblasts] are under occupation, not recognized by Russia. Also, it is an ongoing war." What do you mean Russia wouldn't recognize its own illegitimate annexation of four Ukrainian oblasts?

What do you mean it is not the same situation? Russia annexed Crimea in 2014 (which isn't internationally recognized) and the other four in 2022 (which also aren't internationally recognized). What's the difference here? I don't see any.

This was an option provided by Vespucci, so I decided to test it out by adding them to places I knew would match up with the data in OSM.

Hello, please don't reclassify a residential road just because it intersects the two carriageways of one road. An unnamed road that does this would be classified as a tertiary LINK, but this road is clearly not unnamed. Thanks!

changeset/173858345

Except that I have an objections: it still does exist (go to this area on Bing Maps Aerial, for example), but it's not used anymore (hence disused:highway=residential).

Okay, I guess that makes sense. I'll put that on me for misinterpreting the text. Thanks!

Hm, how about highway=primary + motorway=yes?

Done

(Also, I just realized that my proposal is still in its draft phase, partially because I needed to come up with a better tagging scheme first.)

1. You're completely right. There is a gantry right above the SPUI junction. However, by convention, the `traffic signals` node should be placed at the location where vehicles need to stop. In this case, it's before the stop marking line visible in Bing Maps Aerial. That's where I placed the traffic signal, and that is why I made that segment a motorway. I've added the gantry to the database and changed it back to secondary.
2. Thanks for sharing the info; I had no idea I had to do that first. There's already a discussion in the OSM Forum about highway classifications, so I'll likely change my tags to make more sense. Once again, thanks!

Because the key `old_name` does not apply to the sidewalk. If I had tagged the sidewalk as `old_name=Brandywine Way`, that would've meant that the sidewalk itself used to be named "Brandywine Way," which is incorrect. `street:old_name` perfectly encapsulates the situation I am accounting for here, where 𝘁𝗵𝗲 𝘀𝘁𝗿𝗲𝗲𝘁 𝙖𝙨𝙨𝙤𝙘𝙞𝙖𝙩𝙚𝙙 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝘀𝗶𝗱𝗲𝘄𝗮𝗹𝗸 used to be called Brandywine Way.

If you run the validator in JOSM, it will complain that there's an "alt_name without name." If the name "2100 South Freeway" isn't signed anywhere, that can be indicated with `name:signed=no`. If there is no other name that the freeway goes by, wouldn't the nickname that locals use (which is the only name aside from the designation, which is not a name) be put in `name` (since there's no "official" name)?