piebro/osm-data huggingface dataset:
Udarian (2026-02-18 01:31:07+00:00): next time can you please leave a better changeset comment as the comment on this one doesn't really tell me anything about what you did in this changeset. A good changeset comments doesn't need to be to complex, something like "added description to business" would have been sufficient for this changeset. For more information on changeset comments see https://wiki.openstreetmap.org/wiki/Good_changeset_comments

Happy mapping,
Udar.
NorthCrab_upload (2026-02-18 06:31:36+00:00): 🗺️ Witaj na OpenStreetMap!

Zauważyłem, że Twoja zmiana zawiera adresy wymagające dodatkowej uwagi. Przygotowałem listę obiektów oraz dodatkowe informacje:

Nazwa ulicy nie istnieje w okolicy. Jeśli adres ma nazwę ulicy, upewnij się, że jest ona poprawna. Jeśli nie, usuń addr:street, a nazwę miejscowości przekaż w addr:place.
https://www.openstreetmap.org/way/1479942810

Dokumentacja adresów (po polsku):
https://wiki.openstreetmap.org/wiki/Pl:Key:addr:*

W razie problemów lub pytań, proszę pisać. Chętnie pomogę.
Pozdrawiam! 🦀
Branko Kokanovic (2026-02-19 08:56:58+00:00): Zdravo,
Samo da javim da si imao malu gresku u nazivu ulice (Јована Јовабовића Змаја), ispravio sam. Svaka cast za ostale izmene!
Taya_S (2026-02-27 14:12:10+00:00): Reverted some low quality edits by sockpuppet account

https://www.openstreetmap.org/changeset/179133451
Taya_S (2026-02-18 07:13:57+00:00): Hello abtal1,

Regarding https://www.openstreetmap.org/node/3142518378, you've both removed the name, and removed the shop type. Currently this object is just a "shop=yes". Could you explain why you removed these tags?

Regarding https://www.openstreetmap.org/node/13455502892, what's with the brackets? And is that a personal name, or indeed the name of the neighbourhood? Also, why does a neighbourhood have opening hours?

Please answer these questions.

Best regards,
Taya Snijder,  
On behalf of the OSMF Data Working Group
What does
NeisBot (2026-02-18 02:54:22+00:00): Hi Michael Collins, welcome to OSM!

Thank you for your contributions to the map. I have reviewed your recent edits and noticed that 94% of the changes in this set involve deletions, including:
- 144 building(s)

Could you please confirm if these deletions were intentional or if they occurred by mistake?

Looking forward to your response.

#DeletionsCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=178705190
Michael Collins (2026-02-18 05:19:04+00:00): Yes, the buildings were deleted purposefully because they were not identifiable as buildings in the Bing imagery. In most cases, they were bushes or fenced-in ground areas.
Baloo Uriza (2026-02-18 14:27:46+00:00): Including the name=* on the sidewalks is a good idea (for the same reasons that divided roadways have names on both sides).
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/178705219
LexiFoxi (2026-02-19 02:20:51+00:00): Are you saying to add the name=* to the sidewalk for each sidewalk that parallels a road, likely how I had noted it in other areas?

Wanting to make sure how to correct it and remember for future edits.
Baloo Uriza (2026-02-19 12:40:55+00:00): Exactly.
Frank Peng (2026-02-19 01:19:49+00:00): Hello MooPoo7, I noticed that you removed lanes, turn lanes, maxspeed:advisory=*, destination:lanes=*, change:lanes=*, and placement=* tagging from those roads in this changeset. I don't think those tags are outdated. Could you explain if the removal of those tags was intentional? Thanks.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/178705225
MooPoo7 (2026-02-19 01:36:07+00:00): Sorry for not being clear in the changeset! This interchange just wrapped up a major renovation, so all of the lane tagging needs to be resurveyed. I removed those tags since they are now incorrect, and the absence of those tags highlights the need for them to be re-added in the future.
ChaireMobiliteKaligrafy (2026-02-18 11:17:07+00:00): Hi! Can you explain the rationale for this change? the delivery driveway was disconnected from the main road. Thanks! (I fixed it already)
PhattyMatty (2026-02-18 11:49:03+00:00): Sorry, it is the unmarked crossing. This is not a safe spot to cross the road.
ChaireMobiliteKaligrafy (2026-02-18 12:51:39+00:00): OK, thanks for the info. However, the fact that the crossing is unsafe is information that should be added to another layer outside of openstreetmap. In Quebec, it is legal to cross the street at any intersection, except where there is a forbidden sign for pedestrian, which is very rare and not the case here. Thanks and have a nice day!
NeisBot (2026-02-18 04:33:57+00:00): Hello, welcome and thank you for your contribution to OSM!

Your changeset was commented because your added description, note or slogan contain detailed text that may be interpreted as promotional or SEO-related. To ensure OSM remains neutral and focused on map data, I recommend keeping descriptions concise, factual, and free from marketing or promotional language.

⚠️️ Problematic element (limit 1):
https://osm.org/node/13574971705 v1

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Repair shop"

#MapWithoutSpam
NeisRevert (2026-02-26 05:33:08+00:00): 🔄🤖 Partly reverted due to either a lack of response from the contributor or remaining promotional text by https://osm.org/changeset/179067813
(Clean up leftovers from previous edits)
NeisBot (2026-02-18 04:36:51+00:00): Hello, welcome and thank you for your contribution to OSM!

Your changeset was commented because your added description, note or slogan contain detailed text that may be interpreted as promotional or SEO-related. To ensure OSM remains neutral and focused on map data, I recommend keeping descriptions concise, factual, and free from marketing or promotional language.

⚠️️ Problematic element (limit 1):
https://osm.org/node/13574972544 v1

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Wellness Clinic"
---
ตัวอย่างเช่น รูปแบบที่เป็นกลางและเป็นข้อเท็จจริงมากกว่าของข้อความของคุณอาจเป็น: "คลินิกสุขภาพ"
---
(Auto-translation)

#MapWithoutSpam
The self wellness (2026-02-18 08:27:19+00:00): thank you
b-jazz (2026-02-19 01:23:55+00:00): FYI, I fixed up a bunch of golf=hole ways that you had done recently. Please be aware that direction matters and the way should be drawn from the pin to the hole/green. Hopefully I found them all, but I just wanted you to be aware for your golf course map that you contribute to. thanks.
b-jazz (2026-02-19 01:26:20+00:00): Also, when you create a multipolygon relation with a fairway and a green (or various other combination of inner ways), you should tag the fairway way as fairway as you've already tagged the relation with inner/outer ways as a fairway. To also tag the outer way is wrong. thanks.
ChehrehBargi (2026-02-18 08:17:01+00:00): @masoudghorbany
Every program has its own rules. It is not acceptable for someone to violate these rules for their own convenience. Such edits are tracked and dealt with by reviewers. You are in changesets 178670826, 178671058, 178671110, 178679554, 178673226, 178670009, 178673092, 178673059, 178672997, 178672902, 178672856, 178672902, 178672819, 178668353, 178672325, 178670726, 178670646, 178670548, 178670427, 178670308, 178670112 and 178669930 You have repeated this action without paying attention to the rules, in addition to being aware of them.
NeisBot (2026-02-18 04:48:40+00:00): Welcome, and thanks for your edits!

I noticed a few unintended crossings between roads and/or between roads and buildings in this changeset. This usually happens when geometry snaps incorrectly. Additionally, changes to tagging (e.g. modifying highway types or adding tags) can lead to unexpected crossings being detected afterwards.

In total, I detected 39 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/304692737 v5 | 15 crossings
https://osm.org/way/732426895 v3 | 14 crossings
https://osm.org/way/305224762 v2 | 10 crossings

⚠️ Dragged Nodes (max 3):
https://osm.org/node/3092775103 v3
https://osm.org/node/3098247971 v2

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=178707476
NeisReview (2026-02-26 05:33:10+00:00): ✅ Should be fixed by 
https://osm.org/changeset/178763072
NeisBot (2026-02-18 05:06:39+00:00): Welcome, and thanks for your edits!

I noticed a few unintended crossings between roads and/or between roads and buildings in this changeset. This usually happens when geometry snaps incorrectly. Additionally, changes to tagging (e.g. modifying highway types or adding tags) can lead to unexpected crossings being detected afterwards.

In total, I detected 12 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/145068120 v11 | 9 crossings

⚠️ Dragged Nodes (max 3):
https://osm.org/node/2354807225 v3

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=178707874
NeisReview (2026-02-26 05:33:10+00:00): ✅ Should be fixed by 
https://osm.org/changeset/178750018
Frans S (2026-02-28 13:17:20+00:00): We welcome you as a new mapper.
Thanks for your contribution to this project.
This changeset is reviewed by a Global Validator to check that the tasks have been mapped in accordance with the quality standards of HOTOSM. 
We cannot expect from a new mapper that he/she delivers high-quality mappings from the start, so we offer some guidance.
Please pay attention to the next summarized issues. (see attached document with examples for more info)
-------------------------------------------------------------
Issues found on your mappings
A: Inaccurate mapping. 
C: Collected adjacent buildings and mapped it as 1 building.

E: Buildings not squared or rounded.


Explanation can be found in this document which  might be helpful to strengthen your mapping skills
https://docs.google.com/document/d/1Swwz-ZwM3_YOstqstsmCg1-lNAPbnMLpi1Al-h-2UOQ/edit


Best regards and keep mapping!
Frans S
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.org/changesets/178708253
EvanSiroky (2026-02-19 06:02:37+00:00): Source: https://data.sacog.org/datasets/SACOG::sacog-regional-centerline/about
NeisBot (2026-02-18 06:54:50+00:00): Hello, welcome and thank you for your contribution to OSM!

Your changeset was commented because your added description, note or slogan contain detailed text that may be interpreted as promotional or SEO-related. To ensure OSM remains neutral and focused on map data, I recommend keeping descriptions concise, factual, and free from marketing or promotional language.

⚠️️ Problematic element (limit 1):
https://osm.org/node/13575073296 v1

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Tour operator office"
---
Zum Beispiel könnte eine neutralere und sachlichere Version deines Textes lauten: "Büro des Reiseveranstalters"
---
(Auto-translation)

#MapWithoutSpam
Tanzanian Pioneers (2026-02-18 07:54:35+00:00): Updated. Done
rempshaener (2026-02-18 17:27:50+00:00): Hallo,

du hast um eine Prüfung deiner Bearbeitungen gebeten.

Ich habe eine Anmerkung zu den Saugstellen.
Das Tagging ist fast okay, nur das
content=water
drinking_water=no
ist wenig zielführend und Namen bei Saugstellen müssten auch raus.

Problematischer: In OSM wird nur erfasst, was man vor Ort sehen kann, siehe z. B. https://openstreetmap.de/osm/was-geh%C3%B6rt-nach-osm/
In der Gegend liegen recht gut Mapillary-Bilder vor, auf denen keine Saugstellen zu sehen sind. D. h. ohne vorbereite Fläche oder noch besser einer passenden Beschilderung wäre das nichts, was in OSM erfasst werden sollte. Daher meine Bitte, die Saugstellen wieder zu löschen.

Bei Fragen bitte melden.
Viele Grüße
muralito (2026-02-18 16:32:41+00:00): Hi. Based on which source did you these changeset? Esri World Imagery as tagged?
LakeLouise (2026-02-19 06:44:45+00:00): Hello muralito,
I cited Esri since it shows the two residentials as a possible dual carriageway. Upon further review I understand this does not provide sufficient oneway evidence and happy to defer to your knowledge.
eggie (2026-02-18 09:32:26+00:00): Oke M Hilbrink, maar je hebt helaas geen rekening gehouden met de OV routerelaties.
Die zijn nu onderbroken.
Zo'n rotonde dien je dan op te knippen in segmenten en de routes weer doorverbinden.
MVG
eggie
eggie (2026-02-18 09:36:56+00:00): Drie busroutes hersteld.. junction=roundabout toegevoegd
eggie (2026-02-18 09:47:16+00:00): Kruising fietspad verbonden met De Vogelweide.
Straatnaam van rotonde verwijderd.
Geen straatnamen toevoegen aan rotondes.
eggie (2026-02-18 09:53:25+00:00): Voetpad en Vogelweide verbonden dmv node
eggie (2026-02-18 09:54:38+00:00): Tip..  Je mapt met JOSM. Wanneer je de validatie zou draaien haal je al die fouten eruit. 
Met Josm kun je ook prima die routerelaties weer goed krijgen.
Mapse
eggie
eggie (2026-02-18 09:59:30+00:00): Zuidelijke fietspad loopt niet meer daar dus verlegd naar het zuiden.
https://viewer.satellietdataportaal.nl/@52.33833,6.637011,19/?datastrip=20251215_PNEO-03&sensorname=Pleiades-NEO
M Hilbrink (2026-02-18 11:05:50+00:00): Hoi Eggie,

Ik heb JOSM gebruikt, snapte de error ook niet geheel, alleen dat fietspad de weg kruist maar dat is ook zo. Rotonde opknippen wist ik niet.

Doe ook niet zo heel vaak (eerder niet) dergelijke omvangrijke aanpassingen, daarom ook de validatie gevraagd aan de community.
eggie (2026-02-18 11:12:21+00:00): Oke...   De validatie zegt dan dat in je in zo'n geval een verbindingsnode moet aanbrengen anders de fout Crossing ways.
Het zou anders niet routeren. 
Tja .. en routerelaties zijn ingewikkeld in het begin.
Daar hebben veel mappers moeite mee en beginnen er niet aan. 
Je kunt in zo'n geval hulp vragen op het forum of gewoon een opmerking op de kaart plaatsen. Dan past een ervaren mapper het wel aan.
Het klopt in ieder geval allemaal weer en is weer actueel. :)

MVG
eggie
MHBFDEU (2026-03-03 10:28:15+00:00): Hallo Tommy, 
melde dich doch bitte mal bei mir per Mail. Wenn du lokal viel mappst, bist du vielleicht der richtige Ansprechpartner. 
Gerade zu diesem Gebiet.
Violaine_Do (2026-02-18 23:58:05+00:00): Bonjour Mat, As tu regarder les conventions de cartographies (en discussion) pour la Polynésie française avant de modifier le travail de la communauté locale? https://wiki.openstreetmap.org/wiki/FR:French_Polynesia/FR:French_Polynesia_tagging_guidelines#Routes Si oui merci de discuter directement sur la page avant de rétrograder la hiérarchisation faite. Le contexte polynésien est spécifique, les définitions auxquelles nous avons travaillées sont issues de près de dix années de travail avec des collègues urbanistes, des membres de l'administration compris. Merci par avance pour tes contributions constructives,
Violaine_Do (2026-02-19 01:13:09+00:00): Après réflexion, je l'ai rétrogradé en tertiaire, ça parait plus cohérent au regard de tes modifications précédentes, un entre deux ! Bon mapping
totera (2026-02-18 08:32:35+00:00): "dalla Rete risulta"? Su che cosa hai basato le tue modifiche?
Pucciotrex30 (2026-02-18 08:37:16+00:00): c'è il tag source
totera (2026-02-18 21:42:05+00:00): Non ci sono né cordoli né erba in quella foto (ad ogni modo il tag source si usa sul gruppo di modifiche, non sugli oggetti)
Violaine_Do (2026-02-18 23:59:23+00:00): Bonjour Mat, As tu regarder les conventions de cartographies (en discussion) pour la Polynésie française avant de modifier le travail de la communauté locale? osm.wiki/FR:French_Polynesia/FR:French_Polynesia_tagging_guidelines#Routes Si oui merci de discuter directement sur la page avant de rétrograder la hiérarchisation faite. Le contexte polynésien est spécifique, les définitions auxquelles nous avons travaillées sont issues de près de dix années de travail avec des collègues urbanistes, des membres de l'administration compris. Merci par avance pour tes contributions constructives,
mat (2026-02-19 06:20:19+00:00): Bonjour Violaine,
Je n'étais pas au courant d'une classifications spécifique à la Polynésie française.
Il faudrait toutefois que cette classification reste "en accord" avec les règles générales, à savoir que les voies des réseaux primaines/secondaires et tertiaires sont des voies de transit. Ça signifie que ce sont des voies que l'on emprunte pour aller sur d'autres vois plus précises comme unclassified/residential/service/etc. Ce que ça signifie surtout, c'est qu'une voie de transit se termine a ses deux bouts par soit une d'autres voies de transit plus élevée ou de desserte plus précise, mais elle ne peut pas se terminer "brutalement".
Violaine_Do (2026-02-19 19:31:36+00:00): Bonjour Mat, 
pas de soucis, c'est une classification en amélioration continue donc si tu as un regard dessus je t'invite vraiment à y contribuer via l'outil discussion du wiki. Pour ce qui est des règles générales, peux tu m'envoyer une référence car sur le wiki je n'ai jamais vu de référence à des routes qui ne se termineraient pas brutalement. 
Les iles hautes de la Polynésie française ont globalement un développement du réseau en peigne du fait de la topographie notamment, ce cas de figure est donc inévitable. Après il yaurait l'option de mettre le début de la route en secondaire et la fin en tertiaire ou résidentielle mais ça me parait quand même peu souhaitable, il me semble que j'avais vu une discussion décourageant cela, il faudrait que je retrouve. 
Un autre point important à prendre en compte en Polynésie est l'aspect insulaire, chaque ile repositionne son propre référentiel car indépendant les uns des autres. Aussi une route secondaire à Tahiti ne desservira pas le même type de localité à l'échelle de la PF qu'à Moorea. Ce qui mène à des routes secondaires qui sont importante à l'échelle de l'ile mais qui ne desservent pas tant d'habitation que ça en comparatif à Tahiti. 
Ce qui me mène à la définition sur la hiérarchisation des routes sur le wiki : il fait appel à la taille des localités qu'elles desservent, mais ne parle pas de fin de route. 
A te lire,
mat (2026-02-27 06:45:11+00:00): En fait, c'est la définition même de "transit", par exemple https://www.le-dictionnaire.com/definition/transit : "(Transports) Fait de traverser une ville, une région, sans s’y arrêter."
Une route des réseaux tertiaires et au dessus est une route de transit, c'est à dire qu'on l'emprunte pour aller ailleurs, mais qui n'est pas la destination.
Violaine_Do (2026-02-27 18:56:18+00:00): Oui on est daccord sur la définition du mot, le sujet est que les définitions ne parlent pas de transit justement (a part l'interprétation fr) Voir ici :  https://wiki.openstreetmap.org/wiki/Key:highway  Si un lieu dans le wiki, officiel, le faisait transparaitre je veux bien que tu m'envoies la référence, merci!
Violaine_Do (2026-02-18 23:58:56+00:00): Bonjour Mat, As tu regarder les conventions de cartographies (en discussion) pour la Polynésie française avant de modifier le travail de la communauté locale? osm.wiki/FR:French_Polynesia/FR:French_Polynesia_tagging_guidelines#Routes Si oui merci de discuter directement sur la page avant de rétrograder la hiérarchisation faite. Le contexte polynésien est spécifique, les définitions auxquelles nous avons travaillées sont issues de près de dix années de travail avec des collègues urbanistes, des membres de l'administration compris. Merci par avance pour tes contributions constructives,
Violaine_Do (2026-02-19 01:23:07+00:00): Commentaire générique envoyé un peu vite, je te rejoins sur la qualification de la route de ce lotissement, je t'invite quand même à apporter tes commentaires sur le wiki pour faire évoluer la définition au besoin. A noter quand même que certains lotissements qui finissent sans issue sur Tahiti seront quand même en secondaire (cas avec plusieurs voies structurantes ou en boucle et desservant une quantité d'habitation notable à l'échelle de l'ile) Merci et bon mapping.
Bienson (2026-02-19 06:09:55+00:00): Und auch im vierten Versuch ist es immer noch nicht korrekt.

Und noch einmal:

https://wiki.openstreetmap.org/wiki/DE:Key:circumference?uselang=de

"Beispiel
circumference=2.3 beschreibt Stamm mit einem Umfang von 2,3 Metern"

Jetzt hast du "circumference=3,40" eingetragen.
NeisBot (2026-02-18 07:42:50+00:00): Hello, welcome and thank you for your contribution to OSM!

Your changeset was commented because your added description, note or slogan contain detailed text that may be interpreted as promotional or SEO-related. To ensure OSM remains neutral and focused on map data, I recommend keeping descriptions concise, factual, and free from marketing or promotional language.

⚠️️ Problematic element (limit 1):
https://osm.org/node/13575113608 v1

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Lake Svitava"
---
Na primjer, neutralnija i faktičnija verzija vašeg teksta mogla bi biti: "Jezeru Svitavu"
---
(Auto-translation)

#MapWithoutSpam
NeisRevert (2026-02-26 17:33:02+00:00): 🔄🤖 Partly reverted due to either a lack of response from the contributor or remaining promotional text by https://osm.org/changeset/179095481
(No visible changes after review)
CAM-Gerlach_Repair (2026-06-05 03:04:03+00:00): Fixed SEO spam name=* and phone=* formatting for Lake Tour Svitava POI in changeset 183671844

https://osm.org/changeset/183671844
Bienson (2026-02-19 06:12:09+00:00): Und auch nachdem ich es das zweite Mal klar und deutlich formuliert habe, nutzt du weiterhin "name=LB-025".
NeisBot (2026-02-18 07:57:45+00:00): Hello, welcome and thank you for your contribution to OSM!

Your changeset was commented because your added description, note or slogan contain detailed text that may be interpreted as promotional or SEO-related. To ensure OSM remains neutral and focused on map data, I recommend keeping descriptions concise, factual, and free from marketing or promotional language.

⚠️️ Problematic element (limit 1):
https://osm.org/node/13575073296 v3

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Tour operator office"
---
Zum Beispiel könnte eine neutralere und sachlichere Version deines Textes lauten: "Büro des Reiseveranstalters"
---
(Auto-translation)

#MapWithoutSpam
NeisReview (2026-02-26 17:33:08+00:00): 👍 Thank you for updating the element by https://osm.org/changeset/178713956
NeisBot (2026-02-18 08:00:40+00:00): Welcome, and thanks for your edits!

I noticed a few unintended crossings between roads and/or between roads and buildings in this changeset. This usually happens when geometry snaps incorrectly. Additionally, changes to tagging (e.g. modifying highway types or adding tags) can lead to unexpected crossings being detected afterwards.

In total, I detected 9 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/495011389 v4 | 8 crossings

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=178712622
NeisReview (2026-02-26 17:33:25+00:00): ✅ Should be fixed by 
https://osm.org/changeset/178759216
Dodko (2026-02-20 16:23:24+00:00): Treba pridať access=private a nie zbytočne písať poznámku to aplikácie nerozoznajú.
CAM-Gerlach_Repair (2026-06-20 23:53:22+00:00): Clean up and consolidate duplicate nodes/tags for SEO POIs in in changeset 184371667

https://osm.org/changeset/184371667
ChehrehBargi (2026-02-18 19:00:00+00:00): @masoudghorbany
You have also committed 11 incorrect changes today, related to using multiple tag information in the name tag. Your previous edits in this regard are as follows
178670826, 178671058, 178671110, 178679554, 178673226, 178670009, 178673092, 178673059, 178672997, 178672902, 178672856, 178672902, 178672819, 178668353, 178672325, 178670726, 178670646, 178670548, 178670427, 178670308, 178670112 , 178669930, 178707284