Good question: motor_vehicle=designated appears to be one way of saying that the road is specifically for motor vehicles, alongside motorroad=yes and expressway=yes (the latter is a recent trend according to https://taginfo.openstreetmap.org/keys/expressway#chronology). They also seem to be in use on public highways in Madrid according to Overpass Turbo (sorry for long link): https://overpass-turbo.eu/?Q=%5Bout%3Ajson%5D%5Btimeout%3A250%5D%3B%0A%7B%7BgeocodeArea%3AComunidad%20de%20Madrid%7D%7D-%3E.searchArea%3B%0Away%5B%22motor_vehicle%22%3D%22designated%22%5D%5B%22highway%22%7E%22%5E%28motorway%7Ctrunk%7Cprimary%29%22%5D%28area.searchArea%29%3B%0Aout%20geom%3B&C=40.13713%3B-3.48051%3B8

Has there been any discussion that led to the discouragement of landuse=* in areas with well-mapped buildings in the area? If so, then landuse=* may have to be updated with a "regional variations" section or something.

I have to disagree with the comment, because many cities in the world, such as London, Singapore, and even neighbouring Nassau County, have landuse=* to indicate the main usage of the land, even if the area is well mapped with buildings. I wish to ask what makes the situation different in New York City?
---

Published using OSMCha: https://osmcha.org/changesets/166046420

I would agree to retag as shop=appliance. The other tag has only ten uses compared to 9,774. However, each remaining instance must be reassessed individually.

Good point. I'll remove that, even though Arkadag is the only main destination from that junction.

Clarification: it's the small track that is presumed split in half.

I wish to know why are you changing road classifications without consulting the community, and why are you leaving vague changeset comments for changesets that make big changes like this one?

Dang it, forgot to close the changeset before moving to another area.

I also just fixed that.

I think I have corrected the tags now.

I'm sorry about the mistake there, I think I did get carried away while trying to address the Osmlse parking errors.

There is a case for stop_area relations: we already have these for Transport for London’s rail services, in addition to countless rail services worldwide.

I am also not sure if tag duplication is a major problem since I do not know of railway station codes changing frequently: the only thing that may change frequently is the operators, and I only went by what was specified in public_transport=stop_area. When train franchises change names, we can always run it via Overpass Turbo.

However, I will be happy to try a different method that will keep existing station nodes. I should improve on that.

In the early days of OSM, track_detail indicated where individual tracks were mapped. According to taginfo, the UK and Sweden were the main users. See https://lists.openstreetmap.org/pipermail/talk/2015-October/074462.html for more info.

The reconstruction of the boundaries covers the route clockwise from Hillingdon/Hounslow to Barnet/Harrow.

See junction=yes#How_to_use_on_an_area. Feel free to correct it if necessary.

Hi, your changeset broke valid data regarding lanes and lighting, although it may not be apparent at first. If in doubt, use JOSM, since it comes with the tag conflict resolution detecting thing.

Got it.

It was too ambiguous to include the ferry at the time, because it doesn't operate 24 hours a day.

Pas de panique! I managed to flush the changeset with changeset/48456866. All I had to do was add your road crossing back, and fill a gap in the Route Nationale 1 relation.

If you like, I can revert it entirely but I am not sure about the tone of language in the comment.