piebro/osm-data huggingface dataset:
freebeer (2019-09-17 01:43:12+00:00): i'm not sure where the place=suburb comes in, because all i am doing is reverting an ongoing country-wide undiscussed mechanical edit that multiple users have taken issue with and the DWG has weighed in on.  mechanical edits such as this that are affecting multiple tens of thousands of mapper contributions.

i'm not sure either how this would be triggering any sort of alarms, but the edits in the first place should have triggered just as many alarms unless you've done something out of the ordinary.

if the original mechanical retagging had been acted upon sooner then there would have been fewer changesets, but i have seen no discussion of this on the tagging mailing list, talk-us as it appears to be country-wide aiming at 100% coverage, or even in the general talk mailing list where a similar revert of a mechanical edit in saxon switzerland has been discussed but not acted upon yet.

are you getting notifications for the edits carried out like
relation 9266256 last edited as v2; restoring previous version 1 by 'stevea'
?  that shouldn't be the case as v3 bears my username and v2 bears the other user's,

and how is a changeset in hawaii setting off alarms for you?  california i maybe could see.

anyway, the earlier mechanical edits mixed together several uncontroversial edits with other controversial ones.  which still should be documented and discussed, but without a clean separation they are not so easy.
stevea (2019-09-17 01:52:51+00:00): Your "not sure" is likely because you haven't read the History of the node.

It appears (I do believe this but I could be slightly mistaken) that I entered FIXME tags which get 'bot corrected to fixme and somehow your bot gets involved as "something you edited" (as did I, or I entered a FIXME).

It's not gigantic, it's annoying, it's "like" an alarm going off (when it doesn't need to) as it's a mechanical ping-pong between FIXME and fixme and FIXME and your bot notices and I get notified because I'm in the edit history.

I am editing in Hawaii as I help user:ZeLonewolf with admin_level, place, census polygon tagging on Oahu as he was importing census and we've been sort of tight  the last few days off-list (so you wouldn't know that) after being public on talk-imports for a few weeks.  I don't expect you to know that either but it has been public and our database is so open you could look at histories or read a talk-page or click the History tag as it keeps all of us better informed.

I hear you when you say "not so easy" and I appreciate whatever efforts you expend to pour a little cool water on your 'bots, thanks in advance for those efforts.  Yes, it is the edit trails where we overlap where such triggers go off, now I hope you have a better idea how to quiet it down.  Cheers.
freebeer (2019-09-17 03:17:54+00:00): ohhh-kay...

this changeset reverted a changeset that touched nearly a hundred items.  i would not be reviewing every item.  one changeset covered around 5'000 items, maybe part of california heavily mapped where users aren't afraid to voice uncertainties.

i take it you somehow get a notification if you are in the edit history for everything someone edits?  wow.  i did not know that was possible, and i certainly would not want that for all the items i've seen you edit, what with prolonged edit wars and the number of items that aren't at v1.

your FIXMEs were not bot-changed, but by a user who has failed to reply to any changeset comments (a DWG block could be needed) and seems to be running mostly mechanical edits, some aplying iD presets or controversial retagging, which is frowned on by the osm community i know.

a bot would be something like wall-e or xybot, well documented and mostly accepted by the community.  i do not run such a bot.  i use scripts that act on manually selected edits, whether vandalism, changes-gone-bad, or in this case an unapproved and undiscussed mechanical edit.

like i say, i've no idea how or why you get a notification, but i'd think there should be the possibility to not get a trigger when osmtools makes an edit.  the bot label you see is a bit iffy to go by as i've seen bad edits use it where you *should* want to see what is up, while trusting those who run osmtools to be doing undeletions or reverts to a previous edit state, or other DWG-type edits that look to be all it can do when in capable hands.

but without knowing how the notifications originate, i can't suggest a way to implement that exclusion (or if it's desirable.  i've only randomly seen my work appear like too often in this retagging, where in the changeset discussions seen at https://resultmaps.neis-one.org/osm-discussion-comments?uid=905716  - 52 of them so far, 62 comments, not a single reply or change of behaviour - , i hope it won't have to continue to go up by much).  that was the only way i was aware of to learn of my reverts without searching them out.
stevea (2019-09-17 04:41:27+00:00): I appreciate that you took the time to type all that, even the snark about California.

I have not had "prolonged edit wars," that is a false characterization on your part and looks a lot like you casting the first stone.

Whether something is at v1 or not matters not.  Somebody has to enter data the first time.

Good to hear that as some loose-cannon user is making a mess, you are on the hunt.

Scripts, bots, both are "automated edits" and your distinctions are awry, largely meaningless.

"You have no idea why I'd get notification" is no excuse for either lack of acknowledgement that I did, or taking responsibility that it was your changeset (via automated edit scripts) that caused it to happen.

This does sound like it can be swept away as a simple misunderstanding, of which I firmly place onus of responsibility squarely on your shoulders.  While I appreciate that you are trying to limit damage or vandalism by an as-yet-unnamed perpetrator, you look like one yourself when your countermeasures produce unintended and unpleasant results.

Please be more careful with your automated edits in the future.  If you don't understand what the tools you are using do, including unintended consequences, I (and other members of the community) prefer you not use them.
freebeer (2019-09-17 06:53:44+00:00): (this isn't wanting to post.  try again)

the so-called california snark was an honest comment that while i see you are active all over, i would expect that if you have opted into notifications somehow, i would expect it to be geographically limited to your area of greatest interest, as the feeds i am aware of provided by osm cover a fairly limited area.  so that to get full coverage of the us of a you would need to divide into multiple squares.  which if you did so, you would be seeing a lot more revert activity over the years that i encounter.

but then i have never ever received notification from osm (just the occasional heads-up via the message system) that anyone has edited an item i have worked on, despite knowing many thousands have been touched.

the edit wars do not refer to your activity, but to outsiders, the worst case i know being a particularly persistent vandal in rochester michigan who may have finally given up after a live three-pronged defence with immediate reversions.  some pokemon vandals fall into this category before they give up.  further edit wars appear to take place in disputed areas.  in any case the version numbers often rapidly increment into the dozens to hundreds with no action on your behalf.

i am not going to speculate why you take offence other than to state it is irrelevant to this revert, except where the user already made a second pass over an area despite being asked by the DWG to stop the retagging several days before.

i understand fully well what my tools do.  they connect to the api server, download info about the changeset, then for each item, perform a GET to get the necessary data to either determine whether the item has since been modified, or to increment the version with a PUT with an earlier data status.  it then sends a comment to document what has been done (also helping with recordkeeping for widespread cases like the driveway deletion carried out in small steps where i missed one) and closes the changeset.

it sends no mails.  it makes no other api calls related to messaging, if that is possible.  it is just like any other edit whether carried out by josm, or iD proxy automated validator retagging edits.

i get it, there is something notifying you of every change made to any object you touch, and apparently the retagging to kick this all off didn't bother you despite happening just as many or more times, and i take it you would have the same objection if the DWG had stepped in in my stead and used the very same tools to perform the same reverts, again touching items you have modified.

you can if you like choose to tag things with the lowercase fixme it seems some want to force on all mappers but as a non-data tag meant for human mappers, i have chosen to respect the choice of the original mapper to use a tag that sticks out prominently in multiple ways.

i take responsibility for what my changesets do to the map data.  but i cannot take responsibility for unintended consequences if someone has wired themselves up to be notified for every item i upload, for that would be absurd, yet still possible to do with minutely updates.
stevea (2019-09-17 08:08:47+00:00): Nice chatting with you.
chachafish (2019-09-17 13:16:30+00:00): Hello and thank you for your additions to the map. In this changeset it looks like you've incorrectly deleted five buildings that were created years ago. Could you please go back and replace these buildings and keep the editing history? Thanks :) Also, quite a few of the buildings you've created in this area are not "squared". Please keep in mind that in OSM, if buildings should have square corners you can use the shortcut "q" to square them. Thanks :)
freebeer (2019-09-18 02:49:24+00:00): i count eight objects below.

which is weird in that in another changeset with numerous deletions, nothing appears at the start of the list.

in achavi, though, i see seven in the two areas deletions are obvious.

got it, that last bit is an outer part to one of the other two.
chachafish (2019-09-18 04:08:17+00:00): Yep, you're right. I missed those two buildings. Now I count a total of eight deletions along with the small roof section. https://nrenner.github.io/achavi/?changeset=74552438
freebeer (2019-09-18 04:50:06+00:00): they're back.  man, i don't think the effort to write a script to feed the numbers below was worth the bother...
chachafish (2019-09-18 10:52:29+00:00): Awesome! Thanks for doing that :)
freebeer (2019-09-22 14:14:17+00:00): the idea behind the script came about seeing mass deletions elsewhere mixed with additions and other changes that would be lost by a revert, that i've had to let slide.

now i can keep an eye more closely on user plitscheplatsch (however it's properly spelled, never was enough a sandmännchen fan) when pointing out suspicious changesets, that happens periodically.

the enhancement i need to add is to work by a changeset id, rather than either a list from below (20 per page gets wearisome) or from commandline analysis of a downloaded osmchange xml file linked at the bottom of the page here.
chachafish (2019-09-17 12:45:24+00:00): Hello, thank you for your additions to the map. Could you make future changesets smaller so it's easier to see what is being changed? Thanks :)
Burisma (2019-09-18 18:07:41+00:00): You continue to perform worldwide mechanical changes: not good!
Olyon (2019-09-18 20:02:12+00:00): Sorry, everyone. I wanted to divide it into several changeset but I made a mistake. I will not do it again.
chachafish (2019-09-17 12:45:01+00:00): Hello, thank you for your additions to the map. Could you make future changesets smaller so it's easier to see what is being changed? Thanks :)
Flurps (2019-09-17 13:38:25+00:00): Hi there,

This tagging has no real place in OSM at the moment and should be corrected/removed.

Most companies wanting to show this stuff using OSM keep their data in a separate database and overlay it using OpenLayers/Leaflet etc.

Thanks,
SomeoneElse_Revert (2021-09-07 00:59:36+00:00): This changeset has been reverted fully or in part by changeset 110823595 where the changeset comment is: Following a report to the DWG, and a discussion with the user, reverting some changesets that used Google as a source.
Warin61 (2019-09-17 05:09:27+00:00): Hi,

Welcome to OSM!

The closed way 725213138 for a building is not correct. The way should not double back on it self. 
See https://tools.geofabrik.de/osmi/?view=areas&lon=145.05718&lat=-37.97285&zoom=18

Do the simplest thing - just draw the outside of the building. This is its foot print on the ground.
felipeeugenio (2019-09-23 20:41:21+00:00): Estimado, por favor no borrar cosas. Borró el cementerio, la universidad y por lo menos tres entidades públicas más para reemplazarlas por nodos. Ruego por favor discutir esto con la comunidad chilena en https://t.me/OSMcl
chachafish (2019-09-17 12:43:42+00:00): Hello, thank you for your additions to the map. Could you make future changesets smaller so it's easier to see what is being changed? Thanks :)
freebeer (2019-09-17 15:21:36+00:00): it's an automated edit that is prefixing colour codes with an octothorpe.

however like many such simplistic automated edits, it's not well thought out and the one example i grabbed, https://www.openstreetmap.org/way/604112653 , shows a 50% success rate and 50% failure in detecting each instance of colour.
skquinn (2019-09-21 07:10:50+00:00): If that's really what is going on, "Fix with Osmose" doesn't tell us that. "Prefix color codes with '#'" would.
felipeeugenio (2019-09-23 21:13:44+00:00): Estimado. Borró toda el área residencial de Talca. Ya fue reparado, por favor más cuidado con sus ediciones. saludos
viloan (2019-09-17 00:46:14+00:00): Bem-vindo(a) ao OpenStreetMap e parabéns pela sua primeira edição! :-)

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 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
Se você está mapeando por causa do jogo do Harry Potter, as dicas e explicações na página anterior também são úteis para você.

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!
Alecs01 (2019-09-18 05:48:48+00:00): Il Parco Sempione (leisure=park e name=Parco Sempione) è questo oggetto dal 2011
https://www.openstreetmap.org/way/115896315/history
Che tu affermi (in privato via messaggio, mai in pubblico) di averlo mappato tu per primo è assurdo, anche dopo che ti è stato fatto notare l'errore, dimostra solo che non capisci cosa stai facendo. E per di più hai l'arroganza di non ammetterlo e accusaretu per primo tutti gli altri di sbagliare, che è sicuramente peggio che fare qualche banale errore di inesperienza. Complimenti, davvero.
Alecs01 (2019-09-17 19:14:28+00:00): Giusto per la cronaca e per non lasciare la discussione solo via messaggio privato, questi sono alcuni degli errori di Arkeopterix che ho corretto, alcuni dei quali ha ripetuto di nuovo, come togliere l'area pedonale di Piazza Duomo in questo changeset.

non ha nessun senso il modo in cui hai modificato questa relazione https://www.openstreetmap.org/relation/1651244/history quando il parco è descritto da questo percorso https://www.openstreetmap.org/way/115896315 ancora, qui hai tolto l’altezza da questo edificio, non proprio uno qualunque https://www.openstreetmap.org/way/431233568/history qui hai tolto altri tag senza motivo https://www.openstreetmap.org/way/315667468/history senza contare che questa linea della metro https://www.openstreetmap.org/way/85594146 la hai fatta incrociare con oggetti in superficie, cosa che ovviamente non dovrebbe succedere credo che hai anche cancellato il percorso che collegava la piazza pedonale a qui https://www.openstreetmap.org/way/184759168 che ora manca quest’altro tratto di strada invece https://www.openstreetmap.org/way/196295509 è rimasto scollegato dal resto … e mi limito a quello che ho visto
skquinn (2019-09-21 07:09:38+00:00): This may have been done by people fixing warnings generated by iD itself. Pretty sure JOSM uses the lower-case "fixme" by default as well.
TravGW (2019-09-17 19:37:40+00:00): Concerning this road https://www.openstreetmap.org/way/71372992 
You do not need to convert a single highway into a divided highway unless there is a physical barrier dividing the ways. Also this change may have broken the route relation although I haven't checked.
freebeer (2019-09-18 01:03:19+00:00): yep, that's a centre turn lane for most of its length.  and some of those turns it allows are not mapped from both directions.

and yes, the route relation is buggy.
mbethke (2019-09-17 07:52:47+00:00): Hi,
that phone number was fine, it should be in international format. See https://wiki.openstreetmap.org/wiki/Key:phone#Usage
cheers,
Matthias
Kovoschiz (2019-09-17 09:26:49+00:00): Lai Wan is another name for Lai Chi Kok Bay
mavl (2019-11-10 13:04:32+00:00): This changeset was redacted. Reason: an incompatible source.
SomeoneElse (2019-09-19 21:12:01+00:00): Hello, 
You've recently changed https://www.openstreetmap.org/way/667593487/history from a garden to a park.  Can you explain why you think it is better described as a park than a garden?
Best Regards,
Andy
simplyee (2019-09-20 00:23:20+00:00): Hello Andy 

So there's a little play area for children with painted in hop scotch on one side and a rubber area for kids to bounce balls without disturbing the building with noise. 

Maybe playground would be better ? Due to the recently added greenery I assumed park would be better. It's like an all in one. One corner garden. One corner for children as the adults garden, ect.
SomeoneElse (2019-09-20 00:25:54+00:00): Yes - that does sound more like a playground to me.
simplyee (2019-09-20 00:29:25+00:00): So should I adjust that? It's more greenery than play ground with a little walk way. But up to you. You can adjust it. I'm replying to the email I received when you messaged me. So I don't have my computer with me at the moment.
SomeoneElse (2019-09-20 00:33:31+00:00): It's up to you and other local mappers really - does the place look more like https://wiki.openstreetmap.org/wiki/Tag:leisure%3Dpark or https://wiki.openstreetmap.org/wiki/Tag:leisure%3Dplayground ?  The way that you're describing it it sounds more like the latter, but you've seen it, I haven't.
simplyee (2019-09-20 00:35:50+00:00): Yeah more like the latter . Not enough space for a park like that. But here in the city we have small parks that just have space and benches. The garden in this case was just to keep elderly and adults more active. And to have more community with all ages.
aseerel4c26 (2019-09-17 05:45:39+00:00): siehe https://wiki.openstreetmap.org/wiki/Sturm_2019-08-18_im_Kreis_Offenbach - Diskussion möglichst dort
Warin61 (2020-04-23 07:51:07+00:00): Hi,

I don;t understand the name on a house of 'Possums Home". Can you explain?
Peter W34 (2020-04-23 08:21:07+00:00): Hi Warin.
That would have been a name plate attached to the front of the house. I would have a photo.
Peter
Warin61 (2020-04-23 10:43:37+00:00): Just looks a little strange.
I added the cop shop and RFB.
trial (2019-12-26 10:56:34+00:00): Bonjour, l'agence de voyage n'a pas été reprise, j'ai donc mis shop=vacant.
Kovirii (2023-03-03 02:07:29+00:00): Why do the roads wiggle?
dufekin (2023-08-28 23:14:30+00:00): I'm not sure.  I traced the roads from Bing areal imagery.  Previous data were very poorly aligned.  I tried to follow the center of the road or the yellow line.  Some of the imagery makes the roads look wavy, especially in areas of hilly or steep terrain, but some roads twist and turn in real life too.  Today's imagery doesn't have this problem.
Cebderby (2019-09-19 00:00:11+00:00): I see you've not added names for any of these roads or removed the construction=residential tags, or changed the limits of the construction or residential areas - did you survey the site to see what is actually in occupation, or just change them all arbitrarily?
purbitap (2019-09-19 12:19:06+00:00): Hi Cebderby,
Thanks for looking into my edit.  This edit was based on the GPS traces of our driver partner. However I understood your concern and have made the edit "Removed the construction = residential" tag . Couldn't add any information related to road names as there is no source available to add. Let me know if in case you have any further suggestion. Always happy to learn from community.

Regards,
purbitap.
kreuzschnabel (2019-09-17 10:34:07+00:00): Hallo Kuhbaner, schön, dass du mitmachst, die weltbeste Karte noch besser zu machen. Eifrige „Neumapper“ geraten schnell mal kurz in die Aufmerksamkeit der Community :) fühl dich also nicht „beobachtet“. Nur ein kleiner Hinweis: „Zufahrt Bauhof“ ist für mein Gefühl (bin nicht ortskundig) nicht der Name dieses Weges, sondern eher eine Beschreibung, die in description=* gehört und nicht in name=*. Eine bessere Idee wäre es, den Bauhof als Fläche zu erfassen (z.B. als Gewerbefläche, und da kann dann meinetwegen Bauhof als Name dran), dann wird die Funktion des Zuweges schon daraus klar. Mach weiter so! Ich hab auch mal angefangen :)
mavl (2019-11-10 13:04:12+00:00): This changeset was redacted. Reason: an incompatible source.
Wulfmorn (2020-07-17 15:34:34+00:00): Hi. This street seems to have either incorrect name value or incorrect oneway-value. https://www.openstreetmap.org/way/407744013/history
cquest (2020-07-20 08:43:41+00:00): Oups... fixed !

Merci :)
eggie (2019-09-17 09:00:23+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privébericht.
MVG,
Eggie
b-jazz (2019-09-17 18:36:09+00:00): Hello. I'm guessing you are doing this as an SEO company on behalf of a client, right? (There is nothing wrong with that, but there are a couple of guidelines that you should be following.) Can you reply so that we can discuss this? Thanks.
bikepiper (2024-06-20 23:12:44+00:00): Hier liegen zwei landuse=meadow teilweise übereinander: way #298496077 (10 Jahre alt) und #725268976 (5 Jahre). Ich denke einer davon sollte entfernt werden.
ma-rt-in (2019-09-18 09:18:45+00:00): Hallo,
bitte zweichne mMn keine Flächen auf die Punkte von Straße, das sieht zum einen zwar schön auf der Karte aus, entspricht aber nicht der Wirklichkeit und ist beim weiteren mappen eher stöhrend.

vg
DerGuteMercator (2019-09-18 09:39:56+00:00): Ich habe die nicht so gezeichnet, ich habe lediglich Flächen modifiziert, die bereits so gezeichnet waren. Bin selbst nicht glücklich damit, hatte aber keine Lust, die alle aufzulösen.
ma-rt-in (2019-09-18 09:41:52+00:00): Hallo,
ok. Das Problem ist, das Way 725273422 in V1 steht und dieser Straßenpunkte mitnutzt. Daher meine obige Anmerkung.
vg
DerGuteMercator (2019-09-18 09:44:04+00:00): Das war eine aufgeteilte bestehende Fläche, daher sind die Knoten dort.
Milancer (2019-09-17 10:55:06+00:00): Zdravím, prosím opatrně s opravami budov, některé mají nastavené vlastnosti pro 3D zobrazení. Vysílač Javořice to bohužel dost schytal.
Něco o 3D:
https://wiki.openstreetmap.org/wiki/Cs:Jednoduch%C3%A9_3D_budovy

prohlížeč 3D:
https://demo.f4map.com/#lat=49.2173739&lon=15.3382933&zoom=16

Děkuji.

Milan
Österreichischer Puppenmacher (2019-09-17 11:58:59+00:00): Omlouvám se, díky za upozornění. Že likviduji 3D objekt mě nenapadlo. Nastuduji odkazy a zkusím to nějak obnovit.