piebro/osm-data huggingface dataset:
SirKingIke (2018-04-03 09:38:15+00:00): @Wegabschneider: Grundlegend hast du Recht, aber hier wird gepöbelt nicht mehr kritisiert. Da musste ich mich mal wehren. Man muss ja nicht alles mit sich machen lassen :-)
Ja grundlegend habe ich mir auch schon mal überlegt was passiert wenn jemand mit dem eigenen Weg im Garten nicht einverstanden ist - schlussendlich ist rechtlich okay - moralisch fragwürdig - und es gibt ja wie du sagst diese Sache mit den "einmal Accounts". Meiner Erfahrung nach ist aber auch jeder "Lead" im Online-Marketing was positives. Aber das ist schlussendlich ja auch Ansichtssache.
highflyer74 (2018-04-03 09:52:04+00:00): @SirKingIke: Unter "pöbeln" verstehe ich etwas anderes. Wenn Du Dir mal die von mir und anderen verfassten Kommentare ansiehst (http://resultmaps.neis-one.org/osm-discussion-comments?uid=5671084), wirst Du feststellen, dass alle recht sachlich schreiben. Insofern ist der Begriff "pöbeln" hier etwas fehl am Platz. Damit will ich's gut sein lassen. Ich will mich mit Dir gar nicht streiten und würde mich freuen, wenn Du mal auf einem OSM Treffen vorbeischaust. Da kann man vermutlich ein paar Dinge aus der Welt schaffen. Online ist das immer etwas schwierig. Schönen Tag Euch zweien!
viloan (2018-04-02 20: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!
dan980 (2018-04-06 15:30:20+00:00): ciao, le cascate vanno mappate con l'etichetta "waterway=waterfall", da applicare su un nodo del torrente (o del fiume).

natural=peak si usa invece per i picchi montuosi
natural=water per i laghi
sergmauri (2018-04-07 17:27:28+00:00): Ciao e grazie mille per le informazioni; purtroppo non sono ancora molto pratico nell'uso delle etichette, ma trovo spesso incongruenze tra le indicazioni sulle carte Osm e la realtà rilevata con gps sul posto e verificata con l'utilizzo di google hearth e carte Igm, come in questo caso nel quale il torrente, i limiti amministrativi e le immagini satellitari non coincidono. Ti chiedo la cortesia di farmi capire se e come sia possibile trasferire i propri tracciati sulle carte (quando non già esistenti, ovviamente) e come etichettare gli ovile che incontro. Grazie
dan980 (2018-04-07 17:41:36+00:00): Per gli ovili disegns un’area intorno agli edifici e usa landuse=farmyard . Come programma per caricare i dati ti consiglio di usare Josm, che ha un validatore molto potente che ti avverte di eventuali errori. Per io resto c’è la Wiki italiana, e questo sito (http://www.msmountain.it/varie/mappa_osm/consigli.html) molto utile per imparare le basi
fatuus (2018-04-11 11:25:36+00:00): Skulle precis in och ändra. Då var det gjort! Snyggt!
AndersAndersson (2018-04-12 07:33:55+00:00): :)
Milad s (2018-04-02 20:37:38+00:00): Ok
Milad s (2018-04-13 17:51:11+00:00): True
SomeoneElse_Revert (2018-04-28 23:29:58+00:00): This changeset has been reverted fully or in part by changesets 58510954, 58506260, 58507519, 58514650, 58514174, 58505701, 58509392, 58500784, 58512130, 58515035, 58510461, 58506875, 58508734, 58513728, 58513212, 58511524, 58502701, 58504854, 58509968, 58508131, 58512688 where the changeset comment is: Reverting recent unedited changes by Bonya_23, see http://resultmaps.neis-one.org/osm-discussion-comments?uid=4355762 and https://www.openstreetmap.org/user/Bonya_23/blocks for laundry list of issues; no communication.
jan-di (2018-04-02 20:43:36+00:00): Korrektur: Waldweg zwischen Nievern und Miellen hinzugefügt.
Milad s (2018-04-02 20:42:44+00:00): Ok
Milad s (2018-04-13 17:50:49+00:00): True
eggie (2018-04-02 21:16:21+00:00): Please don't add info on the map that is already there, I will delete your contribution.
gscholz (2018-04-03 05:25:57+00:00): Hola,
this changset has damaged boundary relation 108044:

http://tools.geofabrik.de/osmi/?view=areas&lon=-80.05374&lat=-3.71059&zoom=12&opacity=0.76

Can you please fix this?

Saludos
Guido
Milad s (2018-04-02 20:49:57+00:00): Ok
Milad s (2018-04-13 17:50:26+00:00): True
5m4u9 (2018-04-19 20:28:13+00:00): al editar debes tener cuidado de mover negocios, si lo haces volverlos a poner en su lugar
chachafish (2018-05-14 15:47:02+00:00): Howdy :) Thanks for your additions to the map. In case you weren't aware, the minimum requirements for addresses are 1) street number and 2) street name. You can check the link below. Could you return to this edit and add the minimums? Cheers :)  https://wiki.openstreetmap.org/wiki/Key:addr
chris66 (2018-04-23 17:36:16+00:00): leisure=stadium für ein NSG?
viloan (2018-04-02 21:21:01+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!
eggie (2018-04-02 22:18:30+00:00): Je verplaatst gewoon overal adressen? Wat heeft dat voor een zin?
eggie (2018-04-02 22:19:19+00:00): http://overpass-api.de/achavi/?changeset=57753010
eggie (2018-04-02 22:21:13+00:00): Ik zet deze changeset terug. 
Door dat geschuif met de kaart in editor iD krijg je onbedoelde effectie. Zie achavi
eggie (2018-04-02 22:22:15+00:00): Helaas gaat dat niet meer. Ga je de adressen weer terug zetten svp?
eggie (2018-04-03 06:19:14+00:00): kruipeind 38 hersteld
eggie (2018-04-03 06:21:27+00:00): voetboog 51 hersteld
eggie (2018-04-03 06:23:32+00:00): voetboog 51 hersteld
eggie (2018-04-03 06:27:23+00:00): School de Schakel en Prins Bernhardlaan 50 hersteld
eggie (2018-04-03 06:30:05+00:00): Schuiven met de kaart in de editmodus is de oorzaak. Editor iD is wat dat betreft een onding. Beter overstappen naar JOSM. editor josm stap voor stap
https://forum.openstreetmap.org/viewtopic.php?id=53710      
Daar schuif je met de rechtermuis en edit je met de linker. Bovendien heeft deze een validator om verkeerde uploads te voorkomen.
Eerder contact middels PB gehad.
eggie (2018-04-03 06:31:48+00:00): Olivier van noortstr 31 hersteld
FajrAl (2025-02-24 08:07:32+00:00): M fastfood?
tbo47 (2025-02-24 08:20:33+00:00): I left the country a long time ago. Please delete if it doesn't exist anymore. Thanks
chachafish (2018-04-07 01:43:58+00:00): Hello, the edit you made to the post office here has popped up as an error. The minimum requirements for an address are addr:street and addr:housenumber. Can you please add the required minimum keys? Thank you
mueschel (2018-04-03 09:22:34+00:00): Hi,
you might want to change 149 times 'souuce' to 'source'.
Cheers, Jan
eggie (2018-04-02 22:17:14+00:00): Maarten... Wat is je edit? Graag beschrijven wat je doet.
Hjart (2018-04-03 15:22:13+00:00): Arealer hvor der er fældet træer vil jeg mene tagges mere korrekt som "scrub" end som "grassland". Se f.eks. https://help.openstreetmap.org/questions/55032/scrub-area-in-forest-how-to-map
og https://wiki.openstreetmap.org/wiki/Tag:man_made%3Dclearcut
Hjart (2018-04-03 10:30:52+00:00): Bemærk at jeg har rettet alle de broer du har angivet: https://wiki.openstreetmap.org/wiki/Key:bridge#How_to_map
Andrew Matheny (2018-04-03 01:03:40+00:00): Hi there-

Two things:
First, could you explain why this section of the highway should be upgraded to highway=motorway when it only connects a trunk highway to a primary highway? 

In the US, highway=motorway tagging is (with few rare exceptions) typically reserved for either highways that are part of the Interstate Highway System or highway=trunk ways that pass through major urban areas where a major highway (usually US- prefix) functions as a motorway for commuters. Beyond that, state highways 
are usually (but not always) tagged with highway=primary (or in some cases, highway=trunk) because the ease of access usually doesn't change that much to warrant a motorway tag.  It also helps them render consistently across styles, since motorways are given priority with large-scale rendering (which would make this segment render by itself rather than being part of a coherent network).

Second, could you explain what about clay_c's changeset is vandalism? This user has over 5,900 changesets and the edits are part of a MapRoulette challenge that has been set up by the community to reclassify segments of highways that have been improperly upgraded to motorway. It seems like at least commenting on the changeset to foster a discussion and give the other user an opportunity to respond would be the best step here, rather than reverting the changeset without first contacting the user.

Thanks!

Andrew
Baloo Uriza (2018-04-03 01:27:52+00:00): I also agree this looks like a clear case of trunk.
UAN51 (2018-04-03 01:56:14+00:00): Hello Andrew,
This section of MO 13 should be a motorway (aka freeway) because it has met the requirements to be a freeway. This section of MO 13 has no at-grade intersections (with the exceptions of the termini), has a median, and has a high speed limit. Freeways are not required to be part of the Interstate or U.S. highway system. AASHTO defines freeways as  “arterial highways with full control of access. They are intended to provide for high levels of safety and efficiency in the movement of large volumes of traffic at high speeds. With full control of access, preference is given to through traffic by providing access connections with selected public roads only and by prohibiting crossings at grade and private driveway connections”  found in FHWA's Freeway Management and Operations Handbook. It is not required that freeways are connected to other freeways. Does this 7 mile portion of MO 13 function like a freeway? Yes it does. It's a freeway between Lexington and Richmond. Does this stretch of MO 13 have random at-grade intersections in between exits? No. Another thing, most US highways are tagged primary unless it's a 4+ lane expressway (trunk) or part of it is freeway (motorway). State routes are secondary unless part of NHS or carry high volume traffic (primary) or expressway (trunk) or freeway (motorway). Next thing, number of changesets does not relate to knowledge of roadways. I think the "Check Motorway Upgrade" in MapRoulette needs to be reconsidered. It seems that the entire community have different definitions of what a motorway (aka freeway) is. I am basing the definition of freeway from AASHTO and FHWA. I did DM clay_c, but he took too long to respond. If you have any questions or comments, please respond in this changeset or DM me.
-UAN51
Baloo Uriza (2018-04-03 02:06:02+00:00): Generally speaking, changeset comments are the best way to contact someone regarding a specific change, plus keeps the whole thing out in the light for others to pick up on.

My concerns with this is that OpenStreetMap isn't the AASHTO, and with this transitioning cleanly into surface roadways on either ends, this acts more like a grade separated portion of Spartan Drive south of MO 10 (and especially with it discontinuing quickly after US 24), or a first phase of upgrading the route to a freeway later.  Once they upgrade the MO 13/10 interchange and extend the MO 13 interchange, yeah, motorway it then.  You say it has no intersections, yet right there, you have one at Walmart Avenue.

Trunk fills that nice grey area that things like MO 10 itself, the section of MO 13 that is the subject of this changeset, and other "freeway like, but not quite all the way there" objects.
UAN51 (2018-04-03 02:25:55+00:00): Even though OpenStreetMap is not the AASHTO, keep in mind that the government owns all of the roads and highways. A portion of our tax dollars go to building and maintaining all roads and highways in the USA. OpenStreetMap doesn't own these roads or highways. Walmart Drive is the endpoint of the freeway; I didn't say north of Walmart Drive was freeway. Between Walmart Drive and US 24, there are no at-grade intersections. Like you said, this portion of MO 13 does seem like it is a first-phase of a freeway between I-70 and Richmond. It is preferred to keep this stretch of MO 13 as motorway since it meets the requirements. Plus, it would help Richmond and Lexington with economic development. MO 10 to the north of this segment is not a motorway because it is not a divided highway.
Baloo Uriza (2018-04-03 02:45:14+00:00): What AASHTO or MODOT consider it is not the determining factor for OpenStreetMap when it comes to the highway=* tag.  Right now, I don't believe this is a clear enough case of motorway to justify the tag.  Eliminate the intersection, slap on a continuously flowing interchange at MO 10 and don't drop to single carriageway at the south end, and yeah, that's a motorway.  It's got the future potential to be motorway, but for now it really looks like more of a trunk.
UAN51 (2018-04-03 02:57:29+00:00): If AASHTO, FHWA, or MoDOT does not determine the highway=* tag of a stretch of a road or highway, then what does? OpenStreetMap Wiki says that motorways are Interstate, Freeway, or a divided highway with no at-grade intersections  (Source --> https://wiki.openstreetmap.org/wiki/United_States_Road_Classification) while at-grade intersections are endpoints of the motorway. The Wiki seemingly does not go against FHWA's or AASHTO's definition of a freeway/motorway. Also, why downgrade this stretch to a trunk highway when it qualifies for a motorway/freeway?
Baloo Uriza (2018-04-03 03:28:48+00:00): It has an at grade intersection, though.  Walmart Avenue.

Looking through the wiki, it appears that some pages have been gamed a bit away from where things have largely settled in regards to how trunk is typically used in the United States, and various pages aren't in agreement on this anymore.  In practice, anything that hits Interstate standards or close to it, and doesn't go to single carriageway at either end, would be a motorway.  Less than that but otherwise, would be a trunk.

I honestly can't tell anything about MO13 that's different than MO 10 except they slapped down a dozen or so kilometers of a second carriageway with plans to expand later as funding becomes more available.
UAN51 (2018-04-03 04:02:06+00:00): Walmart Drive is an endpoint of the freeway (as in that's where the freeway ends which I said already). The wiki page I linked you is part of an organization called WikiProject United States. They based their standards off of the US administration; so should all of users editing in the United States. If you or the others in the OpenStreetMap community don't like FHWA's definition of a freeway, go complain to them or complain to AASHTO. You and I don't own the highways and roads in the United States; you and I don't determine the definition of roads and its entities in the United States; you and I don't determine the street name or the highway number of a road; the government determines all of that. I'm basing my edits off of how the US government defines roads and so should others. Single carriageway at either end doesn't determine motorway vs trunk;  no government agency said that. Show me what OSM Wiki page said that; you gave me no quotes and/or no links to sources. At least I quoted from AASHTO/FHWA and linked you to an OSM Wiki page that agrees with it. MO 13 has met the requirements (divided highway and no at-grade intersections except at endpoints) and MO 13 functions as a motorway/freeway so it qualifies to be a freeway between Walmart Drive and US 24.
Baloo Uriza (2018-04-03 11:55:20+00:00): Sorry, intersections even at the end (and going to single carriageway also counts) still counts as an intersection and disqualifies it as a motorway.  It wasn't vandalism to change it to trunk, and the government classification doesn't count.
Andrew Matheny (2018-04-03 15:31:18+00:00): Thanks for the detailed response.

I certainly see the logic in your thought process for why this should be a motorway, but the problem with using AASHTO/FHWA/any other government or industry standards—or even government planning documents—is that their functional classification system follows certain definitions based on their own goals and objectives: namely thoroughfare planning, traffic modeling, and right-of-way management. They also tend to follow those definitions strictly because they're maintaining an "authoritative" data set in a large organization and the classification can determine everything from how they prioritize improvements down to right-of-way management when they're reviewing permit applications for curb cuts onto these highways.

On the other hand, we have some slightly different goals and objectives in OSM. Our functional classification system is based not only on the physical or functional (in an engineering sense) characteristics of the highway, but also a) how it fits in with the hierarchy of the road network and its relative importance, and b) working with a standardized tagging system in a global dataset. When I look at this stretch of highway on aerial imagery, I agree with you that *physically* that stretch looks no different than some of the other freeways in rural areas that have a motorway tag. But when we zoom out and see its place in a network—connecting a trunk to a primary, or more precisely, just a dual-carriageway split of a primary highway—it's clear that this segment's place in the hierarchy is equal to the segments it connects to; in this case, primary or trunk. It's also clear that the importance of this segment is at least equal to that of the ones it connects to, but isn't greater (in other words, tagging this as motorway makes it seem as if people travel on US-24 or MO-10 to get to MO-13, when the reality is MO-13 is the connector between those two important highways)

You can get a sense of what I mean at a visual level by zooming out to level 10, and you'll see that the Mapnik style treats this an important highway and renders the "MO 13" ref sign even though none of the other segments of the highway are signed (and rightfully so). This is going to be true in almost every style that uses OSM data, since motorways are seen as the most important roadways and are rendered and labeled at higher zoom levels. 

Just to give you another example where OSM standards differ from some of the 'official' (for lack of a better term) functional classifications, in the US we typically tag collectors with highway=tertiary. You often won't find them designated as "collectors" on a thoroughfare plan, but we can tell it's a collector based on the fact that it's the only street that connects the residential streets in a neighborhood to the nearby arterial roadways. From the OSM perspective, tagging a street that runs from an arterial (highway=secondary or primary) to residential with a tertiary makes sense in the hierarchy
UAN51 (2018-04-03 16:14:02+00:00): @Paul Johnson On a larger scale, I-35 ends at intersections and goes to a city street. I know that I-35 has connections with other Interstates and is an Interstate itself, but I'll let you think about this.

@Andrew Matheny It's clear that there is a mix of opinions on how all roads are being tagged in OpenStreetMap. Your position makes sense only for rendering purposes, but I don't see any of this documented on any Wiki page (unless you can show me). Let's talk with WikiProject United States members since they created the wiki page that you and others don't agree (https://wiki.openstreetmap.org/wiki/United_States_Road_Classification). I'm not a member of WikiProject United States so I'm not the guy to talk to. Also when I was talking months ago to a different user about HFCS maps, they told me how HFCS maps are inaccurate representations of roads and pointed me to this (https://wiki.openstreetmap.org/wiki/United_States_Road_Classification).
Baloo Uriza (2018-04-04 01:37:52+00:00): I 35 probably should be a trunk north of the MN 194 interchange and south of Loop 20 as well.  The segment between those two interchanges would be a motorway.  MO 13 has no such major interchanges.  It's pretty much the same character as long stretches of US 75 in Oklahoma.
UAN51 (2018-04-04 02:18:38+00:00): You've gone too far. Interstates are motorways with NO EXCEPTIONS. You've absolutely disregarded everything I've said up to this point which is unacceptable. I've made my points as clear as possible; I've backed it up with documentation while you haven't. Freeways can end at an intersection. Stop making up your rules that contradict FHWA and WikiProject United States. You have a problem with that? Go complain to WikiProject United States or FHWA. Have a nice day.
maxerickson (2018-04-04 13:50:53+00:00): I've upgraded the wiki:

https://wiki.openstreetmap.org/wiki/United_States_Road_Classification#Motorway
UAN51 (2018-04-04 14:13:40+00:00): maxerickson, your actoin raises three points/questions: 1.) Did you write that because two random people said that? Is this to directly attack me? 2.) Did you discuss with members of WikiProject United States before updating that wiki page? 3.) Because Andrew and Paul are mapping things that were previously undocumented, does that mean they were wrong the whole time? Something's ethically wrong with this situation.
maxerickson (2018-04-04 14:24:53+00:00): I wrote it because I believe it. It's not an attack on anybody. No, I didn't discuss it with anyone, but no one who wrote anything there previously bothered to discuss it with me either.

It may seem absurd that I'm pointing at my unilateral change to the wiki as an argument to justify a particular way of mapping, but that's pretty much the situation with any use of the wiki as justification for a particular way of mapping, it's likely to reflect the views of whoever last edited the page.
UAN51 (2018-04-04 14:38:39+00:00): I suggest you discuss with the people of WikiProject United States (and perhaps other US mappers) with your propose change to the Wiki page. Changing the Wiki page without discussion will only make this situation worse because its unethical. This almost seems to be a dictatorship. Andrew and Paul did have undocumented practices previously; I had documented support previously (until you changed it).
maxerickson (2018-04-04 14:49:49+00:00): Please look at the edit history of the page. There's no group of people behind it, it's mostly what one person said 9 years ago.

The way I understand 'wiki', instead of discussing my proposed changes at length, I can just make them and then if there is too much disagreement they can be removed. That's part of why there is a history feature.

In any case, the 5 people that have edited the page in the past do not have more say over US highway tagging than the broader US community.