piebro/osm-data huggingface dataset:
TourenbikerFKB (2017-11-01 22:23:22+00:00): und bitte rechte Winkel machen, sofern das Gebäude rechte Winkel hat (was meist der Fall ist). Dafür gibt es eine Funktion im Editor.
mavl (2018-12-25 20:55:40+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 21:50:09+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
maraf24 (2017-11-02 22:06:47+00:00): To nie jest podwórze gospodarcze. Dlaczego tak oznaczasz?
mavl (2018-12-25 21:04:37+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 21:34:41+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 19:16:33+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 19:22:54+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 21:03:19+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 20:17:18+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 19:28:58+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
geow (2017-11-01 15:49:47+00:00): Hi jalmer, die von dir gelöschte Wiesenfahrt und der Trampelpfad am rechten Uferdeich der Thalkirchner Ache ist je nach Jahreszeit durch Schilfbewuchs nicht immer gut sichtbar, das ist richtig. Trotzdem existieren diese Wege und werden u.a. von Fischern als Zugang zur Bucht an der Antworter Achen genutzt. 

Ich habe deine Löschung daher rückgängig gemacht (revertiert) und dabei die trail_visibility des Uferweges  auf bad geändert. 

Wenn ein eingezeichneter Weg wirklich nicht mehr benutzbar erscheint, kann statt einer Löschung auch der prefix abandoned:highway=path verwendet werden. Das gibt anderen Mappern leichter die Möglichkeit, die Begehbarkeit bzw. Benutzung zu anderen Jahreszeiten vor Ort zu prüfen.

Ich bin dort mehrmals im Jahr unterwegs und kann dir bestätigen, dass dieser Weg genutzt wird - nicht nur von Bibern ;)

Schöne Grüße
Klaus
mavl (2018-12-25 21:39:57+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 20:52:01+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 20:29:31+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 21:08:35+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 21:06:31+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 19:48:12+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 20:11:55+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
gion274 (2017-11-14 17:58:12+00:00): Ciao Arlas,
tanto per capire e regolarmi eventualmente per il futuro, ti chiedo come mai hai tolto addr:city e addr:country.
Io avevo seguito la wiki per le sedi del CAI http://wiki.openstreetmap.org/wiki/CAI dove le mettono. Per le altre aggiunte
addr:place potrebbe anche starci, invece la subkey addr:neighbourhood sembra non esistere, esiste place=neighbourhood non applicabile al tag in questione.

http://wiki.openstreetmap.org/wiki/Key:addr
http://wiki.openstreetmap.org/wiki/Key:place
Cordialmente
Arlas (2017-11-14 18:01:16+00:00): Ciao. Addr:city e country sono superflui e non andrebbero aggiunti (si desumono dalle relazioni). Addr:neighbourhood esiste solo qui. Una vecchia proposta per associarlo al place neighbourhood che è rimasta negli anni. Venezia ha gli indirizzi associati al sestiere e non alla via
Arlas (2017-11-14 18:10:17+00:00): Pensa che quando ho iniziato ad aggiungere gli housenumbers anni fa era obbligatorio solo "addr:housenumber". Poi ci sono stati vari problemi nel riconoscimento dell'indirizzo quindi andrebbe obbligatorio anche "addr:street". Qui a Venezia street si dovrebbe sostituire con il sestiere, tag neighbourhood + tag place
gion274 (2017-11-15 17:49:32+00:00): Ciao Arlas, rileggendo alcune wiki:
- addr:city e addr:country "May not be required if boundary=administrative is used correctly"
quindi ci possono anche stare a maggior motivo se non so o non voglio indagare se il buondary è corretto o meno.
Venezia ha una relazione boundary di livello 8 quindi non solo il centro storico ma tutto il comune compresa terraferma.
Sarebbe utile avere anche una relazione tipo 10.

- addr:neighbourhood ho trovato la tua talk "Venice (Italy) addresses" penso che addr:place possa soddisfare le nostre esigenze "Sometimes, addresses don't contain the name of any street. Some addresses are made with the scheme "<name of some territory>, <number of house>". It can be the name of a village, islands, territorial zone"
continuare ad aggiungere una key come addr:neighbourhood che non esiste quindi non viene riconosciuta da nessun render non so che senso possa avere.

- addr:place=* e addr:street=* ho visto che OSM Inspector li fa coesistere senza problemi (se il nome della strada è esattamente quello taggato)

per quanto riguarda in maniera specifica il Tag della sede CAI mi sono accorto che OSM Inspector dà come non riconosciuto l'addr:number e anche l'addr:street
provvedo subito a correggeli cambiando 883/C in 883C ed eliminando addr:street=Sestiere di Cannaregio (probabilmente riconosce solo Cannaregio)
Arlas (2017-11-15 18:49:49+00:00): Devi comunque prendere con le "pinze" anche quello che trovi nella wiki che è scritto da noi mapper. La regola d'oro è non mappare per il render. Molte cose poi anche se sono diventate standard non sono ancora "funzionanti" o renderizzate.
Arlas (2017-11-15 18:52:56+00:00): Metti addr:place cannaregio e addr:neighbourhood cannaregio. Ci sono due richieste per l'utilizzo specifico del tag a Venezia su osmand e nominatim
gion274 (2017-11-15 20:04:49+00:00): Mai detto di mappare PER i render, era solo una constatazione e una domanda "che senso ha". Se mi fai qualche esempio concreto delle cose standard non ancora "funzionanti" o renderizzate, magari capisco meglio.

secondo me è sufficiente addr:place, per addr:neighbourood (che personalmente non ritengo necessario) aspetterò che le richieste fatte vengano eventualmente accettate e messe in wiki, osmand lo conosco e lo classifico come render
sorcrosc (2018-08-24 20:55:15+00:00): Concordo con gion274. addr:place è il tag corretto in questi casi e non è necessario inventarsene altri.
Arlas (2018-08-25 06:06:18+00:00): Non ne sono stati "inventati". Addr:neighbourhood esisteva ai primi tempi dell'aggiunta del tag addr, in cui il tag place non funzionava. I sestieri sono taggati come neighbourhood e quindi andrebbe addr:neighbourhood come tag più specifico. Place potrebbe essere maleinterpretato nel ranking degli indirizzi
sorcrosc (2018-08-25 23:39:34+00:00): È chiaro che addr:neighbourhood è stato utilizzato prima che fosse introdotto addr:place, ma non ce n'è più bisogno. Questi sono indirizzi comuni composti da località e numero (addr:place e addr:housenumber).
Non serve nient'altro, addr:place va bene per tutti i tipi di place, comprese anche le piazze (addr:square).
mavl (2018-12-25 21:36:14+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 21:22:00+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 21:06:43+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 20:42:25+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 21:51:46+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 21:47:04+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 20:13:49+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 19:16:50+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 21:26:30+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 20:57:07+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 19:50:12+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 21:37:42+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 20:52:53+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 19:36:34+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 20:15:07+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 20:54:24+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 20:35:07+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 21:28:15+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 20:11:34+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 21:00:01+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
literan (2017-11-01 11:02:17+00:00): Добрый день. Не надо ставить кривые теги на регулируемые пешеходные переходы (корректно - highway=crossing+crossing=traffic_signals). В этой части откачу.
Hind (2017-11-17 09:48:47+00:00): Зачем теперь эстакада обозначена там, где её нет? Точка была нанесена по ПОД.
Hind (2017-11-17 09:51:20+00:00): Поправил геометрию.
literan (2017-11-18 11:52:51+00:00): здесь вот лабуда осталась: https://www.openstreetmap.org/#map=18/55.79641/37.96341 Я бы поправил, да ПОДов нет
mavl (2018-12-25 20:52:09+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
daganzdaanda (2017-11-18 00:11:09+00:00): Hi Tubk86, 
you are still adding addr:housenumber=ks and addr:place=a to some nodes. Why? What meaning do these tags have for you?
daganzdaanda (2017-11-19 14:00:29+00:00): If this is a University project (DITAGIS), maybe your professor would like to get into contact with the OSM community? The way things are going at the moment is not very sustainable, and wasting a lot of effort of students and other mappers.
daganzdaanda (2017-11-19 14:03:07+00:00): FYI, please see also the comments here:https://www.openstreetmap.org/changeset/51162011#map=18/10.83807/106.77783
will_p (2017-11-02 09:19:07+00:00): Hi Mike,

I object to the change you have made here. You have changed bridge=chain to bridge=yes. How has the data been improved by this? You appear to only be stripping out information. I don't believe there is any consensus that bridges must only be tagged with bridge=yes. bridge=chain identifies a distinctive type of bridge.

I notice you have been making similar changes in dozens of other changesets. If you are going to systematically alter bridge tagging in this way, you really should discuss it with the community first. The fact that you have chosen to make these changes over several months, often with one object per changeset, does not change that, because it is clearly systematic.

Regards, 
Will
Mike Baggaley (2017-11-02 09:26:25+00:00): Hi Will, the reason for doing this is that bridge=chain is not rendered as a bridge by OSM, and is not included in the list of approved values. The bridge has a note on it saying it is a chain so no information has been lost.
Regards,
Mike
Richard (2017-11-02 13:37:22+00:00): note= tags aren't machine-readable - so in practice, moving things from a machine-readable tag to a note means that they are practically lost to all consumers.

At the very least, this should have been moved to bridge:structure= rather than a note= .

There is no "list of approved values". Those documented on the wiki are simply "informal standards" (as http://wiki.openstreetmap.org/wiki/Map_Features explains) and removing information like this is discouraged, to put it mildly.
SK53 (2017-11-02 13:39:46+00:00): On the contrary information has been lost: changing a tag to a note is always information loss. You are changing tagging for the renderer, a practice which has been discouraged for many years. Instead you should a) file an issue with the rendering github repository and b) improve the wiki documentation. There are NO APPROVED VALUES, only widely used tags. This particular bridge seems to be unusual and therefore has historic value.
SomeoneElse (2017-11-02 13:43:43+00:00): To be honest, as there's no highway or railway over it I'd add the "man_made=bridge" object (as a closed way) if possible.
It'd donkey's years since I've been to the Priest House though, so my memory isn't up to it.
Mike Baggaley (2017-11-02 15:56:09+00:00): The difficulty with having an indeterminate set of bridge values is that it is impossible to determine which of the unusual values are actually bridges. For example, there were quite a few bridge=culvert tags which on examination mostly turned out to be waterways below roads and should not have had a bridge tag at all. Therefore it is not possible to say that bridge-* means there is a bridge (which I assume is also why the OSM renderer does not show non-standard values as bridges). In this particular case I could not decide what the correct structure should be, as 'chain'  doesn't really describe it fully, so left it with just the note. Please accept my apologies if you are offended by this change - I will happily add bridge:structure=<something> if you can give me a suitable value.

I note that whilst many tags say something along the lines of "use other values as appropriate", the wiki for key:bridge states "The tag has a short list of main values given below; additional types and properties of bridges can be described with bridge:structure=*, bridge:support=*, and bridge:movable=*." which I think suggests that other values are not intended to be used in the main bridge= tag.
SomeoneElse (2017-11-02 17:37:33+00:00): > The difficulty with having an indeterminate set of bridge values is that it is impossible to determine which of the unusual values are actually bridges.

Speaking as someone who's done that, no it isn't:

https://github.com/SomeoneElseOSM/SomeoneElse-style/blob/master/style.lua#L506
Mike Baggaley (2017-11-02 17:46:02+00:00): >Speaking as someone who's done that, no it isn't:

What you have actually done there is build your list of 'approved' values :)
Richard (2017-11-02 17:50:24+00:00): > it is impossible to determine which of the unusual values are actually bridges

That's a genuine issue, but one which would be better fixed by removing the not-actually-a-bridge values than by removing the actually-a-bridge values. ;)
SK53 (2017-11-02 17:53:59+00:00): No, he's built a list of values which he finds useful. One of the main points of OSM is to allow the description of the unusual & idiosyncratic because a rigid list of approved values inevitably cannot cope. People enforcing a set of values devalues what OSM is about. For instance you have changed a number of bridge=footbridge which I have added over the past few months. It may be an inadequate tag to capture what I want to do, but it certainly has more meaning than bridge=yes. For a start it makes them much harder to find if I wanted to enhance the tagging. If unusual bridge values upset you I suggest you render your own map & stop tagging for OSM-Carto.
SomeoneElse (2017-11-03 12:27:53+00:00): Yes - what SK53 has said is correct.  It's probably clearer to look at some of the other examples in the same file (barriers, shops, offices).  For example, depending on the application it might make sense to render or otherwise process a cycle_barrier the same as a motorcycle_barrier or it absolutely might not.
user_5359 (2017-11-02 18:44:03+00:00): Welcome to OSM! What did you mean with opening_hours Fr-Su 10:00-21:00, 09:00-18:00. Can this written as Fr-Su 09:00-21:00 ?
Mappyland (2017-11-03 00:34:04+00:00): Per the website, the store hours are 

Mon – Thur 10:00am – 6:00pm
Fri – Sun 10:00am – 9:00pm
Mappyland (2017-11-03 00:35:00+00:00): Also, website is: http://camphuacosprings.com/
user_5359 (2017-11-04 14:47:07+00:00): I have modified the opening_hours value.
mavl (2018-12-25 21:10:18+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].
mavl (2018-12-25 19:29:58+00:00): This changeset has been reverted fully or in part by changesets 65765733, 65762676, 65758117, 65761081, 65759598, 65754732, 65764253 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage].