piebro/osm-data huggingface dataset:
ftrebien (2026-03-17 15:31:13+00:00): Olá! Sou o principal mantenedor dos dados de pedestres em Porto Alegre. Notei que você está adicionando calçadas separadas em vias onde elas já estavam mapeadas como etiquetas (https://wiki.openstreetmap.org/wiki/Sidewalks#How_to_map), que é o estilo predominante aqui, e também alterando o padrão de mapeamento dos semáforos (https://wiki.openstreetmap.org/wiki/Tag:highway%3Dtraffic_signals#How_to_map). Você está fazendo isso como parte de algum projeto ou organização?
sleep enjoyer (2026-03-17 19:50:31+00:00): Olá! Não faço parte de nenhuma organização. 
Meu interesse é apenas fazer edições no bairro Centro. Não tenho interesse em outros lugares.
A questão de calçadas e etc., era adicionar elementos visuais, inspirado em outras cidades. Parece mais detalhado, mais intuitivo. Mas  é minha opinião apenas.
Nesse sentido, você quer que eu remova esses elementos ou você quer que eu continue?
ftrebien (2026-03-18 02:19:05+00:00): Mapear da forma mais simples (etiquetas na via principal) minimiza o esforço de manutenção e acelera o mapeamento inicial, o que permite informar as ferramentas sobre quais vias têm infraestrutura de pedestre e quais não têm, que é a informação mais importante. Temos uma falta crônica de mapeadores nessa região e no país como um todo; optar pela forma mais complexa tende a deixar o mapa mais difícil de manter, e com isso, desatualizado. O próprio wiki relata que o estilo com calçadas separadas é um fenômeno mais da América do Norte, em boa parte porque lá a maioria das calçadas fica a uma certa distância da pista, separada dela por uma faixa de grama. Então, eu acho que seria melhor remover as calçadas separadas que você mapeou. Note que já existem algumas calçadas separadas em alguns lugares específicos da cidade - eu mapeio separado quando a situação é complexa o bastante pra exigir esse nível de detalhamento. Há ferramentas pra visualizar as duas formas juntas para entender quando é melhor uma ou outra e como conectar as duas.

Para o seu mapeamento fazer uma transição completa de modelo de mapeamento, seria necessário fazer uma série de coisas que você não fez: adicionar footway=sidewalk às vias de calçada, adicionar street:name à calçada com o nome da rua, transferir sidewalk:surface=* das calçadas que já foram mapeadas para surface=* nas novas vias de calçada, remover sidewalk:surface=* das vias principais depois de transferir, definir sidewalk=separate e adicionar foot=use_sidepath nas vias principais. Compare tudo isso com o método atual - a diferença de esforço é considerável

Nesta visualização (https://osm-tiles.james-ross.co.uk/?map=18/-30.0315/-51.2288&layer=standard&layer=overlay&layer=roads) você pode notar que várias vias do centro têm uma borda cinza, que é a calçada já mapeada como etiquetas. É um pouco mais evidente pela cor rosa aqui (https://openstreetbrowser.org/#map=18/-30.03158/-51.22999&basemap=osm-mapnik&categories=footways), mas esta visualização é mais lenta e tem uns bugs de vez em quando. A melhor forma de visualizar as calçadas mesmo é no JOSM com o estilo "Sidewalks" (que mostra calçadas mapeadas dos dois jeitos), mas para isso precisa aprender a editar o mapa com o JOSM, que exige um pouco de dedicação.
ftrebien (2026-03-18 17:53:44+00:00): Obrigado por remover as calçadas duplicadas. Me avise se você pretende restaurar os 43 semáforos removidos, senão eu restauro. 36 deles identificavam onde havia também travessia de pedestre controlada por semáforo.
JakovRajić (2026-03-17 15:18:36+00:00): Used wrong unit, fixed in changeset/180013217
NeisBot (2026-03-17 14:09: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 18 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/31065384 v14 | 10 crossings
https://osm.org/way/819726301 v2 | 8 crossings

⚠️ Dragged Nodes (max 3):
https://osm.org/node/7655138779 v2

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=180009727
iandees (2026-03-17 15:23:28+00:00): Hello! I noticed that node https://www.openstreetmap.org/node/7655138779 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/180013475, 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!
woodpeck_repair (2026-06-11 08:58:37+00:00): This changeset has been reverted fully or in part by changesets 183960337, 183960380, 183960341, 183960408, 183960275, 183960389, 183960221, 183960319, 183960306, 183960280, 183960292, 183960414, 183960349, 183960228, 183960252, 183960358, 183960240, 183960299, 183960267, 183960399, 183960370, 183960328, 183960364 where the changeset comment is: revert low-quality AI building imports
woodpeck_repair (2026-06-11 09:13:01+00:00): This changeset has been reverted fully or in part by changeset 183960779 where the changeset comment is: revert low-quality AI building imports
one_electro_dan (2026-03-17 15:18:13+00:00): Changeset comment should actually say "Updated Faleza Tulcea"
eggie (2026-03-17 16:22:18+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
JakovRajić (2026-03-17 15:23:22+00:00): Used wrong unit and missed a segment, fixed in changeset/180013418
NeisBot (2026-03-17 14:18: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 18 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/99877468 v4 | 10 crossings
https://osm.org/way/432465939 v4 | 3 crossings
https://osm.org/way/432465944 v3 | 3 crossings

⚠️ Dragged Nodes (max 3):
https://osm.org/node/4315059955 v3

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=180010217
NeisReview (2026-03-25 17:33:27+00:00): ✅ Should be fixed by 
https://osm.org/changeset/180115410
JakovRajić (2026-03-17 15:25:25+00:00): Used wrong unit, fixed in changeset/180013549
fredlenoir (2026-06-01 09:17:50+00:00): Bonjour, a mon avis, le début et la fin de la route doit être maintenu en hihway: unclassified. Actuellement, l'itinéraire vélo est coupé  (pas de continuité) après la barrière. je propose de couper l'ancienne voirie en 2 et de garder les bouts. entre ces 2 troncons, on retrouve la piste cyclable qui doit être taggée selon le panneau F99aou c
ToniE (2026-03-21 12:03:51+00:00): Hallo,

Du hast hier die Baustelle "Sauerlacher Straße" in Deisenhofen wieder als highway=residential (statt construction) und auch die Straßenbegleitenden Fußwege als nutzbar hinterlassen. Die sind alle bis Ende November 2026 gesperrt (mit Ausnahmen: Anlieger, ...).

Das würde ich gerne wieder in den vorherigen Zustand versetzen.

BTW: "swmhlea", steht "swm" für "Stadtwerke München"?

Gruß,
Toni aus Ottobrunn

war am Donnerstag erst wieder vor Ort und hatte auch diesbezüglich Kontakt zur Gemeinde Oberhaching.
swmhkarto (2026-03-23 08:58:21+00:00): Hallo Toni,

tut mir leid, das wusste ich nicht. Gerne kannst du das korrigieren.
 
Es handelt sich um die SWMH GmbH. 

Liebe Grüße :)
ToniE (2026-03-23 09:25:41+00:00): Servus, danke und: "alles gut".

Bzgl. "SWMH GmbH":

Für den Fall, dass jemand im Auftrag einer Firma bei OSM tätig ist bitten wir als Community um die Beachtung einiger Regeln:

- Organisiertes Mappen 
https://wiki.openstreetmap.org/wiki/DE:Organised_Editing_Guidelines

- Automatisiertes Mappen 
https://wiki.openstreetmap.org/wiki/DE:Automated_Edits_code_of_conduct

- Import von Daten aus anderen Quellen https://wiki.openstreetmap.org/wiki/Import/Guidelines

Und natürlich immer wieder: die Lizenz der genutzten Daten beachten https://wiki.openstreetmap.org/wiki/DE:Import/Guidelines#Schritt_3_-_Lizenz_absichern

Z.B. sind "Google" und andere kommerzielle Quelle und sogar der "Bayern-Atlas" als Quelle tabu.

Viel Spas noch. Liebe Grüße
Toni
NeisBot (2026-03-17 14:27:42+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 35 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/1489791902 v1 | 35 crossings

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=180010689
Wildsharky (2026-03-25 10:32:53+00:00): Reverted in changeset id:180047223
mcliquid (2026-03-17 16:30:11+00:00): Die Ergänzung von bicycle und foot "yes" ist in dem Fall unnötig. Siehe dazu: https://wiki.openstreetmap.org/wiki/OSM_tags_for_routing/Access_restrictions#Germany
matthewsheffield (2026-03-22 00:54:12+00:00): Hi, I hope you are well. I noticed you changed the description of Mernda Community Hospital to "healthcare speciality: urgent" from "emergency:type :urgent_care", I would be interested to know why you did this? If you don't know the site also has dental services, mental health, dialysis, pharmacy, radiology and other allied health. None of these are provided on an urgent care basis. I had set it so that it displayed the state of it's emergency department provision correctly. What do you think?
matthewsheffield (2026-03-22 00:55:16+00:00): Oh, actually, radiology is part of urgent care, but, that's by the by.
mueschel (2026-03-22 09:40:26+00:00): Hi,
"emergency:type" is not used as a tag in any place around the world. 
It doesn't convey any of the details you added above and is very unlikely to be understood by any software making use of OSM.

"healthcare:speciality=urgent" is documented, and doesn't have any implications on which services are provided. 
healthcare:speciality can take a list of values to add all the facilities available - it doesn't mean that this is the one and only speciality of the hospital.
matthewsheffield (2026-03-25 06:36:03+00:00): Okay, that sounds reasonable. I found that tag somewhere online, but I agree with your reasoning, especially about rendering. Thanks.
NeisBot (2026-03-17 14:36:42+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/13655141482 v1

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Will writing office"

#MapWithoutSpam
NeisReview (2026-03-25 17:33:13+00:00): 👍 Thank you for updating the element by https://osm.org/changeset/180035612
pitscheplatsch (2026-05-19 20:01:49+00:00): Reverted by https://www.openstreetmap.org/changeset/182896267
Kovoschiz (2026-03-18 13:42:07+00:00): The gore sections shouldn't be parallel. They reflect how they are angled. It's not realistic to make it parallel, then suddently angled at the tip.
小智智 (2026-07-27 23:14:00+00:00): Sorry you have joined paths which are at different levels in the real life and it results in level jumping in the routing engine near Kings Cross. Please don't do that again.
Vandana@28 (2026-07-28 10:13:35+00:00): Hi, 
I acknowledge and thank you for the feedback.
NeisBot (2026-03-17 15:21: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/way/74457804 v5

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Granite showroom"

#MapWithoutSpam
NeisRevert (2026-03-25 17:33:16+00:00): 🔄🤖 Partly reverted due to either a lack of response from the contributor or remaining promotional text by https://osm.org/changeset/180419525
(Restore previous tags. No changes)
eggie (2026-03-17 16:35:37+00:00): Hoi...  Zorg wel dat al je [paden een verbinding hebben met de hoofdrijbaan.
Hier zit je pad aan de landuse grass vast ipv aan het Rooseveltplein. 
MVG
eggie
eggie (2026-03-17 16:37:45+00:00): Pad doorverbonden
Je edits https://overpass-api.de/achavi/?changeset=180013541
NeisBot (2026-03-17 15:36:44+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/13655266616 v1

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Floating dock"
---
Zum Beispiel könnte eine neutralere und sachlichere Version deines Textes lauten: "Schwimmender Dock"
---
(Auto-translation)

#MapWithoutSpam
NeisReview (2026-03-25 17:33:19+00:00): 👍 Thank you for updating the element by https://osm.org/changeset/180014745
NeisBot (2026-03-17 15:39:49+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/11832175784 v2

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Car repair shop"
---
Ví dụ, một phiên bản trung lập và khách quan hơn của văn bản của bạn có thể là: "Cửa hàng sửa chữa ô tô"
---
(Auto-translation)

#MapWithoutSpam
NeisRevert (2026-03-25 17:33:22+00:00): 🔄🤖 Partly reverted due to either a lack of response from the contributor or remaining promotional text by https://osm.org/changeset/180419531
(Restore previous tags. No changes)
Comino (2026-03-17 20:49:41+00:00): Hi,

In your edit you use the tag "payment:cryptocurrencies=yes".

The tag "payment:cryptocurrencies=*" was a payment tag proposal which was rejected by the OSM community. Use this tag only when cryptocurrencies are NOT accepted.
Source: https://wiki.openstreetmap.org/wiki/Proposal:Cryptocurrencies_with_payment_tag and https://wiki.openstreetmap.org/wiki/Key:payment:*#Cryptocurrencies

Please REMOVE the payment:cryptocurrencies=yes !

Thank you.

Happy mapping,

Edwin Comino
BTC Map
https://www.openstreetmap.org/user/Comino
FroschForscher (2026-03-21 21:45:00+00:00): > https://www.openstreetmap.org/way/296746427
> motocar=designated
  (kein "r")="designated"

sollte das motorcar=destination sein?
APneunzehn74 (2026-03-21 22:12:20+00:00): Danke, hab's korrigiert. Und nein ist kein destination, der Platz ist explizit für PKW also motorcar=designated.
iandees (2026-03-17 20:19:45+00:00): Hello! I noticed that nodes https://www.openstreetmap.org/node/6605488244, https://www.openstreetmap.org/node/8236460242 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/180026759, 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!
greatnameguys2472 (2026-03-25 03:15:12+00:00): It also seems like a parking lot service road was accidentally upgraded to primary in this edit. I went ahead and reverted that too
Frans S (2026-03-27 13:30:23+00:00): Hello. Thanks for mapping.
Please do not cluster buildings.
Each building needs to be mapped individually
Please map them accordingly.
Best regards
Frans S (2026-03-27 13:36:30+00:00): And don't include the yard within the walled plots.
https://www.openstreetmap.org/way/1489814820/history#map=19/15.449958/32.478797
Best regards
I removed all clustered buildings.
eggie (2026-03-17 16:24:38+00:00): Dag Sary.. Probeer een manier te vinden om eerst de adresnode te selecteren en dan info bij te taggen.
Organic maakt anders dubbele adressen en bovendien ontbreekt steeds de plaatsnaam.
MVG
eggie
Sarys (2026-03-17 21:48:33+00:00): Dank voor je feedback. In de Organic Maps-app op mijn telefoon kan ik enkel een organisatie toevoegen door het huisnummer aan te klikken omdat de optie om toe te voegen anders niet eens tevoorschijn komt. Ook niet als ik op een gebouw klik. Bij mijn weten selecteer ik daarmee al zo precies mogelijk. Omdat we met verschillende tools werken kan ik me voorstellen dat het resultaat er anders uit kan zien. Organisaties voeg ik op momenten toe wanneer ik er bijvoorbeeld net geweest ben en dan is mijn mobiel het meest praktische daarvoor. Anders vergeet ik het toe te voegen op momenten dat ik wel achter de laptop zit. Heb je een tip hoe ik het via mijn mobiel beter kan aanpakken? Is er bijvoorbeeld een betere app voor?
eggie (2026-03-17 21:54:04+00:00): Hoi... nou eigenlijk niet.
Alle gebruikers hebben dit probleem bij iets nieuws toevoegen.
Maar een bestaande adresnode bewerken gaat dan weer wel?
Sommigen passen het later aan met een reguliere editor op de pc.
Je zou het eens kunnen opwerpen op het forum van osm. Wie weet of iemand een oplossing heeft?
Mapse,
eggie
NeisBot (2026-03-17 16:09: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 24 potential crossings.

⚠️️ Problematic elements (top 3):
https://osm.org/way/1410047964 v3 | 14 crossings
https://osm.org/way/1195269007 v1 | 8 crossings

⚠️ Dragged Nodes (max 3):
https://osm.org/node/11093656410 v3

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=180015819
iandees (2026-03-17 20:20:59+00:00): Hello! I noticed that nodes https://www.openstreetmap.org/node/11093656410, https://www.openstreetmap.org/node/9735573040 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/180026794, 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!
Frans S (2026-03-27 13:09:26+00:00): Hello. Thanks for mapping.
Very accurate mapped.
Just a remark. When you see constructions with visible walls, but no roof, you can map these as building=construction + construction=building.
Best regards and keep mapping
Frans S (2026-03-27 12:43:41+00:00): Hello. Thanks for mapping.
Please tag buildings just as building=yes when you map for HOTOSM. Details will be added by local mappers with local knowledge,
Just map the buildings themselves instead of a complete plot, including the yard.
Best regards
dzidek23 (2026-03-19 12:06:03+00:00): That's a great edit. One thing to note is that paths must be connected to another routable object (another path or a road), otherwise we could not navigate through that path (not like we probably would in this place).

I made some small additions and reduced the size of the church yard. Don't know if you are aware there are OSMUK Cadastral Parcels available in the Backgrounds/Overlays menu. They show exact size of the plot, be it a church or private property. Sometimes it is helpful to establish where paths or service roads are.
dzidek23 (2026-03-19 12:08:13+00:00): Also, you might wonder how do people know what has changed in the area, there's a handy tool for that:

https://tyrasd.github.io/latest-changes/#12/52.5833/-0.2682
Colbertson (2026-03-17 19:03:21+00:00): Changes look good, thanks for mapping a previously missing church.
Colbertson (2026-03-17 19:04:37+00:00): e: nvm the church was previously a node and i didnt notice. still good changes though
markalex- (2026-03-17 19:49:01+00:00): Two notes about address tags:
1. As far as I understand, introduced addr:* tags will be striped by latvia-bot on next run, since ref:LV:addr=* is not present.
2. Is house number correct? Previously same place had house number 51 (which again was stripped by bot). It seems like 51 was assigned to structure that was where https://www.openstreetmap.org/node/9834190253 now, so I wouldn't say that it is an immediately obvious correct number either.
ronery-mapper (2026-03-17 21:03:21+00:00): 1) ref:LV:addr added;
2) Yes, it's Brīvības iela 49, būve nr. 38010020009008 according to kadastrs.lv data.
ronery-mapper (2026-03-18 11:04:24+00:00): Latvia-bot removed all addresses and ref:LV:addr altogether, why?
HellMap (2026-03-18 11:44:18+00:00): The short answer is because the official address point location is not on the church building, but away from it on a (non-existent/new) building outline in cadaster. It also looks like 51, not 49, which is already assigned to the building west.
ronery-mapper (2026-03-18 11:47:02+00:00): Well, it is 49 in cadaster though...
HellMap (2026-03-18 12:09:40+00:00): The bot uses address data from https://data.gov.lv/dati/dataset/varis-atvertie-dati , which doesn't have these cadastral address assignments directly, just one address per location and the bot tries to place it at that location. I personally agree with you that the bot should not remove this, I'm just not sure how to implement this. Normally, the land owner is supposed to request VZD to fix the location. I'd like there to be a distance threshold in bot's logic to allow someone to manually "assign" a building on OSM. Or it could involve the bot parsing something like https://data.gov.lv/dati/dataset/kadastra-informacijas-sistemas-atvertie-dati/resource/2aeea249-6948-4713-92c2-e01543ea0f33 which I believe has data for each building. You'd need to talk to the bot author (on Zulip or something), I don't really know more technical details.
ronery-mapper (2026-03-18 12:14:30+00:00): As long as it doesn't remove the name I'm fine with it.
letsridebikes (2026-03-17 16:25:17+00:00): Reported. See https://github.com/streetcomplete/StreetComplete/issues/6776
letsridebikes (2026-03-17 22:42:00+00:00): see also https://community.openstreetmap.org/t/bt-telephone-kiosk-data-inadvertently-wiped-by-streetcomplete/142413