piebro/osm-data huggingface dataset:
multimodaal (2026-05-23 12:22:03+00:00): Beste @Beheerder Veluwe Noord: 
Heeft u misschien iets meer informatie over het recente verloop van paden hier?
was hier gister en het lijkt erop dat dit pad uit uw changeset onlangs is afgesloten voor publiek: https://www.openstreetmap.org/way/1468709979/history  ?
Zie https://www.openstreetmap.org/way/1468709979/history
Klopt het dat de route is omgelegd ten zuiden van de langgerekte waterpartij : https://www.mapillary.com/app/?pKey=4548851985348971
(ik kon gister niet zelf verder onderzoeken omdat ik met de fiets was en fietsen daar niet is toegestaan..)
Bedankt voor uw informatie!
eggie (2026-01-20 12:41:19+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
CapitaineMoustache (2026-03-18 20:50:51+00:00): Bonjour Mtrelaguite !

Félicitations et merci pour avoir ajouté votre commerce sur OSM !
Je me suis permis de retoucher vos contributions (vous aviez par mégarde déplacé la Rue de la Gaieté et le bureau Proman à proximité), tout est réglé désormais !

Avant d'envoyer vos modifications, n'hésitez pas à jeter un oeil sur le validateur de données.
Et en cas de fausse manip', faites "Annuler" (Ctrl+Z sur votre clavier ou le bouton flèche arrière dans le coin en haut à droite).

L'éditeur iD que vous avez utilisé est assez piégeux lorsqu'on veut glisser sur la carte, il arrive souvent qu'on bouge des objets sans le vouloir !

Enfin, sachez que votre commerce est déjà répercuté dans plein de cartes, d'applis et de sites qui utilisent OSM comme cartes.app, un super site français qui se veut une alternative à Google Maps, voyez vous-même :
https://cartes.app/?allez=Octopus%2C+repaire+deboussol%C3%A9%7Cn4554228141%7C1.07978%7C43.61380#19/43.6138295/1.0803066

Ce visuel est directement intégrable sur votre site web si vous le souhaitez, il suffit de cliquer sur le bouton "Intégrer".

Bonne continuation et n'hésitez pas si vous avez des questions !
eggie (2026-01-20 13:14:34+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privebericht.
Gebouwen uitlijnen mbv een schuingenomen luchtfoto gaat niet goed. Ik heb het weer aangepast aan de BAG vorm en het adres verwijderd. Er is een adresnode.
MVG,
Eggie
Namens de OSM Community
empty_child (2026-01-21 08:42:47+00:00): Well, it's not a good idea to rename this way. I, personally, prefer preserving Latinization without translation. If you have a point about direct translation, please write it down.
empty_child (2026-01-21 08:43:16+00:00): Otherwise, I plan to revert this changeset and this one (https://www.openstreetmap.org/changeset/177474249)
Jk488 (2026-01-21 10:57:25+00:00): Other neighborhoods in OSM are named similarly in English, such as Airport Settlement, Tetrikhevi Settlement, etc., and I thought that would be the preferred way, considering that such neighborhoods are usually referred to as the "main component" of the name ("Koniaki", "Hualingi"), dasakhleba sometimes works as a clarifying element, and translation would work the same way in English
empty_child (2026-01-21 16:35:33+00:00): Understandable. But it's a bit tricky logic. Why shouldn't we translate Koniaki in this case? ;)

All this question about:
1) full translation,
or 2) partial,
or 3) none, transcription only

I can't follow all the changes that happen (especially with current problems of the German Overpass server), but I try to be more or less consistent in my own (I use the third option usually). The third one, because, well, I can't remember the existence of official translations and in an attempt to make a foreigner's life easier in case of searching the district (by eliminating "settlement" and using the original word).

What's your opinion after this bed sheet of text?
Jk488 (2026-01-21 17:38:52+00:00): From my pov I think it comes down to my perception that "Koniaki" is the actual name (and IMO such names should usually be transliterated), and settlement/dasakhleba as a clarifying element that can be translated and be ignored if the context is clear. I'd also prefer clear rules and consistency but I think it depends on each neighborhood.

Here’s another thought: the English name could just be Koniaki, while Koniaki Settlement and Koniakis Dasakhleba added as alternative names (or some other combination), leaving the Georgian name as it is (or doing the same with Georgian too for consistency). I'd prefer this or the partial translation, but as a not-that-experienced editor I’m open to any suggestions/reverting it
empty_child (2026-01-21 20:44:04+00:00): > Here’s another thought: the English name could just be Koniaki, while Koniaki Settlement and Koniakis Dasakhleba added as alternative names

Reasonable. And following this idea, it's better to review all "settlements" in Tbilisi. And crosslinks too. If this toponym is widespread, we should check it separately.
With "settlements" outside the city, you're opening a black hole (~50 places) in all of Georgia.
yelisey90 (2026-01-22 10:44:26+00:00): I can only notice the great variability of naming as of now: Shankhai https://www.openstreetmap.org/node/3659867594/history , Samretsvelo https://www.openstreetmap.org/node/6276184773/history , Airport https://www.openstreetmap.org/way/199479145/history , 8th Legion https://www.openstreetmap.org/node/930617567/history , Lisi https://www.openstreetmap.org/relation/20108635 , Lilo https://www.openstreetmap.org/way/57792577/history , Orkhevi https://www.openstreetmap.org/node/11042041829/history , Tetrikhevi https://www.openstreetmap.org/way/1334988507/history

Some have Wikipedia articles with დასახლება in title, like https://ka.wikipedia.org/wiki/ლილოს_დასახლება , some without https://ka.wikipedia.org/wiki/თეთრიხევი_(თბილისი)

J4kee has added Lisi as ლისის დასახლება to the template at Wikipedia: https://ka.wikipedia.org/w/index.php?diff=prev&oldid=4821136 , but just as Lisi here to OSM.

One consideration is that without დასახლება / Settlement the locality may sometimes be confused with other objects, like the Airport , Didi Lilo & Patara Lilo villages, Lisi Lake... Some are really unclear without it, like საქნავთის დასახლება http://www.nplg.gov.ge/gwdict/index.php?a=term&d=89&t=2192 (which BTW should be reinstated as the correct name of https://www.openstreetmap.org/way/77767105/history ). Also note that this dictionary gives the names in full, like საქნავთის დასახლება  and http://www.nplg.gov.ge/gwdict/index.php?a=term&d=89&t=1348 . So at least in cases where confusion is likely or where the name is more of a genitive clause like საქნავთის დასახლება, I think it would be better to leave დასახლება in name, also providing alt_name without it.

Considering translations... In case of Russian, in many cases a historic name from Soviet times can be found, like here https://commons.wikimedia.org/wiki/File:2025-04-17_Old_street_sign_at_21_Revaz_Japaridze_1st_Lane.jpg or like поселок грузнефти in the dictionary entry above; and such names would likely still be used by native or near-native speakers of Russian from Georgia. So in case of name:ru I definitely favour translation.

In case of name:en... Well, in the majority of cases there aren't any established names for Georgian toponymy in English (with some exceptions as Narikala instead of Nariqala), so this argument is not valid. However, I would also favour translating to "Settlement"... Like J4kee noted above, it's not an essential part of a name, more like a qualifier; if transliterated, it looses this functionality and only makes the name look more complex and inexplicable. If we need some examples from outside OSM, here is one: https://transit.ttc.com.ge/#/board-info/1:2621/arrival-times https://transit.ttc.com.ge/#/board-info/1:2919/arrival-times

All in all, I would consider the issue with დასახლება similar to street names. Sometimes foreign names of streets are kept unchanged, like Karl-Marx-Allee in English or Бейкер-стрит in Russian. But if we agree to translate გამზირი to "Avenue", even though გამზირი lacks the avenue's usual sense of having trees on the sides, so why should we leave დასახლება untranslated...
Jk488 (2026-01-22 12:03:42+00:00): About Lisi in Wikipedia, I had to add "settlement" because otherwise it'd get redirected to this page: https://ka.wikipedia.org/wiki/ლისი_(მრავალმნიშვნელოვანი). I'll add it as alt_name as it's also used sometimes.

I agree that some neighborhoods like Saknavtis Dasakhleba, Samretsvelo Dasakhleba wouldn't make sense in Georgian without dasakhleba part, so the whole name should be transliterated.

Adding alt names in every existing form would work the best, but I’m still unclear about the primary name: should it be Koniaki or Koniaki Settlement?
SomeoneElse (2026-01-20 23:08:59+00:00): ¿qué?
eggie (2026-01-20 15:24:09+00:00): Bets Gijsbert.. Je hebt hier een driveway getekend over een fietspad.
Dat werkt niet,
MVG
eggie
eggie (2026-01-20 15:28:00+00:00): Ik heb het iets aangepast.
De fietsoversteek 'moet' ook blijven werken. 

MVG
eggie
Matija Nalis (2026-01-22 03:19:37+00:00): Hi, and thanks for helping improve the OSM map!

I've noticed that yesterday you've added crossing:barrier=double_half  on https://www.openstreetmap.org/node/1911690814/history/4 near Kula Norinska in Croatia.

That "double_half" value however seems unlikely in Croatia - it would mean 4 half-barriers ("4 polubranika") on the railway crossing (two at each side of the railway).

Is it correct, i.e. what you wanted to map? And if so, do you remember what was your source? 

Thanks in advance!
SPLATPLAYS (2026-01-22 04:10:56+00:00): After analysing recent street level imagery and wiki information this has been changed to crossing:barrier=half in order to properly reflect the real life information in #177547978 .
NE2 (2026-03-18 00:07:39+00:00): Apart from a few likely-AI Facebook posts and a few fake gold signs made for photos, I'm only seeing brown ceremonial name signs: https://www.google.com/search?udm=2&q=trump+blvd+palm+beach
JeroenHoek (2026-03-18 07:57:27+00:00): If the name signs are there (as you note), and the official mandate signed, what more do you need?
NE2 (2026-03-18 08:03:56+00:00): You're not understanding how street names work in Florida. There are green signs at every intersection, ground level and overhead, that read Southern Blvd. On the other hand, when the state legislature assigns a name, it's usually posted on a few special brown ceremonial signs, and the normal green signs are not changed. I'm planning to drive down to West Palm soon to verify that the green signs have not been changed, but if they had we both know there would be a bunch of photos out there showing it, not just those of the brown signs.
JeroenHoek (2026-03-18 08:24:56+00:00): What you did here, stuffing the name you don't like in an undocumented key called 'ceremonial_name' is simply wrong and comes close to vandalism. If you disagree with which name is official, do something about it, but use the approved tags such as alt_name, name, and official_name.

Kindly restore the name to one of those. Searching for that name should yield this road.
NE2 (2026-03-18 08:27:54+00:00): Even in the source you provided:
"The new signs should be installed by September. The names are ceremonial, meaning postal addresses and emergency-response systems will continue to use Southern Boulevard."
Perhaps alt_name works, but I wouldn't call it any more official than Southern Boulevard.
JeroenHoek (2026-03-18 08:32:25+00:00): It's not up to you or me what it is called. Don't hide stuff you don't like in unused keys, and don't hide what you are doing by not mentioning it in your changeset comments.
NE2 (2026-03-18 08:32:56+00:00): PS: don't forget to add "PBSO Motorman Highway" to the portion between Lion Country Safari Road and Royal Palm Beach Boulevard, as the article says was also named at the same time (https://www.pbcgov.com/pubInf/Agenda/20250708/3A2.pdf states the limits).
NE2 (2026-03-18 08:44:32+00:00): I've put them both in the alt_name field. Hopefully this resolves the issue.
Minh Nguyen (2026-03-18 15:37:39+00:00): NE2 is right. The brown blade signs are merely memorial name designations. This is extremely common in cities across the U.S. When mappers bother to tag them at all, it usually goes in official_name=*, but some mappers prefer memorial_name=* instead.
Minh Nguyen (2026-03-18 16:46:55+00:00): alt_name=* is also fine. The main thing is to keep Southern Boulevard as the name=*.
JeroenHoek (2026-03-18 17:09:50+00:00): They put the name in alt_name now, which is fine. What is not fine is what I mentioned above:

> Don't hide stuff you don't like in unused keys, and don't hide what you are doing by not mentioning it in your changeset comments.

The same goes for 'memorial_name' with its 50 uses. That is a way to hide stuff you don't like when alternatives which are well-supported (alt_name, official_name) exist. Anyone wishing to use that tag is welcome too, but one of the better supported alternatives should be used in conjunction (like alt_name). There is no need to hide this (moronic) name from search engines and data consumers.

Good changeset comments make note of the essence of the edit. Not mentioning removing a name sign-posted (and highly controversial too) is just bad etiquette in OSM.
Minh Nguyen (2026-03-18 17:44:56+00:00): Please put your pitchfork away and assume good faith. Changeset 180033385 was clearly about more than this one obscure street name that you care way too much about. Perhaps the changeset comment could’ve called out this particular retagging. I think we can give NE2 the benefit of the doubt that it was an oversight. If he had wanted to cover his tracks, he wouldn’t have commented on this changeset, alerting you to his edit.

NE2’s edit was clearly more correct than incorrect. Before you toss around accusations of “close to vandalism”, remember that your initial edit was based on a forward-looking article from a local TV station that someone overseas may not have the local context to interpret correctly. Anyone in the U.S. would by now be familiar with such reports of “renamings” that turn out to be memorial name designations. NE2 is asserting that this is a memorial name designation and I see no evidence to refute that. The law is very clear that a memorial name designation is not intended for wayfinding, so it isn’t a candidate for name=*. [1]

Over the years, memorial_name=* has come up often in OSMUS Slack because mappers believe official_name=* is putting too fine a point on it and alt_name=* doesn’t distinguish them as memorial name designations. These mappers are fine with it falling out of search results, because it amounts to trivia. Some mappers don’t even bother to tag any name and map the sign instead. I personally use official_name=* because I haven’t encountered enough instances of a feature having both an official name and a memorial name designation, but I guarantee you that if we take this conversation to the forum, memorial_name=* will proliferate as a result.

[1] https://mutcd.fhwa.dot.gov/pdfs/11th_Editionr1/mutcd11theditionr1hl.pdf#page=571
JeroenHoek (2026-03-18 17:58:56+00:00): A name which is reported on in every news medium all over the world is neither 'obscure' nor 'trivia'. Don't downplay something like that.

If users come across news articles referencing that name, they should be able to find it. This goes for all memorial, honorary, ceremonial, or whatever names.

If I can find Sesame Street in New York (https://www.openstreetmap.org/way/5673018), I should be able to find this one.
Minh Nguyen (2026-03-18 18:06:56+00:00): The name got reported on because of its namesake, not because of “ground truth” as you put it. It’s functionally obscure because, by law, it can’t be posted anywhere you’d be able to navigate based on it. It’s trivia because memorial name designations are so exceedingly commonplace. That is not to say anyone would be against geocoders exposing this information, appropriately downweighted to reflect relatively minor functional utility. Do I understand that you would be fine with memorial_name=* if only it were better supported by Nominatim?
JeroenHoek (2026-03-18 18:36:45+00:00): Don't twist words like that. A name can be completely pointless in terms of 'by law it can't be posted anywhere you'd be able to navigate based on it', that doesn't make it obscure or trivial, even within the context of OpenStreetMap. We're not building a database exclusively for in-car turn-by-turn navigation.

memorial_name=* seems pointless and too US-specific to me. In any case, removing such names from supported keys should not happen before a new key is better established (this includes Nominatim, but also in terms of numerical use; other data consumers should have a chance to support it too).
Minh Nguyen (2026-03-18 22:18:28+00:00): In case there’s any misunderstanding, if a highway=* is known by multiple names, the common name usable for wayfinding should go in name=*. [1] I never said name=* has to be usable for in-car navigation specifically. I am sympathetic to the argument about searchability, hence my habitual use of official_name=*, but many mappers recognize that this is far from ideal. After all, federal law emphatically states that these names are *not* official.

Changeset 180078301 records another memorial name designation in Miami, Avenue of the Americas. In one Mapillary frame, you can see how this city distinguishes between a memorial name designation and a generic alt_name=*, Biscayne Boulevard Way. [2] Granted, New York City doesn’t make the distinction so apparent. Different state, different standards. They figure everyone should know that streets in Lower Manhattan are denominated by ABCs and 123s. Prompted by your comment, changeset 180075547 scales Sesame Street back to just the block on which it’s signposted.

As far as the on-the-ground rule goes, Trump Boulevard is nothing more than a single double-sided sign posted at one end of the street, which I’ve taken the liberty of adding in changeset 180080039. It takes a certain amount of wishful thinking to extrapolate this into name=*, so I hope we can leave it here at alt_name=*. However, this will be a prime candidate for memorial_name=* once a proposal gets underway.

[1] https://wiki.openstreetmap.org/wiki/Key:name#Values
[2] https://www.mapillary.com/app/?pKey=329012028614409
MxxCon (2026-03-20 04:25:57+00:00): I think it's been brought up before, but the "memorial" name doesn't seem the best choice when such features (and not always streets) are sometimes named after living people and sometimes not even people. Perhaps "dedication" name is a better word.
Minh Nguyen (2026-03-22 02:34:04+00:00): Yeah, I just mentioned memorial_name=* because it’s in use and matches federal terminology. I forgot that honorary_name=* is more common. But this would all need to be sorted out in a broader discussion, not here.
justinsenemy (2026-03-27 21:53:38+00:00): Hi Santosh, we went over this problem a few months ago (we previously spoke in changeset/175797809) way/1468717973 has been removed permanently.  Kindly, please do not add it back again without an in-person survey.
sbedwal_Lyft (2026-03-31 00:22:36+00:00): Hi justinsenemy,
Thank you for your message and for bringing this to my attention again. I sincerely apologize for the recurrence of this issue. I fully understand that this was previously addressed, and I take full responsibility for ensuring it does not happen again. Additionally, I am reviewing my processes to prevent similar mistakes in the future, so that the integrity of the map data is maintained.
I appreciate your patience and your continued efforts in helping maintain data accuracy.

Best regards,
Santosh
quincylvania (2026-02-15 03:27:05+00:00): Hey, just noting that not every part of every way in the canoe route relation is paddleable. At least one dam is here: https://www.openstreetmap.org/way/43584028
scarapella (2026-02-15 11:35:24+00:00): Oops. Thanks for the heads up.  I’ll sort that out.
quincylvania (2026-02-15 15:49:59+00:00): No worries, I already fixed it up around the three dams I found.

I've seen a few cases like this in OSM where people just added route=canoe relations to rivers without much detail. Michigan has a few that still need cleanup I think.
scarapella (2026-02-15 20:29:11+00:00): Thanks. I need to tighten up my overpass query it looks like!
NeisBot (2026-01-21 07:25:38+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/way/903467959 v5

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Fashion store"
---
Par exemple, une version plus neutre et factuelle de ton texte pourrait être : « Magasin de mode »
---
(Auto-translation)

#MapWithoutSpam
NeisRevert (2026-01-28 07:32:51+00:00): 🔄🤖 Partly reverted due to either a lack of response from the contributor or remaining promotional text by https://osm.org/changeset/177792506
(No visible changes after review)
YomanNH (2026-01-20 14:21:40+00:00): Szczegóły przejścia są np. na tym węźle: https://www.openstreetmap.org/node/1158004754. Po co duplikujesz te same informacje na linii?
Thomas Chua (2026-01-20 13:21:25+00:00): This is a wrong delete. How to undo?
kenken234 (2026-01-20 14:29:12+00:00): Reverted
https://www.openstreetmap.org/changeset/177478935
Dodko (2026-01-20 14:00:55+00:00): Aký je zdroj adresy?
Obec takú adresu nepridelila, neexistuje.
https://ibb.co/8L8mbtM5
Marek Pagáčik (2026-01-20 14:07:33+00:00): Ahoj, je to adresa nášho domu, pridávam lebo nás tu nevie nik nájsť. Google hodil číslo 310 do prostred cesty a druhá 310 je za lomítkom na začiatku obce smerom na ružomberok. Ak môžeš schváľ nám to. Číslo máme rovnaké pre odvoz smetí- lístky i na faktúre od OVS
Marek Pagáčik (2026-01-20 14:13:32+00:00): Skúšal som ti preposlať faktúru OVS ale neberie ju.. ak mi dáš email. Príp. Iný kontakt prepošlem...
Dodko (2026-01-20 14:20:08+00:00): Je budova skolaudovaná, máte zameraný adresný bod a pridelila obec adresu?
Ak áno treba naháňať úradníka na obci aby to zapísal do registra adries, v tomto stave ani záchranári na 112 nevedia o existencii adresy.
Marek Pagáčik (2026-01-20 14:27:26+00:00): Adresný bod je zameraný , kolaudácia podaná 17.12.2025, adresa používaná pre odvoz septiku i smetí. Rozumiem o čom hovoríš. Nespochybňujem. Ale ak zadáš "Vyšnokubínska 310" tak ti nájde RD "Vargovci" kde je adresa Vyšnokubínska .../310 čiže ako druhá číslica. Keďže naše tam nieje tak všetci blúdia lebo my sme na opačnej strane obce....
Marek Pagáčik (2026-01-20 14:30:57+00:00): Ak mi dáš kontakt kde sa da hodiť goto čo pdf, môžem ti tam fať pdf faktúru z OVS, zameranie sdresného nodu či foto fasády s číslom. Inak ak sa pozrieš na googli na náß dom z pohľadu z cesty...už tam majú náhľad, malo by to tam byť vidoeť tiež ... Zatiaľ
Dodko (2026-01-20 14:34:40+00:00): V prvom rade vyrieš to s úradníkom na obecnom úrade nech urobí svoju prácu poriadne, ak to bude vložené napíš.
Marek Pagáčik (2026-01-20 14:38:20+00:00): https://ibb.co/kgBKxQYs
Dodko (2026-01-20 14:38:39+00:00): Tu si vieš online skontrolovať, či úradník zapísal adresu do registra a oficiálne existuje.
Dovtedy sa nedá dať ani trvalý pobyt.
https://portal.minv.sk/wps/portal/domov/com.ness.ra/com.ness.ra_/com.ness.ra.addresses/com.ness.ra.addresses.address_verify/!ut/p/a1/
Marek Pagáčik (2026-01-20 14:42:49+00:00): Dík, aspoň som sa dačo priučil, nech darí
https://ibb.co/5X7LTMcT
NieWnen (2026-01-20 19:34:39+00:00): Czym jest church:id? 
Nie wygląda na prawidłowy tag. Zewnętrzne referencje powinny być z z użyciem ref/ref:*, pytanie na co on wskazuje?
WieKo68 (2026-01-20 20:06:35+00:00): Już to kiedyś pisałem. To numer w bazie SEP. Może rzeczywiście przenieść go do tagu o nazwie ref:church:id