piebro/osm-data huggingface dataset:
eggie (2025-05-19 19:11:24+00:00): https://wiki.openstreetmap.org/wiki/File:Praha,_Kbely_072.jpg

https://wiki.openstreetmap.org/wiki/Tag:traffic_calming%3Dtable

Als bovenstaand aangepast.
gr eggie
Rodrigo Rega (2025-05-25 14:30:59+00:00): Hola.

El comentario de este conjunto de cambios no es lo suficientemente descriptivo para que el resto de usuarios se hagan una idea de cuáles han sido los elementos que se han editado. Por favor, consulta la siguiente página para saber como hacer comentarios que faciliten el trabajo de revisión de ediciones: https://wiki.openstreetmap.org/wiki/ES:Buenos_comentarios_en_conjuntos_de_cambios

Gracias por tus aportes a OpenStreetMap.

Un saludo.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/166492855
Anónimo785612 (2025-05-25 17:29:51+00:00): 👍
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/166492855
somehundred (2025-05-19 19:52:37+00:00): Iepriekšējais vārds nav pilnīgi nepareizs, jo tas apzīmē teritoriju ap Bastejkalnu. Pareizi būtu, ja Bastejkalna teritorija tiku atdalīta no šī laukuma un nosaukta kā "Bastejkalna parks".
Mister_R2 (2025-05-20 04:55:55+00:00): Nu jā, bet es arī par to tieši domāju, ka bija bastejkalna daļa ar to vārdu tikmēr atlikušais ar šo. Bet es īsti nezināju kurš no abiem ir labāk derams, tad es apskatījos, ka wikipēdijā ir Kanālmalas apstādījumi, ne Bastejkalna parks.

https://lv.wikipedia.org/wiki/Kan%C4%81lmalas_apst%C4%81d%C4%ABjumi

Esmu atvērts uz abiem nosaukumiem.
Colbertson (2025-05-20 07:15:12+00:00): Pats bastejkalns atzīmēts gan kā place=locality un natural=peak
https://www.wikidata.org/wiki/Q810581
locality ar jocīgu wikidatu
somehundred (2025-05-21 14:12:36+00:00): Es saku, ka Bastejkalna teritoriju var nodēvēt kā "Bastejkalna parks", bet pārējo teritoriju - "Kanālmalas apstādījumi". Abi ir pareizi.
Mister_R2 (2025-05-22 13:09:35+00:00): Es piekritīšu par to, ka būtu jāsadala parks uz Bastejkalnu un Kanālmalu.
os-emmer (2025-06-12 17:06:50+00:00): Hallo Christoph Lotz,

du hast hier
https://www.openstreetmap.org/node/9202798957
und in der Umgebung addr:country=UG gesetzt. Bist du dir sicher, dass das stimmt? Laut Grenzverlauf liegen einige der Adressen nicht in Uganda sondern in der Demokratischen Republik Kongo.
War addr:country=Uganda vielleicht nicht nur ein Tippfehler, sondern ein inhaltlicher Fehler?
NorthCrab_upload (2025-05-19 19:41:01+00:00): 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.

"Pątnów":
https://www.openstreetmap.org/node/12849577899
https://www.openstreetmap.org/node/12849577934
https://www.openstreetmap.org/node/12849578016

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! 🦀
Minh Nguyen (2025-05-19 19:38:23+00:00): Addresses are from https://gis.countyofnapa.org/portal/apps/webappviewer/index.html?id=0bbafe490c58430da719ff851c78b7fa
MarcoR (2025-05-19 21:42:18+00:00): Ciao Francesco,
visto che stai aggiungendo un po' di civici ti segnalo che una delle poche regole che la comunità italiana è riuscita recentemente a stabilire è quella di specificare l'esponente di un indirizzo senza separatore e tutto in minuscolo, ad es. 123ter invece di 123/TER (vedi https://wiki.openstreetmap.org/wiki/IT:Addresses); ambasciator non porta pena :)

Buon mapping,
Marco
Francesco Niccolini (2025-06-14 15:01:19+00:00): Ciao Marco,

grazie della segnalazione.
Provvedo subito alla correzione.

Buon mapping,
Francesco
René84828 (2025-07-18 21:32:36+00:00): Ist das neu, dass der Vorauer Schwaig Trail eine Einbahn ist? Letztes Jahr war das noch nicht so. Auf den Ersten Blick kann ich auch auf der Homepage der Wexltrails nichts finden. Zumindest zwei Touren bei denen man auf diesem Trail zum Gipfel fährt sind dort zu finden. https://www.wexltrails.at/de/deine-wexl-trails/trailinfo/touren/gipfeltour-ueber-die-vorauer-schwaig
gt3400 (2025-07-19 09:42:40+00:00): Ich sehe, das der ein cycleway ist, was wohl irreführend ist. Wenn ich das war, dann ist da was schief gelaufen. Ausserdem sehe ich da auch 2 MTB Relationen? Sollte wohl nur eine sein. Kannst es gerne ausbessern. Ich kann es mir auch ansehen wenn ich wieder am Computer bin.
gt3400 (2025-07-19 11:30:47+00:00): So ich habe das jetzt behoben und das leisure=track auch entfernt, da es laut Doku für Bahnen in Sportzentren gedacht ist. Das mit der Einbahn weiß ich jetzt auch nicht sicher. Ich hätte gedacht es ist nur bergab.
gt3400 (2025-07-19 11:33:05+00:00): Ja, die Homepage der Wexltrails ist da ziemlich eindeutig. Habe das oneway ebenfalls entfernt. Danke.
eggie (2025-05-19 20:27:23+00:00): Welkom bij OSM Marieke,
Waarom source=psychologist
Moet dat niet zijn 
Tag:healthcare=psychotherapist

MVG
eggie
eggie (2025-05-19 20:31:11+00:00): De tagging heb ik aangepast zodat het ook rendert op de kaart. website toegevoegd.
Gr eggie
Psycholoog Marieke (2025-05-20 05:05:11+00:00): Dank je! Is er ook een optie "psychologist"? Een psychotherapist heeft nog 6 jaar langer gestudeerd dan ik :-).
eggie (2025-05-20 05:18:02+00:00): Goedemorgen... Ik heb het aangepast naar psychologist.
Verder algemeen office=therapist toegevoegd voor rendering.
Evt kun je phone=+31......  toevoegen.

MVG
eggie
Mateusz Konieczny (2026-02-07 13:54:42+00:00): Hello! https://www.openstreetmap.org/node/12849577745/history has addr:flats = House that was added in this edit
info that something is built as house goes to building=house, not into address field. Please, help with this cleanup
gymate (2025-05-19 20:42:53+00:00): Excuse me for reverting the operator values—I'll change them back shortly.

(See https://github.com/KAMI911/osm_poi_matchmaker/pull/137 for the underlying reason.)
gymate (2025-05-30 15:15:12+00:00): I've corrected them: https://www.openstreetmap.org/changeset/166977301
habi (2026-05-18 07:09:15+00:00): Hey Höisi
Du bedienst Organic Maps falsch.
Das Restaurant heisst "Il Boccone" und nicht "Il Boccone ital. Restaurant Konstanz".
Bitte mach *keine* solchen Änderungen in OpenStreetMap.
Gruss,
habi
Sanniu (2025-05-20 12:53:13+00:00): Hi, the https://www.openstreetmap.org/way/1388090494 - is it roundabout?
The_Nickname (2025-05-20 07:58:10+00:00): Danke!
ilias_ (2025-05-20 00:19:01+00:00): Reverted, please take the time to learn OSM before changing and administrative boundary to a cliff, thank you.
AndyB_66 (2025-10-06 15:44:07+00:00): https://wiki.openstreetmap.org/wiki/Pl:Dobre_komentarze_zestawu_zmian
Kinsio (2025-05-21 00:18:29+00:00): Hi Comino, thank you for your contributions to OpenStreetMap. I noticed that this changeset is missing a source=* tag, which makes it difficult for other mappers to easily determine the reliability of the information you're using to make edits. In the future, please be sure to use the source=* tag to document where you got your information. You can find more details about the source=* tag here: https://osm.wiki/Key:source.

Additionally, you seem to be part of the BTC Map organized editing project; please add the #btcmap hashtag to the changeset comment of all changesets you submit for this project, in accordance with the Organized Editing Guidelines <https://osmfoundation.org/wiki/Organised_Editing_Guidelines#Edits_to_the_map> and BTC Map's contributor instructions <https://gitea.btcmap.org/teambtcmap/btcmap-general/wiki/Tagging-Merchants#changeset-comments>.

If you have any questions, feel free to reach out and I'll do my best to help.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/166495297
NorthCrab_upload (2025-05-19 20:31:00+00:00): Zauważyłem, że Twoja zmiana zawiera nadmiarowe informacje. Przygotowałem listę obiektów do poprawy oraz dodatkowe informacje:

Paczkomat nie powinien mieć nazwy.
https://www.openstreetmap.org/node/12848273066

Pozdrawiam! 🦀
NeisBot (2025-05-19 20:28:30+00:00): Hello Juanin23, welcome to OSM, and thank you for your contributions!

I've taken a look at your recent edits and wanted to discuss a few discrepancies I noticed regarding the surrounding environmental features. Specifically, the locations in your edits don't seem to align with the typical geographical characteristics expected in that area. Here are some (max 10) relevant links to the edits:
https://osm.org/way/1388092789

Could you please take a look?
Looking forward to your response.

PS: I have also sent this message through the OSM messaging system for your convenience.

#Somewhere
---
https://resultmaps.neis-one.org/osm-change-viz?c=166495679
NeisReview (2025-05-20 10:54:25+00:00): Reverted by https://www.openstreetmap.org/changeset/166517813
SD Mapman (2026-02-13 20:18:04+00:00): Are there actual plans to connect the N-66 gap in Louisville? Last time I was there the dead-end spur east of N-50 didn't look like it would ever be used as a state highway again.
Stretch Longfellow (2026-02-13 21:36:08+00:00): Yes, work has begun! About time.
eggie (2025-05-20 05:23:10+00:00): Welkom bij OSM,
Wanneer je het adres verandert gaat niet het bedrijf naar de nieuwe locatie.
Methode is adresnode leegmaken en adres intact houden en op de nieuwe locatie de adresnode opzoeken en weer aanvullen.

MVG
eggie
eggie (2025-05-20 05:25:30+00:00): Het oude adres is inmiddels hersteld door een medemapper.
MVG
eggie
123pc (2025-05-21 12:37:19+00:00): ah ok bedankt
chris66 (2025-08-19 20:50:32+00:00): Nummern für die Säule am Hallenbad Rohrkamp:

DE*GWE*EAC1105
EAC1106
geomaniX (2025-08-20 10:55:25+00:00): Perfekt, Danke.
Habe sie hinzugefügt.
geomaniX (2025-08-20 10:55:41+00:00): https://www.openstreetmap.org/changeset/170718420
Sylabowy Kot (2025-05-19 22:08:56+00:00): W końcu :D
ul. Fangora mapowałem rok temu z poziomu iD, z kolei sam plac w JOSM z ostrymi jak żyleta podkładami. Jest różnica. 
W ramach tego changesetu nie ruszałem jeszcze obszaru trybuny i nowego trawniczka przed nią, bo ta i tak otrzymała nową formę, która chyba jeszcze nie została zaewidencjonowana. 
Południowe ogrodzenie TR też raczej do ostatecznej poprawki chyba dopiero po otwarciu placu.
Glassman (2025-05-19 23:36:51+00:00): #TIP: connect the footway to a road to allow multimodal routing. I went ahead and made the change to give an example.
Ranger Kel (2025-05-20 23:19:39+00:00): cool thank you!
skquinn (2025-05-19 23:25:27+00:00): Comment should be just "add buildings", remainder was autocompleted by mistake
Merna_mahmoud (2025-05-21 13:53:53+00:00): Hello Sandalss,
Thank you for your contribution to OpenStreetMap in Oman.
According to our information, the correct way to the road network for the branches for the street  shall be of the same road classification, but I noticed you changed the classification of some streets to link
Examples of streets:
https://www.openstreetmap.org/way/498352593
https://www.openstreetmap.org/way/798968764
https://www.openstreetmap.org/way/798968781
Do you have a specific concept to implement in the country?
Regards,
Merna_mahmoud
Sandalss (2025-05-22 01:17:29+00:00): Hello,

I've tried my best to interpret information from the wiki for highway tags. From what I've understood trunk roads are used for high-important or high-performance highways and A13 connects the biggest city in the governorate of Musandam, Khasab, to the UAE, Ras al Khaimah, while also passing by Bukha which is one of the four provinces in Musandam and passing many villages such as Harf & Qada. All of these factors led me to believe that the highway is high-important as it's the most important highway in the governorate (until the new Dibba - Lima - Khasab highway is finished). If I am misunderstanding the meaning of trunk roads, please let me know.
Merna_mahmoud (2025-05-22 13:59:57+00:00): Hello Sandalss,
 Thank you for your quick response
This is a link to a wiki page that explains how to use the classification for links
see:https://wiki.openstreetmap.org/wiki/Highway_link
Therefore, when the road has branches, it is preferable for them to be of the same classification as the main road, so that the road classifications are consistent with the road network.
Examples :
https://www.openstreetmap.org/way 333615073
https://www.openstreetmap.org/way 982878313
https://www.openstreetmap.org/way 1012680223
While we use links when it is a transition from one street to another (connecting two streets )
Examples :
https://www.openstreetmap.org/way 982878311
https://www.openstreetmap.org/way 982878312
For these reasons, all streets were modified, such as the one mentioned above.
Happy to connect with you
Regards,
Merna_mahmoud
santamariense (2025-05-21 12:21:55+00:00): Comentário não condiz com a edição que foi feita. Mudanças não foram discutidas com a comunidade, haja visto que é um assunto delicado, sempre alvo de discussões.
Mateusz Konieczny (2025-12-11 16:56:21+00:00): Hello! https://www.openstreetmap.org/node/3012311759/history has amenity = convenience that was added in this edit
What was meant by amenity=convenience? Is it a convenience shop? Then shop=convenience is likely a better tagging, see https://wiki.openstreetmap.org/wiki/Tag:shop=convenience .
Mateusz Konieczny (2026-02-09 12:06:59+00:00): Hello! https://www.openstreetmap.org/node/12849844601/history has flag:type = commercial that was added in this edit
what was meant by flag:type=commercial ? How it differs from flag:type=advertising ?
diamondarmorsteve (2026-06-09 18:27:02+00:00): Bridgewater was most likely tagged place=town due to its size and economic importance, not its official designation. This sort of "official designation" should only go on the relation for the city, not the place node. The boundary relation represents the local government's boundaries. The place node represents a "populated place", which is a separate thing from a municipality.

I have retagged Bridgewater as a town due to its average population for a Boston suburb; additionally, it is not a major retail/business hub, only a secondary one.
RDreher (2026-06-09 19:08:05+00:00): The convention of using the terms "city, town, village" etc in a way idiosyncratic to some weird niche field of geography rather than in ways meaningful to the local social and political conventions of said places and the people who call them home, is utterly idiotic. The insistence on this imperious one-size fits all approach has long ago driven me away from contributing to this community though, so do whatever the heck you want. Call Bridgewater a hamlet or a deserted island for all I care. Actual people who actually know places like Bridgewater first hand have too much of a life to care about this stupid map. By the way, all the roads around the collage are out of date, lacking the annoying barriers that have been put up on just certain sides of the road to prevent through traffic leaving the train station or something. Since you seem to know so much about Bridgewater, why don't you update those?
radiotrefoil (2025-11-02 12:05:08+00:00): Hi Stephen, do you know if the construction way/1388119671 is completed yet?
MxxCon (2025-05-27 15:12:02+00:00): Hello.
If this is a driveway then it should just be updated as such, rather than outright deleted.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/166501799
Allison P (2025-05-20 02:33:49+00:00): When was the parking lot torn down?
StreetSurveyor (2025-05-20 02:42:03+00:00): The parking spaces are to the left of the street.
NeisBot (2025-05-20 02:53:35+00:00): Hi jesseive, welcome to OSM!

Thank you for your contributions to the map. I have reviewed your recent edits and noticed that 97% of the changes in this set involve deletions, including:
- 1 building(s)
- 3 natural(s)
- 2 landuse(')

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

Looking forward to your response.

PS: I have also sent this message through the OSM messaging system for your convenience.

#DeletionsCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=166502787
aharvey (2025-05-20 03:24:25+00:00): This is a 6 story office building, I would be surprised if a small nutritionist business took up the whole building. The street level imagery indicates there is likely multiple tenants here. If you have office space here best to just add a node within the building, rather than on the building.

Further your website https://www.rosiewareclinicalnutrition.com.au/services lists no office address and says all services are online/phone only "I am currently only offering online consultations within Australia.", so I'm not sure adding this here is best.

Based on this I'll remove the tags from the building.
ChaireMobiliteKaligrafy (2025-05-20 10:34:24+00:00): Bonjour! Merci pour vos ajouts! Pour le nombre de voies, utilisez mettre un nombre entier. Pour spécifier la largeur, utilisez plutôt le tag width.

Merci!
b-jazz (2025-05-21 04:29:31+00:00): RE: https://www.openstreetmap.org/way/1388134712

Please don't use the "lollipop" style of mapping golf course elements as you've done in the URL above. You need to create proper multipolygon relations in order to map features like roughs/bunkers that are within other features like fairways. Please see https://osm.wiki/wiki/Tag:leisure%3Dgolf_course#Common_mapping_pitfalls and https://osm.wiki/wiki/Relation:multipolygon for help in understanding how to map this situation. If those aren't clear, please let me know and I'll help explain them further. Thanks.
Golferboy (2025-05-21 14:22:54+00:00): Hi B-Jazz. I did need to lollipop those features because I needed them to be perfectly accurate for me to import them into a golf simulator and anytime relations are used in OSM those features don't show up inside the simulator. Since I am now done using these features I am perfectly okay with deleting the ones that are considered to be "lollipopped." I will go around and delete some of the ones I think are lollipopped, feel free to let me know if I missed any.
Allison P (2025-05-21 20:50:21+00:00): Don't lollipop features in the first place. The solution to flaws in your golf tool is not to damage data quality for everyone else for any length of time.
Golferboy (2025-05-21 21:33:33+00:00): As I said before. I do need to lollipop some things in order for the tool to pick it up. I'm not the one who created the tool so I don't have any control over changing it so it can accept data with relations. I can delete any features that are lollipopped after I have downloaded the data I need to make the "data quality better." But saying "just don't lollipop things" doesn't help me. If there's another way for me to spline those features without having to use relations. Feel free to let me know, otherwise, I'll move on and in the future I will delete any lollipopped areas after I'm done with them.
Thank you for your time.
Allison P (2025-05-21 21:41:01+00:00): We have long understood the flaw in the software you use for course design. Have the developer fix the tool instead of making wrong edits to the map. OSM doesn't use splines, but polygons, by the way. Knowingly making wrong edits to the map is vandalism. I will ask you just once to under no circumstances add "lollipops" to the map. I am happy to have any number of other users and/or mods reiterate the same if you won't take it from me.
Golferboy (2025-05-21 21:48:26+00:00): Is there some way of creating polygons of those features without having to use relations? I know this is a very large problem in the OSM community and I would love to be able to find a solution that satisfies both sides.
b-jazz (2025-05-22 02:47:48+00:00): Hi Golferboy,

We are aware that there are third-party applications out there that don't work correctly. You need to understand that OpenStreetMap is a *massive* community with thousands of different tools and those tools need to follow the rules set out by OSM, not the other way around. Just imagine if I used a tool that had a bug and could only handle 5 nodes to define a fairway, so I started drawing rectangles and told everyone else to deal with my bug and that I'll eventually get around to cleaning it up. You shouldn't be saving these workaround drawings at all. 

For starters, you might want add your voice to the pull request (software fix) that was implemented 2 months ago but has yet to be incorporated and released. This will most likely fix your problem, but you need to get your tool's developer to give it some attention.

If you continue to create lollipops, the OSM data integrity group will probably start locking you out of your account until you can follow the same rules everyone else follows. None of us want that. We want to see great contributions continue to be added to the map. Everyone wins.
Golferboy (2025-05-22 14:07:51+00:00): Hi b-jazz. 
I will try to advocate for the tool to be updated. Unfortunately, I seem to be one of the only people in my community interested in fixing this problem, and our community is just as massive as yours. And the tool was made by one person who I am not close to since I am fairly new to this community. Again I will try my hardest for this change to be made, since like you, I want OSM to look the best it can be. 

If I may be so bold, no one has ever told me why lollipopping is bad. I understand very well that it is bad, but every person I've heard, whether from my community or yours has only said that it's bad. Why is it so bad? What exactly does it break in OSM for it to be considered bad?

I do want to continue to be a helpful part of the OSM community and all I ask is for a small amount of leniency that I am trying to be as rule-abiding as I possibly can. Even before this interaction I have been trying to make as few lollipops as possible while still being able to get the data I need and trying to fix them afterwards. I also would like to mention that I have fixed the area in question of anything that even remotely resembles a lollipop. I understand that this is probably not enough for you but all I can promise to do is to create as few lollipops as I can and as you say, take the "Eventually fixing them," out of the picture. And fix them as soon as I have exported the data I need. 

I understand this is probably not enough for you, and again all I ask is for a small amount of leniency until such a time as the tool has been changed. I would like to finally add that I am not one of the people you should be after since I am someone who genuinely cares about the state of this issue and I'm not one of those people who leaves awful lollipopping edits lying around. I have even encountered some of these myself and I have worked hard at fixing them for the good of the OSM community. 

Finally, I went back through the terms of service and I realized there's  no ruleset there about things like lollipopping. I'm wondering whether it would be wise for some of the moderators to come together and create a ruleset to add to the terms of service to help with this problem. obviously, it won't fix all of it, but it will help.

Thank you for your time and effort in moderating OSM and I hope that this resolves my particular situation.