I have remapped this portion of Registon ko'chasi correctly in changeset 153333465. Note that if you want to make further changes to the intersection of Kulolon ko'chasi and Registon ko'chasi, the primary_link roads (which I added a few days ago) are new and do not yet appear on Bing or Esri imagery.

One week ago, in changeset 152999693, I remapped Registon ko’chasi in Samarqand completely between Universitet bulvari and Islom Karimov bo'gi: originally this road was incorrectly mapped as a dual carriageway, but there is in fact no physical separation between the directions. It is a single way with lanes=4, lanes:forward=2, lanes:backward=2. This can easily be verified by a personal survey of the street.

It looks like my correct tagging has now been undone. Please tell me whether you did this in this changeset, or if the fault lies in subsequent changesets by use ChromeLotus.

Your edits to Registon ko’chasi in Samarkand are incorrect. That is, in changeset 152999693 one week ago, I remapped Registon ko’chasi completely between Universitet bulvari and Islom Karimov bog’i: in an earlier version, this road was incorrectly mapped as a dual carriageway, but it is in fact a single carriageway with lanes=4, lanes:forward=2, lanes:backward=2. This is easily verifiable by doing a personal survey of the road.

Somehow this correct mapping was undone, either in changeset 153159867 by user FUZZY_42, or in your recent changesets. Please let me know if you were responsible for this error, otherwise I will revert all the way back to FUZZY_42’s changeset.

Please do not remove footway=sidewalk tags from highway=paths in Poland representing combined or segregated footways/cycleways, as you did with way 864232970. The footway=sidewalk tag is widely used in Poland on such ways that are indeed sidewalks. The Osmose bug layer may complain about this, but this is a false positive in Osmose, not an error.

I see that you have added the names to many mosques in Uzbekistan. However, you wrote the names in ALL CAPITAL LETTERS. This is not correct. Every time you did this, it generated a bug in the Osmose layer asking mappers to correct the error. This is a lot of work for your fellow mappers!

I would be grateful if you could get a set of all mosque names you have added in Uzbekistan, and correct the capitalization of these names.

Why have you added the name "Qabriston" (and its English translation) to all Sunni Muslim cemeteries in Uzbekistan? This is a generic name, already expressed by landuse=cemetery, and therefore it should not be added as the name= tag. The name= tag should be the actual name (if any) of each cemetery according to the sign posted at its entrance.

Why did you remove the footway=sidewalk tag from way 1036888497? footway=sidewalk tags are widely used on segregated footways/cycleways in Poland that are indeed sidewalks to neighboring roads. If you saw this tagging flagged by Osmose, then this is a false positive in Osmose, not an error.

Please don't add generic name= tags, like "Stomatologiya" for an amenity=dentist. This information is already expression by the amenity=dentist tag. The name= tag should contain the exact name of the dentist.

Please don't add wild camping places to OpenStreet (“Хорошее место для палаткиа”، “Good camping area”). The tourism=camp_site tag is for official camping sites only. For unofficial ones, they can be added to some other project like the iOverlander app.

highway=crossing, crossing=traffic_signals nodes in Nukus are in the wrong place. You added them where pedestrians would stand and wait to cross. However, the standard practice all over the world is to place these nodes on the street, at the intersection with the highway=footway, footway=crossing. Please help me in cleaning up these erroneous Nukus pedestrian crossings.

Why did you change way 30746989 from highway=path to highway=cycleway? I did an on-the-ground survey here and found that there was official EU signage that this is a footway/cycleway, so highway=path foot=designated bicycle=designated is the modern tagging used for this signage (as can be seen e.g. in the JOSM and Vespucci presets).

"The fact is that in Azerbaijan there are a lot of identical names, and in order to initially identify them correctly, the name of the settlement is added"

This is not necessary. Already many years ago, the OSM community began deprecating the is_in: tags, and your edits are simply repeating the same deprecated behavior, but without even the processability of a tag.

"The fact is that there are navigation programs that are mainly used in Azerbaijan ... do not accurately reflect some objects, and sometimes they simply do not display them."

The fact that some renders do not display the correct tag is not a reason to use an incorrect tag. If you have been active on OSM for some many years, then I assume that you already know the fallacy of “mapping for the renderer”. As I map, I will remove these incorrect instances of amenity=townhall.

I understand that you live here and know the local specifics. However, that does not mean that you can map wildly different from the rest of the world. If you have been part of the OSM community, then you may already know instances when a country had one power user whose practices were strange in a global context, and eventually the DWG had to get involved.

Please do not add a \ character and the city district of POIs to their name= tags, as I see you have done for hundreds of POIs in Baku. This is not a standard way of tagging names on OSM.

The map of Baku is full of amenity=townhall nodes, but these are incorrect. For example, the car repair shop at 40.3080260, 49.7870886 should not be tagged amenity=townhall. Please see the OSM wiki for the correct usage of this tag:

osm.wiki/Tag:amenity%3Dtownhall

Also, if I made any changes to intersections, they often came with the addition of turn:lanes and surface tags, so if you are (IMHO unnecessarily) reverting, then ensure that the new tags are preserved in any revert.

Judging from what I saw of SoCal when I began mapping, pencil-tip intersections are not considered incorrect. (Extended pencil tips are, and I have removed what few I have come across).

I mean, with regard to this particular way: osm.org/way/406459444

But if you relied on the fixme tag elsewhere along the road to guide your or others’ future edits, then sorry for removing it.

OK, with regard to East Meats Avenue, I see on this way that I removed a fixme=“This should not be a dual carriageway”. However, Bing imagery shows a road marking that many mappers would interpret as physical separation, and therefore tagging the road as two separate oneway ways seemed to be in accordance with the common conventions in this region from before I mapped here.

Again, I don’t believe I downgraded intersections, but if you believe that there is some error, please give me the exact coordinates.

With regard to “jumping all over the world”, I spent most of 2023 and early 2024 working on the greater Los Angeles and San Diego regions. Right now, however, I am mapping where I am traveling. There is nothing unusual about this in the OSM community.

Please give me a link to the actual way where I removed the fixme tag. This edit was months ago and I have made many hundreds of edits in the Los Angeles region from imagery.

With regard to traffic signals, I don’t believe that I added any in the wrong location. Most of my edits in the Los Angeles region involving traffic signals has been removing duplicate traffic signals at complex intersections, as described on the wiki:

osm.wiki/Tag:highway%3Dtraffic_signals#Complex_intersections

Did I make a mistake in this process somewhere?