piebro/osm-data huggingface dataset:
AndresDuhour (2021-06-19 11:27:02+00:00): Buen día! ha agregado muchas calles rurales como urbanas. Voy a corregir la clasificación a highway=track. Saludos!
chnav (2020-01-13 14:07:31+00:00): Full revert. Mass edits using wrong mapping practice. These are T-junctions, not Y- or V-junctions.
Pellissippie (2020-01-13 22:51:46+00:00): I responded here: https://www.openstreetmap.org/changeset/78033345
eggie (2019-12-17 07:25:03+00:00): Reverted by changeset #78511678
eggie (2019-12-17 07:30:19+00:00): Dag Krepno,
De changeset heb ik teruggedraaid. 
Dit is op de kaart een kwetsbaar gebied vol met multipolygonen die voor de juiste rendering zorgen. De landuse is al gemapt op de outer van een ingewikkeld stukje mapping als landuse=grass  Dat zie je waarschijnlijk niet want dit staat op de outer-relatie.
Neem in zo'n geval contact op met de voorgaande mapper als je zaken ingrijpend gaat veranderen. Beter nog niet aan beginnen en zeker niet met een "speeltje" als editor iD.
Zou het voorlopig zo laten. 
MVG,
Eggie
Kovoschiz (2019-12-17 07:43:31+00:00): See Discord.
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/78500403
Kovoschiz (2019-12-17 07:43:39+00:00): See Discord.
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/78500403
Kovoschiz (2019-12-18 09:41:23+00:00): Are you going to fix this?
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/78500452
Kovoschiz (2019-12-18 09:41:56+00:00): Hello?
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/78500509
mbethke (2019-12-17 07:11:36+00:00): Hi,
I suppose you wanted to tag that area, too? ;) I just did that, tagged as a lake.

cheers,
Matthias
Kovoschiz (2019-12-17 07:54:51+00:00): Thank you. I helped you add the address.
            ---
            #REVIEWED_GOOD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/78502448
DaveF (2020-01-28 00:15:18+00:00): Hi
There's already a railway=station node so deleting duplicates from building.
JayTurnr (2021-01-28 22:03:25+00:00): Would shop=vacant be better than disused:shop=yes?
samthecrazyman (2021-01-31 17:09:31+00:00): That can be changed - when I edited these, vacant shop was unavailable under the iD editor and I just changed it to what the wiki said but it is now so could well be changed. Good spot
JayTurnr (2021-01-31 21:09:02+00:00): No worries :)
Kovoschiz (2019-12-17 07:43:56+00:00): See Discord.
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/78505241
BCNorwich (2019-12-17 07:54:05+00:00): Hi, Your contributions have been amended, cold you please have a loo at the changes for your future reference.
Regards Bernard.
Kovoschiz (2019-12-17 07:44:33+00:00): https://discordapp.com/channels/550009593468813312/550324691001147422/656398523838758913
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/78506710
phidauex (2019-12-17 06:27:30+00:00): Hi, welcome to OSM! Please be aware that you are editing the live map database which is published immediately, so please don't enter test or other unverified information. Please remove the offices you created, or they will be reverted. If you need to test something, there is a development server you can use.
BCNorwich (2019-12-17 07:59:48+00:00): Hi, it is OSM practice to amend/correct what is already mapped rather than delete and redraw. Thus the history of the original mapping is kept along with your corrections.

In this case the school area outline should have been corrected instead of deleted. 

Regards Bernard.
Kovoschiz (2019-12-17 07:44:54+00:00): https://discordapp.com/channels/550009593468813312/550324691001147422/656398758338101281
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/78507033
Kovoschiz (2019-12-17 07:45:06+00:00): https://discordapp.com/channels/550009593468813312/550324691001147422/656399471520776193
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/78507167
Kovoschiz (2019-12-17 07:43:48+00:00): See Discord.
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/78507592
WoodWoseWulf (2019-12-20 21:27:56+00:00): Hi blackcat3434,

This location is already on the map:
https://www.openstreetmap.org/way/82862977

On OSM there's a few principles we try to maintain for good practice, two of them are:
Not tagging for the renderer:
https://wiki.openstreetmap.org/wiki/Tagging_for_the_renderer
and 
One feature, one OSM element:
https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element

If a particular renderer isn't displaying national parks, that's an issue with the renderer, not with OSM.
literan (2019-12-17 18:00:26+00:00): я уже просил не прилеплять линии деревьев к серединам дорог. Удалил, повторенье - мать ученья
Mazda05 (2019-12-17 19:14:27+00:00): котельная - это не name, это тип объекта
Ars-UA (2019-12-18 12:39:27+00:00): Пока не знаю, как сделать правильней. Надо подумать.
Mazda05 (2019-12-18 19:55:56+00:00): информация, как размечать котельные, есть на wiki
Cyrille37 (2019-12-29 08:05:50+00:00): Bonjour,
Pourquoi ne pas avoir mit cette pizzeria comme "restaurant" cat il me semble que le "food_court" sert à autre chose.

Quand je passe devant (oui, je ne m'y suis pas encore arrêté) ça ressemble à une pizzeria avec son propre local, donc pas "food_court".
https://wiki.openstreetmap.org/wiki/FR:Tag:amenity=food court

Merci et bonne contribution.
ShubhamZope7010 (2019-12-17 06:38:05+00:00): i am blogger at https://readingreneereviews.com/best-offset-smokers/
locke (2020-02-10 12:37:04+00:00): Hi, you recently added a highway-tag to the clutha gold trail further south of Lawrence. Is this part of the trail already existing and has been built and can be used, or is it still proposed/planned?
Regards
Stephan
Frans S (2020-01-09 14:34:10+00:00): Hello. Thanks for mapping. 
I review mappings and validate. A request.
On this changeset you only mapped buildings with a somewhat dark roof. Quit an number of buildings with a natural colour roof were not mapped. I know . Sometimes it is hard to see the difference between a building and farmland or yard. Always check for a shadow to proof that the object is above groundlevel and thus probably a building.
Don' let buildings cross highways of connect nodes to other features
Best regards and keep mapping
Kovoschiz (2019-12-17 07:45:20+00:00): https://discordapp.com/channels/550009593468813312/550324691001147422/656400093687054347
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/78510473
Kovoschiz (2019-12-17 07:45:28+00:00): https://discordapp.com/channels/550009593468813312/550324691001147422/656400224683556868
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/78510837
Kovoschiz (2019-12-17 07:45:39+00:00): https://discordapp.com/channels/550009593468813312/550324691001147422/656400467454197790
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/78511000
user_5359 (2019-12-26 16:11:13+00:00): Hello! You added a bigger number of unknown tags 
ACRES, AGNCY_ID, AGNCY_TYP, HOLDING_ID, MNG_AG_TYP, UNIT_ID
in this change set. Please explain the source of this information and the meaning of the keys. See also http://overpass-turbo.eu/s/Pfg
stevea (2019-12-26 17:33:11+00:00): They are from CPAD 2019b data, as documented on our Contributors and Santa_Cruz_County,_California wiki pages.

While I endeavor during these additions to remove all tags (except sometimes ACRES and usually UNIT_ID, so that we may compare between older CPAD, OSM versions and newer CPAD versions of the data), other tags (like the ones you mention) can and should be removed.

As the latter wiki mentions, "Sometimes tags from the shapefile in ALL CAPITAL LETTERS were left in the data when they do not logically map well to OSM tags. Where objectionable, these can be deleted."

I have been and do "better tag" on these.  However, I don't see some stray tags finding their way into our map as a major problem.  You are welcome to delete these, too.  I appreciate you calling them to my attention.
user_5359 (2019-12-26 19:48:17+00:00): I don't have anything against a version number (source) and / or an ID from the source (ref:source). However, I am not a friend of undocumented keys, which also violate the rule of lower case and British English. Furthermore, an area indication (ACRES) to a key without unit is difficult and only conditionally suitable for debugging. If the area is needed, it can be calculated from the OSM data and does not have to be stored with an unrealistic number of decimal digits in the OSM data.
stevea (2019-12-26 20:03:44+00:00): Going forward (and backward, as it has been included for exactly this reason), in time, UNIT_ID is a highly-useful tag to "index" between various versions of CPAD data (so far we are up to a third, though we no longer call them v1 / 2016a or v2 / 2018a, as no v3 was coined with 2019b, we now simply say "CPAD 2019b" and will do that going forward).  So, please do continue to expect to see UNIT_ID in these data, it isn't unreasonable to include this for these reasons, so we do.  (When I say "we," I include many local California-based OSM volunteers who use and coordinate CPAD data into OSM, such as doug_sfba, with whom, among others, I/we coordinate these activities).

ACRES is often included because the most common thing to change from version to version is the area-size of the unit, and the value of this key changing is a clear indication this happened (and so older data should be updated with the newer data).  If a unit's shape changes in a subtle way, that can be hard to see visually, but this always will change the ACRES value, even by a tiny amount, so the many-digits of precision are helpful, perhaps even crucial to detect this.  Several bytes of data are not "an unrealistic number of decimal digits," as this technique of using area to detect subtle changes in version-to-version data is both clever, effective and relatively low-cost (in terms of data stored).

The keys included may be undocumented, true, but there is no secret where they come from, why they are included (to wit, this and other changeset comments like it).  Obviously you have noticed that as we begin our third (only partial, only carefully) bringing-into-OSM of these data (it's not an import, more like a one-at-a-time curation), there is some evolution of process, and that has included leaving in tags which do not (always) map well to documented OSM tags.  Also, OSM tags (like park, national_park, natural_reserve and protected_area) have evolved, too, over the years, so it's very much like "changes chasing changes."

Again, I have said here and in wiki, "where objectionable, the tags may be removed" as well as "a few stray tags here and there as we evolve a process to better improve protected-areas in California are not a major problem."  I've documented, I answer politely in changeset comments, I do not keep secrets nor am I trying to "get away with anything" as we do these things.  Don't like the tags?  Remove them, please.  I (and others) don't seem to find them a problem.
stevea (2019-12-26 20:33:51+00:00): Think of ACRES as a kind of checksum of the data, as that is how it gets used (for comparison purposes between versions of data).
freebeer (2019-12-27 01:40:25+00:00): UNIT_ID as you use it, seems a property of the source data that, much like the TIGER wozzit numbers that get automagically deleted upon editing by most editor utilities, and are stored as subtags of top-level tiger tags.  that sentence lost its way mid-stream, if you find it, please send it home.

i feel what you should do is to map these into subtags of the accepted OSM top-level `source' tag as this info is relevant to that and as you note, is useful within OSM for debugging or troubleshooting or version-tracking.

i'm no tagging whiz, having just taken one, but anyway, from what little i've paid attention to, i'd guess there could be something like source:cpad:version=whatever that includes the value presently stored in UNIT_ID and makes it immediately obvious what it is with no need to consult the wiki.  tweak the grammar as needed to match OSM conventions, be they version:cpad:source or whatever, i tend to ignore such details while holding on to the general idea.  replace `:version' with whatever OSM uses to represent same, `revision' or wossit.  leave out the `cpad' if the second-level version-alike tag exists in general, though i've tended to note the source itself becomes a subtag, if i'm not imagining things.

ACRES should also be a subtag under source:cpan or whatever; again as i pay no attention to tagging details, i don't know if something on the order of `checksum' or `uuid' is accepted and in use, and for that matter if in the former case, there are established standards like `crc16', `md5' and so on, and if `uuid' also refers to a specific format.  then it will be obvious that this is a property of the imported data, rather than an arbitrary tag, and it will be clear that these tags are useful for OSM data maintenance and coördination with the original source, as opposed to tags only meaningful outside of osm.

feel free to ignore my input as i readily admit to having only a superficial view of what's going on here.  thanks.
stevea (2019-12-27 01:58:53+00:00): Thank you for your opinions.
user_5359 (2019-12-27 05:02:45+00:00): I really appreciate your work and I also answer respectfully. 
And I'm not the only one who worries about rash adoption of original keys, although there are quite useful suggestions according to OSM standard, which would allow a clean classification without further sources. 
And because I appreciate your work, I won't make the mistake of a mass edit, because I can't identify your hidden needs for the non-OSM specific key. 
Please consider these wishes at least in your future actions, because there is enough work to be done on data quality.
stevea (2019-12-27 05:07:04+00:00): This isn't rash, this isn't adoption.  This is a live, plastic map made by humans, plural.

The process being built is not radically altered by the plastic uses of tags as they are used here; it is human and organic.

Because of the tone here, I have begun to formulate in my mind a plan, rough sketch and several ways forward.  There seems a way of conflating a well chosen tag that serves as a sort of checksum of data which editors can use as a comparison token, of sorts.  That's it in a nutshell, it might take me hours, days or weeks to hatch it.  There are no hidden needs, rather "non-OSM specific keys" aren't seen as a major crime, more like you are seeing eraser crumbs and I'm taking a deep breath right now to blow them away.  That's all.

I hear the concerns.
stevea (2019-12-27 05:48:28+00:00): It is helpful for me to absorb more community input about "source" tags:  explicitly set on each datum or does a reference to the source in changeset comments suffice?  I've watched the trend towards the latter for many years, yet I consider an explicit source tag on each CPAD datum, perhaps with a sub-namespace flavor.  Whatever I do can and will be documented as "a simple thing to do when uploading CPAD data" in a rule or two.

But for now, I think I'm on track with this.  Another week or month, could be a few days.  I'm a busy person.  Feedback appreciated.
stevea (2019-12-30 21:59:07+00:00): I have created https://wiki.osm.org/wiki/Using_CPAD_data

Feedback is welcome and appreciated.

If you'd like me to "go the extra mile" and search and purge older tags, I will do so if requested, but I consider that an annoying errand, as there isn't a great deal of this "cruft" around, and going forward, this newer protocol will reduce/eliminate it.

The wiki offers the same advice as in Santa Cruz County:  "Where objectionable, these can be deleted. However, please leave intact (older) tags of ACRES and UNIT_ID."
SHARCRASH (2022-07-13 11:13:01+00:00): Hi!
In v11 you've introduced this bollard www.openstreetmap.org/node/69049381 on a secondary road... This clearly is very unlikely to exist and as far as i recall when I passed there there has never been a bollard. I've just tried now if routing services still would pass over it, of course not, this for two years and half. So I consider this as a serious error from you even if you're a beginner in OSM, I think you should have some basic sense to realise that this is strongly to be avoided. 

Also adding this bollard has nothing to do with HOTOSM project 3603.
booktiger (2020-10-17 08:08:33+00:00): 南八里庄站已经取消，而且没有预留。
Kovoschiz (2019-12-17 10:57:29+00:00): Bay =/= place named after the bay (cf Causeway Bay, Kowloon Bay)
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/78512922
minghong (2019-12-17 11:01:06+00:00): Please don't make it personal.
Lei Yue Mun is officially recognized as a suburb:
https://www.map.gov.hk/gm/map/search/keyword/Lei%20Yue%20Mun#0
Kovoschiz (2019-12-17 11:10:30+00:00): >Please don't make it personal. 
You have been personally making all these edits. Who should I talk to? 
>Lei Yue Mun is officially recognized as a suburb: 
The problem here is Lei Yue Mun Village =/= Lei Yue Mun again
Kovoschiz (2019-12-17 11:15:15+00:00): Lei Yue Mun Village is this group of villages here.
Kovoschiz (2019-12-17 10:59:50+00:00): A saddle can be a neighborhood (cf Cha Liu Ngau), only that this one probably isn't.
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/78513189
minghong (2019-12-17 11:02:42+00:00): Yes, so no need to comment on this one.
Kovoschiz (2019-12-17 11:09:11+00:00): >Yes, so no need to comment on this one.
Yes, so you should probably correct your edits
Kovoschiz (2019-12-17 11:00:36+00:00): There's no "already covered by" "the housing estate".  You need add the parent object.
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/78513552
minghong (2019-12-17 11:06:35+00:00): There is no need to separate every little area as a neighborhood. Having suburb is good enough.
Kovoschiz (2019-12-17 11:11:48+00:00): >There is no need to separate every little area as a neighborhood.
There's no "need" to delete this. You should edit it as something else, like `landuse=` 
>Having suburb is good enough.
That's not how a data hierarchy work.
Kovoschiz (2019-12-17 11:12:32+00:00): There's no parent object for Taikoo Shing and Lei King Wan, if you missed my first comment.
iWowik (2020-01-25 18:59:42+00:00): Рад вас приветствовать в проекте, я заметил, что вы рисуете домики, к тому же нарушаете порядок наименования улиц (не пишете слово улица).

Скажите пожалуйста, где вы берете адреса для домиков?
Обычно их не просто найти.
Vinber (2019-12-21 06:55:24+00:00): Bonjour et bienvenue sur OpenStreetMap,
vous avez déplacé seulement la station service, est-ce que le supermarché est aussi déplacé à cet endroit ?
L'imagerie aérienne ne permet pas de voir tout cela, juste un champs :)
Bonne journée
Sindoni Dominique (2019-12-21 07:25:14+00:00): Oui, le supermarché a déménagé également. Je vais essayé de le placer.
Vinber-Pro (2019-12-21 08:02:41+00:00): Super, merci ! Si vous avez des questions, besoins d'aides, vous n'hésitez pas !
Bonne carto
user_5359 (2019-12-19 19:04:06+00:00): Hello! Short question: What is the meaning of operator:s (see http://www.osm.org/node/7062689852 as example)
mueschel (2019-12-19 11:42:20+00:00): Hi,
could you explain the meaning of these three relations? They don't have any common and documented tag.

Thanks
Jan
Abn_976 (2019-12-20 12:23:58+00:00): Bonjour, 
C’est juste une erreur de ma part. Je suis en train de digitaliser le bâti depuis QGIS, mais j’ai oublié de supprimer les champs avant d’exporter vers OSM. 
Merci pour les signalements.

Hello,
It’s just a mistake on my part. I'm digitizing the frame from QGIS, but forgot to delete the fields before exporting to OSM.
Thanks for the report.
Fizzie-DWG (2021-02-13 05:30:48+00:00): Hi PG. Just playing with Overpass & I noticed that you mapped this a while back. Thanks for your enthusiasm, but I’m wondering if there's any particular reason that you mapped it as landuse=military + military=training_area? Thanks, Fizzie
PhysicalGraffiti (2021-02-13 09:23:36+00:00): No, looks like an error on my part.
Fizzie-DWG (2021-02-14 00:12:09+00:00): Thanks - we've all done it!
532910 (2020-11-22 20:00:49+00:00): Уважаемый, у вас капс заело?
user_5359 (2019-12-19 19:11:39+00:00): Welcome to OSM! Please use in OSM for the keys explicitly British English. For more details have look on the website http://wiki.osm.org.
Jesús Gómez (2019-12-17 18:23:11+00:00): Hola, el mapa ya tiene añadido Bodega Fuente De.
Elimino este nodo por estar duplicado.
hsc666 (2019-12-17 17:18:55+00:00): Hallo Jens2345 und herzlich willkommen bei OSM! Ich habe mir Deinen Änderung angesehen, werde aber nicht so recht schlau daraus. ;-) 
Du hast der Hausecke von Nr. 3 einen Namen gegeben. Vermutlich wolltest Du /das/ nicht machen. Nimm Dir die Zeit, z.B. im Wiki (<https://wiki.openstreetmap.org/wiki/DE:Hauptseite>) zu lesen, wie man Dinge einträgt. Falls das hier eine Firma sein soll, könntest Du einen neuen Node an der richtigen Position innerhalb des Gebäudes platzieren und mit passenden Tags versehen. Du könntest z.B. hier suchen, ob etwas passendes dabei ist: <https://wiki.openstreetmap.org/wiki/DE:Key:office>.
Viel Spaß beim Mappen und falls es Fragen gibt, melde Dich einfach hier oder im Forum. Es wird sich immer jemand finden, der hilft.
VG
hsc666
user_5359 (2019-12-18 04:54:49+00:00): Hallo Jens2345, auch von meiner Seite Willkommen bei OSM! Hallo hsc666, auch ich bin über diesen "name-only" Eintrag gestolpert und wollte schon meinen Standardhinweis eintragen. Ich habe mir aber erlaubt, den Eintrag bereits anzupassen: Der name ist offiziell eine Webseite, die das dort an­säs­sige Unternehmen betreibt. Nur bei der Klassifizierung mittels office schwanke ich zwischen adveritising_agency oder it.
Kovoschiz (2019-12-17 11:03:03+00:00): Please don't delete `public_transport=stop_position`
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/78518402
Leo Slager (2019-12-18 00:08:39+00:00): Dag Tim,
Je hebt de Kanaaldijk Noord Oost veranderd in een fietspad.
Gelet op de bushalte en de route van buslijn 261 kan dat niet juist zijn.
Ook de recente satelliet beelden laten geen werkzaamheden aan de weg zien.
Het fietspad vanuit het Zuiden eindigt dus bij de Havenweg.
Ik neem de vrijheid je wijziging terug te draaien.
jfd553 (2022-03-01 20:51:08+00:00): The name of the street is "Rue King Ouest", as it appears on street signs.
jfd553 (2022-03-01 20:53:50+00:00): I'll change it. But now you know that the name tag must conform to what can be seen on street signs :-)
Kovoschiz (2019-12-17 11:05:44+00:00): This is obviously an `embankment=yes`, no? If you are describing its structure, `bridge=yes` can co-exist with it. One upper, one lower.
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/78518969
Kovoschiz (2019-12-17 11:16:21+00:00): May I know why you removed `junction=roundabout` from Cheong Lin Rd roundabout?
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/78519599
user_507893 (2020-01-28 18:30:46+00:00): Hallo,
warum genau hast du die Buslinie 4244 gelöscht, anstatt daraus die 4200 zu machen?

http://www.nimmbus.de/fahrplanbuch/plaene/4200R-1.htm
ma-rt-in (2020-01-28 18:33:01+00:00): Hallo,
wenn man soviele Änderungen bearbeitet wie ich, kann das schonmal vorkommen. Willst du die wieder reaktivieren?