piebro/osm-data huggingface dataset:
woodpeck (2019-06-30 16:04:37+00:00): @BeKri, @xogalla - das Hinzufügen einer unvollständigen Adresse zu einem Gebäude ist nicht besonders hilfreich. Wenn man den betr. Mapper dabei ertappen würde, dass er diese Information nicht aufgrund von Ortskenntnis hinzufügt, sondern durch "Raten" der nächstgelegenen Straße (da kann man ja durchaus mal schiefliegen, gerade bei Eckhäusern), dann kann man ihm zurecht auf die Finger klopfen. Das reflexartige Löschen unvollständiger Adressen, nur damit irgendein QA-Tool "grün wird", ist aber nicht statthaft - aus den o.g. Gründen (gehört das Eckhaus jetzt zur A-Straße oder zu B-Straße, sind die Häuser an diesem Feldweg postalisch noch hier oder schon dort...) kann auch eine unvollständige Adresse sinnvoll sein. Ich bitte darum, auf solche Löschungen zu verzichten. @opendcc bitte nur dann unvollständige Adressen eintragen, wenn dies aufgrund von Ortskenntnis geschieht - ein Erraten oder automatisches Setzen von Werten aufgrund von Grenz-/PLZ-Polygonen ist nicht erwünscht. Ebenfalls sind addr:*-Tags an Dingen, die keine Adresse haben, wie Briefkästen, Sitzbänken oder Bäumen unerwünscht. @alle, der nächste, der hier nach dem Motto "revertieren kann ich auch" unsere Zeit verschwendet, kassiert eine Sperre. 

Danke für die Aufmerksamkeit   
Frederik Ramm, OSMF DWG
opendcc (2019-06-30 17:18:36+00:00): > @opendcc bitte nur dann unvollständige 
> Adressen eintragen, wenn dies aufgrund 
> von Ortskenntnis geschieht

So ist es. Ich war sicherlich mehr als zehnmal dort, um das auf den Stand vor dem Edit zu bringen. Aber jetzt sind da von den Häusern gelegentlich nur noch unverbundene Eckpunkte übrig. 

 Manchmal tagge ich es mit Papier (noch rollend) und bin mir zuhause doch nicht mehr sicher - wo genau gehört jetzt die 5 hin? Briefkästen, Sitzbänken oder Bäumen habe ich im übrigen noch nie mit addr getaggt (und wenn, dann ist es klar ein Editfehler) - eher schon mit genus:de.

Viele Grüße

Wolfgang
BeKri (2019-07-30 00:34:44+00:00): Hallo Wolfgang, 
1 Monat vergangen, wie weit bist DU ???
Du weist doch, ein ADRESSeintrag beginnt mit der
HausNUMMER !!!
Schon alles nachgetragen ?
Auch in Schätzwinkel schon alles überprüft ?

Wenn Du mir schon unterstellst ich würde Deine Arbeit sabotieren, dann würde ich wenigstens TATEN folgen lassen.
Aber Du bist ja grad mit Anderem beschäftigt ;-))
Wie sieht es mit den paar hundert anderen Einträgen ohne HausNUMMER von Dir aus ?
Wie kommst Du eigentlich vor 2 !!! Jahren (16.12.2016) bei
https://www.openstreetmap.org/way/458120920
auf  Mobil-Oil-Straße obwohl auf dem Luftbild die Ausfahrt zur Haydnstraße geht ?
Sicher warst Du vor Ort, hast Dir aber LEIDER nicht die Hausnummer merken können ...
oder hast Du woanders reingeschaut ??? ;-)) irgendsowas wo wir eigentlich nichts übernehmen dürfen ...
Oder warum kommst Du hier grad auf die Mobil-Oil-Straße ???
So nebenbei ... es ist die 56 ;-)) aber nur so unter uns ...
Wolfgang, wenn Du schon lamentierst ich mache Deine "Arbeit" kaputt,
dann  mach doch BITTE wengsten das umstritten Stadl fertig und kümmer dich um die blöden blauen Knöpfe in Schätzwinkel, BITTE! DANKE !
Alles andere ist doch nur Geheule !

Mit der Hoffnung auf Tatkraft von Dir
derBeKri
opendcc (2019-07-30 03:59:17+00:00): Guten Tag,

erstmal verbitte ich mir die Kopierunterstellung. Ansonsten war ich nochmal in Stadl und Unterreit und habe soweit die Notizzettel und das Gedächtis tragen Nummern, Öffnungszeiten usw. erfaßt. Kannst ja auch mal hinfahren!

Wenn Du im Ampfing die Nummer 56 nachgesehen hast, warum trägst Du das nicht ein?

Auch mit der Hoffnung auf konstruktive Tatkraft von Dir

opendcc
Leo Slager (2019-06-27 23:50:01+00:00): Top
Karthoo (2019-06-28 08:06:51+00:00): Welcome! Thank you for your first edits. Please seperate the housenumber from the street address. And usually we map phone numbers with '-' instead of '.' between the numbers (like +1-234-567-8901). If you have any questions feel free to ask.
freebeer (2019-07-05 08:42:20+00:00): doctor,
the use of the hyphen as separator seems to be something specific to the us or north america.  i am not familiar with international norms, but other countries make local use of parentheses and the forward stroke which give way to a space, or preferably a dot for grouping for readability.

for example in switzerland we had a number which roughly matched the ddd-dddd of the us, but could also and usually was grouped as ddd.dd,dd for better consumption.  i am used to reading the numbers aloud as a series of digits, but it seems the custom in other languages is to speak a pair, a la four-and-twenty blackbirds.

in danmark the grouping i expected was dd.dd.dd.dd, with the full-stop often replaced by a space.  however as a space is also the typical IFS, it is far easier to double-click with a mouse on a phone number written without a space but using the . or, for the us, the - as a grouping separator.

and having a separator makes a huge difference for human parsing, particularly where the grouping follows a pattern.  that is, +1 or +44 localises the number to a country/continent, .212. gives further refinement to an area, then beyond that my memory of phone systems falls to pieces, so that my danmark memory of 80.dd.dd.dd says nowt about any patterns linking numbers to geography.

long story cut short, the dot as separator is what i expect to see, although without an ITU reference to back me up.  the us has its own non-conforming customs, and i applaud anyone dragging them into the 20th century (said a few days after speaking to my sister who did not grok the summer temperatures where i am approaching 40°, despite her science/geography background).

by the way, the example you give of +1.234. ... immediately rings invalid warning bells to me, as a combination of my age and disconnect from technology flags the us area code as invalid.  this is probably no longer true as i have seen so many osm phone numbers breaking my parsing that i need to update my half-century-old wisdumb to modern standards.  perhaps there are still unbreakable rules like the national lampoon yellow pages of 555-xxxx phone numbers that were then invalid.

i really need to a) update me awareness, b) adapt to new technology, or c) abandon this mortal coil.
Karthoo (2019-06-28 08:04:28+00:00): Welcome! Thank you for your first edit. If you have any questions feel free to ask.
viloan (2019-06-27 23:21:13+00:00): Bem-vindo(a) ao OpenStreetMap e parabéns pela sua primeira edição! :-)

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 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
Se você está mapeando por causa do jogo do Harry Potter, as dicas e explicações na página anterior também são úteis para você.

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!
DressyPear4 (2020-09-05 05:31:25+00:00): Olá, evite alterar a classificação de vias sem justificativa.
Evite adicionar áreas de matas exageradas( sobrepondo locais onde nem tem vegetação).
Allison P (2020-02-19 17:06:45+00:00): Should Edgewater be mapped as a city? It certainly doesn't have the population or amenities that would indicate a city. Just because it has 'city' in the name doesn't mean it should be mapped as one; otherwise, all incorporated municipalities in states like Idaho would be cities and the map would be cluttered.
chachafish (2020-02-20 03:04:25+00:00): Hello. Thank you for your question. From my perspective, it is irrelevant whether Edgewater is mapped as a city or not. OSM does not have strict guidelines as to what defines a place as a city. However, OSM does have an "on the ground" rule. Edgewater officially refers to itself as a city, whether people outside the city consider the place a city or not. In addition, the state government of Colorado also considers Edgewater to be a city. Colorado state government has a list of metropolitan districts, towns and cities. In this list, Edgewater is listed as a city. So, using the OSM "on the ground" rule, and based on the definitions used by Edgewater and the state of Colorado, Edgewater is a city. https://www.cleargov.com/colorado https://www.edgewaterco.com
freebeer (2020-02-20 06:29:25+00:00): the `on-the-ground' rule doesn't refer to definitions and terms used by other sites, but to how a disinterested mapper, when confronted by the object in question, would choose to map it in osm terms going by osm definitions.

there are plenty of so-called parks referred to by other authorities that do not qualify as osm urban parks, to pick an obvious example.  the definitions used by these outside authorities are irrelevant to osm, and have nothing to do with the on-the-ground rule that excludes third-party influences.

i have no opinion here as i use everyday words like town or city to refer to things that clearly are not, in casual speech, as for me these are destinations, and not as distinguishing categories.  also different languages distinguish the terms differently, so i say `city' to mean a compact village that is clearly not the surrounding not-village.
highflyer74 (2019-07-02 10:17:42+00:00): Moin hankox und willkommen bei OSM!

Da Du noch neu hier bist, kannst Du nicht wissen, dass wir nicht mehr existierende POIs per https://wiki.openstreetmap.org/wiki/DE:Lifecycle_prefix kennzeichnen, statt sie zu löschen. Dadurch erhält man die Historie eines OSM-Objekts (die beim Löschen verloren geht) und man verhindert (z.B. bei einem Gebäude) dass dieses vom nächsten Mapper wieder eingezeichnet wird, weil er es noch auf irgendeinem Luftbild sieht.

Auch die von Dir erstellten Notes (Fehlermeldungen) solltest Du schliessen, wenn Du sie erledigt (also selbst geändert geändert) hast. Ich schaue mir das nochmal an und passe entsprechend an.

Wenn Du weiterhin Lust hast, zu OSM beizutragen, kann ich Dir sehr den Editor JOSM (https://josm.openstreetmap.de/) ans Herz legen. Dieser macht die Bearbeitung sehr viel komfortabler und sicherer, da er vor potentiellen Fehlern warnt.

Ein tolles Tutorial im PDF Format, welches von einem engagierten Mit-Mapper erstellt wurde, findest Du hier:

https://wiki.openstreetmap.org/wiki/File:Osm-tutorial.pdf

Weiteren wichtigen Lesestoff gibt es hier:

https://wiki.openstreetmap.org/wiki/DE:Good_changeset_comments

https://wiki.openstreetmap.org/wiki/DE:Good_practice

Wenn Du Fragen hast, immer her damit!
Famlam (2019-06-28 04:56:24+00:00): Dankjewel Leo! Weet jij toevallig ook of 
ref:IFOPT=NL:Q:40100020
zone=4010
op de 'nieuwe' halte ook van toepassing zijn? Zone vermoed ik van wel, maar die identifier zou ik echt niet weten. Fijn dat je in ieder geval wist welke bussen naar de andere halte moesten!
Leo Slager (2019-06-28 22:47:37+00:00): Eén van onze bus experts heeft daarvoor een overzicht gemaakt uit het officiele haltebestand van de busbedrijven:
http://maasluip.nl/osm/NDOV.html
Leo Slager (2019-06-28 22:48:14+00:00): ref:IFOPT=NL.Q:40100100
Famlam (2019-06-29 13:56:48+00:00): Dankjewel!!
DressyPear4 (2019-06-28 02:04:49+00:00): Olá, essas vias no meio das lavouras não são usadas para roteamento, então o ideal é que se use highway=track (estrada agrícola)
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/71689531
Karthoo (2019-06-28 08:03:54+00:00): Welcome! Thank you for your first edits. If you have any questions feel free to ask.
NunoCapeloCaldeira (2019-06-28 12:58:16+00:00): again, incorrect edits on this one. you moved the Savoy Palace construction yard to Price Albert pub, which isn't part of it. Also a few other deletions without keeping the object history. please reply or will have to revert
flylow (2019-06-29 13:07:07+00:00): No, I did exclude the pub. I did not move the way (construction) but only two nodes and added on more and I was not responsible for the northeast corner.
flylow (2019-06-29 13:26:38+00:00): The turn_restriction made no sense but I can revert the correct mapped ones:
r8087395
r8060492
r7973314
r6109386.
r3257725 did you break yourself some time ago.
NunoCapeloCaldeira (2019-06-29 13:30:32+00:00): tey make perfect sense, as you removed the u turn, any route calculator will allow u turns now.
flylow (2019-06-29 13:45:23+00:00): w453715993
w453715988
w453715984 
w448141508 where deleted because I did connect two ways. One the last one I did select in the wrong order. Sorry
flylow (2019-06-29 13:54:18+00:00): Four of the six nodes had duplicate objects as area or node. So I merge them keeping the tags of both and the other two nodes where simply duplicated nodes.

Still do not find any mistake.
SomeoneElse_Revert (2022-09-25 09:08:53+00:00): This changeset has been reverted fully or in part by changeset 126607484 where the changeset comment is: Reverting some names from a suspect source; see https://www.openstreetmap.org/user_blocks/6295
Irfandi IRM-ED (2022-12-01 01:03:08+00:00): Hi.

I readjusted the geometry and resolved the road crossing warning
Constable (2019-06-28 06:41:24+00:00): Hi there Melannial, welcome to OSM and thanks for your map edit!
I've just stumbled upon this note https://www.openstreetmap.org/note/1827342 and would like to give you a quick tip about.
I've noticed you added the trail as multiple standalone sections:
https://www.openstreetmap.org/note/1827342
https://www.openstreetmap.org/way/700237054
https://www.openstreetmap.org/way/700237053
and some more.

In order to make things easier, you should have been drawing just one section. Drawing multiple sections is a method only used when those sections need to be tagged with different values, which happens (as an example) when a section is paved, the next one is unpaved or so.
If you like, please try merge all those short ways, otherwise I could help doing that.
Thanks
santamariense (2019-06-28 12:37:15+00:00): I think you've kept an old changeset comment though you've changed the place to be mapped.
That's don't represent a issue to OSM data itself, but sounds weird though.
Have a good mapping.
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/71690160
medrano93 (2019-07-02 00:07:37+00:00): Thanks for catching that. I'll be sure to be more careful next time.
santamariense (2019-07-02 00:54:04+00:00): you're welcome
viloan (2019-06-28 01:23:43+00:00): Bem-vindo(a) ao OpenStreetMap e parabéns pela sua primeira edição! :-)

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 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
Se você está mapeando por causa do jogo do Harry Potter, as dicas e explicações na página anterior também são úteis para você.

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!
SomeoneElse (2019-06-28 14:13:30+00:00): Hello,
What was your source for the access change here?
Best Regards,
Andy
unnsyeda (2019-06-30 01:53:07+00:00): Hi Andy,
Thanks for writing to me. With reference to the motor vehicles parked in the satellite imagery and our delivery agent GPS traces I added motor_vehicle access tags to these roads. As per community feedback reverted my changes. Please let me know if you have any further suggestions.
Changeset: 71746779

Regards,
unnsyeda
SomeoneElse (2019-06-30 08:38:33+00:00): Hello unnsyeda,
Thanks for that.
Regards,
Andy
viloan (2019-06-28 01:27:00+00:00): Bem-vindo(a) ao OpenStreetMap e parabéns pela sua primeira edição! :-)

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 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
Se você está mapeando por causa do jogo do Harry Potter, as dicas e explicações na página anterior também são úteis para você.

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!
GOwin (2019-06-29 03:38:01+00:00): Hi @GrabPHVicPuno. Kindly review your other edits where you've been adding barriers as ways which is breaking routability of the affected roads. 

These POIs are better mapped as nodes. 

If you have questions, feel free to get in touch with the local community: https://osm.org/wiki/PH/channels
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/71690846
Karthoo (2019-06-28 08:02:48+00:00): Welcome! Thank you for your first edits. The sidewalks you added are pretty inaccurate. When you can't see them well on the background imagery you can switch the imagery by pressing 'B'. If you have any questions feel free to ask.
NunoCapeloCaldeira (2019-06-28 12:53:35+00:00): hello, it's the third time i ask you to justify your edits and you still haven't replied. if you don't reply, will have to revert your changesets that contain incorrect edits
flylow (2019-06-29 12:45:40+00:00): Sorry, did not check my mails, better write me a message with osm than a comment.

What is wrong with this changeset ?
NunoCapeloCaldeira (2019-06-29 12:46:30+00:00): you deleted several elements on these changesets without keeping it's history and adding it again within the same changeset
NunoCapeloCaldeira (2019-06-29 12:47:37+00:00): 71689774
71640922
71640094
71616559
flylow (2019-06-29 13:05:19+00:00): I did not do this on purpose, can you please, give me on explicit example, as I want to understand what is going wrong and/or what I have to change in my way of editing. Thanks
NunoCapeloCaldeira (2019-06-29 13:11:18+00:00): you deleted elements (some added more than 7 years ago) and readded them. that's not how to proceed. maintain the element history. https://osmlab.github.io/osm-deep-history/#/node/1769107200 added in 2012, you just deleted it and created a new one 
https://osmlab.github.io/osm-deep-history/#/node/6572681941 without respect to the element history.
on this changeset you added multiple shingles as points, shingles tag can only be added to areas as mentioned on the wiki https://wiki.openstreetmap.org/wiki/Tag:natural%3Dshingle

on changeset 71689774 you added surface as concrete when it was correct, paving stones. 

These are only a few examples of multiples mistakes and not following OSM guidelines.

Also do not add many changes in the same changeset, do less and submit more changesets. when i revert these, all of your work will vanish as you edit more than 1000 elements per changeset.
flylow (2019-06-29 14:54:50+00:00): That is the wrong way of reverting !
flylow (2019-06-29 14:57:36+00:00): > on changeset 71689774 you added surface as concrete when it was correct, paving stones. 

I fixed overlapping ways, right. If I did set the wrong surface to one or two ways. Please tell me the ways or change it yourself.
flylow (2019-06-29 15:02:37+00:00): > on this changeset you added multiple shingles as points, shingles tag can only be added to areas as mentioned on the wiki https://wiki.openstreetmap.org/wiki/Tag:natural%3Dshingle

Wrong, I did delete the tag. You did add it in changeset:
https://www.openstreetmap.org/changeset/71463691
flylow (2019-06-29 15:14:30+00:00): > on changeset 71689774 you added surface as concrete when it was correct, paving stones.

Where ?
arivenid (2019-07-09 07:38:12+00:00): "Hi Hanif IRM-RV,

Trust you are well. While reviewing the road network in Surabaya, I have come across theway 654641422 classified as 'Unclassified'. However, going by the aerial imagery and other ways around, this seems to be 'Residential'.

As of now correcting the data. Please suggest if it is otherwise

Thanks in advance."
Hanif IRM-RV (2019-07-10 02:36:09+00:00): Hi arivenid
Thanks for your suggest. I think this road (654641422) is appropriate set to unclassified, beacuse this road connecting between two settlements in the West and the East.

https://wiki.openstreetmap.org/wiki/Tag:highway%3Dunclassified
SomeoneElse_Revert (2019-06-28 04:37:04+00:00): This changeset has been reverted fully or in part by changeset 71693207 where the changeset comment is: Reverting a persistent sockpuppet in Rochester.  See block 2548 et al
Wilmer Osario (2019-06-30 20:55:05+00:00): La Av. Lecuna no debería tener la misma prioridad que la Av. Bolívar (highway=primary) ya que ambas inician y terminan en el mismo lugar, y siendo ésta última de mayor consideración vial, la Bolívar es la que lleva la mayor prioridad.

Si la Lecuna tuviese que ser (highway=primary), la Av. México/Universidad, que es su contraparte, también tuviera que tener la prioridad de "primaria", ocasionando que hayan 4 avenidas con (highway=primary) atravesando el centro de Caracas, desordenando completamente la circulación de la zona (y pudiendo generar problemas con las aplicaciones de enrutamiento).

Tampoco la Av. Bolívar puede tener una prioridad más alta que la que ya tiene (highway=primary).

Y tampoco la Bolívar puede tener una prioridad menor que la México/Universidad y la Lecuna.
andi9876 (2019-08-04 14:44:49+00:00): Dear, why you add lots of pharmacys
andi9876 (2019-08-04 14:45:03+00:00): ?
SomeoneElse_Revert (2020-01-21 23:41:50+00:00): This changeset has been reverted fully or in part by changeset 79881305 where the changeset comment is: Reverting some mechanical edits that included China Wok, where the mechanically added values may be incorrect, where other mappers haven't touched the objects since.  See https://www.openstreetmap.org/changeset/72812470 for details
santamariense (2019-06-28 12:17:35+00:00): O mais adequado é utilizar o próprio ponto da conexão das ruas nas esquinas para marcar o semáforo. Também não se deve dar nomes descritivos aos objetos como "semáforo".
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/71693115
MarinhoV (2019-06-28 12:33:03+00:00): Anotado!
SomeoneElse_Revert (2019-06-28 04:37:04+00:00): This changeset reverts some or all edits made in changeset 71692412.