Mapper deleted their own nodes. -- @NothingG, your track did not properly connect with the road in two places which I fixed.

Reverted in osm.org/changeset/163284326 - mws21313, if you perform a large-scale deletion like that, you need to give reasons that explain why the deletion was warranted.

Dear cicitheexplorer, thank you for your contributions to OpenStreetMap. The text you enter in the "changeset comment" field is seen by other humans and meant to be a concise description of what your edit entails; it could simply be "traced buildings" or something like that. However, writing the completely unintelligible hashtag salad "#hotosm-project-14910 #Accenture #ACNPhilippinesFY25 #acnphl #corpcitph #acnph_40 #onecioph", and thereby treating your fellow mappers as if they were a machine, is considered disrespectful. There as a separate field during upload where you may add hashtags; don't write changeset comments that consist entirely of them.

Dear CoRo67, OpenStreetMap has policies and rules too. Where those of your employer and those of OpenStreetMap contradict, you cannot automatically assume that those of your employer have priority.

When something is a private path/track/trail but clearly exists on the ground, we usually mark this with an "access=private" tag (or sometimes also "access=no" as you have done in some cases). We do not delete something outright that exists on the ground, like for example that part of osm.org/way/508134677 that extends into the watershed.

Your local knowledge is welcome and we would love to enlist your help in documenting which paths actually do not exist on the ground (as in: when I go there I don't see a path), or which paths may exist but be forbidden to use. However this changeset clearly violates our rules at least in some places and hence I am reverting your changes for the time being.

If you would like to discuss this issue and ultimately find out how changes can be made that reflect your policies without violating ours, the US community forum at https://community.openstreetmap.org/c/communities/us/78 would be a good start!

Dear user celicni,

you are adding a large number of name:sr tags to places in Turkey, even to the smallest of villages which until that time had only Turkish and at best a secondary Kurdish name.

As you know, we do not add transliterations as name:xx tags - a name added in this way has to be a name in its own right, not just the product of some automatism.

You need credible sources for these additions or else they will have to be reverted.

What is, for example, your source for name:sr=name:sr Богруделик on osm.org/node/2311601715?

Your edits are also made using a software that advertises itself as "java agent v2". As you know, automated/mechanical edits to OpenStreetMap have to be discussed before they can go ahead. Could you point us to the place where this has been discussed with the Turkish community?

Best
Frederik Ramm
OSMF Data Working Group
Ticket#2025030510000545

Hello Marco12234, did you notice that one of the tracks you added in this changeset leads directly through a building? Was there no warning displayed when you uploaded the edit? Please be more careful about these things in the future. Also, can you explain what your changeset comment "#hotosm-project-18212+;#OMGuru+;#OSMPh+;#aphub+added+roads" is supposed to mean? Remember, the changeset comment is for human beings to read and understand. Try to write something more legible next time. Thank you!

The removed path on the NE side of Oyster Creek did look a bit haphazard - https://overpass-api.de/achavi/?changeset=163216021 - though a proper reason for its deletion would be welcome.

(DWG Ticket#2025030410000387)

Dear Hubert, your videos are interesting but we can't allow the addition of 3rd party YouTube links to OSM because this would lead to an inflation of people trying to earn money on their YouTube content and we're ill-equipped to have more than one link in the first place. Maybe it is possible to somehow add your videos to the Wikipedia/Wikidata pages we link to.

DWG Ticket#2025030410000252

Hallo ChrissW-R1, ich verstehe ja, dass man (vielleicht gerade zur Faschingszeit) über solche Trumpismen lieber lacht als sich zu grämen, trotzdem ist OSM kein Platz für solche Witze. (Irgendjemand irgendwo freut sich schon, Deine Aktion als "Beweis" dafür zu nehmen, dass man sich auf OSM ja nicht verlassen kann.) Leite doch Deine Energien in sowas wie https://gulfof.mapquest.com/?name=ChrissW-R1 - dann können wir alle darüber lachen. Edits revertiert - DWG-Ticketnummer folgt

Dear jenie ann, thank you for your contriubtions to OpenStreetMap. The "Changeset comment" field is an important field that you can use to tell the rest of the OSM community what you did in that change. It can sometimes feel a bit onerous but it is very useful for quality assurance purposes.

Many of your changesets contain a lot of "hashtags" in the comment field but hardly any human readable information. It would be great it you could make it so that actual human beings can understand what the message is.

In this particular changeset, which adds buildings in Colombia, you have used a couple of hashtags that seem to point to projects in the Philippines which is probably a mistake?

Hello WWMapper101, DWG here. Thank you for involving us (Ticket#2025022110000507). Archie is right, the validator might hint at potential issues but its suggestions should never be followed blindly. Always cross-check with aerial imagery - else you risk adding "crossing:markings=no" to a crossing that is wrongly tagged as "unmarked"!

(Also, adding "crossing:markings=no" to a "crossing=unmarked" adds zero information, it unnecessarily adds a new version and increases our history database. It's ok to choose the "new" tagging when you add a new crossing, but going over all existing crossings and "fixing" them is of little use.)

Dear qaewsrdtfcvgbhqsdesqw, while you are free to choose from a wide range of user names, please consider that OpenStreetMap is a community project, and other mappers will from time to time want to discuss your edits with you. Think about whether your user name "qaewsrdtfcvgbhqsdesqw" is conductive to such discussions!

In the future when you upload data to OSM, please fill the "comment" field with a human-readable description of your edit (e.g. mapped buildings in XY city, corrected geometries, whatever). Hashtags belong in the "hashtags" field; a changeset comment like " #hotosm-project-16505;#OSM-TW;#OMGuru" doesn't make sense to 99% of OSMers and may even be considered disrespectful.

See also osm.org/changeset/162585182

Dear Mimansa Gulati, please pause your edits and explain. You have deleted existing buildings in the area without any explanation, and relpaced them with odd shapes that do not match aerial imagery. "#IITBHU" is not a good enough explanation for this. Why have you deleted the existing buildings from OSM - have these been demolished? What is the data source for your additions?

Dear Harsh_IITBHU, please add proper changeset comments to your uploads. "hhhh" or "mm,mmm," are not sufficient. You can group many trees in one upload and then you can write "added trees" or something.

Dear TheManinHighCastle, please do not add Chinese names to name tags outside of China. There are "name:zh" and other tags to record the Chinese name. If you want a map that displays Chinese names outside China, set up your own tile server. DWG Ticket#2025021510000251

Hallo trailschneck, ManuelB701 hat recht, bitte erfasse keine überbauten Bahnen. Ich habe die jetzt wieder gelöscht. Grundsätzlich möchte ich Dich auch um einen respektvolleren Umgangston bitten; Du kommst hier ziemlich patzig rüber. (DWG Ticket#2025021510000233)

If you could email to data@osmfoundation.org with [Ticket#2025021410000315] in the subject - then this would get inserted into the correct DWG ticket automatically. Thank you!