piebro/osm-data huggingface dataset:
dvdhoven (2018-02-21 06:27:24+00:00): Als je buslijnen repareert, laat dan andere routes heel aub.
In Wekerom op de rotonde had je een gat geslagen in 25-93. Waarschijnlijk heb je de rotonde doorgeknipt zonder eerst alle routerelaties op te halen.
Dit gebeurt vaak als mensen met overpass  specifieke relaties ophalen en er niet aan denken dat er meer is, dan die specifieke relaties.

Vriendelijke groeten,
Dick van den Hoven
Leo Slager (2018-02-21 09:27:10+00:00): Dick, bedankt voor de tip. Ik zal mijn werkmethoden aanpassen zodat het niet weer gebeurd. Maar het is natuurlijk weer zo0n uitzondering waarbij fietsers op de rotonde rijden ipv de fietspaden !
Constable (2018-02-21 09:19:37+00:00): ciao, benvenuto su opentreetmap!
Ho visto che stai usando le immagini satellitari di bing, occhio che in questa zona non sono ben allineate alla mappa, io ti consiglio di usare le ESRI Clarity, sono più vecchie ma riusciresti a fare un lavoro migliore.
Ciao
da_pigo (2018-02-21 20:11:14+00:00): Ciao! Grazie per la dritta, provvederò ad allineare tutto con la mappa da te consigliata
Constable (2018-02-22 07:54:58+00:00): nessun problema, io conosco un pochino la zona, se pensi possa servirti un parere o una mano a fare qualcosa scrivimi pure.
Ciao
Constable (2018-02-22 07:56:36+00:00): anzi, prima ne approfitto io per chiederti una mano.
Giorni fa ho aggiunto questo tratto https://www.openstreetmap.org/way/559411608, a breve non ho modo di passare, mi confermi che è a doppio senso?
grazie
luked2000 (2018-02-20 23:44:45+00:00): *Yas Marina. Lovely.
Lokai (2018-02-21 03:29:57+00:00): Hallo und Willkommen bei OSM.

Der von dir kartierte Park sieht aus wie eine Grasfläche mir Trampelpfad bspw als Abkürzung. Ein Park ist das wohl nicht, prüfe das und ändere das ggf.

Verdacht auf: https://forum.openstreetmap.org/viewtopic.php?id=57174

Schöner Gruß
BCNorwich (2018-02-23 07:45:02+00:00): Fiction reverted.
sorcrosc (2018-02-24 00:42:23+00:00): Le vie di accesso alle abitazioni andrebbero mappate come highway=service, con l'aggiunta di service=driveway se servono soltanto la residenza.
Attenzione anche ai nomi. L'iniziale di Via, Viale, ecc. va messa in maiuscolo.

Grazie
Lorenzo
viloan (2018-02-21 00:42:45+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!
user_5359 (2018-02-21 05:01:31+00:00): Welcome to OSM! Please have a look on Node https://www.openstreetmap.org/node/2853861034. Is the laundry really part of the street?
Constable (2018-02-21 09:13:38+00:00): hi there, watch out, you did draw this road on top of a already existing one. In this case you should have just replaced the existing road tags with a more appropriate one, having roads overlapping each other is not correct, please make sure you fix this up.
Thanks!
Constable (2018-02-21 09:15:14+00:00): Hi, I just noticed you just signed up so I'd like to welcome you to the OSM project, feel free to reply here in case you feel like you might need some help
Here you can find all the things about the project: http://wiki.openstreetmap.org/wiki/Main_Page
Thanks
Constable (2018-02-25 18:04:29+00:00): no answer so far
Supaplex (2019-02-08 16:39:18+00:00): 恭喜您完成第一次的地圖編輯！ 歡迎加入開放街圖，群眾共同參與，繪製生活週遭大家關心事物的共編地圖。以下是相關的參考資料，歡迎隨時指教與提問。

編輯須知
台灣的標示依循準則可參考 http://wiki.openstreetmap.org/wiki/Taiwan
常見的圖徵標示方式可參考 http://wiki.openstreetmap.org/wiki/Zh-hant:Map_Features
給Pokemon Go玩家的建議：https://wiki.openstreetmap.org/wiki/Tips_for_new_(Pokemon_Go)_mappers

台灣社群網站
台灣 OpenStreetMap 網站 http://www.openstreetmap.tw
臉書粉絲頁OpenStreetMap台灣 https://www.facebook.com/opestreetmaptaiwan/
台灣社群Facebook社團 https://www.facebook.com/groups/OpenStreetMap.TW/
郵件論壇 https://lists.openstreetmap.org/listinfo/talk-tw
Telegram OpenStreetMap Taiwan https://t.me/joinchat/Aqu2IgnTuIidMfREdNmomQ
Telegram OpenStreetMap Asia https://t.me/OpenStreetMapAsia
Slack https://osm-tw.signup.team/

Happy Mapping!
viloan (2018-02-21 01:12:13+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!
user_5359 (2018-02-21 04:54:15+00:00): Welcome to OSM! Note that in OSM description (with defined values) of the objects has the highest priority. Objects that have only one a free text description, have little sense. As home page for the question "How do I describe you?" I recommend the web site http://wiki.openstreetmap.org.
I assume you want to draw a tree. Please try natural=tree, ref =002.
user_5359 (2018-02-21 04:53:56+00:00): Welcome to OSM! Note that in OSM description (with defined values) of the objects has the highest priority. Objects that have only one a free text description, have little sense. As home page for the question "How do I describe you?" I recommend the web site http://wiki.openstreetmap.org.
I assume you want to draw a tree. Please try natural=tree, ref =002 (or ref=003).
berndw (2018-02-21 11:45:56+00:00): Hi

Du hast beim Jahrsfelder Weg motorvehicle=designated gesetzt.

Wäre da nicht besser ein z.B. motorvehicle=agricultural o.ä. angebracht?
designated bedeutet nur da steht ein Schild, aber nicht was für eine Einschränkung gilt.
woktam (2018-02-21 15:32:59+00:00): Hi, ja hast vollkommen recht. Mir wurde im oberen dropdown Menü für den Zugang agricultural gar nicht angeziegt, darum dachte ich designated passt am besten. Habs jetzt geändert, danke.
berndw (2018-02-21 15:50:47+00:00): Danke
wille (2018-02-21 13:06:36+00:00): Olá,

Muito obrigado por suas contribuições ao OpenStreetMap! Revisei essa edição e está tudo correto!

Caso tenha alguma dúvida, pode entrar em contato comigo.
            ---
            #REVIEWED_GOOD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/56536542
SidusMap (2018-08-28 03:51:52+00:00): Terrible. ¿por qué bajaron de categoria carreras importantes como la Carrera 38, 43 y 44? Gran parte de mi trabajo basado en la clasificacion oficial segun la secretaria de transito ha desaparecido.
viloan (2018-02-21 02:12:54+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!
viloan (2018-02-21 02:22:20+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!
viloan (2018-02-21 02:31:44+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!
Protoxenus (2019-01-01 17:44:30+00:00): Hallo, du hast hier 2x die Hausnummer 2c vergeben. Hat die Gartenlaube wirklich auch die 2c? Überprüfst du das noch mal bitte?
Gruß Protoxenus
j1scad (2019-01-05 13:57:20+00:00): Habe die Adressen nochmal korrigiert. Danke für den Hinweis.
Schöne Grüße
marc__marc (2020-02-02 00:02:59+00:00): Hello,
https://www.openstreetmap.org/way/562918524
https://www.openstreetmap.org/way/562918523
are these 2 places 2 tourism=camp_pitch (campsite in American English) forming the same site (campground in American English) which is not entered in osm? or are these 2 places independent?
Regards,
Marc
user_5359 (2018-02-21 04:49:32+00:00): Hello and Welcome to OSM! Please have a look on Relation https://www.openstreetmap.org/relation/8040140.
Constable (2018-02-21 10:23:56+00:00): Hi there, thanks for you contributions.
Please make sure you add proper changeset comments to your edits.
https://wiki.openstreetmap.org/wiki/Good_changeset_comments
Thanks!
wille (2018-02-21 12:59:24+00:00): Hola, Te-Ika

Hay una turn restriction rota en tu edición: https://www.openstreetmap.org/relation/2988772/
El nodo via seleccionado no es el correcto.

Gracias,
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/56537683
Te-Ika (2018-02-22 00:55:42+00:00): Gracias. No sé cómo incluí ese nodo en la restricción que es un error extraño.
DannyMcD (2018-02-22 03:01:01+00:00): Jerome Jodoin Drive is not open (yet), based on my survey on Sunday, although there is a track following the future roadway.  I think highway=construction is the best description at this point.
Matthew Darwin (2018-02-22 04:05:05+00:00): sure, no problem.   I am updating the road status to open when the city marks it open... usually they are late to change status, not early.
Matthew Darwin (2018-02-22 04:25:32+00:00): They changed the road status yesterday.
DannyMcD (2018-02-23 04:02:22+00:00): I think waiting until the road is "operational" is probably the way to go, in the absence of a survey/other evidence.  Better to err on the side of not including roads, rather than including non-existent roads.  A lot of "open" roads seem to be boundary cases; they exist at their final alignment, but they aren't yet paved, and they have the feel of being construction sites.  Someone directed to take them by routing software may well be unhappy.
Matthew Darwin (2018-02-23 04:24:24+00:00): If you have some pics of the area, I would love to have them so I can send complaints to the city...
DannyMcD (2018-02-23 04:37:48+00:00): I don't think the city is wrong - its classification system is just different from that of OSM.  The city has three categories for road status ("comwork", "open", and "operational") while OSM has two (highway=construction and highway=*) with the city's middle category roughly split between OSM's two categories.
Matthew Darwin (2018-02-23 04:44:33+00:00): Yes, I know the statuses.  usually when they mark it open, the road is actually driveable.
GerdP (2018-10-08 09:04:20+00:00): Hi! Please don't use highway=junction for this kind of objects. The tag junction=yes is enough and the additional highway tag might confuse routing programs.
Nutchanon Wetchasit (2018-10-08 13:49:43+00:00): Duly noted. For this intersection, the concern is now addressed in changeset 63312065 <https://www.openstreetmap.org/changeset/63312065>.

Anyway, does this also apply to node-based intersection, where intersection a node on the road itself? (Like this one: <https://www.openstreetmap.org/node/373455280>)

P.S. `highway=junction` is a thing I originally just picked from some existing (node-based) intersection on the map few years back when I didn't know how to map it yet. Some time later, I realized it wasn't documented on the Wiki, but I kept adding them anyway.
GerdP (2018-10-08 14:37:42+00:00): I only know highway=motorway_junction for nodes. I think that the highway tag should be used with great care because routing is one of the major uses of the OSM data. It is always hard to understand that a tag is okay for nodes but not for ways or areas, so I would not use highway=junction anywhere.
freebeer (2018-02-28 19:44:44+00:00): Hallo %s,
Unfortunately you have made several beginning mistakes in this changeset.
Most critically, you have used unaligned satellite imagery from Digital Globe that I've just measured shows an offset of nearly 8 metres from the much better aligned aerial overflights that are outdated yet still available from Mapbox and others.
If you still want to use the newer Bing imagery, you should first align it to match the buildings carefully mapped by user ENT8R.  Use the `b' command or  the layers icon which allows you to shift the background.
Secondly, iD is a beginner editor with a lot of problems or bad decisions, such as has happened where two buidings have become joined together when you made the mistake of moving them, at 218 1st Ave NW.  Or 224 and the nearby firehouse which are now attached to the residential area outline.
The same has happened with the road you moved which bonded to the administrative boundary outline, shifting parts of it several metres out of the straight line it followed.
There are a lot more places where things that are easiest to maintain when mapped independently, are now joined to other unrelated objects.  My editor makes working with these things rather painful.
Where you have added new buildings, you have failed to quadrilateralise() them to match those added by ENT8R, so they look very irregular and unprofessional in addition to being some 8m away from a more correct position.
Unfortunately, this edit has caused a lot of careful mapping by user ENT8r to now appear very poor.  This is probably the biggest offset of satellite imagery away from aerial overflights I've seen within the US, and unfortunately, in this area, the excellent newer Mapbox sharp crisp and clean imageries, or the ESRI Community up to zoomlevel 22, are not yet available for more precise mapping.
The alignment of the USGS Large Scale Imagery, which I take as a good reference when nothing better like Bing z20 heavily-distorted urban imagery, agrees closely with the archive/Mapbox alignment, DigitalGlobe Standard shows about half the offset of DG Premium here.
Strongthany (2018-02-28 19:48:34+00:00): Well....darn. I hope I made it evident that didn't intend for this. What can I do to help fix this issue?
Hernan (2018-02-21 13:01:36+00:00): Building es para edificios individuales, no para un area de edificios
Constable (2018-03-01 15:52:04+00:00): hi there Martin, do you think this tag would be more appropriate than "alpine hut" for those two remote buildings?
https://wiki.openstreetmap.org/wiki/Tag:tourism%3Dwilderness_hut

thanks
viloan (2018-02-21 05:40:41+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!
stephankn (2018-05-28 21:25:57+00:00): you created polygon way 562939256 with broken geometry. I fixed that. Please try to avoid in the future. Besides this your way of tagging the area is at least unusual. Please clarify with local mappers about the mapping style.
Nakaner-repair (2018-04-18 22:24:59+00:00): This changeset has been reverted fully or in part by changeset 58217008 where the changeset comment is: Revert all changesets by a group of commercial editors everywhere except North and South America. They &quot;fixed&quot; routing &quot;errors&quot; but hided real errors instead of fixing them. See also https://forum.openstreetmap.org/viewtopic.php?id=61964
Baloo Uriza (2018-02-21 18:20:21+00:00): I still have some concerns about this mass attempt at priority creep on the highway=* tag.  https://wiki.openstreetmap.org/wiki/United_States_roads_tagging#Secondary_tag

https://wiki.openstreetmap.org/wiki/United_States_roads_tagging#Tertiary_highways
MikeN (2018-02-21 20:37:18+00:00): I agree about concerns with mass priority creep.   DOT / Government classifications do not directly translate to an OSM classification.  Routers will still select a road when it best matches the travel itinerary and mode.
clay_c (2018-02-21 22:56:10+00:00): Alright, I'll put a pause to this change for a bit. I want to continue this discussion later, though right now I think I just need to take a break. Thanks for being patient.
Baloo Uriza (2018-02-22 01:50:06+00:00): No problem, thanks for being open on this.  Last time there was someone who went a little too strict with the tagging, we ended up with the entire US highway system tagged trunk nationwide
clay_c (2018-02-26 22:47:53+00:00): Alright, I'm back and my head's clear. Thanks for giving me some time.

I want to make sure we're on the same page with a few things. I'm avoiding being strict on tagging, and there's a few FM/RM roads I've tagged higher than secondary as well as state/US highways lower than primary. It's still context-dependent.

After spending a lot of time reviewing untouched TIGER data in various parts of Texas that I've visited, I've come across frustratingly many cases where FM/RM roads were tagged as tertiary and needed to be upgraded, whether urban or rural. It doesn't seem to matter where—there's always going to be something (e.g. county roads, small city thoroughfares) that fits in between FM/RM roads and residential roads in the local hierarchy.

And, as state highways are generally (but not always) higher-priority and longer-distance than FM/RM roads, and roughly as connective and well-maintained as US highways, I upgraded many of them to match that. 

Though admittedly I ended up indiscriminatingly upgrading a lot of FM/RM roads that don't connect any population centers at all. And this is clearly a case where FM/RM roads fit in as tertiary on the hierarchy. My bad.

Going forward, I'll be more conservative changing FM/RM roads to secondary. And in the end I'll review the FM/RM roads I previously upgraded, and downgrade the ones that don't connect population centers.

How does this sound to y'all?
Baloo Uriza (2018-02-27 01:51:13+00:00): RIght, generally a good idea to weight the local functionality with the classification to kind of rank it out.  Like a major thoroughfare through a city (like, say, FM 2786 or CR 150 in Allen) might be underrated even as a secondary.  But, say, FM 1885 or FM 920, northwest of Weatherford?  Yeah, that's a pretty solid argument for a tertiary.

Let's look at TX 183 in Dallas.    Yeah, that's solidly a primary.  Long Avenue just north of that, it's kind of an iffy judgement call on secondary or primary given that it's clearly built to be a major boulevard, but at least on the bing imagery, yeah, not seeing much of anything there trafficwise.

Basically, the idea of US being primary, the highest level of state roads being secondary, and auxillary state, county and city roads would be a safe rule of thumb.  Going higher or lower definitely suggests that they're operating "out of their usual league" to the average viewer, so to speak.

Regionally local to me, OK 66 (given it's overlap with US Historic 66), OK 117 (given it's large size), hit higher than base level.  But not OK 11 between Skiatook and Pawhuska, even though that's the main way to get between Tulsa and the Osage Nation capitol, because there's not really anything else that differentiates it at all from any other state highway twisting through (and if I wanted to stick to more major highways, say, because it's icy and I want to stick to what's the least likely to get me killed while driving a moving truck with everything I own in it, I might zoom out a bit and see US 75 and US 60 instead, or if I'm feeling more adventurous and can reliably count on being able to self-rescue (or at least have AAA find me), I might pull a detour on CR 2561 through Nelagoney or bypass unexpected construction on US 60 by rat-running CR 2732).

Cultural significance can play a role, too, for example, Historic US 66 tends to still warrant a higher rating because of its continued significance and impact today, even if it's largely been bypassed and obsoleted by I 10, 15, 40, 44 and 55.