piebro/osm-data huggingface dataset:
baveggies9999 (2018-01-13 03:36:13+00:00): Fair enough, though it is clear based on both number of signs and the way ODOT/OTA have treated this road that "Creek Turnpike" should be the primary name with "Liberty Parkway" serving as the alternate name.
Liberty Parkway is not a useful designation for navigation and from signage and other administrative actions (e.g. the 364 designation) it is clear that ODOT and OTA regard "Liberty Parkway" as a secondary name.
Baloo Uriza (2018-01-13 03:49:06+00:00): I think an accurate characterization of the situation is that highways and routes get renamed regularly by legislative and executive fiat, and OklaDOT tends to ignore the naming in favor of the local nicknames.

I think you have a strong argument for changing alt_name to loc_name as Creek Turnpike, however, since loc_name is for the informal name that locals call it.

How about loc_name=Creek Turnpike and name=Liberty Parkway?  I think this reflects the local custom and the ground truth more accurately than the previous agreement based on the legislation that named it.
baveggies9999 (2018-01-13 04:00:33+00:00): Isn't loc_name typically used for things that are not commonly signed and are only known by locals? In this case, "Creek Turnpike" is signed on dozens of signs (whereas Liberty Parkway is only signed on a couple), and is known as such in official forward-facing documents and by subsequent resolutions (e.g. that which designated SH-364). I don't think that's in the spirit of the loc_name parameter.
Duke87 (2018-01-13 04:10:36+00:00): Based on the various evidence all parties have provided, name=Creek Turnpike and alt_name=Liberty Parkway seems most appropriate to me. "Creek Turnpike" is not a local nickname, it is what all of the primary guide signage says. "Liberty Parkway" only appears on one or two small roadside signs of exactly the sort honorary names like "State Trooper John Smith Memorial Overpass" and whatnot are typically posted with. Motorists do not navigate by these signs. If someone sees "Liberty Parkway" on a map it is going to mislead them since that is not what any of the signs they will be navigating by will say.
Baloo Uriza (2018-01-13 04:10:49+00:00): reg_name would work, too.  Creek Turnpike isn't a name anyone other than locals and road geeks are going to recognize for this strip based on available signage.

However, keep in mind that people are looking for reassurance after an interchange.  Entering from a midpoint, yeah, nobody really expects a street name for an onramp unless you are used to driving in LA, and not always even then.  The first signs you see from the only two major junctions after entering are for OK 364, Liberty Parkway, or both, not Creek Turnpike at this point.

People not from the area are going to go for the posted name or the route number, and might not necessarily be aware of another name even if you know, and I know, when someone says Creek Turnpike, they mean the whole route, whether we're talking the original Creek Turnpike between Riverside and 169, the Western Extension between 44 and Riverside, or the Liberty Parkway through BA or the Eastern Extension from the Muskogee Turnpike to the Rogers Turnpike.  Even when it was Liberty Parkway with a Creek Turnpike shield, unless you're used to spotting the Flyspeck 3pt font used on the shields, if you're new to the area (as I was the first time I drove it), you see Liberty Parkway and an OTA shield with something (what did it say?) on it, you're immediately thinking, "I screwed up" not "Oh, good, I am on the right road."
baveggies9999 (2018-01-13 04:30:40+00:00): While I appreciate that at two ends of the highway there is a "Liberty Parkway" sign, I find the argument that people can use those two signs for navigation to be somewhat befuddling. 

All of the approaches to this segment of road read "Creek Turnpike" - think about it like a surface street. If I'm driving down Main Street looking for Central Avenue, I know I am turning onto Central Avenue when the approach from Main Street says "Central Ave." Once I turn onto Central I'm not looking for confirming signage. 

In this case, all the approaches to this route segment read "Creek Turnpike," so I find it rather confusing that you'd argue that that road name is only known by "road geeks and locals" and is not more useful than "Liberty Parkway" for navigation.
Duke87 (2018-01-13 04:41:46+00:00): ...but to even get to that point of seeing the sign that says "Liberty Parkway" you will have passed under overhead guide signage that says "Creek Turnpike", such as this one: https://www.flickr.com/photos/watuzi/16990876093/in/dateposted-public/

If I am a driver unfamiliar with the area looking for "Liberty Parkway" I am not going to find it since there are absolutely zero signs for a road by that name until you are already on it. The signs pointing to the road, which I will see first and make a decision of where to exit or turn based on, all say "Creek Turnpike". Every last one of them.

And while you are correct that drivers may be seeking some level of reassurance after entering the road, that is not the intended purpose of the "Liberty Parkway" signs. If it were, would they not logically show the same name as all the other, larger, guide signage that drivers will see first?
Baloo Uriza (2018-01-13 05:26:46+00:00): The confirmation signs say Liberty Parkway.  The approach signs list destinations, which IIRC, are tagged at the major ramps, though not the minor ones, since the intervening ramps are inconsistently signed.  There is no name signage at any ramp in Broken Arrow, just generically "Turnpike East/Westbound" between Olive and County Line Roads, and "Turnpike North/Southbound" between New Orleans and Omaha Streets, on an east-west route, signed as east-west once you're on it, for example.  I don't think anybody's really arguing that the street name sign in that case is what's accurate at all.  Only other signage on that section are either OTA shields or OK 364 shields, and shields are indicative of routes, which are mapped as relations.  Both of these are mapped to OSM convention as relations already.

All of the information is there, at this point, which the data consumer uses is up to the data consumer, not the map data.
Baloo Uriza (2018-01-13 05:31:28+00:00): As for the guide sign for "Creek Turnpike" as a destination, that would be a good value for "destinaton:street=*" on the ramp it's referring to, as these are often the last signs to be updated.  That way a data consumer aware of these tags could say something like "In 250 meters, turn right onto OK 364 West towards Creek Turnpike" and then once it's up on 364, "Continue on OK 364, Liberty Parkway, for 7 kilometers".
Baloo Uriza (2018-01-13 05:33:47+00:00): Just like, using the above example, you were supposed to get off at Elm, without being aware of destination tagging, you'd get "In 250 meters, turn slightly right."  With destination tagging, if it's tagged with destionation:street=Elm Place, then you'd get "In 250 meters, turn slightly right, towards Elm Place."
Baloo Uriza (2018-01-13 05:35:03+00:00): The data is intentionally flexible to be able to deal with situations exactly as messy as this.
Baloo Uriza (2018-01-13 05:37:21+00:00): It's also intentionally flexible to deal with localisms, like calling this loop as "Creek Turnpike" even when it's officially not known as that, but frequently colloquially known as that to a very high degree.  Or to internationalize, like Mission Street being renderable as Yugheea Yusten in Sapulpa if your data consumer is localized with a Mvskoke language preference if you wanted to navigate in Mvskoke, for example.
US Highway 266 (2018-01-13 07:14:30+00:00): But is IS officially known as "Creek Turnpike". We've provided plenty of evidence. What more do you want? What would convince you?
Baloo Uriza (2018-01-13 07:39:44+00:00): The road is officially known as Liberty Memorial Parkway, it's signed as Liberty Parkway, and the route is Creek Turnpike and Oklahoma Highway 364.  The only conceivable argument I'm seeing here is for those that don't understand what relations are and that data consumers can and do also consume relations.
Baloo Uriza (2018-01-13 07:41:14+00:00): Which isn't meant to be condescending to participants in this thread, so much as the ire expressed is most properly directed to developers of software that uses OSM data and is not conforming to use the assumptions you're using for your use case in particular.
Baloo Uriza (2018-01-13 07:50:01+00:00): However, it's a safe default to use Liberty Parkway due to it's signposted status, locals will already be familiar with the situation and be aware even if the data consumer is not, and non-locals will typically be entering just before the confirmation signage.  For someone unfamiliar with the area, seeing OK 364 is enough, which is both on the way (obsolete method) and on the route relation (current method).

Most data consumers, destination tagging unaware, are both route relation and way tagging aware.  Most route introductions (say, northbound surface street to westbound turnpike) will say either "Turn left" or "Turn left towards Creek Turnpike" or "Turn left towards Liberty Memorial Parkway" or "Turn left towards Creek Turnpike, Liberty Parkway, OK 364" or some combination of that as it is.

Basically, just because your data consumer only picks up on one of these things is not an argument against more complete tagging.
Baloo Uriza (2018-01-13 07:57:22+00:00): A similar situation would be in Hood River County.  FS 44 is most highly known as Dufur Valley Road, but most people know it as Camp Baldwin Highway.
baveggies9999 (2018-01-13 16:02:26+00:00): I see this more as a situation like US 6 nationwide, where you have an official designation of "Grand Army of the Republic Highway," and in many states the route itself has occasional signs to that effect. 

OSM does not designate that route as "Grand Army of the Republic Highway" when the road is more commonly known by other names, even if there is occasional signage to that effect and it is officially designated as such, even with in city limits (where it may also be named "Main Street" or something, and the "Main Street" name is what is used since that has more navigational utility).

The approaches from all intersections and interchanges along the Liberty Parkway segment read either "Turnpike" or "Creek Turnpike. "  

I would further dispute that the road itself is officially known as "Liberty Parkway" (it's definitely not "Liberty Memorial Parkway" - there's no evidence to that effect anywhere) any more than it is known as "Creek Turnpike" for reasons already stated above.
Baloo Uriza (2018-01-13 20:06:16+00:00): You're describing a similar situation where the route and the roads that make up the route have different names; it wouldn't surprise me if the relation for US 6 has that name, and if it's signposted and there's documentation backing it up, then yes, I would support updating the name on the relation for route US 6 to that.

The cycleway adjacent to the Liberty Parkway is also signposted as the Liberty Parkway Trail, albeit more consistently than the adjacent Liberty Parkway is signposted.  Liberty Parkway is a member of the route "Creek Turnpike", and is mapped as such.

I'm all in favor of dropping "Memorial" out of the name, since I believe we're all in agreement that part of the name isn't a thing, and moving alt_name to loc_name to reflect the local vernacular.  Heck, I'd even help you if you want to go to the state and get the Liberty Parkway name removed so the ground truth reflects that.  But until that happens, then the reality is, the Creek Turnpike runs over the Liberty Parkway through southern Broken Arrow.
mavl (2018-12-25 00:19:15+00:00): This changeset has been reverted fully or in part by changesets 65744804, 65751034, 65750264, 65748673 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage - https://www.openstreetmap.org/user_blocks/2400].
Laseracid (2018-01-13 03:42:36+00:00): Added farm lands
viloan (2018-01-13 03:44:14+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!
dgitto (2018-01-14 15:10:18+00:00): Ciao, historic=monument è per oggetti "monumentali"(ci si entra dentro, ci si passeggia sopra). I monumenti ai Caduti vanno mappati con
historic=memorial +
memorial=war_memorial
https://wiki.openstreetmap.org/wiki/Tag:historic=memorial
mueschel (2018-01-19 13:17:50+00:00): Hi,
could you explain the meaning of the keys
CommuneLev
Dist_Name
PROVINCE
commune
?
These are not common on administrative boundaries.

Cheers, Jan
phamtranminh (2018-01-26 03:38:53+00:00): Thank you, Jan.
We're trying to update admin boundary. These keys are in original data and we will change as it reflect admin relations.
Cheers, Minh
mueschel (2018-01-26 09:42:54+00:00): Hi,
such changes to tags should be done before importing the data to the OSM database. This is a database that is in use by many people and not a database for testing. Did you follow the import guidelines for this? Can you point me to a description of for example the source of the data and its license?
https://wiki.openstreetmap.org/wiki/Import/Guidelines
phamtranminh (2018-01-26 09:52:08+00:00): Yes, it's just trial for JOSM function for copy data to OSM. We'll remove on next step when following the Guidelines. Second, Data Sharing Agrement with the city government (data ownership) is on going.
Thank you! Minh
Supaplex (2018-01-21 12:44:01+00:00): 恭喜您完成第一次的地圖編輯！ 歡迎加入開放街圖，群眾共同參與，繪製生活週遭大家關心事物的共編地圖。以下是相關的參考資料，歡迎隨時指教與提問。

編輯須知
台灣的標示依循準則可參考 http://wiki.openstreetmap.org/wiki/Taiwan
常見的圖徵標示方式可參考 http://wiki.openstreetmap.org/wiki/Zh-hant:Map_Features

台灣社群網站
台灣 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
Slack https://osm-tw.signup.team/

Happy Mapping!
SomeoneElse_Revert (2018-12-20 00:47:31+00:00): This changeset has been reverted fully or in part by changeset 65626832 where the changeset comment is: Reverting a couple of thousand mostly unnamed, mostly tourist info MAPS.ME points.  Attempts to contact the mapper failed.
SomeoneElse_Revert (2018-12-20 00:51:39+00:00): This changeset has been reverted fully or in part by changeset 65626832 where the changeset comment is: Reverting a couple of thousand mostly unnamed, mostly tourist info MAPS.ME points.  Attempts to contact the mapper failed.
5m4u9 (2018-01-13 08:18:06+00:00): el mapa es de todos y todas, nadie está a cargo, recorre la ciudad y añade por tu cuenta lo que falta, así lo hacemos en varias ciudades/pueblos de bolivia
//
tienes la app mapsme o también StreetComplete para ir completando info
Dario Alejandro Tancara Sossa (2018-01-13 14:17:03+00:00): Estoy añadiendo los lugares y de mas en si creo que redacte mal el comentario a lo que me refiero es que no encuentro los parques y canchas de mi zona por la vista satelital que al parecer no esta actualizada (El mapa Satelital) ya que en zonas donde hay construcciones en la vida real aquí aparecen zonas sin nada solo tierra aunque igual los estoy añadiendo lo que son supongo que el mapa satelital lo actualizaran mas adelante. Por cierto gracias por la informacion del app me es de mucha ayuda
5m4u9 (2018-01-13 17:09:02+00:00): hola dario, eso es solucionable. tenemos varias imágenes disponibles, pero hay que ir cambiando según cada region
//
en el modo editor, hay un icono a la derecha de capas (como azulejos superpuestos) ahí puedes cambiar el predeterminado 'Bing' que es el mas detallado
//
existe varios, puedes elegir entre ESRI o DigitaGlobe Standard que entre estos tendrá imágenes mas recientes de 2016 o enero 2017... lastimosamente municipios de bolivia no ayudan con imágenes satelitales, que nos podrían ayudar
//
si no encuentras la nueva construcción puedes añadir algo referencial a lo real, un punto o un area proximada, luego con el tiempo vamos actualizando
//
si tienes dudas con las aplicaciones me dices, don relativamente sencillas
TheSwavu (2018-01-13 08:07:27+00:00): A tip for next time: if a track's been closed but it's still visible on the aerial imagery I'd leave the way but tag it disused: (https://wiki.openstreetmap.org/wiki/Key:disused:) and add a note that the track has been closed. Otherwise what happens is that mappers will see the track on the imagery and put it back in again.
nevw (2018-01-13 11:32:47+00:00): Hi
Please place the address tags on the building instead of the roadway thanks.
JJIglesias (2018-01-13 06:31:58+00:00): Hay un viejo dicho que dice: "Con tan buena voz y mandando a cantar"
El Mapa es Colaborativo, asi q lo armamos entre todos; a nadie le pagan por hacerlo asi que el "Deberian" bien podria cambiarse por "Deberiamos" para incluirte; ya que pareces conocer la zona; Estas cordialmente invitado a "empezar a actualizar el mapa" y asi "apareceran" en el mapa: parques, negocios, museos, plazas, escuelas, hospitales y demas.
Todo aporte es mas que bienvenido.
Saludos
J.J.Iglesias

PD: te sugiero visitar
https://wiki.openstreetmap.org/wiki/ES:Bolivia:Map_Features
Dario Alejandro Tancara Sossa (2018-01-13 14:14:57+00:00): Estoy añadiendo los lugares y de mas en si creo que redacte mal el comentario a lo que me refiero es que no encuentro los parques y canchas de mi zona por la vista satelital que al parecer no esta actualizada (El mapa Satelital) ya que en zonas donde hay construcciones en la vida real aquí aparecen zonas sin nada solo tierra aunque igual los estoy añadiendo lo que son supongo que el mapa satelital lo actualizaran mas adelante
Svalbard (2018-01-13 06:23:30+00:00): Hallo Fischkopp0815,
als ich den shz-Artikel gelesen habe, kam mir gleich der Gedanke: Wenn in OSM eingetragen, dann löschen. Aber Du warst 4 Minuten schneller ...
Schönes Wochenende!
Svalbard
marc__marc (2020-02-02 00:32:37+00:00): Hello
https://www.openstreetmap.org/node/3161107803
can you draw the extend of it ?
it should include the 3 pitchs you added
https://www.openstreetmap.org/node/5336229729
https://www.openstreetmap.org/node/5336229730
https://www.openstreetmap.org/node/5336229731
Usually the pitches have no name and their ref is simply 1 2 3.
Regards,
Marc
SomeoneElse_Revert (2018-12-20 00:49:33+00:00): This changeset has been reverted fully or in part by changeset 65626832 where the changeset comment is: Reverting a couple of thousand mostly unnamed, mostly tourist info MAPS.ME points.  Attempts to contact the mapper failed.
PlaneMad (2018-01-13 17:45:46+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/55399130
Arun Balaji (2018-01-14 07:44:40+00:00): Thanx. I'm just trying to improve the road networks in South Tamil nadu :)
iandees (2018-01-13 14:39:08+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/55399142
Digne (2018-01-13 16:32:01+00:00): Hallo lithium, 

Ik zag dat er om feedback was gevraagd.

Het ziet er goed uit. Misschien is het handig in plaats van CADO de niet afgekorte versie te gebruiken. Ik kende de afkorting in ieder geval nog niet.
ligfietser (2018-01-13 14:46:13+00:00): Beter AddCycleway links laten liggen in de app aub
streckenkundler (2018-01-13 09:03:21+00:00): Hei.
nature_reserve nur für echte Naturschutzgebiete ist richtig. Trotzdem dürfte das bei der Eiche hier einen Informationsverlust darstellen... stattdessen wäre denotation=natural_monument hier angebracht, wenn der Baum als Einzelobjekt geschützt ist.

Sven
geozeisig (2018-01-13 15:30:48+00:00): danke
DD1GJ (2018-01-13 08:21:08+00:00): Hallo InnIsHkIn, willkommen bei OSM. Die von Dir verwendeten Schlüssel mit laufender Nummer (z.B. leisure_1) entsprechen nicht dem allgemeinen Schema und werden daher nicht ausgewertet. Hinweise zur korrekten Verwendung findest Du unter 

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

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

Wurde da wirklich Wald abgeholzt, um Parks anzulegen? Es gibt da leider ein Problem, weil einige wenige unvernünftige Pokémon-Spieler den Datenbestand massiv verfälschen, um das Siel zu ihren Gunsten zu beeinflussen. Daher werden alle Park-Edits  zur Zeit sehr genau kontrolliert und hinterfragt.

http://blog.openstreetmap.de/blog/2017/01/achtung-pokemon-alarm/
InnIsHkIn (2018-01-13 11:34:32+00:00): Vollkommen richtig, es handel sich um eine Waldfläche. Die Schlüssel muss ich mir nochmal angucken, ganz verstanden habe ich es noch nicht.
Ich bin selber Pokemon-Spieler, werde jedoch versuchen keine unvernünfitigen Änderungen vorzunehmen.
AlaskaDave (2018-01-13 07:13:09+00:00): Somehow, portions of 1211 including this one, got renamed Den Ha (1211). Mapper did not give source. I renamed it to what it was previously, Sunwichai Road, which is a translation of the Thai name tag.
AlaskaDave (2018-01-13 07:45:34+00:00): I checked Google, and it gives Den Ha Dong Mada Road as the name. Thai street names are notoriously hard to map properly because signs bearing the name are rare. Many times the name is just a best guess and might be based on one road sign many km distant.
keithonearth (2018-01-13 20:48:33+00:00): I suspect that the node representing Prince Rupert was deleted, but I don't want to go through the edit history to find it.
下り専門 (2018-01-13 21:19:50+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/55399726
iandees (2018-01-13 14:41:42+00:00): You added this area but forgot to add a tag to it: https://www.openstreetmap.org/way/552756113

Can you go back in and give it a more specific preset? Looks like maybe "Farmland"?
tonyf1 (2018-01-14 00:06:08+00:00): Hi. There's a tourism apartment named Shrestha Hut here? Or maybe its intended as a personal bookmark?
tonyf1 (2018-01-15 21:53:09+00:00): No reply. Transferred address to building and deleted node.
下り専門 (2018-01-13 21:21:10+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/55400049
mueschel (2018-01-17 15:50:06+00:00): Hi,
does this small residential street really have 5 different arabic names?
https://www.openstreetmap.org/way/39662753
سامبا (2018-01-17 16:20:40+00:00): Actually these are 5 separated streets, but I did not have the time to separate them as they were created as one large street.
سامبا (2018-01-17 16:24:27+00:00): I added a note and fixme-tag. If someone has time, it would be nice if this could be fixed.
mueschel (2018-01-17 17:15:13+00:00): Splitting a way in iD is simple: You select the node where you want to split the road, then press "X".