piebro/osm-data huggingface dataset:
viloan (2018-01-12 11:23:17+00:00): Bem-vindo(a) ao OpenStreetMap e parabéns pela sua primeira edição! :-)

Se você está mapeando por causa do Pokémon, dê uma olhada em https://blog.openstreetmap.org/2017/12/01/dicas-para-novos-mapeadores-pokemon-go/?lang=pt-pt

Também temos um portal brasileiro sobre o OpenStreetMap, com várias informações úteis em https://wiki.openstreetmap.org/wiki/Brasil

Enquanto você está se acostumando com o OpenStreetMap, é recomendado que sempre pergunte aos usuários mais experientes antes de remover ou modificar objetos do mapa, especialmente aqueles que são aparentemente "estranhos" ou "fora do lugar".

Além disso, pedimos que não copie dados de mapas proprietários (como nomes de ruas do Google Maps, por exemplo) e que mapeie apenas o que existe na realidade.

Se tiver qualquer tipo de dúvida você pode entrar em contato com a comunidade brasileira através de algum dos canais disponíveis em https://wiki.openstreetmap.org/wiki/Pt:Contact
O canal "Comunidade" do Telegram costuma ser o mais movimentado.

Abraço e boa diversão com suas edições!
John-O (2018-01-16 19:14:54+00:00): Hello!
            I reviewed your changeset on OSMCha and it looks great!
            Thank you very much for your contributions to OpenStreetMap!
            #REVIEWED_GOOD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/55377106
gurglypipe (2018-01-16 19:18:40+00:00): I wish OSMCha wouldn’t do that.
gurglypipe (2018-01-16 19:21:03+00:00): https://github.com/mapbox/osmcha-frontend/issues/248
viloan (2018-01-12 11:43:28+00:00): Bem-vindo(a) ao OpenStreetMap e parabéns pela sua primeira edição! :-)

Se você está mapeando por causa do Pokémon, dê uma olhada em https://blog.openstreetmap.org/2017/12/01/dicas-para-novos-mapeadores-pokemon-go/?lang=pt-pt

Também temos um portal brasileiro sobre o OpenStreetMap, com várias informações úteis em https://wiki.openstreetmap.org/wiki/Brasil

Enquanto você está se acostumando com o OpenStreetMap, é recomendado que sempre pergunte aos usuários mais experientes antes de remover ou modificar objetos do mapa, especialmente aqueles que são aparentemente "estranhos" ou "fora do lugar".

Além disso, pedimos que não copie dados de mapas proprietários (como nomes de ruas do Google Maps, por exemplo) e que mapeie apenas o que existe na realidade.

Se tiver qualquer tipo de dúvida você pode entrar em contato com a comunidade brasileira através de algum dos canais disponíveis em https://wiki.openstreetmap.org/wiki/Pt:Contact
O canal "Comunidade" do Telegram costuma ser o mais movimentado.

Abraço e boa diversão com suas edições!
Colin Smale (2018-01-12 13:57:50+00:00): Hi.... You might not be aware of this but these edits to the rivers are screwing up the admin boundaries... Can you please ensure the boundaries are complete and correct again? Example here: https://www.openstreetmap.org/relation/4253482

Any questions, please get in touch. Otherwise I expect this damage to be repaired quickly...
hornbydd2 (2018-01-12 15:08:04+00:00): Hello,

I followed your link and if I have understood correctly my attempts to update the river network by breaking it at junctions is loosing the relationship with the parish boundary? 

I have stopped my bulk editing and update until I can work out how to resolve this.

It looks like my edits are only affecting the streams that are also tagged as a parish.

If someone added back the parish boundary and left the new junctions as-is then this won't upset what I am doing.
Colin Smale (2018-01-12 15:30:27+00:00): It looks like where you split a way, the "old" half (which retains the original ID) is OK but the "new" part (which gets a new ID) does not inherit the relation membership. You need to make sure the relation membership is copied over. Potentially it is not just parishes, but any relation - including waterways.

As it is you that is breaking things, I think it should be you who fixes it... What is actually your goal with these edits?

Hint: if you look here in after about 1100UTC tomorrow you should see some affected admin boundaries showing up, but as I said, there may be other relations getting broken by these edits.
http://www.loach.me.uk/osm/boundaries/
SK53 (2018-01-12 16:23:39+00:00): In general such topological changes should not be done in OSM. Ideally you should create a post-processing chain which does the splits as required (large numbers of routing tools already do this for road networks). Not only is the risk of breaking other things as pointed out above; but breaking a stream into many little sections tends to make it much harder for people editing to work with. In general changing OSM data to make it easier to consume can also make it harder to maintain: it is thus usually frowned on.
hornbydd2 (2018-01-12 16:50:50+00:00): I have found a plugin in JOSM that allows me to revert changes, I'm running this in the hope this undoes my edits. Interesting argument SK53, I look at the river data and a see an unusable topological nightmare. I was attempting to improve it so that it can be used by the wider scientific community for hydrological analysis free of licensing issues. OS OpenRivers is not perfect and I wanted to improve OSM.  Does the idea of a "post processing chain" not break the ideology of OSM in that you feed back and improve the dataset? If I take a snapshot, improve it then no one else can share the benefits if I don't upload it?
Paul Berry (2018-01-12 17:02:26+00:00): I don't know what your exact aims are, so forgive my question, but can you not use relations to better organise the waterways? Example of my own here: https://www.openstreetmap.org/relation/7851221
SK53 (2018-01-12 17:05:52+00:00): We probably ought to find a way to continue discussion elsewhere as this could be long-winded, I've long had trying OSM for hydrography models on my todo list (see http://sk53-osm.blogspot.co.uk/2014/02/floods-of-transient-data.html). The best way is to publish post-processing tools/code as open source so that anyone can do it. It's also possible to create a versioned curated extract; something I do for a couple of data sets on github (e.g., https://github.com/SK53/ua2 which is relatively complex post-processing & https://github.com/SK53/Irish-Vice-Counties which isn't at all, but versioning and consistency are needed). You can contact me by email on SK53 dot osm at gmail dot com.
hornbydd2 (2018-01-12 19:01:34+00:00): I believe I have been able to revert my changes that I made today.  I want to go away and discuss with others what next step should be. I'm personally for editing OSM so there is one definitive version that everyone can benefit from. Having snapshots with considerable post processing squirrelled away in github or any other site is something I would like to avoid.
SK53 (2018-01-12 19:14:22+00:00): Many thanks for that.

The post-processing step is what all road routing engines do. See the recent email from Frederik Ramm on talk-gb.

It's also unlikely that you can guarantee that any additional data added will be in a topologically convenient form, or that editors will leave your split streams as is. In other words it's always best to plan for data which is not always in the most convenient format when consuming OSM data. Do drop me an email I'm interested in exploring the options.
Colin Smale (2018-01-13 17:09:38+00:00): Unfortunately it appears your reverts were not complete... And now another user (FvGordon) has started to patch up the admin boundaries but I have no idea if they are fixing ALL the broken relations. That may now complicate the revert process, This is starting to become a proper mess.

Take a look at http://www.loach.me.uk/osm/boundaries/ to see where boundary relations are affected. It is a lot of work to check and fix everything!!!
FvGordon (2018-01-14 00:43:46+00:00): Hi.. This evening I saw that many errors on http://www.loach.me.uk/osm/boundaries/ and started repairing the broken boundaries. After having repaired half of them, I saw this changeset and this discussion. Until now I have checked/repared the whole list on that site. Let's see, what errors will be shown on the next run of this tool tomorrow.
Colin Smale (2018-01-14 10:16:40+00:00): Thanks for engaging here. Could I ask you to explain your process for this? Where do you source the knowledge to make the right repairs? I have seen a couple of cases where the admin boundaries have been fixed, but other relations (for example type=waterway=river are not. My opinion is that the person who breaks these things should be given the opportunity to fix them as well - not only because it is their responsibility, but also because they need to learn something. As you know reverting a whole changeset is made much more complex when the objects have been edited in the mean time, and you seem to be on a hair-trigger sometimes, fixing stuff very quickly after it gets broken. Have you thought about having a cooling-off period of (say) 24 hours? You cannot have local knowledge of all the things you fix, so it is only fair that people who do (including the 'breaker') are given a chance as well.
FvGordon (2018-01-14 10:35:07+00:00): When there is a gap in a boundary outline ring, I can see both ends of the gap. Often a segment from an other boundary relation fits to close the gap or (in this case) the river, that he has split.
This morning I have repaired all gaps in type=waterway relations south and south-west of London. I have left type=waterway relations with gaps south east of London which he can repair.
hornbydd2 (2018-01-14 13:24:27+00:00): I'm showing naivety here, I've never seen this website (http://www.loach.me.uk/osm/boundaries/) before. I was expecting to see my [offending] username all over it as someone who has broken a relationship. I was not able to find myself on it and a lot of the areas appear to be elsewhere in the UK. How does one identify the relationships I broke but may have not been fixed by the revert process? In my total ignorance it seems like there is nothing for me fix, but I guess I'm not using this website correctly?
Colin Smale (2018-01-14 13:56:16+00:00): Hi,
The reason your name is not here, is that you have NOT updated the relation when splitting a component way - and this is the exact problem. The fact that a component way (or node) has changed, does not change the relation itself. This is one of the "quirks" of OSM. However a relation in this list is there because it is considered "broken," usually because of a geometrical issue like not being a complete ring.

I notice the list is empty again now - for a large part thanks to FvGordon.
viloan (2018-01-12 11:49:55+00:00): Bem-vindo(a) ao OpenStreetMap e parabéns pela sua primeira edição! :-)

Se você está mapeando por causa do Pokémon, dê uma olhada em https://blog.openstreetmap.org/2017/12/01/dicas-para-novos-mapeadores-pokemon-go/?lang=pt-pt

Também temos um portal brasileiro sobre o OpenStreetMap, com várias informações úteis em https://wiki.openstreetmap.org/wiki/Brasil

Enquanto você está se acostumando com o OpenStreetMap, é recomendado que sempre pergunte aos usuários mais experientes antes de remover ou modificar objetos do mapa, especialmente aqueles que são aparentemente "estranhos" ou "fora do lugar".

Além disso, pedimos que não copie dados de mapas proprietários (como nomes de ruas do Google Maps, por exemplo) e que mapeie apenas o que existe na realidade.

Se tiver qualquer tipo de dúvida você pode entrar em contato com a comunidade brasileira através de algum dos canais disponíveis em https://wiki.openstreetmap.org/wiki/Pt:Contact
O canal "Comunidade" do Telegram costuma ser o mais movimentado.

Abraço e boa diversão com suas edições!
Viajero Perdido (2018-03-11 17:22:36+00:00): Hi OrcaTheBrave.

Re Hasse Lake Park, it looks like you've confused the concept of "park" vs "forest/wood", as you've re-traced the boundary of the park to follow the forest contours.

But a park boundary is a property boundary, and the previous version was more accurate.  Properties in this area tend to be rectangular, and quite likely the east shore of this lake is private property.

Also, leisure=park in this area isn't appropriate; see https://wiki.openstreetmap.org/wiki/Tag:leisure=park
The original leisure=nature_reserve was more suitable.

I'd suggest reverting these changes.
DD1GJ (2018-01-12 17:54:13+00:00): Revert 55377757 55376827 55376423 55376342 55376117 55376047 55375935 55375691, Pokémon-Vandalismus

http://blog.openstreetmap.de/blog/2017/01/achtung-pokemon-alarm/
vng_me (2018-01-12 19:36:02+00:00): Угловой дом наверное имеет двойной адрес?
DD1GJ (2018-01-12 19:30:29+00:00): Revert 55378268, Friedhof wieder hergestellt

http://blog.openstreetmap.de/blog/2017/01/achtung-pokemon-alarm/
dval (2019-10-07 11:52:21+00:00): Hi, Хмурый! Вы в Александрии заменили service на residential с названиями. Но улицы не понятно к какому н.п. относятся. Это отслеживается здесь http://peirce.gis-lab.info/qa/RU-SVE#addr-street (см. на 4 месте). Также на границу Александрии надо добавить place=allotments, чтобы было ясно, что улица находится здесь. Есть об этом в ОСМ-Вики.
Хмурый (2019-10-09 05:40:40+00:00): Привет, dval. Добавил тег place=allotments на Александрию.
dval (2019-10-09 09:32:34+00:00): Боюсь, этого не достаточно. Поскольку вся Александрия не понятно к какому н.п. относится. У нее не может быть адреса Свердловская обл., кп Александрия. Именованные улицы должны находиться внутри полигона place более высокого, чем allotments. Т.е. надо натянуть на неё границы н.п., которому она принадлежит (вот нашел на сайте поселка "В 2014 году принято решение о включении территории поселка "Александрия" в "Земли населенных пунктов", путем расширения границ с.Гусево"). Place allotment сущ. для того, чтобы различить одинаково названные улицы в пределах одного н.п.
maraf24 (2018-01-14 11:38:11+00:00): Drzewa na cmentarzu nie są parkiem.
DD1GJ (2018-01-12 20:07:06+00:00): Hallo husky99, willkommen bei OpenStreetMap. Ehemalige Geschäfte werden nicht mehr als aktiv eingetragen. Wenn Du das dokumentieren willst, benutze bitte https://wiki.openstreetmap.org/wiki/DE:Lifecycle_prefix

Der Kastanienpark und sein Wegenetz sind sehr unglaubwürdig. Kannst Du das Durch ein Panoramafoto beweisen?

http://blog.openstreetmap.de/blog/2017/01/achtung-pokemon-alarm/
viloan (2018-01-12 12:29:31+00:00): Bem-vindo(a) ao OpenStreetMap e parabéns pela sua primeira edição! :-)

Se você está mapeando por causa do Pokémon, dê uma olhada em https://blog.openstreetmap.org/2017/12/01/dicas-para-novos-mapeadores-pokemon-go/?lang=pt-pt

Também temos um portal brasileiro sobre o OpenStreetMap, com várias informações úteis em https://wiki.openstreetmap.org/wiki/Brasil

Enquanto você está se acostumando com o OpenStreetMap, é recomendado que sempre pergunte aos usuários mais experientes antes de remover ou modificar objetos do mapa, especialmente aqueles que são aparentemente "estranhos" ou "fora do lugar".

Além disso, pedimos que não copie dados de mapas proprietários (como nomes de ruas do Google Maps, por exemplo) e que mapeie apenas o que existe na realidade.

Se tiver qualquer tipo de dúvida você pode entrar em contato com a comunidade brasileira através de algum dos canais disponíveis em https://wiki.openstreetmap.org/wiki/Pt:Contact
O canal "Comunidade" do Telegram costuma ser o mais movimentado.

Abraço e boa diversão com suas edições!
erickdeoliveiraleal (2023-02-10 16:48:34+00:00): voce definiu toda esta via como uma rampa de madeira: https://www.openstreetmap.org/way/552582640/history primeiro que não é toda ela, você precisa dividir a área que é elevada, porque voce deixou tudo como "ponte", segundo, não coloque esses nomes genéricos como "rampa de madeira," quando voce nao souber o nome proprio deixe o campo em branco.
CandidoCunha (2023-02-10 16:57:58+00:00): Isso foi feito anos atrás e na época era sim tudo de madeira. Irei apagar e você poderá inserir como quiser.
adrianojbr (2018-01-15 20:03:56+00:00): olá, thiago. tudo bem? refiz novamente a correção para o formato da igreja nossa senhora do perpétuo socorro. atente que, normalmente, os elementos são desenhados com base na sua cobertura do solo. em construções altas isso fica difícil de observar pelas imagens de satélite, então costumamos desenhar com base no teto e arrastar para onde começa no solo.

o desenho que você fez da igreja incorporava as paredes, por isso precisei corrigir.

abraço.
user_5359 (2018-01-12 20:41:11+00:00): Welcome to OSM! Please notice: the minimum keys for an address is addr:street and addr:housenumber! Can you add the value for the house number, please?
nevw (2018-01-13 02:38:08+00:00): Please shift your business location from the footway to the building that it occupies.
Ceodore (2018-01-12 14:58:17+00:00): Thank you!
mavl (2019-01-21 16:08:28+00:00): This changeset was redacted.
viloan (2018-01-12 13:07:23+00:00): Bem-vindo(a) ao OpenStreetMap e parabéns pela sua primeira edição! :-)

Se você está mapeando por causa do Pokémon, dê uma olhada em https://blog.openstreetmap.org/2017/12/01/dicas-para-novos-mapeadores-pokemon-go/?lang=pt-pt

Também temos um portal brasileiro sobre o OpenStreetMap, com várias informações úteis em https://wiki.openstreetmap.org/wiki/Brasil

Enquanto você está se acostumando com o OpenStreetMap, é recomendado que sempre pergunte aos usuários mais experientes antes de remover ou modificar objetos do mapa, especialmente aqueles que são aparentemente "estranhos" ou "fora do lugar".

Além disso, pedimos que não copie dados de mapas proprietários (como nomes de ruas do Google Maps, por exemplo) e que mapeie apenas o que existe na realidade.

Se tiver qualquer tipo de dúvida você pode entrar em contato com a comunidade brasileira através de algum dos canais disponíveis em https://wiki.openstreetmap.org/wiki/Pt:Contact
O canal "Comunidade" do Telegram costuma ser o mais movimentado.

Abraço e boa diversão com suas edições!
Captain_Spork (2018-01-12 16:33:13+00:00): Hallo Richard,

Ik heb je wijzigingen teruggedraaid in changeset https://www.openstreetmap.org/changeset/55384819

Dit is namelijk niet de manier om een park aan te leggen. Het omzetten van landuse naar leisure=park is niet de bedoeling. Hiermee gooi je effectief data weg van de kaart.

Een park is een uitgestrekt gebied met gras, bomen, paden, eventuele vijvers etc. Een park heeft ook vaak een naam.

Een park map je door een nieuwe polygon te tekenen over de landuse heen als een deken. Deze polygon voorzie je vervolgens van de tags leisure=park en name=Naam van park.

Park edits liggen de laatste tijd onder de loep vanwege de zogenaamde 'Pokemon edits'. Hierdoor is al veel schade ontstaan aan de kaart.

Graag reactie.

Vriendelijke groet,
Mark
Richard Wissels (2018-01-12 17:04:20+00:00): Hallo Mark,
sorry, ik ben redelijk nieuw met het toevoegen van data en de correcties van fouten in de kaart in de lokale omgeving waar ik bekend mee ben. Ik zal voortaan ook de juiste wijzen hanteren. ook zal ik de review optie aanzetten voordat ik nog meer van deze fouten maak. Het betreft hier in ieder geval een park met de naam Rusthoff waarbij het mij opviel dat deze nog geen park tags had. Verder voldoet dit park precies aan de dingen die in uw reactie stonden.
bedankt voor de alertheid.
Met vriendelijke groet,
Richard
Captain_Spork (2018-01-12 18:33:49+00:00): Hallo Richard,

Ik zou zeggen, geef het nog eens een poging :).

Nieuwe polygon tekenen over het gebied. Let er op dat hij volledig losligt en dus nergens aan vastplakt.
Polygon taggen met leisure=park en name=Naam van park

Gaat vast goedkomen.

Groeten,
Mark
zors1843 (2018-01-12 14:02:39+00:00): Beste,
Dit is geen park.  Zie wiki : https://wiki.openstreetmap.org/wiki/Tag:leisure%3Dpark
Gelieve te verwijderen a.u.b.
b-jazz (2018-12-16 04:14:37+00:00): Hi there. I'm curious to know why you are adding things like swimming pools and why someone else added a stereo store to a US census statistical area relation. Was this an accident? If not, please clear it up for me. Thanks.
Nakaner (2018-01-12 13:56:58+00:00): Hello!
            I reviewed your changeset on OSMCha and it looks great!
            Thank you very much for your contributions to OpenStreetMap!
            #REVIEWED_GOOD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/55380081
eggie (2018-01-12 14:54:15+00:00): Welkom bij OSM per PB verstuurd
http://wiki.openstreetmap.org/wiki/Welkom_op_OSM

Probeer svp concreet commentaar te geven bij je edits zodat andere mappers het direct begrijpen.
eggie (2018-01-12 14:57:14+00:00): Gebouwen hebben al adresssen via de adresnode. Ook verder info kan hierop anders komen adressen dubble in de data voor. Ik pas het even aan.
eggie (2018-01-12 14:59:33+00:00): Verder heb je het gebouw ontdaan in een andere changeset van building=yes. Het is dus nu van de kaart verdwenen. Dat zal vast de bedoeling niet zijn.
eggie (2018-01-12 15:27:58+00:00): oke
eggie (2018-01-12 15:16:00+00:00): Deadresgegevens horen niet nog een keer op het gebouw. Mocht het gebouw af zijn dan kan de construction er af en wordt het building = house
eggie (2018-01-12 15:25:22+00:00): Ik draai het even terug naar de oorspronkelijke bagimport. Het is onduidelijk wat je hebt gedaan. De oorspronkelijke huisnummers komen van het kadaster import 2017.
Wanneer het niet klopt zelf doorgeven aan het kadaster.
eggie (2018-01-12 15:26:51+00:00): reverted by changeset 55383180
eggie (2018-01-12 15:32:16+00:00): https://bagviewer.kadaster.nl/lvbag/bag-viewer/index.html#?searchQuery=emmastraat%2017%20aa&resultOffset=0&objectId=0197100000499676&geometry.x=237589.48240052&geometry.y=438501.4745982&zoomlevel=7&detailsObjectId=0197010000499678
ToniE (2018-01-12 13:46:24+00:00): Hallo TheNet1996,

weißt Du zufällig noch, zu welcher Buslinie die Haltestelle gehört?
Evtl. Bus 180: Westfriedhof => Kieferngarten (6264705)?
Der ist der einzige Bus, dder diesen Straßenabschnitt befährt.

Andererseits hat der 180er eine Haltestelle hier: https://www.openstreetmap.org/node/4210342372

Ich arbeite viel an ÖPNV bei OSM, daher meine Frage und mein promptes "Anspringen" auf Deinen Changeset-Kommentar.

https://wiki.openstreetmap.org/wiki/M%C3%BCnchen/Transportation/Analyse

Viele Grüße
Toni
TheNet1996 (2018-01-14 11:35:39+00:00): Hi Toni, die von mir erstellte Buslinie ist die 180er. Komisch, das hatte ich eigentlich eingepflegt?! Ich kann dies aber am Dienstag nochmal prüfen - da bin ich dann wieder vor Ort. LG Michael
TheNet1996 (2018-01-16 20:41:44+00:00): Hallo Toni, die von mir eingepflegte Haltestelle scheint nur eine temporäre gewesen zu sein. Heute war dort keine Haltestelle mehr. Ich werde meine wieder entfernen. VG Michael
ToniE (2018-01-16 22:22:44+00:00): Prima, dann ist ja alles wieder in Butter und nichts muss angepasst werden.
LG Toni
__IK__ (2018-01-12 13:37:41+00:00): I put wrong description by accident. The real edit is "Added Keski-Suomen Viestilaitehuolto Oy computer repair shop to Hämeentie 1.
viloan (2018-01-12 13:36:09+00:00): Bem-vindo(a) ao OpenStreetMap e parabéns pela sua primeira edição! :-)

Se você está mapeando por causa do Pokémon, dê uma olhada em https://blog.openstreetmap.org/2017/12/01/dicas-para-novos-mapeadores-pokemon-go/?lang=pt-pt

Também temos um portal brasileiro sobre o OpenStreetMap, com várias informações úteis em https://wiki.openstreetmap.org/wiki/Brasil

Enquanto você está se acostumando com o OpenStreetMap, é recomendado que sempre pergunte aos usuários mais experientes antes de remover ou modificar objetos do mapa, especialmente aqueles que são aparentemente "estranhos" ou "fora do lugar".

Além disso, pedimos que não copie dados de mapas proprietários (como nomes de ruas do Google Maps, por exemplo) e que mapeie apenas o que existe na realidade.

Se tiver qualquer tipo de dúvida você pode entrar em contato com a comunidade brasileira através de algum dos canais disponíveis em https://wiki.openstreetmap.org/wiki/Pt:Contact
O canal "Comunidade" do Telegram costuma ser o mais movimentado.

Abraço e boa diversão com suas edições!
santamariense (2018-02-17 17:33:59+00:00): Creio que se existem os caminhos de pedestre na praça, eles deveriam ser mantidos no mapa
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/55380508