piebro/osm-data huggingface dataset:
haihaus (2026-02-18 21:44:48+00:00): Sorry about that ScrawnyMeowth1, thanks for fixing it for me!
yelisey90 (2026-02-13 22:40:22+00:00): reverted - Cheesefarm is at this location. Maybe Bambina is somewhere nearby?

https://www.openstreetmap.org/changeset/178524266
gurglypipe (2026-02-13 22:36:46+00:00): Hi, thanks for your attention to detail, but I’ve reverted this change because the walls were already correctly tagged as present but abandoned using a lifecycle prefix: https://wiki.openstreetmap.org/wiki/Lifecycle_prefix

Reverted as https://www.openstreetmap.org/changeset/178524173
JonLynch (2026-02-14 20:45:23+00:00): Thanks, I understand the semantic correctness of what you are saying. My motivation is more practical, this wall is used to help people navigate away from Piers Gill, a blackspot on Scafell Pike that has claimed many lives over the years. I am a member of the local mountain rescue team, and people are increasingly navigating with apps based on OSM data. Unfortunately most of these do not render walls with an abandoned prefix. As a follow up, what is the transition between wall and wall abandoned? Most of the walls high on the Lakeland fells are in some state of disrepair. Usually only the intake and lower walls are sheep proof.  It would be a shame to lose the walls from our maps in the name of semantic correctness.
gurglypipe (2026-02-23 10:20:16+00:00): Hiya, thanks for your reply and sorry for the slowness of mine.

Firstly, thanks for taking the time to try and improve the map to help people stay out of trouble. It’s good to have more local knowledge in the map :)

I think the correct fix here is for those navigation apps to render walls with different lifecycle prefixes, in much the same way that Harveys render abandoned walls in grey (rather than black).

Do you know which apps people are using most commonly? It would be worth one of us approaching them to improve their rendering of the data.

In terms of getting abandoned walls to render on openstreetmap.org itself, that would need an issue report to be filed here: https://github.com/openstreetmap-carto/openstreetmap-carto/issues

The difference between in-use, disused and abandoned walls is a bit of a matter of personal judgement. I’d say that ones which are no longer sheep-proof should be tagged as disused or abandoned. Maybe disused if they are mostly whole but with some fallen down sections, and abandoned if they’re worse than that. ruins:barrier=wall if they’re just a low mound of rock or have been robbed out.

That said, sheep can get over anything if they want to!
NeisBot (2026-02-13 22:16:17+00:00): 🌍 Welcome to OSM, dittostein.
Thanks for contributing!

To make collaboration easier and help others understand your edits, it’s best to add a short description of the changes you made. Clear comments help the community follow your work and provide better feedback. You can find tips on writing good comments here[1].

✅ Here is a sample comment based on your map edits: "Added waste baskets, benches"
---
[1] https://osm.org/wiki/Good_changeset_comments

#HelpfulComment #NoComment
mueschel (2026-02-15 10:56:15+00:00): Hi,
what does "stop_point" mean? This tag isn't used in nay other place. I suspect 'ref' or some 'ref:XYZ' would be appropriate.
Snusmumriken (2026-02-15 11:13:46+00:00): I'm afraid I don't understand your question. I don't see a stop_point tag anywhere in changeset.
mueschel (2026-02-15 11:17:47+00:00): Sorry, it wasn't you - the tag was added here:
https://www.openstreetmap.org/changeset/178355758
woodpeck_repair (2026-02-13 21:36:24+00:00): This changeset reverts some or all edits made in changesets 149419217, 149507618, 149872085, 150116891, 151632068, 152844898, 153329674, 153737699, 153827582, 155654034, 156392723, 157331546, 159106865, 159356988, 159703882, 160083896, 160596126, 162295638, 163164145, 163341633, 163734062, 164525058, 164683384, 164777892, 165254886, 166312991, 167183284, 167209199, 167224592, 167236842, 167590918, 168181859, 170110123, 170796956, 171452535, 172455950, 172603358, 172897642, 173493020, 174449068, 174757965, 174954577, 175109468, 175596037, 175616494, 175874186, 176171620, 176647242, 176760730, 177016840, 178181274, 178270444, 178343096, 178377216, 178454979, 178502831.
NeisBot (2026-02-13 21:45: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 7 potential crossings.

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

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=178522966
NeisReview (2026-02-22 05:33:49+00:00): ✅ Should be fixed by 
https://osm.org/changeset/178523055
gurglypipe (2026-02-13 22:40:54+00:00): Should this one have motor_vehicle=private on it, if only authorised (e.g. council) vehicles are allowed on it?
iMacThere4iAm (2026-02-14 10:18:19+00:00): I think so. There are no signs but it's clearly part of the park, not a public road. https://www.openstreetmap.org/changeset/178537427
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/178523002
gurglypipe (2026-02-23 10:09:10+00:00): Super, thanks for checking :)
dcapillae (2026-02-13 22:45:20+00:00): Hola.

Este conjunto de cambios fue revertido.

Cada contenedor de reciclaje se destina a un tipo de residuo diferente, no se deben mezclar. Se mapean como un nodo independiente para no mezclar tipos de residuos diferentes en un mismo contenedor: un contenedor --> un nodo.

Hay que asegurarse de que no haya ya un contenedor en el mapa para el tipo de residuo que deseamos añadir. Normalmente suelen estar cerca unos de otros.

Contenedor azul (papel y cartón):recycling:paper=yesrecycling:magazines=yesrecycling:cardboard=yesrecycling:newspaper=yesrecycling:paper_packaging=yes

Contenedor amarillo (latas, envases y botellas de plástico):recycling:plastic_packaging=yesrecycling:plastic_bottles=yesrecycling:cans=yes

Contenedor verde (botellas de cristal):recycling:glass_bottles=yes

Contenedor marrón (restos orgánicos)Respecto a los contenedores marrones (residuos orgánicos), dado que aceptan tanto restos de comida como restos vegetales (flores u hojarasca) sería conveniente etiquetarlos como «recycling:organic=yes». https://www.openstreetmap.org/user/dcapillae/diary/400818

Gracias por su colaboración.

Atentamente,Daniel Capilla
NeisBot (2026-02-13 21: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 8 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/193407939 v5 | 6 crossings

⚠️ Dragged Nodes (max 3):
https://osm.org/node/6602154235 v2
https://osm.org/node/2039163572 v4
https://osm.org/node/2039163568 v4

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=178523055
SzymonH (2026-02-14 13:54:29+00:00): Cześć! Dzięki za edycję i dodanie aktualnej informacji o wiacie przystankowej. Zniknął jednak tag dotyczący wypustek na przystanku (tactile_paving) - czy coś się tam zmieniło w tej kwestii? Jeżeli nie to proszę o ponowne dodanie tego tagu - robię jeden standard tagowania przystanków w ramach sieci ZTM Kielce i chciałbym zachować porządek.
bxl-forever (2026-02-13 22:08:25+00:00): Hello,

Ko-lab has been on the map since 2021: https://www.openstreetmap.org/node/9169779645
There is no need to create a duplicate point for this. We will revert your edit.
Sébastien Pi (2026-02-17 22:20:30+00:00): Same for Aroma: https://www.openstreetmap.org/node/8022017157
Old POI moved to new location, delete this new one.
Sébastien Pi (2026-02-17 22:28:38+00:00): Also, I did not notice. But please, do not create such a huge changeset for just two nodes: https://wiki.openstreetmap.org/wiki/Changeset
It would have been better to create two changeset here.

Take care, I have already see other users create duplicates with OrganicMap. I have tried a bit CoMap (which is a fork). you can not move a POI. So it is better to just create a note in such situation. So, someone (or you) will be able to update/move existing POI with iD (or another real editor).

Kind regards
Bullitt D Bourbon (2026-02-20 09:24:53+00:00): Hello, l used Organic Maps, and this Changeset is what the app created. It seems like you all assert that/  feel like it's a problem. Why not talk to Organic Maps. Until then people can stop making edits on Organic Maps, right? Peace
Sébastien Pi (2026-02-20 11:34:58+00:00): Hi,

Organic Maps does create a changeset alone :). It is ok to create changesets with OM or other tools. And there is many cases where it is working well.
It is like saying for a car: it is going at 200km/h, too fast. Blame the car, not the driver.

Note: I do not blame you. Just say that people must be carreful. Most of mobile apps have limitation. It is impossible to move a POI with them. But create a duplicate is not the right solution.
In theses cases, where there is some technical limitations, it is better to just create a note. So, someone (or you) will handle it later.

And thank you for your contribution.
Bullitt D Bourbon (2026-02-20 20:24:09+00:00): Hey l see how the problem is place solidly on me. Therefore l can just uninstall organic maps
Sébastien Pi (2026-02-20 22:04:02+00:00): As I said, I do not blame you. Lots of people can make mistake (me too) and it is not wrong to make mistake.
My comments and @bxl-forever one's are just to help you to do better the next time. Not to discourage you.
Bullitt D Bourbon (2026-02-22 13:59:27+00:00): Well seems some people can never make a statement without troubling owners of the project to correct THEM, what is wrong with THEM.
Software is never wrong.
It's a great way to deter unsolicited participation. Thanks though.

l noticed the Microsoft Open Maps table at Fosdem, l wonder. This conversation is over.
marc__marc (2026-02-20 19:04:21+00:00): Bonjour,
merci pour cet ajout.
n'hésites pas à renseigner le no de téléphone au format international +32
Cordialement,
Marc
felipeeugenio (2026-02-14 13:11:27+00:00): Estimado. Esto es un proyecto en serio. Sus ediciones están siendo reversadas apenas las hace. Por favor desistir de ediciones vandálicas.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/178523468
burrscurr (2026-02-24 18:50:50+00:00): Hallo gasdriver_de,

wenn ich es richtig sehe, hast du die Querung https://www.openstreetmap.org/node/8767403622/history/5 von crossing=unmarked zu crossing=island geändert. crossing=island wird mittlerweile nicht mehr verwendet, stattdessen wird crossing:island=yes benutzt, um nicht mehrere Eigenschaften im crossing-Schlüssel zu vermischen. Kannst du bitte entweder crossing=island entfernen und stattdessen crossing:island=yes + crossing:markings=yes/no/... + crossing:signals=yes/no setzen ODER alternativ das vorherige Tagging crossing=umarked wiederherstellen (= nicht-signalisierte Querung ohne Markierungen)?

Das Tagging von Crossings ist leider manchmal (unnötig) kompliziert...

VG
burrscurr
Rainero (2026-03-15 18:00:59+00:00): Revert mit changeset/179911444
(unzulässige Quelle)
JonLynch (2026-02-14 20:45:36+00:00): Thanks, I understand the semantic correctness of what you are saying. My motivation is more practical, this wall is used to help people navigate away from Piers Gill, a blackspot on Scafell Pike that has claimed many lives over the years. I am a member of the local mountain rescue team, and people are increasingly navigating with apps based on OSM data. Unfortunately most of these do not render walls with an abandoned prefix. As a follow up, what is the transition between wall and wall abandoned? Most of the walls high on the Lakeland fells are in some state of disrepair. Usually only the intake and lower walls are sheep proof. It would be a shame to lose the walls from our maps in the name of semantic correctness.
gurglypipe (2026-02-23 10:20:21+00:00): (Replied on https://www.openstreetmap.org/changeset/178522105, let’s keep discussion there)
felipeeugenio (2026-02-14 13:57:13+00:00): Hola Tomás. No usamos nombres para hacer descripciones, solo nombres oficiales.

saludos y gracias
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/178524234
NeisBot (2026-02-13 22:45:42+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/13546540311 v2

Could you please revise your text accordingly?

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

#MapWithoutSpam
NeisRevert (2026-02-22 05:33:44+00:00): 🔄🤖 Partly reverted due to either a lack of response from the contributor or remaining promotional text by https://osm.org/changeset/178885365
(No visible changes after review)
eggie (2026-02-14 07:28:00+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privebericht.
MVG,
Eggie
Namens de OSM Community
NeisBot (2026-02-13 22:48:43+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/13546679129 v2

Could you please revise your text accordingly?

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

#MapWithoutSpam
NeisRevert (2026-02-22 05:33:44+00:00): 🔄🤖 Partly reverted due to either a lack of response from the contributor or remaining promotional text by https://osm.org/changeset/178885366
(No visible changes after review)
AurélienQ (2026-06-12 13:35:50+00:00): Hello,
Je me permets de te faire remarquer qu'en complétant ce bâtiment, tu as simplement... enlevé le tag principal de l'objet 🙃 : building=*
Je l'ai donc remis.
osmviborg (2026-02-14 06:06:13+00:00): Please touch the address nodes. Addresses in Denmark are imported from an official database and maintained automatically. Thank You.
osmviborg (2026-02-14 06:47:18+00:00): Please 'don't' touch 🤭
vojtechzaboril (2026-02-14 09:01:50+00:00): Hi, thanks for the info. What will happen, will it make another node in next import? If yes, I think that the import tool should check if the address node exists.
Or please explain the reason in more details. Thanks
V
osmviborg (2026-02-14 09:09:35+00:00): Moved back to where it belongs.
Further reading: https://lgms.nl/p/osm/cached-wiki/?search=autoaws&title=Special%3ASearch&go=Go#How_to_map
stasiu512 (2026-02-13 23:27:16+00:00): Korekta zamknięcia drogi.
Norbert Dichter (2026-02-14 11:17:00+00:00): Hello, thanks for mapping and welcome to HOT. Thank you for your contribution. The buildings you mapped are well done as to their location. But pay attention to the squareness of the corners. Always draw buildings as square and precise as you can. Then add the Building feature type. And last, right click it and click the square icon. Or just hit the Q-key.
Also please keep in mind: many buildings are very close but do not actually touch each other, try to map them close to each other without letting them connect or share nodes with each other, roads, or residential area outlines. In the iD web editor, holding down the "alt" key will keep nodes from "snapping" to each other and accidentally connecting.  Thanks so much for your contribution, Norbert 'Nodi' Dichter, HOT validator.
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.org/changesets/178525240
TrickyFoxy (2026-03-04 10:29:00+00:00): Здесь действительно станция зарядки или просто подстанция?
Frame&Focus (2026-06-06 11:26:35+00:00): Thank you!
NeisBot (2026-02-14 01:21: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 26 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/1474752592 v2 | 25 crossings

⚠️ Dragged Nodes (max 3):
https://osm.org/node/13529158915 v2
https://osm.org/node/13529158917 v2
https://osm.org/node/13529158918 v2

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=178526767
Warin61 (2026-04-16 00:28:12+00:00): Hi
Relation 20215780 trees .. had a shared segment as found by 
https://tools.geofabrik.de/osmi/?view=areas&lon=177.59345&lat=-41.79260&zoom=6&baselayer=Geofabrik%20Standard&overlays=duplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways%2Cduplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways

I have corrected this ... 
and simplified from many ways to 2 ways - one outer and one inner.
AlwynWellington (2026-04-16 09:49:53+00:00): hi and regret I am away from the country at present.
And unable to make any considered comments on my phone.

Kia ora, Alwyn
NeisBot (2026-02-14 01:54:48+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/65441443 v14

Could you please revise your text accordingly?

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

#MapWithoutSpam
NeisRevert (2026-02-22 05:33:45+00:00): 🔄🤖 Partly reverted due to either a lack of response from the contributor or remaining promotional text by https://osm.org/changeset/178885367
(Restore previous tags)
NeisBot (2026-02-14 01:57:43+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/65547633 v10

Could you please revise your text accordingly?

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

#MapWithoutSpam
NeisRevert (2026-02-22 05:33:45+00:00): 🔄🤖 Partly reverted due to either a lack of response from the contributor or remaining promotional text by https://osm.org/changeset/178885368
(Restore previous tags)
NeisBot (2026-02-14 02:18: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 7 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/683237518 v5 | 7 crossings

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=178527442
NeisBot (2026-02-14 02:42: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 7 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/683237518 v5 | 7 crossings

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

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=178527695
NeisBot (2026-02-14 05:06:24+00:00): 🌍 Welcome to OSM, 沒有名字.
Thanks for contributing!

To make collaboration easier and help others understand your edits, it’s best to add a short description of the changes you made. Clear comments help the community follow your work and provide better feedback. You can find tips on writing good comments here[1].

✅ Here is a sample comment based on your map edits: "Adjusted node positions"
---
[1] https://osm.org/wiki/Good_changeset_comments

#HelpfulComment #NoComment
NeisBot (2026-02-14 04:54: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 20 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/431231965 v5 | 10 crossings
https://osm.org/way/431231975 v4 | 9 crossings

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

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=178529521
nevw (2026-02-14 06:17:49+00:00): Hi, I think Aldi would be better tagged as a supermarket
https://wiki.openstreetmap.org/wiki/Tag:shop%3Dsupermarket
Also addr:street needs to be added to accompany the housenumber address
nevw (2026-02-14 06:19:02+00:00): I see the addr:street is present
FigTree3184 (2026-02-14 06:25:50+00:00): Thanks for feedback.   My first attempt at this.
nevw (2026-02-14 07:40:06+00:00): Actually it is already mapped.
 so I deleted your duplicate.
https://www.openstreetmap.org/way/422548452#map=19/-28.073641/153.444605&layers=D
Sorry I didn't check properly earlier.
nevw (2026-02-14 07:41:35+00:00): Link without the blue lines...
https://www.openstreetmap.org/way/422548452#map=19/-28.073641/153.444269
NeisBot (2026-02-14 05:54: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 11 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/1338425765 v1 | 5 crossings
https://osm.org/way/1338425756 v1 | 5 crossings

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

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=178530501
CAM-Gerlach_Repair (2026-06-21 20:12:58+00:00): Reverted adding SEO spam POI with advertising/malformed tags and source=* of Google Maps, which is not allowed by both OSM and Google policies (see https://osm.wiki/Google ), in changeset 184404860

https://osm.org/changeset/184404860