piebro/osm-data huggingface dataset:
maro21 (2026-04-26 19:55:36+00:00): > można by zmapować droge jak należy

Droga jest zmapowana jak należy: https://www.openstreetmap.org/way/1494980163 - jest to jak na razie jedyna droga tutaj.

> Cała Polska mapuje highway=construction od momentu wydania ZRiD

Pisanie "Cała Polska" to błąd poznawczy - nadmierne uogólnianie, wyciąganie daleko idących wniosków na podstawie pojedynczych wydarzeń: https://en.wikipedia.org/wiki/Faulty_generalization
Jeśli ktoś mapuje highway=construction od momentu wydania ZRiD, to najlepiej mu zwrócić uwagę, bo w OSM mamy zasadę https://wiki.openstreetmap.org/wiki/Ground_truth

> a śladu po znaczniku dalej nie ma

Budowa jest oznaczona: https://www.openstreetmap.org/way/1432082200
Langlaeufer (2026-04-29 14:12:26+00:00): Wenn der Radweg weitern baulich vorhanden ist (hier rotes vs graues Pflaster) dann bleibt er auch ohne Beschilderung ein (nicht-benutzungspflichtiger/sonster/Bedarfs-Radweg) von daher versteh ich nicht warum die cycleway:both=no setzt?
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/181822600
klnkengi (2026-04-29 15:34:09+00:00): Am Bürgersteig auf der Nordeite der Bahnhofstraße westlich des Bahnübergangs steht an jeder Einmündung ein Vz. 239 mit dem Zusatzschild "Radfahrer absteigen". "Radfahrer absteigen" ist zwar etwas verwirrend, aber ich verstehe das so, dass damit der ehemalige Radweg aufgehoben ist und Radfahrer die Fahrbahn benutzen sollen. Der südliche Gehweg ist mit Vz. 239+1022-10 beschildert und entsprechend gemappt.
Langlaeufer (2026-04-29 19:54:26+00:00): Ich würde Radfahrer absteigen nur auf den Bahnübergang  beziehen. Hat übrigens  keine verhehrsrechtliche  Wirkung.

Das 239 1022-10 gilt nur bis nur nächsten kreuzenden Straße danach würde die Augenscheinliche Trennung wieder einen getrennten Rad und Gehweg daraus machen.
Langlaeufer (2026-04-29 19:55:17+00:00): ... bei fehlender Beschilderung
klnkengi (2026-04-29 23:12:43+00:00): Auf den Bahnübergang bezieht sich das "Radfahrer absteigen" definitiv nicht. Die Kombination aus Vz. 239+"Radfahrer absteigen" steht in Fahrtrichtung Westen HINTER dem Bahnübergang und wird dann hinter jeder Einmündung zwischen der Clara-Zetkin-Straße und der Parkplatzufahrt zur Grundschule Borgsdorf wiederholt. Diese Beschilderung muss ziemlich neu sein, in Mapillary ist sie noch nicht zu sehen.

In Fahrtrichtung Osten steht die Kombination 239+1022 auf jeden Fall hinter den Kreuzungen Birkenwerderweg, Feuerdornweg und vor dem Bahnübergang. Ob sie dazwischen wiederholt wird, kann ich nicht 100 % sicher sagen, weil ich in Richtung Westen unterwegs war.
Langlaeufer (2026-04-30 04:49:03+00:00): O.k da erklärt es. Ist neu. Magst du die Beschilderung nachtragen damit es klar ist woher das Tagging stammt  oder soll ich das anhand deiner Beschreibung machen?
klnkengi (2026-05-01 10:51:48+00:00): Hab' die Beschilderung ergänzt.
Langlaeufer (2026-05-01 13:13:33+00:00): Danke Dir.
divaddivag (2026-04-27 05:49:41+00:00): 🙏
PèreForez (2026-04-27 21:45:48+00:00): Pardon divaddivag je n'ai pas compris ton message !
divaddivag (2026-04-28 06:07:42+00:00): Salut Père Forez, un merci (🙏) rapide pour avoir corriger la position de la plaque sur le bon bâtiment! Bien à toi
PèreForez (2026-04-28 08:24:36+00:00): Je ne connaissais pas ! Sur cette rectification,  il  se trouve que je suis passé juste devant en allant à Merville pour une visite familiale !
ika-chan! (2026-05-02 13:03:45+00:00): The closure of the road was reverted because no reason was given in the changeset comment.

https://www.openstreetmap.org/changeset/182115884
Ορφέας Μαρκετάκης (2026-05-02 23:23:07+00:00): Actually this part of the road is currently under construction. It is part of the renovation of the παράκαμψη Ρεθυμνου (βόρειου οδικού άξονα Κρήτης) so it is now closed and under construction
ika-chan! (2026-05-03 13:28:00+00:00): Hello, thank you for replying: I think we only mark the road as under construction if the temporary closure for upgrades is for a long time, like more than one month.

In London, there was recently a month-long closure of an elevated road from March to April 2026, but editors over there did not mark the affected roads as under construction (sources: https://www.openstreetmap.org/way/101500/history and https://tfl.gov.uk/info-for/media/press-releases/2026/april/a40-westway-to-reopen-to-traffic-tonight).

You can change it back to under construction if the total closure of the carriageway is for more than one month, but you need to leave a changeset comment, otherwise there would be confusion (see https://wiki.openstreetmap.org/wiki/Good_changeset_comments).
Ορφέας Μαρκετάκης (2026-05-03 20:08:13+00:00): checked how long this specific project will last (the upgrade of the Rethymno bypass on the Northern Road Axis of Crete), and according to the schedule it will remain closed at least until June, with possible delays. So it would be best for it to remain marked as a road under construction. Sources: https://rethnea.gr/se-pliri-exelixi-oi-ergasies-gia-tin-parakampsi-rethymnou-tou-voak/
ika-chan! (2026-05-03 21:04:27+00:00): Okay, I will assume that to be more than one month, and I reinstated the status in changeset 182178858: however, please leave a changeset comment in your edits, to reduce risk of confusion.
felipeeugenio (2026-04-25 21:09:30+00:00): Hola. 
Dos comentarios.
1) una zona de drop off no es un estacionamiento
2) todas esas restricciones para doblar a la derecha, no será que el camino es de un sentido?


saludos
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/181823397
jptolosa (2026-04-26 02:06:38+00:00): Hola sebaver, a qué se deben todas esas restricciones de giro?
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/181823397
maraf24 (2026-07-01 18:40:51+00:00): Taki zestaw zmian trudno jest przejrzeć i  zamiast robić 9 różnych opisów, prawidłową i mocno zalecaną metodą jest zrobione 9 osobnych zestawów zmian.
mcliquid (2026-04-26 07:24:12+00:00): Ex quo tempore in Helvetia Latine loquitur?
9_tab (2026-04-26 09:19:28+00:00): Electio confoederationis pro nomine eius est lingua Latina ab saeculo XIX. 

https://hls-dhs-dss.ch/it/articles/009827/2020-09-15/

Linguae a cantonibus electae discrepant.
mcliquid (2026-04-26 18:58:35+00:00): The argument about Latin is mixing up two different things. According to the OSM wiki, "default_language" is defined as:

> “the most likely language of the "name=*" tags in the region … It does not indicate which languages are spoken in the area, or the official languages of the region.”

In Switzerland, the "name=*" tags are clearly not in Latin, but in German, French, Italian (and sometimes Romansh), depending on the region. Latin is not used for place names, street names, or any other on-the-ground naming.

The wiki also explicitly states:

> “Always use just one language code per region”

and

> “This tag should never be set to multiple semicolon-separated values … because it has no meaning to the data consumer.”

So using "la" here is not appropriate:

* it does not reflect the language of the actual "name=*" tags
* it is based on the Latin form "Confoederatio Helvetica", which is unrelated to how names are tagged in OSM

For Switzerland, the situation is admittedly complex due to multilingual regions. However, the correct conclusions are:

* "default_language=la" is clearly incorrect
* "default_language=de" for the whole country is also questionable
* the most consistent approach is either:

  * no "default_language" on admin_level=2, or
  * handling it on sub-regions where a dominant language exists

Could you clarify what data consumer benefit you expect from setting "default_language=la"?
9_tab (2026-04-27 11:20:20+00:00): > **"default_language=de" for the whole country is also questionable

That seems wrong to me. The agreed upon common country-name for Switzerland is in Latin. This is found everywhere in the country (check next time) and has been stable since the 19th century (see article).

It's possible that the linguistic compromise isn't the same in other countries. I read in Germany, it's illegal to edit maps in anything but "de".

Neither Latin nor German are commonly spoken ("loquitur" as you wrote) in the country, but this isn't relevant.

default_language=de might have lead to "de" poping up in odd places in Switzerland. Problems I started fixing.



> Latin is not used for place names, street names, or any other on-the-ground naming.

This isn't relevant either, as the tag will only apply to the country-level as cantons, districts, etc. have different defaults. 

Samples: 

for https://www.openstreetmap.org/relation/1687730 it's "it", 

for https://www.openstreetmap.org/relation/1684782 it's "fr", 

for https://www.openstreetmap.org/relation/1686703 it's "de",

etc.


> “Always use just one language code per region”

I don't think the key ever had several values. You might be confusing it with other places. The value here shouldn't have any adverse effects. Is there something you think could go "clearly wrong"?


> Could you clarify what data consumer benefit you expect from setting "default_language=la"?

The default <language> allows users to select the name:<language> for the country (name:la that is), if they choose not to use the current value in "name" directly.
mcliquid (2026-04-27 11:31:31+00:00): I think there is still a misunderstanding about what `default_language` is meant to represent.

The wiki is quite explicit:

> “This tag is set to the most likely language of the `name=*` tags in the region … It does not indicate … the official languages of the region.”

and importantly:

> “It is the majority of the other, smaller locations is what causes localization problems.”

So the key point is: **it is about the language of the actual `name=*` values across the dataset**, not about a symbolic or politically neutral country name.

For Switzerland, the vast majority of `name=*` tags (settlements, streets, POIs, etc.) are **not in Latin**. They are in German, French, or Italian depending on the region. Latin is essentially **absent from real `name=*` usage**.

Because of that, setting `default_language=la` does not reflect reality and gives misleading signals to data consumers. A consumer interpreting this tag would reasonably assume that names in Switzerland are primarily in Latin, which is clearly not the case.

Regarding your use case:

> “The default <language> allows users to select the name:<language> for the country (name:la that is) …”

This is not how the tag is intended to be used. `default_language` is **not a selector for which `name:xx` should be preferred for a specific feature (like the country name)**. It is a heuristic to help choose between `name=*` and `name:xx=*` **based on the dominant language of the dataset in that region**.

Using it to force `name:la` for Switzerland effectively repurposes the tag away from its documented meaning.

So in summary:

* The existence of *Confoederatio Helvetica* does not justify `default_language=la`
* Latin is not the language of `name=*` tags in Switzerland
* The tag should reflect actual data usage, not a neutral naming convention for one object

If the goal is to expose or promote `name:la`, that should be handled directly via `name:la=*` (which already exists for the country), not by redefining `default_language`.
9_tab (2026-04-27 13:13:47+00:00): To solve this in your direction, I guess there several solutions:

- remove the tag entirely
- add multiple values as in name (so it aligns therewith). The wiki mentions that this isn't preferred, but used that way.
- align name with name:la
- define default_language for all subregions (so "la" is only applied where relevant).
mcliquid (2026-04-27 13:19:48+00:00): Thanks for outlining the options — that helps clarify the direction.

From the wiki and how the tag is used in practice, I would strongly lean toward:

→ removing the tag entirely on admin_level=2
9_tab (2026-04-27 13:26:15+00:00): I'm ok with that. 

default_language is mostly set in regions, but still needs work around CH-GR.
SomeoneElse (2026-04-26 08:38:25+00:00): Hello,
Thanks for updating this.  There were a couple of townlands and a couple of parishes that shared the line of the previous road, so I've added in a new line https://www.openstreetmap.org/way/1503887691/history and added them to that to fill in the gap.
Unfortunately these "relationship memberships" aren't really clear in the online editor...
Best Regards,
Andy
irishwill2008 (2026-04-26 10:00:51+00:00): Hey Andy,

Appreciate looking into this! I assumed that line was some road since I live in Delvin myself and that does not exist. You cannot drive between those if that makes sense? Of course I am completely new to this and only made the edit as I am a Software Engineer currently using OpenStreetMap and while testing some routing, it was generating routes through the various cul de sacs. Then realized I could contribute and update.

Just curious then what that edit you made means so I understand for next future updates! :) Since both of those roads are no longer joined since the new build of the main road from Delvin to Mullingar.

I guess you can check Google Maps to also understand as that is pretty accurate right now. Appreciate it buddy!
SomeoneElse (2026-04-26 10:13:57+00:00): Hi Will,
The new bit I added https://www.openstreetmap.org/way/1503887691 isn't a road, it's just a "relation member" of those townlands and anglican parishes.  You can see the faint line at https://www.openstreetmap.org/#map=19/53.585524/-7.135129 , but that map doesn't show many names at that zoom level.
Many maps do update pretty much immediately the OSM data updates, although sometimes there's some caching involved - it wouldn't surprise me if it took a day or so.  Eventually Hiskinstown and Williamstown (Rochford) will appear in the same way that Mulchanstown does at https://www.openstreetmap.org/#map=18/53.586003/-7.136881 .
As for Google Maps - no, we can't use that, due to various licence compatibility issues.  See e.g. https://wiki.openstreetmap.org/wiki/FAQ#Why_don't_you_just_use_Google_Maps/whoever_for_your_data? .
Best Regards,
Andy
mcliquid (2026-04-26 07:21:42+00:00): Grüß dich, wieso werden die postalischen Adressen entfernt?
ChrisFromRV (2026-04-26 09:16:24+00:00): Weil nicht garantiert ist, das an der genau selben Stelle auch wieder Häuser gebaut werden. Außerdem sollte dort irgendwann irgendein "Wohnprojekt" gebaut werden, ändert sich die Straße "Fallenbrunnen" vielleicht auch. Auch für Navis usw. sind unbebaute Nummern uninteressant.
mcliquid (2026-04-26 18:49:25+00:00): Hat die Stadt Friedrichshafen die Flurstücke entwidmet, damit die Hausnummern ungültig werden?
rene78 (2026-04-28 08:41:38+00:00): Ich hab diesen Änderungssatz erstmal wieder rückgängig gemacht, damit die Hausnummern wieder drin sind. Hoffe, dass ist okay.

Die Umrisse der abgerissenen Gebäude können ja später für die Neubauten verwendet werden. So bleibt die Historie erhalten.
mcliquid (2026-04-28 13:07:51+00:00): Danke dir! Bing und Esri zeigen die Gebäude nach wie vor an, da schadet es aus meiner Sicht nicht den Lifecycle-Prefix noch etwas länger stehen zu lassen.
FrookMartineli (2026-05-15 02:02:39+00:00): Something got screwed up when you did this.  883999185 was a boundary (I think) that is now showing as a cycle path. I don't think that's what you meant to do.
Grass-snake (2026-05-09 16:32:50+00:00): Здравствуйте, вопрос про улица Липовая Аллея (https://www.openstreetmap.org/way/83918439), проверил по ФИАС, там указано "ул. Липовая Аллея". Проверил адреса, указанные в ПКК, там улица встречается примерно в 2 раза чаще, чем без улицы. Если не возражаете, хотел бы вернуть обратно "name"="улица Липовая Аллея" (с указанием аллеи в alt_name).
Grass-snake (2026-05-14 18:00:00+00:00): Не дождался ответа, исправил как посчитал нужным.
https://www.openstreetmap.org/changeset/182663796
Im Fokus (2026-04-25 23:23:21+00:00): Fehler im Änderungssatz-Kommentar:
Döringstraße ist Unsinn, gemeint war der südl. Teil der Talstraße
detective-fiasco (2026-04-25 23:34:57+00:00): This is a demo of a newer tagging of this specific sign - Needed for cases when the sign is installed by itself
dpolovinkin (2026-04-29 09:00:51+00:00): please leave meaningful comments describing what you've changed - https://wiki.openstreetmap.org/wiki/Good_changeset_comments, you leave this meaningless "bmb" for years as I see

I'll report your profile to OSM admins if any more comments like that will be added
munkhbayar b (2026-05-06 05:06:35+00:00): Hello. I don't speak English, so I couldn't comment in the comment section every time I edited it. Sorry.
dpolovinkin (2026-05-06 05:27:07+00:00): there is no requirement to make comments only in English :) feel free to do it in your own language
munkhbayar b (2026-05-06 05:29:51+00:00): I'll pay attention from now on. Thank you.
MarinoBM (2026-05-24 16:27:16+00:00): Hola Ufones de Aliste: has cambiado de forma errónea la clasificación de estas carreteras. Los criterios para su clasificación están recogidos en las Directrices de etiquetado para Castilla y León
Red Complementaria Local: highway=tertiary
https://wiki.openstreetmap.org/wiki/ES:Directrices_de_etiquetado_espa%C3%B1olas#Castilla_y_Le%C3%B3n
Este conjunto de cambios ha sido revertido.
Un saludo

https://www.openstreetmap.org/changeset/183116431
MarinoBM (2026-05-24 16:27:17+00:00): Hola Ufones de Aliste: has cambiado de forma errónea la clasificación de estas carreteras. Los criterios para su clasificación están recogidos en las Directrices de etiquetado para Castilla y León
Red Complementaria Local: highway=tertiary
https://wiki.openstreetmap.org/wiki/ES:Directrices_de_etiquetado_espa%C3%B1olas#Castilla_y_Le%C3%B3n
Este conjunto de cambios ha sido revertido.
Un saludo

https://www.openstreetmap.org/changeset/183116431
OldManCelli (2026-07-13 15:57:58+00:00): Hello Magritte, I think there might be some confusion here about how to represent buildings in OSM. Generally buildings are defined as a single shape to depict the footprint of the building. If there are parts that you want to detail then those should be tagged as building:part=yes. Some of the edits here have buildings overlapping other buildings.
pwbriggs (2026-04-25 23:56:00+00:00): Tracking relation cleanup:
* 3 variants of NB 7 done
iandees (2026-04-26 14:50:31+00:00): Hello! I noticed that node https://www.openstreetmap.org/node/8545114817 was moved a long distance in this changeset. This is a common mistake that happens when you click on a point and drag to move the map. The point moves with your mouse instead of the map.

I moved things back to where they were before in https://www.openstreetmap.org/changeset/181849146, so no harm done!

To avoid this in the future:
- Try to click on an empty part of the map when you want to move around
- If you see a point move by mistake, press Ctrl+Z (or Cmd+Z on Mac) to undo it

Happy mapping!
iandees (2026-04-26 14:50:30+00:00): Hello! I noticed that node https://www.openstreetmap.org/node/12374505457 was moved a long distance in this changeset. This is a common mistake that happens when you click on a point and drag to move the map. The point moves with your mouse instead of the map.

I moved things back to where they were before in https://www.openstreetmap.org/changeset/181849147, so no harm done!

To avoid this in the future:
- Try to click on an empty part of the map when you want to move around
- If you see a point move by mistake, press Ctrl+Z (or Cmd+Z on Mac) to undo it

Happy mapping!
ajmat (2026-04-27 06:34:29+00:00): Reverted in changeset id: 181874765
Wildsharky (2026-04-28 10:55:23+00:00): Reverted in changeset id:181875344
MappingMore (2026-05-02 04:11:53+00:00): Reverted in changeset id:182099854
felipeeugenio (2026-04-26 13:14:25+00:00): Por favor no agregar información privada.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/181828452
iandees (2026-04-26 14:50:46+00:00): Hello! I noticed that node https://www.openstreetmap.org/node/7385102552 was moved a long distance in this changeset. This is a common mistake that happens when you click on a point and drag to move the map. The point moves with your mouse instead of the map.

I moved things back to where they were before in https://www.openstreetmap.org/changeset/181849160, so no harm done!

To avoid this in the future:
- Try to click on an empty part of the map when you want to move around
- If you see a point move by mistake, press Ctrl+Z (or Cmd+Z on Mac) to undo it

Happy mapping!
NorthCrab_upload (2026-04-26 03:51:11+00:00): Zauważyłem, że Twoja zmiana zawiera niepoprawne adresy. Przygotowałem listę obiektów do poprawy oraz dodatkowe informacje:

Duplikat adresu w okolicy. Adres można oznaczyć na dwa sposoby: na obszarze (dokładniejsze) albo na punkcie. Aktualizując adres, należy się upewnić, czy w okolicy nie pozostały żadne duplikaty.
https://www.openstreetmap.org/way/912190047

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! 🦀
NorthCrab_upload (2026-04-26 03:21:37+00:00): Zauważyłem, że Twoja zmiana zawiera niepoprawne adresy. Przygotowałem listę obiektów do poprawy oraz dodatkowe informacje:

Duplikat adresu w okolicy. Adres można oznaczyć na dwa sposoby: na obszarze (dokładniejsze) albo na punkcie. Aktualizując adres, należy się upewnić, czy w okolicy nie pozostały żadne duplikaty.
https://www.openstreetmap.org/node/13762309228

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! 🦀
NorthCrab_upload (2026-04-26 03:31:35+00:00): Zauważyłem, że Twoja zmiana zawiera niepoprawne adresy. Przygotowałem listę obiektów do poprawy oraz dodatkowe informacje:

Duplikat adresu w okolicy. Adres można oznaczyć na dwa sposoby: na obszarze (dokładniejsze) albo na punkcie. Aktualizując adres, należy się upewnić, czy w okolicy nie pozostały żadne duplikaty.
https://www.openstreetmap.org/node/13762309228

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! 🦀
NorthCrab_upload (2026-04-26 03:51:07+00:00): Zauważyłem, że Twoja zmiana zawiera niepoprawne adresy. Przygotowałem listę obiektów do poprawy oraz dodatkowe informacje:

Duplikat adresu w okolicy. Adres można oznaczyć na dwa sposoby: na obszarze (dokładniejsze) albo na punkcie. Aktualizując adres, należy się upewnić, czy w okolicy nie pozostały żadne duplikaty.
https://www.openstreetmap.org/node/13762309228

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! 🦀
felipeeugenio (2026-04-26 13:12:48+00:00): Araoz? con Z? Nunca había visto ese apellido escrito así. Cual es la fuente de este cambio?
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/181829169
felipeeugenio (2026-04-27 11:56:24+00:00): no hay respuesta del editor. Se corrije cambio.
tastywater (2026-04-26 03:39:19+00:00): surveyed, charger no longer exists.
TrickyFoxy (2026-04-27 10:37:03+00:00): 👋 Не вносите личные заметки в OpenStreetMap. Используйте раздел Метки в приложении
wies1 (2026-04-26 07:58:26+00:00): Hallo,

mal ne Frage:
Was meinst du mit:  gnss (rtk/sapos)

Gruss

wies1
vichada (2026-04-27 17:57:22+00:00): Hi,

die survey Methode
unni-geo (2026-04-28 07:41:23+00:00): Ist es das: https://www.youtube.com/watch?v=z5wPqP9Bbm0 ? :-)
gosgtan (2026-04-26 09:38:54+00:00): Bonjour, vous pouvez faire un revert. Je viens de vérifier, l'arrêt est bien utilisé par les lignes scolaires du réseau
0xb7767000 (2026-05-04 08:41:52+00:00): Danke fürs wiederherstellen des POI!
Ich habe jetzt auch noch meine Infos aus dem Hinweis ergänzt:
https://www.openstreetmap.org/changeset/182193123
luismtorresv (2026-04-26 20:25:07+00:00): Oops, it seems that the EV charging point wasn't added? Hmmm