piebro/osm-data huggingface dataset:
Fraxi (2025-10-03 15:20:42+00:00): Of course, there are exceptions when the building has not been divided and has addr:housenumber=20-22 for example. Then dealers could explicitly add their shop is located on №22(for instance). As for "If the shop later closes, the node can be deleted" - it is better to replace shop's tag with "shop=vacant" to have history of the node kept and later new date for a new shop might be added. I hope I would be understood, sorry if my English is poor.
rhhs (2025-10-03 16:18:44+00:00): I think the page is this one https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element
"An area object with a node object inside, both with the same tags representing the same real-world feature."
An address is a property of the building (or more correctly for Bulgaria: the land the building stands on), so it should be added to the building (the "real-world feature" it belongs to) and only to the building.
donovaly (2025-10-03 20:13:37+00:00): Many thanks for your replies.
Regarding the reply from @Fraxi: this is no argument not to add for all shop nodes the address. Sure, if there is e..g an office building where you have 10 different offices, 2 per floor, the building is cluttered with nodes and visually only few will be displayed. However, important is that the data is there, that Apps and data crawlers can get the info about that there is the particular shop.

My practical experience is that it is often impossible to divide a building into shapes to match house numbers. For example a shopping mall can house dozens of shops and for example in Germany these shops will have different house numbers, depending what street is the nearest to their location in the building. So the mall building can have a different street address than the shops inside. Then some areas have strange numbering history, like some cities use e.g. 7, 7A, 7B, while other use 7, 7B (so there is no 7A), some use 7A, 7B (there is no plain 7), some use "7" for the main building, but the shops inside all have numbers like "7/1" etc. There are so many different possibilities to number a shop. Some shops use for example post boxes, thus have a completely different address than their location would imply. So the most save and clear is to add the house number and also street to the shop. It does not harm but assures the data are available. I mean, no mapper is forced to add the address, but it makes sense to do so and instead of informing mappers about possible doubling of data, one should inform mappers that having the address for the shop is an advantage.
donovaly (2025-10-03 20:17:14+00:00): To https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element:
there is nothing written that one should not also add the address to shop nodes.

By the way, I only add the address if I know it for sure. I most cases I take the one given at the website of a shop because (in others I take the one from business cards I got) this is the only way to get it right.
donovaly (2025-10-03 20:27:48+00:00): > An address is a property of the building (or more correctly for Bulgaria

But some of my business partners use post boxes, thus the official address (the one in the trade register) is on that post box, thus independent of e.g. the main office's location.

However, the main issue remains - independent of a city an its particular cadastre rules, web crawlers should get info about shops. The shop owners want to get found and the apps want to provide users e.g. how to route to a location. It is impossible for a crawler to know in advance that Sofia has the rule that if a node is inside an OSM area having a house number, the shop always has the same number, while in Shumen it might not be the case. Or take Berlin where on some areas shops with entrance at the backside of the house gets the suffix "b" while shops with entrances to the main street get "a". Or in Tirana (I lived there) the official address is the number of the entrance of a building. So the house has e.g. number "53" but the official address of my company there is "53/1" (and as funny as it is, there is no "53/2" only a 52/3.

Should apps like OSMAnd~ learn all cadastre rules of all countries? (and in e.g. Germany even every municipality has its own numbering rules)
rhhs (2025-10-04 16:53:28+00:00): When a business' address is different from that of the building it is in, then of course it should be added.
Also note https://wiki.openstreetmap.org/wiki/Key:shop#Address_information "Make sure to add address tags (or avoid adding them) in accordance with tagging practices used within the local community." i.e. it is accepted that there are local variations in tagging practices.
Dimitar155 (2025-10-04 19:04:56+00:00): @donovaly, you are right that it is not inherently wrong to add addresses to POIs. The concern is more about the consequences for data maintenance. Once address data is duplicated, future mappers need to keep it consistent - and in practice, this often doesn’t happen. For example, if a notary moves to another location, the node might be moved, but in many cases the address tags remain unchanged, which leads to errors. I still happen to find such cases from 6-7 years ago...

Another side effect is that it can hide the StreetComplete address quest for the building. If a POI carries the address, but the building does not, a new building might never get its address quest shown. That leaves gaps in coverage.

QA tools can help detect such inconsistencies, but it still means additional work for other mappers to investigate and correct them. From a database perspective, duplication is usually avoided in favour of relationships: here, the relationship is "POI X is located in building Y, which has the address". That ensures one reliable source of truth for the address.

That said, adding the address directly to the POI makes sense when it genuinely differs from the building’s address. In those cases, the information is valuable and necessary.

In short, the KISS principle (https://en.wikipedia.org/wiki/KISS_principle) applies here (and not only here).

P.S. Whether a business uses a PO box for its mail is an operational detail of that business and, as far as I know, not something OSM typically records. You can of course tag their ЕИК, which points to our trade register. Anyone who needs this info can go directly to their page on the trade register and see their mailing/HQ address.
donovaly (2025-10-07 20:45:18+00:00): > Once address data is duplicated, future mappers need to keep it consistent - and in practice, this often doesn’t happen. For example, if a notary moves to another location, the node might be moved, but in many cases the address tags remain unchanged,

This cannot be an excuse not to add addresses. It is simple wrongdoing to move a node and not updating it. This contradicts the idea of OSM in my opinion.
donovaly (2025-10-07 20:53:33+00:00): > it can hide the StreetComplete address quest for the building

I am an "excessive" StreetComplete user (was once even #1 user in Albania :-) ) and don't see this. However, SC is just one app, there are many more. I also reported already several bugs to SC to help improving it.

You have not replied to my main point: I map to:
* benefit personally to later find addresses, routes and info (I now live here)
* to help the shop owners

For both it is important that the info is available and there is no reason why the house a shop is in should be used to provide info. This info: house address is also shop address might be true for Sofia, or maybe not or maybe not for all Bulgarian municipalities and what about in general? No app in the world can find out that local rules might apply (house numbers, PO-box numbers). Therefore mappers should be encouraged to collect as much info as possible.

And again, if a shop closes, the node can simply be removed or changed to the successor. If a shop moves, of course a node must then be updated - updated location is logically also an updated address.
Dimitar155 (2025-10-08 07:53:14+00:00): Open SC, go to https://www.openstreetmap.org/way/227493587 and find its address quest. I wasn't able to. Possibly because the Billa node already has an address.

Now, using Nominatim search for "бул. Черни връх 94". It finds only Billa but not the pharmacy I want to go to. The pharmacy is in the same building but it doesn't have an address. Maybe we should duplicate it?

Now look for "Златовръх 4, София", It finds everything except the payment centre (not sure why) and the insurance office (for which I've put an apparently wrong address).

You can also look for "бул. Черни връх 100". Do we have to put this address on all 100+ shops in this mall? What benefit would we get that we are not getting currently?

This is why we either:
1) put the address on every building (and on shops within if it differs from the building)
or
2) on every building and shop (but that applies to all shops of that building if the building doesn't have an address).

Which one is easier to follow and verify that it is being followed? Which one requires more time to be spent on every object?

> This cannot be an excuse not to add addresses. It is simple wrongdoing to move a node and not updating it. This contradicts the idea of OSM in my opinion.

> And again, if a shop closes, the node can simply be removed or changed to the successor. If a shop moves, of course a node must then be updated - updated location is logically also an updated address.

You are absolutely right - OSM relies on correct editing. If a shop closes or moves, updating the node (and its address) is simply part of proper mapping.

However, most of us have limited time for OSM - we map in our spare moments, between work or study. So, it makes sense to prioritise things that provide real value to end users, and leave tasks that software can infer automatically to the software while also making sure that we keep it as simple as possible to avoid some mistakes (like forgetting to update the address of the shop when we move it).

> No app in the world can find out that local rules might apply (house numbers, PO-box numbers). Therefore mappers should be encouraged to collect as much info as possible.

Actually, this rule does apply globally: add addresses where they differ, not everywhere. If local conditions mean the address truly differs from the building’s, then yes - add it explicitly. Otherwise, duplication just creates more maintenance work without improving the map. And yes, every app is capable of inferring the address from the building. Not only that but most apps do it in less than 1 second!
b-jazz (2025-10-01 05:03:14+00:00): RE: https://www.openstreetmap.org/way/1434444359

Hello Doctor,

Thanks for the golf course contributions, but there are a bunch of problems with this hole as you've mapped it that cause others to clean up behind you.

* you split the green area into two different ways and joined them up with a multipolygon. That is not the correct use of a multipolygon here.
* you created a green outside an existing green. I think you were trying to create a fairway fringe around the green. 
* you overlapped the fringe polygon with the existing fairway polygon instead of extending the existing fairway around the green. This is also incorrect.

I'm happy to help you golf courses correctly. Please be careful going forward and reach out if you aren't sure how to map something. Also, you might want to visit the golf_course wiki at https://wiki.openstreetmap.org.
yelisey90 (2025-09-30 21:04:47+00:00): Is it two-way for common automobiles? If regular public can drive only in one direction, bur there is a lane for buses or taxis going in the opposite direction, then it's oneway=yes + oneway:psv=no
Geosyndicate (2025-09-30 21:18:29+00:00): Yes, this particular section is now two-way for personal cars. One bus lane and two regular lanes in southern direction and one lane in northern direction (which briefly used to be only a bus lane) - 4 Lanes in total. Please keep in mind that satellite images are not updated as frequently or are not visible enough to distinguish current road layout. Therefore, please refrain editing this if you don't happen to be physically at place to know the situation. It's not the first time I am reverting this road segment.
Filip009 (2025-12-03 14:03:13+00:00): Zdravím, neznačené trasy do mapy nepatria. https://www.openstreetmap.org/relation/19665196
tonyfodora (2025-12-03 15:38:57+00:00): Uhol pohľadu 👀 Nevidím v tom problém, každý kto ide on-line, tak mu to pomôže , ostatný pekne po malovanej značke.
Filip009 (2025-12-03 15:49:50+00:00): Základná vec OSM je overiteľnosť https://wiki.openstreetmap.org/wiki/Cs:Ov%C4%9B%C5%99itelnost
tonyfodora (2025-12-03 16:16:51+00:00): Máloktorý trail je značený značkami., Max jedna malá tabuľka  a niekedy len číslo a je toho plná OSM, ten kto hľadá na mapach ,tomu to pomôže a ten kto nie , tak ani nevie že dáky trail existuje. A na OSM je značený. MTB jazdcom online OSM pomôže sa lepšie orientovať. Inak je potom použiteľná na iba tepelná stopa na niektorých mapách.
Filip009 (2025-12-03 16:20:40+00:00): Väčšina z tých trás má aspoň tabuľu, kde sú singletracky pomenované a vyznačené.
MassCartog (2026-07-08 15:02:00+00:00): Hey GA_Kevin, are you sure about this? I'm looking at the Bing imagery and do not see it. I just see a shadow area caused by some trees. I also dont see it in any historical imagery. Also not in Esri, Mapbox, no outline of the "lake" in USGS 3d elevation map. Also not seen on any other mapping service that I looked at.

Also "Hornet Lake" does not show up on any official source around Bemiss, Georgia. The original chageset was made by someone that also added the home there too. My guess it was the home owner adding a made up "lake" in their backyard for was was maybe just some standing water.

Could you provide some source for a Lake being at this location? I cant see it and I cant find any source for "Hornet Lake".
Yog Sot (2025-09-30 23:46:14+00:00): bezkolizyjnośc tej trasy robi wrazenie ;D
IrdiIs (2025-10-08 13:39:53+00:00): Great job for the addresses. May I ask how did you do that? Did you use ASIG data as layover and copy it, or did you import them directly? I want to add the addresses to other areas too but manually copying the data is a pain, so if you got any tricks up your sleeve, please do share. 

Thanks for your contribution!!
ibanez (2025-10-08 20:00:07+00:00): Thank you. I used ASIG for the numbers/street names and ESRI for the building outlines, and a mixture of both for the image offset. I assume that the OSM/ASIG licenses are compatible, but I haven't checked this. This means that all mapping efforts will be undone if someone decides that this is an illegal data import. I usually do this, but the reason I haven't checked is that I don't understand Albanian and many of the legal documents are written in Albanian. To minimize this risk, one approach is to separate the mapping (land use, buildings, roads) from the addresses. I proceeded as follows with the mapping. 1. I use the roads in ASIG as ground truth. There, I also check whether they are largely covered and fill in any gaps. For roads that have a name, I assume highway=residential in the local environment. 2. Based on the mapped roads, I look for the satellite images that have the highest orthogonality (90 degrees from above). There I draw the building outlines. This is best done in the id editor in grid mode (key 'W'). I always make the outline rectangular with the 'Q' key. Since I don't know what a residential building in Albania typically looks like, all outlines get building=yes. 3. I add the addresses (only addr:street + addr:housenumber via the ASIG layer) and transfer them to the address field of the building outline. The city and postal code are usually resolved via the admin relations, so they are unnecessary. For buildings that are difficult to draw in several parts and have several different addresses, I also set separate address points. However, I think addresses belong on the outline. This also leads to better integration in the browser/editing tool. Sometimes you have to zoom in and out of the ASIG layer to see the house number. Sometimes it is relatively difficult to see which street the house number belongs to. It is best to look for 1 and 2 at the beginning of the street and then work your way up.
That's how I did it. Feel free to ask if you need support.
goodidea (2026-03-05 20:30:58+00:00): Hallo tintinmaster!

Bin gerade in der Bahnhofstraße. Kleine Info: deine Änderungen bei diesem Knoten waren nicht richtig: https://www.openstreetmap.org/node/2145619311/history/18 (Änderung von Nico's Diner zu Orient Kebab). In dem Gebäude ist weiterhin Nico's Diner drin, ohne Änderung. Orient Kebab ist bloß noch dazu gekommen ...

Ich korrigieren es gerade nochmal ...

Außerdem mit StreetComplete bitte aufpassen. Das entfernt ungefragt Tags wie z.B. wheelchair oder old_name, die sich in der Regel nicht ändern bei einem neuen Geschäft (oder einem leerstehenden). Dann am besten gleich nochmal hinzufügen. Oder was anderes als StreetComplete für sowas benutzen. Danke und Grüße!
silversurfer83 (2025-10-01 20:36:22+00:00): Hi :)

Wenn ich das richtig sehe war dieser node für den Radverleih des Bikeparks gedacht. Wenn das korrekt ist, dann sollte das vielleicht auch wieder so erfasst werden.
Ich gebe dir recht, dass der Bikepark ggf. besser erfasst gehört.

Grüße
silversurfer83
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/172677063
alone_traveller (2025-10-02 10:52:40+00:00): Hast Recht, gut erkannt! Ich habe noch service:bicycle:retail und service:bicycle:rental hinzugefügt, siehe https://osm.org/changeset/172743473.
iandees (2025-09-30 20:46:47+00:00): Hello! Please be careful in these areas around the U, as you added back a building and some landscaping that has been demolished. Peik Gym, for example, finished being taken down just a month or two ago.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/172677216
Kabooshki (2025-09-30 21:19:55+00:00): gah, you're correct, I didn't realize the gym had been torn down. fixed in #72679795
NeisBot (2025-09-30 20:06:38+00:00): Hi af1312, welcome and thanks for your contribution!

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].

Based on your map edits in this changeset, I’ve drafted a suggestion for what a comment could look like: "Added traffic surveillance camera with ALPR type, Flock Safety brand, operated by Harbour View HOA"
---
[1] https://osm.org/wiki/Good_changeset_comments
af1312 (2025-09-30 20:37:16+00:00): Noted, ty
infeeeee (2025-10-01 12:12:08+00:00): Szia! Üdv az OpenStreetMapen!

Ilyen általános infókat nem a névben kell tárolni, hanem más címkékben: https://wiki.openstreetmap.org/wiki/Names#Name_is_the_name_only

Javítva itt: https://www.openstreetmap.org/changeset/172703497

Ha kérdésed merülne fel, a magyar szerkesztő közösség elérhetőségeit megtalálod ezen az oldalon: https://wiki.openstreetmap.org/wiki/Hungary/Közösség#Elérhetőségek

További jó térképezést!
streckenkundler (2025-10-04 19:47:12+00:00): @Openminded320 Vielen "herzlichen Dank", daß du mal wieder unnötigerweise Grenzen geschrottet hast! Ganz Toll :(
Im übrigen ist es "aller bestes" Mapping, wenn du als wenig sagenden CS-Kommentar  "Binz etc" schreibst und dein CS aber bis nach Berlin geht... 

Beachte auch tunlichtst: https://wiki.openstreetmap.org/wiki/DE:Good_changeset_comments

...grenze deine CS immer und stets so gut ein, wie es geht!!


verärgerte und immer noch "auf Entschuldigung und Danke für die Reparatur in Berlin" wartende und Grüße...
Openminded320 (2025-10-05 14:44:59+00:00): Hallo Steckenkundler,
ich möchte mich für Deine Übersicht über meine CS bedanken und bedauere
ausserordentlich, daß ich Dir durch meine Fehler viel Arbeit beschaffen habe.
Es war gewiss nie meine Absicht und ist wahrscheinlich des Umstands geschuldet, dass ich ziemlich neu hier bin.
Ich bin eigentlich hierher gekommen, um so viele Hydranten wie möglich einzutragen, um einem Freund auszuhelfen, der der Freiw Feuerwehr ist.
Dann bin ich durchs Gassi gehen mit meinem Hund immer mehr eingestiegen und habe die Orientierung, bzw.den Fokus bei dem Kartenbearbeiten verloren. Wenn Du es positiv nehmen möchtest, habe ich "Lust auf mehr" gehabt. Durch die zunehmenden Details habe ich den Überblick verloren.
Ich werde mich mehr konzentrieren und vorsichtiger vorgehen. 
Wie gesagt, hundertprozentig kann ich nicht versprechen keine Fehler zu machen, aber die Rückmeldungen von Dir sind angekommen
VG openminded320
Strubbl (2025-10-05 18:50:52+00:00): Hi openminded320,
du hast bei Binz den Parkplatz w975312604 gelöscht. Existiert der wirklich nicht mehr? Ich habe den vorerst mal wieder hinzugefügt, weil ich glaube, dass in diesem Changeset einiges schief gegangen ist.
Kannst du bitte den Lifecycle-Präfix für Dinge nutzen, die vor Ort nicht mehr verfügbar sind, aber die noch im Luftbild zu sehen sind?

Lifecycle-Präfix:
https://wiki.openstreetmap.org/wiki/Lifecycle_prefix

VG
streckenkundler (2025-10-05 19:25:51+00:00): Hei openminded320,

meinerseits Entschuldigung angenommen... Du erwähntest Hydranten... 
Schau dir da speziell https://waldbrand-app.de/mapcomplete/waldbrand.html?z=14&lat=52.4082&lon=13.23715&tab=3 oder https://www.osmhydrant.org/de/#zoom=15&lat=52.40984&lon=13.22206 oder http://www.openfiremap.de/?zoom=14&lat=52.40437&lon=13.22162&layers=B00000T an. Bei ersterer gibt es auch eine eigene App! Bei den ersteren beiden kannst du auch mit deinem OSM-Account direkt bearbeiten.

Ansonsten...

bei Grenzen und beim OSM-Datentyp Multipolygon: Ich beobachte regelmäßig, daß in bestimmten Konstellationen iD Dinge tut, die der Nutzer nicht will, gerade wenn Anfänger bearbeiten... Darum stets Vorsicht walten lassen!

Danke und Grüße...
UtterClutter (2025-10-01 07:41:33+00:00): Good call, thanks
CAM-Gerlach_Repair (2026-06-12 07:49:31+00:00): Cleaned up remaining SEO spam and other tagging for Dogtopia POI in changeset 184003630

https://osm.org/changeset/184003630
Bienson (2025-10-01 00:25:54+00:00): Reverted in https://www.openstreetmap.org/changeset/172683647
Gonéo (2025-10-10 13:56:36+00:00): Bonjour, tu as ajouté un cycleway:left=track sur un morceau de la Rue Jean Rigaud mais pas toute la rue. Il est en conflit avec le cycleway:both=no. La piste n'est pas visible sur les imageries aériennes. Si tu es dans le secteur, peux-tu corriger et où compléter si tu as les infos?
Cèparlà (2025-10-10 20:29:45+00:00): Bonsoir, les pistes cyclables dont très compliquées a Lyon. Dans cette zone elles sont en partie située sur le côté des trottoirs et bien séparées de la route. Au début de la rue Jean Rigaud elles sont situées sur les côtés de la chaussée.
Le fond de carte Lyon Orthophoto 2022(5cm) est plus précis.
Cordialement
Gonéo (2025-10-11 09:59:37+00:00): Effectivement c'est en partie visible sur l'ortho 2022. L'aménagement est bien tordu, une fois en piste une fois en bande, une fois derrière le trottoir. Ça ne ressemble pas à un aménagement qualitatif.
Strubbl (2025-10-05 19:06:34+00:00): Hallo Openminded320,
das Stadion in way 481736868 habe ich wieder hinzugefügt. Das hattest du gelöscht. Hat das einen besonderen Grund oder war das ein Versehen?

Auch die kaputten Multipolygone für die Äcker von Rel. 8515832 und 8515833 habe ich wiederhergestellt. Bitte keine Objekte löschen, die du nicht verstehst.
Gerade Multipolygone würde ich nicht mit dem iD-Editor bearbeiten.

Auch das Stückchen Wald in w 999925028 habe ich wiederhergestellt. Es ist im Luftbild noch zu sehen und ich wüsste nicht, dass das vor Ort gerodet worden wäre.

Kannst du bitte vorsichtiger mit dem Löschen von Objekten sein und den Lifecycle-Präfix nutzen wie in dem anderen Änderungssatz vorgeschlagen?

Die Wege, die du beim Kreisel der Seebrücke gelöscht hast, dienen dem verbesserten Routing über die Fläche, weil Router noch nicht über Flächen routen können, sondern nur an den Kanten der  Fläche. Und die von dir gelöschte Grasfläche ist auch m.W. immer noch dort. Bitte nicht mehr löschen.

VG