piebro/osm-data huggingface dataset:
Arkhendeloss (2026-04-27 09:53:14+00:00): Merhabalar. Anlıyorum, haklısınız öyle yapacağım. HaritaDuzenlemeHesabi da bana gönderdikleri mesajda OHM'e yüklememin gerektiğini söylediler. Reddit'ten tanıştığım başka biriyle eski tramvay hatlarını OSM'e ekliyorduk (bir nevi proje usülü ile) ona da haber vereceğim OHM'e geçmesi için. Sağ olun, size de iyi çalışmalar.
Supaplex030 (2026-04-19 21:55:29+00:00): Hallo hubandspoke, vielen Dank für deine vielen Ergänzungen in der letzten Zeit! Ich habe gesehen, dass du hier in Oberschöneweide einige Parkbuchten etc. erfasst hast - insbesondere dafür vielen Dank!

Ich habe noch ein paar Hinweise dazu:

- Du kennst vielleicht schon die Seite aus dem OSM-Wiki zum erfassen von Straßenparkraum: https://wiki.openstreetmap.org/wiki/Street_parking. An vielen Stellen ist der Parkraum bereits als Attribut der Straßenlinie erfasst (parking:left/right/both). Insbesondere bei Parkbuchten lohnt es sich - wie du es getan hast - diese auch mit separaten Geometrien zu erfassen. Die OSM-Tags an der Straßenlinie kannst du anschließend so anpassen, dass dort nur noch der Hinweis "separate" erscheint (z. B. "parking:right=separate", wenn es auf der rechten Seite der Linie Parkbuchten gibt, die du separat erfasst hast).
- Eine Stellplatzzahl (capacity) sollte nur angegeben werden, wenn die Stellplätze markiert sind. Oft ist das hier der Fall und deine Angaben sind sehr gut und zuverlässig. An manchen Straßen sind die Stellplätze nicht markiert; dann lässt sich die Anzahl besser aus der Geometrie (Länge des Abschnitts/der Parkbucht) ableiten.
- Einfaches, "unmarkiertes" Straßenparken auf der Fahrbahn sollte eher nicht mit einer separaten Geometrie erfasst werden - dafür eigenen sich die Attribute an der Straßenlinie besser.

Das nur als kleine Hinweise, weil es mir gerade aufgefallen ist, als ich den Parkraum hier in der Gegend etwas überarbeitet habe. Deine Änderungen waren ansonsten aber sehr gut und präzise.

Vielleicht kennst du ja schon das OSM-Parkraumprojekt? Da verarbeiten wir die OSM-Parkraum-Daten, um Stellplatzzahlen und mehr für ganz Berlin zu berechnen: https://tilda-geo.de/regionen/parkraum-berlin?map=16.7/52.4618/13.5205

Schreib mir gern, wenn ich etwas missverstanden habe oder du Fragen hast.

Beste Grüße und Happy Mapping
Alex
hubandspoke (2026-05-07 07:32:51+00:00): Hallo Alex,

entschuldige bitte die späte Rückmeldung! Danke für deine detaillierten Hinweise und die Präzisierungen. Ich versuche mich nach bestem Wissen und Gewissen an den Wiki-Empfehlungen/Vorgaben zu orientieren, leider rutscht mir dann hier und da noch etwas durch.. Jedenfalls fand ich auch die Dokumentation des Verkehrswende-Meetups super, um hier als Beginner mitzumachen.

Viele Grüße

hubandspoke
TheSwavu (2026-04-19 05:40:24+00:00): Hi,

The correct tag is junction=roundabout. See https://wiki.openstreetmap.org/wiki/Tag:junction=roundabout

Thanks
InfernoOSM (2026-04-19 05:42:48+00:00): Must've misremembered, thanks!
eggie (2026-04-18 09:12:13+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privebericht.
Feedback Je hoeft geen oneway=no toe te voegen aan wegen. Dat is default.
MVG,
Eggie
Namens de OSM Community
eggie (2026-04-18 09:18:27+00:00): De parkeerplaats heb ik overgezet naar het vlak.
Ricardo0hh (2026-04-18 18:28:20+00:00): Super, goed om te weten dank je wel. Gr Ricardo
StC (2026-04-18 16:17:14+00:00): Bonjour,

ce changeset a brisé la continuité d'un itinéraire pédestre qui passe par là. Je vais tenter la réparation. Un commentaire plus pertinent aurait pu aider.
woodpeck_repair (2026-04-18 08:36:48+00:00): This changeset reverts some or all edits made in changesets 181480487, 181480771.
bartgron (2026-04-18 19:12:30+00:00): Zastanawiam się co ty tu stworzyłeś i nie mogę pojąć...
Obydwa zestawy zmian są nieprawidłowe i zostały wycofane.
Pozdrawiam
Fraxi (2026-05-15 21:51:50+00:00): Мите, извинявай, 
при n13738151634 има и за пластмасови бутилки:
https://www.mapillary.com/app/?pKey=602757876177777&focus=photo&x=0.02136833529522586&y=0.5602661604466925&zoom=2.3890759932334507&lat=42.023407237203&lng=23.098300750396&z=17
NeisBot (2026-04-18 09:15:43+00:00): Hello, welcome and thank you for your contribution to OSM!

Your changeset was commented because your added description, note or slogan contain detailed text that may be interpreted as promotional or SEO-related. To ensure OSM remains neutral and focused on map data, I recommend keeping descriptions concise, factual, and free from marketing or promotional language.

⚠️️ Problematic element (limit 1):
https://osm.org/node/13739510691 v1

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Animal boarding facility"

#MapWithoutSpam
NeisBot (2026-04-18 09:21:40+00:00): Welcome, and thanks for your edits!

I noticed a few unintended crossings between roads and/or between roads and buildings in this changeset. This usually happens when geometry snaps incorrectly. Additionally, changes to tagging (e.g. modifying highway types or adding tags) can lead to unexpected crossings being detected afterwards.

In total, I detected 87 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/1500666808 v1 | 12 crossings
https://osm.org/way/1500666797 v1 | 8 crossings
https://osm.org/way/1500666790 v1 | 7 crossings

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=181489743
pitscheplatsch (2026-04-18 10:36:14+00:00): In this case, it seems the reported issues are false positives. The geometries were not changed in a way that would introduce crossings, and the tagging adjustments did not create any new conflicts.

Sorry for the inconvenience, and thanks again for your map edits.

Best regards,
Pascal
NeisBot (2026-04-18 09:24:46+00:00): Hello, welcome and thank you for your contribution to OSM!

Your changeset was commented because your added description, note or slogan contain detailed text that may be interpreted as promotional or SEO-related. To ensure OSM remains neutral and focused on map data, I recommend keeping descriptions concise, factual, and free from marketing or promotional language.

⚠️️ Problematic element (limit 1):
https://osm.org/node/9418441349 v2

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Gabinet stomatologiczny"
---
Na przykład, bardziej neutralna i obiektywna wersja Twojego tekstu mogłaby brzmieć: "Gabinet stomatologiczny"
---
(Auto-translation)

#MapWithoutSpam
bartgron (2026-04-18 19:13:51+00:00): Edycja jest nieprawidłowa i została wycofana. Proszę o uważne mapowanie i niedodawanie opisów firm, które są reklamami.
Pozdrawiam
Fraxi (2026-04-18 09:28:05+00:00): Контейнер(1).
osmviborg (2026-04-18 10:16:08+00:00): Hej, den rigtige måde at gøre det er at give bropillerne højde: https://www.openstreetmap.org/changeset/181491532
NeisBot (2026-04-18 09:42:40+00:00): Welcome, and thanks for your edits!

I noticed a few unintended crossings between roads and/or between roads and buildings in this changeset. This usually happens when geometry snaps incorrectly. Additionally, changes to tagging (e.g. modifying highway types or adding tags) can lead to unexpected crossings being detected afterwards.

In total, I detected 53 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/1500669561 v1 | 10 crossings
https://osm.org/way/1500669562 v1 | 7 crossings
https://osm.org/way/1500669565 v1 | 7 crossings

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=181490250
eggie (2026-04-18 10:08:00+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privebericht.
Feedback  Je hebt de doolhof nu 2x op de kaart gezet en het bos verwijderd.
De tag voor doolhof is dan attraction=maze
De dubbele vermelding zal ik verwijderen


MVG,
Eggie
Namens de OSM Community
eggie (2026-04-19 09:06:16+00:00): Wanneer er iets staat dat op gras lijkt dan landuse=grass  Solitaire bomen kun je dan toevoegen op een node met natural=tree.
Gewoon op het klembord zetten en dan steeds plakken.
Op vlakken tag ik geen access=private. 
Volgens de wiki mag het wel. Wel evt op de paden als dat staat aangegeven.

Gr eggie
NeisBot (2026-04-18 09:51:40+00:00): Welcome, and thanks for your edits!

I noticed a few unintended crossings between roads and/or between roads and buildings in this changeset. This usually happens when geometry snaps incorrectly. Additionally, changes to tagging (e.g. modifying highway types or adding tags) can lead to unexpected crossings being detected afterwards.

In total, I detected 33 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/1500692406 v1 | 5 crossings
https://osm.org/way/1500692405 v1 | 3 crossings
https://osm.org/way/1500692344 v1 | 3 crossings

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=181490505
NeisBot (2026-04-18 09:51:43+00:00): Hello, welcome and thank you for your contribution to OSM!

Your changeset was commented because your added description, note or slogan contain detailed text that may be interpreted as promotional or SEO-related. To ensure OSM remains neutral and focused on map data, I recommend keeping descriptions concise, factual, and free from marketing or promotional language.

⚠️️ Problematic element (limit 1):
https://osm.org/node/13739510691 v2

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Animal boarding facility"

#MapWithoutSpam
eggie (2026-04-18 10:12:06+00:00): Het adres stond er nu 3x op.
Van de gebouwomtrek heb ik het verwijderd.

MVG
eggie
JhowieNitnek (2026-04-18 15:10:15+00:00): The tunnel does have a name, https://databrussels.be/en/id/streetname/4655 this is the official name reposetory of street, stations tunnels etc in Brussels
bxl-forever (2026-04-18 17:05:42+00:00): This is a long-standing problem with UrbIS data (which has been copied into the BeSt address register).  They use descriptions, which have been (imho incorrectly) transcribed into the same text fields they use to name streets.  This is why this description looks like "an official name for the tunnel".  Current practice on OSM is that names are not descriptions.  I understand that it’s difficult when there are official databases around that look like they gave it a "name".
JhowieNitnek (2026-04-18 20:54:43+00:00): I see your point, and I agree that descriptions should not be treated as names in principle. That said, in this case it still appears to function as a name: unusual and descriptive, yes, but presented in the source data in the same way as other official names, which makes it difficult to interpret it otherwise.
RaphaelPasloin (2026-04-19 08:51:55+00:00): This revert is for my point of view not faulty , i will try to explain : 

- Best address dataset is for "address" (yes it's self referecence but let's me explain not for geographical name or something else see  the UML of the EU directive : https://inspire-mif.github.io/uml-models/approved/html/ (annex 1)  and this dataset : https://datastore.brussels/web/data/dataset/a8c9ccde-5c2b-11ed-913a-900f0cda5d5c#quality is for address nothing else ! 

https://datastore.brussels/web/data/dataset/a8c9ccde-5c2b-11ed-913a-900f0cda5d5c#quality

The fact they also use other referential is a "abuse" of the uml model, or saying in another manner , they need it to construct their dataset but it's not an authorative data ; only " Avenue du Parc Royal 61
Koninklijk Parklaan 61 " is a authorative data (subject if exist or not it's another debate but there is a lot of inexisting address on the dataset)

The geographical name etc is another thing (there is some data in urban brussels , brussels mobility etc) but with caution as they all use the same source

Just one exemple : https://databrussels.be/en/id/streetname/2199

We all agree that we will not name it Inconnu (Tunnel SNCB) - Ongekend (Tunnel NMBS)

And as i have already explain street name, place name are given under only one authority : Municipality, i doubt we can find 1 decision of naming theses tunnel metro.

Have a good day.
Raphael
JhowieNitnek (2026-04-19 08:56:21+00:00): These names don't fall under the municipality but the Region, like the region decides the names of the metro station and road tunnels
LordGarySugar (2026-04-23 19:19:43+00:00): Hi, I'm not sure what happened here but quite a few ways got duplicated, I've run the validator over this area so hopefully I've removed them all now, e.g. duplicate hedges, streams and farm tracks. Maybe you know something
Thingummy (2026-04-24 10:35:14+00:00): Thanks for that, I remember a couple of glitches, where it said "another member has amended your changes" and gave my own name." Then crashed when I put in "save mine" quite a few times. I reopened and reloaded about 10 minutes later. I guess, two (maybe three) duplicate caches were produced, and two ended being updated. I had Co-pilot check the Changeset number, and usedOsm inspector just now, they say no issues now, but that's about all I know how to do. Thanks for resetting them.
9_tab (2026-04-18 10:50:32+00:00): Any idea why https://www.openstreetmap.org/way/1500181260 was deleted? MFlamm work on this complex, messy and continuously changing location yesterday, presumably after a careful surveys he is known for.
d_berger (2026-04-18 22:42:10+00:00): It's not complex, it's a construction zone, that's daily business in OSM. Also, we're both mapping for over 10 years and exchanged our modus operandi a few days ago.

He knows how to contact me, if I made an error. Also, neither of us requires a block warden. You theorize; instead you should have figured out, that merging objects in OSM results in the deletion of all objects but one. Simple as that.
9_tab (2026-04-19 11:14:44+00:00): Good to hear — a simple explanation is always helpful. I think remote edits should generally be reviewed locally.

Please allow me to be skeptical about daily edits by PT mappers: we don't all agree about the quality of the sources they use or the assumptions about the sources' information content. Local editors tend to know when a bus route would cross a bridge that was removed years ago.

Just a word of caution: even if this is routine in theory, the reality on the ground at this location had not matched our map for some time. Gladly, MFlamm ventured to fix it — I personally didn't feel comfortable doing so.
VicWM (2026-07-06 00:17:23+00:00): hey, just wanted to let you know you still need the highway=* as a road type and then can add the junction=roundabout tag :) 
https://wiki.openstreetmap.org/wiki/Tag:junction%3Droundabout
Thanks!
bernward1 (2026-04-18 16:37:46+00:00): Der Fahrweg des Taxibus 822 ist nicht mehr zusammenhängend. Ich habe den Fehler durch Changeset 181506772 behoben. (zwei Wegabschnitte waren in der Relation verrutscht.)
Bitte zukünftig darauf achten, dass keine Lücken in den Fahrwegen der Buslinien entstehen.
BrummsLee (2026-04-19 10:47:27+00:00): Danke für die Korrektur!
Das war nicht meine Absicht, da etwas an der Buslinie zu zerschießen. Sorry!
Hab das gar nicht gemerkt, daß da ne Relation mit involviert war, sonst hätte ich es gleich mit korrigiert.
silversurfer83 (2026-04-19 19:06:13+00:00): Moin Paul und herzlich willkommen bei OSM :)

du hast darum gebeten, dass sich jemand diese Änderung ansieht. Mach ich mal.

Sieht ganz gut aus.

Zwei Kleinigkeiten:

- Die Fläche natural=sand sollte nicht mit dem Pfad verbunden sein.

- Die beiden neuen Pfade hast du aktuell als highway=footway erfasst. Ich würde aus der Ferne eher zu highway=path tendieren, da footway in DE ein VZ239 impliziert.

Bei Fragen immer raus damit

happy mapping

silversurfer83
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/181493074
SuperPaul5000 (2026-04-21 13:58:56+00:00): Hallo Silversurfer,

Danke, dass du dir meine Änderungen angeschaut hast. Deine 2 genannten Punkte habe ich angepasst. 

changeset: 181628955

LG Paul
geomaniX (2026-05-18 18:50:33+00:00): Moin!
Du hast hier drei Fahnenmasten erstellt (vgl. https://wiki.openstreetmap.org/wiki/DE:Tag:man_made%3Dflagpole) und diese "Poller" genannt.
Zwei Sachen: 
- Ein Fahnenmast mitten auf den Straßen ergibt nicht wirklich Sinn. Aufgrund der Namen vermute ich mal, dass es ein Poller werden sollte? Das Tag dafür ist allerdings barrier=bollard (siehe https://wiki.openstreetmap.org/wiki/DE:Tag:barrier%3Dbollard).
- Ein Name wird nur vergeben, wenn es auch der offizielle Name ist (https://wiki.openstreetmap.org/wiki/DE:Namen#name_ist_nur_der_Name). Poller ist hier allerdings nur beschreibend und in diesem Fall nicht benutzt.

Aus den Tags des Changesets sehe ich, dass du Organic Maps zum Mappen benutzt. Die App ist dafür nicht wirklich entworfen worden und in der Hinsicht leider sehr schlecht, so dass ich nur abraten kann, diese zum Mappen zu benutzen.
Viel geeigneter ist OsmAnd (das durch die OSM-Erweiterung auch kostenlose Kartendownloads ermöglicht), StreetComplete, Every Door oder Go Map!!.

Bei Fragen einfach melden!

VG 
geomaniX
Supaplex (2026-06-18 05:47:43+00:00): Hi YuiChan

We received a report about your edit, which is sometimes not reasonable, and some mappers reach out to you ask what happened. Here is the list:

    osm.org/changeset/181493395
    osm.org/changeset/178454873
    osm.org/changeset/166955635
    osm.org/changeset/166955173
    osm.org/changeset/165941591

You don’t respond to any of them. That is not ok for a collaborative project, OpenStreetMap. We will block you for your non-response.

If you have any questions, you can email data@osmfoundation.org, contains “Ticket#2026061710000122” in the subject field.

German Translate by Google Translate

Hallo YuiChan,

wir haben eine Meldung über Ihre Bearbeitung erhalten, die teilweise nicht nachvollziehbar ist. Einige Kartennutzer haben Sie kontaktiert, um den Grund zu erfahren. Hier ist die Liste:

osm.org/changeset/181493395

osm.org/changeset/178454873

osm.org/changeset/166955635

osm.org/changeset/166955173

osm.org/changeset/165941591

Sie haben auf keine dieser Meldungen reagiert. Das ist für ein Gemeinschaftsprojekt wie OpenStreetMap nicht akzeptabel. Wir werden Sie aufgrund Ihrer fehlenden Reaktion sperren.

Bei Fragen können Sie eine E-Mail an data@osmfoundation.org senden. Bitte geben Sie im Betreff „Ticket#2026061710000122“ an.

Dennis Raylin Chen, Data Working Group, OpenStreetMap Foundation

data@osmfoundation.org, [Ticket#2026061710000122]
iandees (2026-04-18 12:40:48+00:00): Hello! I noticed that nodes https://www.openstreetmap.org/node/10789810678, https://www.openstreetmap.org/node/5373066327, https://www.openstreetmap.org/node/794698221, https://www.openstreetmap.org/node/9993648916 were 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/181496662, 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!
kingkingHK (2026-04-18 12:36:30+00:00): Hi there, would you please discuss on e.g. Discord first? NSI is only a collection of the most commonly used tags and has no guarantee on correctness. Specifically, I disagree with using zh+en in `network=`, as see network as a normal tag (i.e. en only) and not a text. (Also, there's an obvious typo in `network:short=`, and missing `network:zh`.)
vectorial8192 (2026-04-18 17:38:46+00:00): I view the entries at NSI to be of some degree of correctness. If anything, I will let the public transport mappers review the NSI presets and then everyone can help update the existing relations to what is really the correct values. This can happen in parallel.
kingkingHK (2026-04-19 03:40:15+00:00): As said, NSI simply collects the most commonly used tags, which can be contradictory or incorrect or include typoes. E.g. `network=九巴龍運 KMB & LW` is also documented in NSI. If you don't have an opinion on networks then I would simply suggest you don't change it.
vectorial8192 (2026-04-19 14:08:16+00:00): Your highly-justified and personally-agreeable complaint fails to explain why iD/NSI only notices issue on E41, but not e.g. E32/E36P.

Also, afaik NSI is not automated, and we may modify NSI presets manually.
Kovoschiz (2026-04-19 18:26:46+00:00): No, they need to removed first https://github.com/osmlab/name-suggestion-index/pull/6283
kingkingHK (2026-05-30 06:13:54+00:00): @vectorial8192

> we may modify NSI presets manually.

Please re-read what I said. And remember not to deny the antecedent.

------------

Quoting you from a previous changeset:

> if the warning system could automatically fix warnings (i.e. blindly accepting the fix proposals) and the fixes were correct, then we all would not even need to be here.

We OSM mappers are needed because warning systems don't know what's actually happening irl. It is only us that can like go there and have a look. Warning systems at most are assistants that point out problems, not executives that actually knows what's up.

------------

See https://www.openstreetmap.org/changeset/183384408

It is about time we actually work on reaching a consensus for `network=`.
vectorial8192 (2026-05-31 08:00:56+00:00): OK, this is seeming going to a dead end.

If NSI preset seems wrong, I hold it; normally this is followed by NSI update proposals. If NSI preset seems right ("have some degree of correctness") then I adopt it. This has nothing to do with what tags are correct.

NSI is clearly for standardization, not for correctness.

It seems @kingkingHK you are disappointed by NSI having wrong preset details rather than me adopting NSI "blindly". I looked at NSI proposal, and thought/concluded it was reasonable. There is no "blindness". I imagine your reaction would be different if NSI got it right, and then I adopted it. Home come such difference?

I generally have low interest in public transport mapping, and only minimally do them as side effects of specific changesets. If anything, you can start/resume the discussion at Discord, though I am less likely to join in.
faraz_munj (2026-06-30 14:41:08+00:00): Thanks for contributing, please don't add duplicate of an existing entry, you are welcome to fix exiting entry and improve on it.
I merged both entries and fixed them for now.
Herwescheluc (2026-04-20 08:46:05+00:00): Guten Morgen!

In OSM gilt die Regel "name only", daher bitte im Wiki (https://wiki.openstreetmap.org/wiki/DE:Namen#name_ist_nur_der_Name) mal nachschlagen, was hier angebracht ist, denn es steht ja alles eigentlich schon in der description.

Und: Darf man hier wirklich im Gebäude überall Rauchen?

Grüße aus Herborn

Andreas
balint36 (2026-05-08 15:36:24+00:00): https://www.openstreetmap.org/way/190936454/
https://www.openstreetmap.org/way/1500720503/
Nem hiszem, hogy olyan jó a magyar vasút teljesítménye, hogy 9 kilométeren át magasvasúttá alakításk át a Környe-Pápa vasútvonalat.
Mirci0k (2026-04-18 11:53:27+00:00): Just for clarity, I added the details from my local knowledge and with some help of the aerial photos, I forgot to add the tag
GinaroZ (2026-06-22 10:51:38+00:00): What is this? https://www.openstreetmap.org/way/1500720753
Zaneo (2026-06-22 11:31:07+00:00): This was a typo/fat finger of tree which auto corrected to tram.

I’ve fixed to tree row, thanks for the catch!
Mirci0k (2026-04-18 11:53:41+00:00): Just for clarity, I added the details from my local knowledge and with some help of the aerial photos, I forgot to add the tag
Troels Arvin (2026-04-18 11:55:27+00:00): The change resolves note 4704608.