piebro/osm-data huggingface dataset:
eggie (2023-03-28 10:48:37+00:00): Dag Mikjew

In het begin wordt meegekeken. weet je nog. Je hebt nu een aantal wegen op eenrichtingsverkeer gezet. Dat zou allemaal goed kunnen. Maar meestal zijn tweewielers daarvan uitgezonderd.
Is dat hier het geval.
Dan toevoegen
oneway:bicycle=no  .. (ivt ook voor moped en mofa)  Het routeert anders niet meer voor fietsres hier.

Je edits
https://overpass-api.de/achavi/?changeset=134213898

MVG
eggie
eggie (2023-03-28 10:55:18+00:00): Pas je het zelf aan?
oneway:bicycle=no
oneway:moped=no
oneway:mofa=no
eggie (2023-03-28 12:37:44+00:00): Aangepast... routering klopt weer.
Groet
eggie
elgolfo (2023-03-28 11:42:53+00:00): Hi dolomynum,

as this road was not restricted for motor vehicles in the past: are there any signs visible, which restrict the access?

Regards
Moritz
dolomynum (2023-03-28 12:01:04+00:00): Hi Moritz,

this report came from a user - we work on a navigation app which uses OSM (magic earth), and we get frequent mails regarding map issues.

This user wrote: "Die Straße Am Schulacker von Egsdorf nach Zesch am See im Bundesland Brandenburg ist - schon seit mehreren Jahren - für Kraftfahrzeuge gesperrt. Fußgänger und Fahrrad i. O."

I checked on Google Maps for confirmation, and Google also avoids this road when planning for cars.

If it's a mistake, then please revert it.

Kind regards,
Gergely
elgolfo (2023-03-28 13:59:15+00:00): Hi Gergely,

nice to see how reports are processed (being also an active Magic Earth user). At least last year there was no restriction on this road.
My suggestion is:

* I revert this change
* put a Note for further check there
* next time I'll be there I've a look personally

Maybe the reporter confused the legal status with the road condition. It is really bad and nobody wants to drive there voluntarily by car, but access is permissive.

Btw. could be good to have something like "fixing reports for Magic Earth" in your profile.

Best regards
Moritz
dolomynum (2023-03-28 17:12:18+00:00): Hi,

Yes, that is OK with me. I've checked it now on mapillary but I could see no such sign (though the photos are several years old).

Kind regards,
Gergely
streckenkundler (2023-03-31 15:30:25+00:00): @Moritz an @Gergely

Well... This is also one of those ways that are no longer highway=unclassified for me. There are a few problem roads in the corner...
- https://www.openstreetmap.org/way/281412409
- https://www.openstreetmap.org/way/344127522

For me, the original EN definition of highway=unclassified no longer applies here. For me, these are freely accessible ways but not connecting roads in the sense of the definition of highway=unclassified.

The topic is also discussed here:

https://community.openstreetmap.org/t/highway-unclassified-oder-eigentlich-doch-highway-track/94250
Sven
fkv (2023-06-01 02:31:46+00:00): Der Beschreibung nach war das auf dem Gipfelplateau? Der Node ist hingegen südlich davon.
fkv (2023-06-01 02:33:56+00:00): PS: "verf." ist gut gesagt. Es ist nichts mehr davon übrig.
kuhni74 (2023-06-01 07:08:28+00:00): Naja, das Schloss war ja sicher größer als 50m². Ich gebe gern zu, dass ich den Ort auch ein bissl rendereroptimierend gesetzt hab, ich weiß dass das nicht goutiert wird, aber es gibt hier im Umkreis von 100m wohl keinen richtigen oder falschen Ort. Ich freu mich über Alternativvorschläge für "verf.", ich wollt halt auch verbal darstellen, dass es das Schloss (fast) nicht mehr gibt.
fkv (2023-06-01 12:06:13+00:00): Das Gipfelplateau hat 40 m Durch messer, das ist mehr als 50 m². Also der richtige Ort ist ungefähr in der Mitte (wo auch der Gipfel ist), oder du kannst eine Fläche mappen um Renderern mehr Möglichkeiten zu geben die Beschriftung woanders hin zu setzen. Außerhalb des Gipfelplateaus ist auf jeden Fall falsch (sofern nicht nur wegen Abgrabung außerhalb).
"verf". steht üblicherweise dort, wo noch Ruinen sichtbar sind. Hier ist aber gar nichts mehr. Nach OSM-Regeln sollten Objekte, von denen keine Spur mehr vorhanden ist, gar nicht gemappt werden. Als geschichtsinteressierter Mensch seh ich das nicht so streng, aber "verf." erweckt halt den falschen Eindruck, zumal ein Verfall ein Prozess ist, der ohne menschliches Zutun abläuft, während hier die Reste gezielt von Einheimischen abgetragen wurden. Darum stattdessen vielleicht besser "ehem." voranstellen, aber Patentlösung hab ich im Moment auch keine.
kuhni74 (2023-06-01 12:41:32+00:00): Da ich nicht weiß, wie die wirklichen Grenzen der archaeological site wirklich sind, wäre jegliches Flächenmappen meinerseits nur Kaffeesudlesen. Größer als nur das Gipfelplateau war es aber laut http://noeburgen.imareal.sbg.ac.at/result/burgid/861 fix. Gerne ändere ich mal von "verf." auf "ehem." um.
fkv (2023-06-01 13:46:14+00:00): Dass es größer war als das Gipfelplateau, kann ich dort nicht herauslesen. Die Vischer-Zeichnung zeigt doch ziemlich klar, dass die Burg das ganze Gipfelpletau ausfüllt, aber auch nicht mehr. Nur das kleine, rechte Gebäude steht außerhalb und ungefähr dort, wo du den Node gesetzt hast. Wenn man für die Fenster und die Einfahrt übliche Maße annimmt, kommt man für die Länge der Burg auch nicht auf mehr als 40 m. Vischer hat die Umgebungen der Burgen oft fantasievoll gezeichnet, aber die Burgen selber ziemlich realitätskonform.
kuhni74 (2023-06-01 13:51:57+00:00): Der Text auf noeburgen ist noch etwas informativer ("Vorwerk") als die Zeichnung
Nakaner (2023-03-28 13:06:38+00:00): Hallo solarisz,

du hast in diesem Änderungssatz einen Weg in der Kernzone des Nationalparks so umgetaggt, dass er wieder auf diversen Karten sichtbar wird. Gibt es hierfür einen besonderen Grund?

Die Community hat sich mit der zuständigen Naturschutzbehörde darauf verständigt, dass in Renaturierung befindliche Wege in hochsensiblen Schutzgebieten nicht gelöscht, sondern mit dem Lebenszyklus getaggt werden.

https://wiki.openstreetmap.org/wiki/Lifecycle_prefix

Viele Grüße

Michael
solarisz (2023-03-29 07:36:34+00:00): Hallo Michael,
ja ist ein Kletterzugang https://www.nationalpark-saechsische-schweiz.de/wp-content/uploads/2013/12/12-Schmilkaer-Gebiet-Blatt-03.pdf und vor Ort nicht durch ein Kreuz als gesperrt markiert, ich war im Winter dort. VG, Stefan
eggie (2023-03-30 07:10:26+00:00): Dag Marcel..
Je vraagt feedback
De adresnode die je op de weg hebt gezet zal ik terugzetten. Die hoort op het gebouw zelf.
https://overpass-api.de/achavi/?changeset=134215789

addr:housenumber	6-211
Nog een tip... Woonstraten zijn highway=residential of wellicht hiet highway=service?

MVG
eggie
marcelsmidt (2023-03-30 08:13:45+00:00): Met dank! tevens voor de tips
eggie (2023-03-30 08:40:50+00:00): Marcel

Het gebouw heb ik wat aangepast comform de belijning van de BGT.
Dan lijkt het meer op wat je in werkelijkheid ziet. 

Mapse
eggie
nyampire (2023-03-29 07:07:09+00:00): OSMへようこそ！

すみません、1点確認させてください。
事務所や警察などの情報をもとに編集をされるとのことですが、緯度経度についてそれらの情報はOSMとのライセンスが整合がとれているでしょうか。
具体的には、どの場所に事務所が存在するかを、Google Mapsで検索していたりしないでしょうか。この件に関して、利用可能なオープンデータは存在していないはずです。

すみませんがご確認のほど、よろしくお願いします。
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/134216308
yakuzamap (2023-03-29 08:26:20+00:00): 歩いてGPSで位置を取得しました。
nyampire (2023-03-31 04:30:37+00:00): コメントありがとうございます、了解しました！
興味を持たれている対象が対象ですので、どうか気をつけて調査ください！
TagaSanPedroAko (2023-06-23 22:10:10+00:00): Americans or Canadians who don't speak German will have no idea what an LKW means. Please stop adding these labels. Those labels are also descriptive; the fact a lane or parking is used by trucks is already highlighted by the hgv= tag. 

(strojový překlad do češtiny)

Američané nebo Kanaďané, kteří nemluví německy, nebudou mít ponětí, co znamená LKW. Přestaňte prosím přidávat tyto štítky. Tyto štítky jsou také popisné; skutečnost, že jízdní pruh nebo parkoviště využívají kamiony, je již zvýrazněna značkou hgv=.
HaPe-CZ (2023-07-03 05:54:08+00:00): In Europe, even outside Germany, the abbreviation LKW (freight) or PKW (passenger) is used. These, on the other hand, do not use the abbreviation HVG. I think the combination LKW / TRUCK is used to describe it, which is understandable to both English and Germans. Some Americans and Canadians don't know the abbreviation HGV either. Stop removing the LKW/TRUCK description. Thank you.
TagaSanPedroAko (2023-07-04 04:40:35+00:00): That doesn't matter. The feature is in North America: German is not generally used there. So, like you're applying what you're doing in Europe assuming North America does the same with those at the border. Please stop.
michael60634 (2023-07-04 05:10:22+00:00): Do not try to apply European tagging norms to Canada and the United States, especially if it's against the wishes of the local mapping community. Note that changesets adding "LKW" and "PKW" may be reverted as those terms are not used here.
HaPe-CZ (2023-07-04 07:06:50+00:00): OSM is a globally accessible project. So even for non-US citizens !!! They must also be able to read the map !!! HGV and LKW are equivalent abbreviations. Only the insulted arrogant one returns correctly made repairs. Only a fool prefers a poorly drawn map with a theoretically good description.
HaPe-CZ (2023-07-04 07:14:55+00:00): @TagaSanPedroAko please use the deepl.com translator ;)
jtracey (2023-07-04 17:19:56+00:00): Even if you believe European mapping guidelines apply here (they do not), it is never correct to put descriptions as names.

https://wiki.openstreetmap.org/wiki/Don%27t_map_local_legislation#Don't_map_for_the_renderer
jtracey (2023-07-04 17:27:06+00:00): See also: 
https://wiki.openstreetmap.org/wiki/Editing_Standards_and_Conventions#Names_are_not_for_descriptions
https://wiki.openstreetmap.org/wiki/Key:name#Additional_data
https://wiki.openstreetmap.org/wiki/Category:Tagging_guidelines_by_continent
https://wiki.openstreetmap.org/wiki/Category:Region_specific_tag
woodpeck (2023-07-04 19:16:20+00:00): Dear HaPe-CZ, I am writing this as a member of OSMF's Data Working Group. Adding "TRUCK/LKW" as a name to any service roads or parking areas is not acceptable. It is not the name of these parking areas. You may use access tags (eg motor_vehicle=no,hgv=yes or hgv=designated) to show that something is for trucks only. OSM is an international platform but that doesn't mean that you can label things on the map so that you and your compatriots have it easier to navigate in America.
HaPe-CZ (2023-07-05 05:56:55+00:00): @jtracey: Yes, it is written there but OSM has many flaws and shortcomings and different markings in editing and on the map. But tags and properties must be traced as object detail. If the information is "on the map" it is quickly visible and faster. Who among "external" visitors will immediately click the arrow and read the tags?
HaPe-CZ (2023-07-05 06:01:12+00:00):  @woodpeck: OSM is an international platform but that doesn't mean that you can label things on the map so that you and your compatriots have it easier to navigate in America.
... 
Here, unfortunately, I see a considerable amount of Americanism and nationalism. Why shouldn't Europeans be able to easily use OSM mapping in America??? Are you following Trump's America First?
michael60634 (2023-07-05 06:07:07+00:00): And with that last comment, and shred of credibility is gone.

But to respond, no, we are not going to use German tagging for features in the US and Canada. It's not "America first" or anything related to the former president. Nobody is forcing mappers in the Czech Republic or Brazil to follow Canadian and US tagging norms.
jtracey (2023-07-05 06:19:02+00:00): I strongly suggest reading the links I provided. The OSM website is not intended for users, it's intended for editors. OSM is not a map, it's a database of map data, which different applications can choose to render as they see fit.  For example, here is a map that uses German OSM tags when rendering: https://openstreetmap.de/karte/

Again, I would suggest familiarizing yourself with the wiki and understanding why this large, rather old project does things a particular way before deciding you know best.
https://wiki.openstreetmap.org/wiki/Tagging_for_the_renderer
https://wiki.openstreetmap.org/wiki/Renderer
HaPe-CZ (2023-07-05 11:38:55+00:00): @ToAll: I just wonder at your nationalistic effort to prove Trump's "America First" point. More and more writers and trolls, you stick here like wasps on honey. No one noticed you were addressing 3 month old edits. :) Bye
woodpeck (2023-07-05 13:07:40+00:00): It appears most "LKW/TRUCK" designations have already been cleaned out by  michael60634 and  TagaSanPedroAko, thank you for that. I have just run a script to get rid of the remainder (including some highway links and service roads) in https://www.openstreetmap.org/changeset/138148251
michael60634 (2023-07-05 15:10:10+00:00): I still don't understand why you are trying to make this a political issue. It's not. And I especially don't understand why you are doubling down on it.

Local mappers are not "trolling" because we don't want to use German truck designations for roads in North America, especially for the "name" tag. In fact, your behaviour is more like trolling, since you are accusing everyone that disagrees with you as having some kind of political bias and affinity for Donald Trump.

We don't notice all incorrect edits immediately as OSM is a volunteer-run project. We aren't paid for this, and we have our own lives that take priority.

If you are overwhelmingly told that you are causing the problem, then maybe you should stop doing what you are doing and reflect on your actions.
clay_c (2023-07-05 18:29:40+00:00): HaPe-CZ, why are you adding German terms specifically? Why not Chinese? Or Spanish? Or Arabic? What criteria are you using to determine which language goes in the name?

If we tried to include every language in the name, then certainly every literate person in the world could read it. But of course, it would be unreasonably long. So the global community of OSM mappers generally agrees that each local community should decide which languages are appropriate for the name.

Despite our significant English-speaking majority, the United States is a vibrant multilingual country. We have plenty of places where multiple languages belong in the name, like Kaser, New York [1] or the Navajo Nation [2]. However, I'm not aware of any border communities in the US with a significant German-speaking population, so naming these lanes "LKW" would be against local tagging guidelines. Nearly all signs in the US (outside of Puerto Rico) are in English, and we map what's on the sign.

As a local of the Czech Republic, you are free to propose changing the language of names in your home country. But when you try to change tagging guidelines halfway across the world in a country you're not familiar with, it's natural that you'll receive negative feedback.

[1] https://www.openstreetmap.org/node/158859890#map=15/41.1194/-74.0627
[2] https://www.openstreetmap.org/relation/9795457
HaPe-CZ (2023-07-06 08:46:05+00:00): @ToAll: I repeat, you're dealing with a 3-month-old edit. You're still sticking here like wasps on honey, just trolling and competing to see who has the bigger ... (ego).
woodpeck (2023-07-06 08:51:55+00:00): The reason this discussion continues is that instead of saying, yes, sorry, I overstepped a line here, you dig your heels in and continue to claim that you were somehow right. This is not the first time you're getting into a conflict with mappers thousands of miles away and believing that somehow you know better. And the fact that this edit is three months old doesn't mean anything - some errors take more than a year to be spotted and fixed, but still one would want to find out why the error happened in the first place and make sure that it is not repeated. The aim of this discussion is to make you understand that your approach and attitude are problematic and you need to change them if you want to make a lasting positive impact on OSM.
michael60634 (2023-07-06 08:58:19+00:00): An edit can still be incorrect and criticized even if it's three months old. Believe me, I know from experience. And for some reason you cannot accept that you made a mistake, and instead resort to calling everyone else trolls instead of accepting criticism. And nobody, other than you, is acting as if they are in some competition. Your behaviour is really not the kind of behaviour required for OSM, because to put it bluntly, you're acting quite immature and refusing to listen to feedback from local mappers. And as I see from comments on talk-ca, you've acted in exactly this way in the past too.
HaPe-CZ (2023-07-06 10:43:47+00:00): The first thing to do is to apologize for the nationalistic insinuations. That's not on my side.
Xandaros (2023-07-14 14:40:26+00:00): I don't think there is anywhere in the world where this tagging would be accepted. It's blatant misuse of the name=* tag. This would have caused issues even in Germany.
clay_c (2023-07-14 14:53:15+00:00): Not to mention, HaPe-CZ is accusing the German and Canadian participants in this conversation of American nationalism.

Personally, I have a lot of complicated feelings about the United States. I'm not particularly patriotic. But I'm not going to start adding Swahili and Hindi names to features in the Czech Republic, and then accuse the locals of Czech nationalism when they notify me that it's against local guidelines. When I map in an unfamiliar country, I talk to the local community and follow their guidelines.
mavl (2023-04-25 09:04:20+00:00): This changeset has been reverted fully or in part by changesets 135307362, 135331978, 135327734, 135318197, 135323168 where the changeset comment is: Hi all. The changesets are reverted [DWG has the request to revert the changesets. Reason: valid data are deleted - https://www.openstreetmap.org/user_blocks/7056].
Martin Constantino–Bodin (2023-04-10 19:20:09+00:00): J'avais déjà mis le toboggan en linéaire : j'enlève le doublon. Ou est-ce qu'il vaut mieux plutôt le garder en tant que PoI ?
Владимир К (2023-03-29 12:34:20+00:00): Добрый день. не нужно подписывать каждый проезд и куда оно ведет. посмотрите пожалуйста ссылки в моем профиле. всё за вами исправил
HJGroenVRFR (2023-03-29 11:01:39+00:00): Hallo,
Zie dat je een aanpassing hebt gedaan in wegen net.
Kunt je aangeven wat je hier mee beoogt en welk voordeel dit bied?  Als dit meerwaarde heeft kan ik dit ook op andere plekken toepassen.
Hoor het graag

Groet hjgroen
mavl (2023-04-25 09:07:32+00:00): This changeset has been reverted fully or in part by changesets 135307362, 135331978, 135327734, 135318197, 135323168 where the changeset comment is: Hi all. The changesets are reverted [DWG has the request to revert the changesets. Reason: valid data are deleted - https://www.openstreetmap.org/user_blocks/7056].
4004 (2023-04-01 23:58:25+00:00): здравствуйте, спасибо за правку.
тут два адреса? я вижу какой то аншлаг со стороны Городничанской, но не вижу что на нем https://www.mapillary.com/app/?pKey=1125049551342538&focus=photo
user_5359 (2023-03-29 16:53:30+00:00): Welcome tom OSM! I remove your SEO SPAM entry (mostly foreign keys and old data)
TagaSanPedroAko (2023-05-17 00:05:13+00:00): Looks like you used the wrong Metro brand for Metro Supermarket or Super Metro. Please be careful as the Metro brand is still not in NSI.

Morag sayop ang imong gigamit nga tatak sa Metro para sa Metro Supermarket o Super Metro. Palihug pag-amping kay ang Metro brand wa pa sa NSI.
spatialia (2023-05-08 19:19:30+00:00): Hey there, just a heads up that I'm reverting the change you added here - sourcing data from Google Maps isn't allowed (and can get the whole project into trouble) - see this wiki article about the Google Maps license and how it forbids use in datasets like OSM: https://wiki.openstreetmap.org/wiki/Google

This page on the wiki has some alternatives to Google Street view (with varying last-update dates) that *are* allowed for use in OSM when cited: https://wiki.openstreetmap.org/wiki/Pick_your_mapping_technique#Street_view_data

Also, the speed limit in this changeset of 40 mph seems incorrect for this location - I've regularly seen 50 along this stretch (including looking at the same street view imagery). Is there a construction restriction (which shouldn't be included in OSM), or do you have an alternative source for that speed?

https://www.openstreetmap.org/changeset/135866527
Makkaroni_100 (2023-04-23 13:00:06+00:00): Auf welche Quelle bezieht sich das, dass es eine Einheitsgemeinde ist?
Wo besteht hier der Unterschied zu Beispielsweise Bitterfeld-Wolfen?
Makkaroni_100 (2023-04-23 13:00:51+00:00): https://statistik.thueringen.de/datenbank/portrait.asp?TabelleID=GE001633&auswahl=gem&nr=61115&Aevas2=Aevas2&SZDT=

Hier geführt als Stadt.
Enock4seth (2023-07-30 22:30:24+00:00): hi, be careful when mapping not destroy existing features. Use correct tags, since you are using JOSM, pressing F3 should help you find presets easily. "road=yes" is not a valid tag. You connected two parallel roads, fixed now. See map features for common OSM tags https://wiki.openstreetmap.org/wiki/Map_features

When mapping building with holes/inner openings, use multi-polygons.

here is a resource for getting started with JOSM https://learnosm.org/de/josm/start-josm/
AurélienQ (2023-04-18 19:11:50+00:00): Juste une remarque, la relation n'a pas été prise en compte dans les modifications (tu n'as pas ajouté les nouveaux chemins à la relations)
Pastèque24 (2023-04-18 19:30:48+00:00): Oui c'est possible, puisque je ne sais pas comment fonctionne le système de relations sur OSM.
AurélienQ (2023-04-19 18:36:56+00:00): Pour résumer, les relations permettent de lier facilement des objets en relations, comme tout les éléments d'une route, ou toutes les parties d'une frontière, ...
Généralement elles sont utilisées pour des itinéraires (de bus,...), infrastructures (voie ferrées, routes,...), sites naturels (fleuve et bassin versant,...).
En l'occurrence la relation qui nous concerne est celle de la ligne nouvelle lyon turin, qui existe déjà. Il suffit avec l'ID de modifier l'objet et d'ajouter la relation (tout en bas) en entrant son nom. Tu peux avoir plus d'infos sur la page du wiki. 
Normalement ils demandent le rôle de l'objet dans la relation, mais dans un premier temps ne t'en occupe pas, c'est plus simple.

J'espère t'avoir éclairé ; )
Si tu ne souhaite quand même pas le faire dis le moi je m'en chargerais. C'est juste que c'est quand même utile de connaitre le fonctionnement des relations, car cela évite d'en abimer lorsqu'on modifie la carte.
Dimitar155 (2023-04-11 19:36:19+00:00): Hello Termininja,

Can I ask you from where you got the streams information? I couldn't locate https://www.openstreetmap.org/way/1157924807 on Bing or any other imagery. It also looks like that stream goes through the middle of some buildings.

Best wishes,
Dimitar
SekeRob (2023-03-28 13:36:35+00:00): And we have a winner, no more rendering of wetland through rivers and canals, in this worked over zone.
Minh Nguyen (2023-07-06 02:17:14+00:00): Hi, I don’t think Mehring Way should be a primary road. Despite the routing of U.S. 27 and U.S. 52 along this street, it’s basically only for accessing the stadiums and parks and for some local truck traffic, but I don’t think it’s as much of a through route as 2nd and 3rd Streets (which aren’t part of any numbered route). Any objection to downgrading Mehring Way back to secondary?
Minh Nguyen (2024-03-13 20:33:35+00:00): Reverted in changeset 148611921.
eggie (2023-03-28 14:07:56+00:00): Beste Mik   Beter geen wegen van de kaart verwijderen en vervolgens opnieuw gaan intekenen. De historie gaat dan verloren.
horae unknown heeft geen zin om te gaan toevoegen aan voetpaden.
MVG
eggie
eggie (2023-03-28 14:08:51+00:00): Verbinding weer hersteld en pad losgemaakt van landuse grass
eggie (2023-03-28 16:31:10+00:00): Weet jij waar de dubbele naam Sportlaan Kennedylaan vandaan komt. Is day wel een officiële naam voor dit wandelpad? 
\groet
eggie
eggie (2023-03-28 18:42:58+00:00): Straatnaam verwijderd
limes11 (2023-08-06 22:59:47+00:00): Hallo,

diese Änderungen wurden revertiert. Diese Wege existieren seit vielen Jahren.

Die Illegalität wird mit access=no ausgedrückt. Dies ist das gängige Vorgehen in Naturschutzgebieten. 

Viele Grüße Limes