piebro/osm-data huggingface dataset:
pitscheplatsch (2019-05-10 06:40:31+00:00): Hi Scott Lewin, welcome to OSM.

Could you please don't remove and redraw more or less the same objects? This deletes the history. Thanks. 
See https://wiki.openstreetmap.org/wiki/Good_practice#Keep_the_history

Furthermore, why did you remove elements, which are still visible in the satellite imagery? 

More information about your changeset: https://overpass-api.de/achavi/?changeset=70093320

#GolfMapping 
--- 
Detected by #SuspiciousOpenStreetMap
viloan (2019-05-10 01:35:52+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 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!
naoliv (2019-05-10 01:48:38+00:00): pokemonster, apenas como aviso, devemos mapear lugares que realmente existem.
Isso que você mapeou claramente não existe.
viloan (2019-05-10 02:08:43+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 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!
mavl (2019-05-10 02:35:33+00:00): This changeset reverts some or all edits made in changeset 70059158.
TravGW (2019-05-10 03:04:14+00:00): Blah. JOSM choked while uploading my last changeset. Hopefully it didn't make any mistakes.
freebeer (2019-05-10 11:57:53+00:00): the v1 building=roof i checked shows no dupe nodes, so looks okay.
also, potlatch2 on the shared nodes with `/' toggles the school and the roof without a third intermediate, so methinks you are good to go here.

'course, i could be wrong.
Gabriel0322 (2019-05-12 01:25:33+00:00): Some of the locations are wrong.   Would you like the correct BCPS locations?   

Go to www.bcps.org/apps/Facilityuse/

Currently have a application in to add augmented reality portals to each sports field.   Just a FYI.
stevea (2019-05-11 16:35:35+00:00): After being edited in this changeset, relation/1015348 is made up entirely of inner members, a nonsensical OSM relation construct.  In short, this national forest is now wrong not because of its data but because it was edited in OSM to become a relation that makes no sense.

Before deleting an outer relation member (especially using the edits-relations-clunkily iD editor), try:

1)  Installing JOSM, a superior relation editor,

2)  If the assertion is that the "forest area that was mapped wrong...and can be mapped more accurately" please find RIGHT data to replace it with.  The source (at usda.gov) was properly tagged, remains an active link, and the shapefile.zip at https://data.fs.usda.gov/geodata/edw/datasets.php?dsetCategory=boundaries was updated as recently as last week.  You will need to install into your JOSM environment the opendata plug-in to open the shapefile, but this both documented and not difficult.

Rather than deleting data (which you assert are wrong), please follow their source tag and improve them with more current, more correct data (asserted by our employees, the USDA, to be right).
stevea (2019-05-12 17:01:40+00:00): Am I really to understand that my assertion in this changeset comment of "the data in this changeset have now become nonsensical and incorrect according to what OSM defines as a valid multipolygon" is responded to with:  that's OK, these wholly incorrect data will "be dealt with eventually?"

I find that to be a most unsatisfactory response.  In my opinion, this isn't a waste of time, it is about presently-incorrect data in OSM being called to the attention of their author so that they may be corrected, if not immediately, then posthaste.  The author's response seems cavalier and unhurried, even as he embarks on an apparent campaign to delete similar data (his May 12, 2019 deletions).

These data were edited and left in a faulty state.  That is all I assert, and I even offer/suggest a methodology to correct them.  So, let's correct them.  Now or soon as this edit was recent and its errors were newly discovered.  Not at some hazily-defined future time when the author decides to to so "if I remember" or "eventually."  I find that disingenuous and a failure at the fair and reasonable scrutiny of other OSM contributors.

I disagree with "nothing more needs to be said about it."  This feels like a stifling of open dialog, the kind of dialog which OSM welcomes and frequently engages in to solve errors in the map.  An error in the map is all we're talking about here.  So, again, let's solve it.  Sooner, not later.

Deleting erroneous data is one thing.  Taking the necessary time to re-introduce correct data is another thing.  Both are good things.  However, editing, then uploading data so they are in error is not a good thing, I believe everybody in OSM agrees.  (Yes, we all make mistakes, I do as well, this appears to be a mistake, let's correct the mistake).

These data are not in error because they are in dispute with the real world (that is one thing and can be harder to solve).  They are in error because they are an erroneous data construct in OSM.  IMO, these should be corrected as soon as possible.
iandees (2019-05-12 17:36:00+00:00): 😩Come on you two. *Please* don't start this pattern again.
stevea (2019-05-12 18:15:09+00:00): OK, I'm resigning this issue here and now.
Adamant1 (2019-05-12 21:42:45+00:00): iandees, SteveA's the one with the problem here.Not me. I explained the edit and said there was nothing more to say about it. I stand by that. learly just trying to pick a fight here over something that's not worth having a fight over because it's a none issue. So it would be good if you didn't implicate me in the clearly one sided squabbling. In the meantime, I'm just going to ignore him. To the enrichment of everyone, including myself. 
'
Thanks Iandees, 

Adamant1

P.S. If SteveA want's to have an actual dialog about this, instead of just going off, he's free to send me a private message with specific question's i'm fine with that. We clearly disagree on some mapping methodologies. Ironically, I sent him a private message about this very thing a few days ago, in order to avoid this exact type of situation in the future, but he refused to discuss things and called my attempt at dialog harassment. So...I guess he somehow thinks this is a better approach. "shrug." 

Anyway, like I said, I'm just going to ignore him. That seems like the best option. I clearly shouldn't have responded to him in the first place. That was my bad, even if it was civil, and I apologize to the community for doing it. People don't have anything to worry about. There won't be more arguing or even none arguing with SteveA. At least not from my end.
iandees (2019-05-12 21:48:52+00:00): Neither of you need to convince me of anything. I don't have time to read the thousands of words written between you two and as excuses to me.

Just be adults. If that's difficult, then maybe this project isn't the right fit for you.
Adamant1 (2019-05-12 22:33:02+00:00): Fine. will do. Already was.
Adamant1 (2019-05-12 23:00:47+00:00): Btw, I was already going to ignore SteveA before you commented. So there wasn't going to be any arguing in the first place. You commenting just extended this unnecessarily. Ignoring someone is the "adult" thing to do. 

As much as we could both "just be adults" by not arguing (which I wasn't doing. SteveA was), you can also "be an adult" by allowing people to deal with their own problems, like I had planed to do before you came along. 

Maybe save changeset comments for things specifically related to the edit. Since that's what the comment system is here for. 

I don't have anything else to say about it and I'm just going to ignore you from now, on along with SteveA. Id appreciate it if you "acted like an adult" by not commenting on my changesets anymore. Especially if it's not directly related to mapping. 

Thanks, 

Adamant1
iandees (2019-05-12 23:15:20+00:00): My comments are directly related to your edits and are a reflection on how you interact with the community, Adamant1. When you're mapping as part of a community, your behavior and attitude towards others in that community are more important than your mapping. When I say "be an adult", I mean don't bicker, write short and succinct messages, work to solve your disputes by assuming good intentions, and don't attack others. If you can't do those things, you don't belong in this community.
Adamant1 (2019-05-13 00:06:22+00:00): "I mean don't bicker, write short and succinct messages"

1. I wasn't bickering in my first message and I had zero intent to write anything after that until you got involved. You said yourself you don't have time to read our long messages, but then your throwing around accusations that I'm arguing when I'm not. I'm 100% allowed to comment on my changeset's. There's nothing bickering about it and there was nothing argumentative in my original message.  

2. I don't see anywhere on here that say's there's a hard "short" limit to messages. I write as long or short messages as I feel it takes to explain something. If you or others think they are to long, your under no obligation to read them. Maybe open an issue on the websites github page and have a limit put on these. It's not problem and just writing long messages in itself isn't "arguing." Sometimes take more then one paragraph to explain. That's sometime's the cost of dealing with complicated issues in this medium and is way I said SteveA could private message me. That's not on me. Btw, just as many people complain about how I'm being to "vague" when I write short messages to (including the ones that complain about long messages). I'm completely sick of hearing it. There's literally no satisfying anyone on here and I'm sick of trying. 

"my comments are directly related to your edits."

You haven't said one single thing here about the forest edit. Feel free to. Otherwise, if you want to go off about your perception of my attitude, send me a private message if you must. Outside of that, your wasting everyone's time. 

"assuming good intentions, and don't attack others. If you can't do those things, you don't belong in this community."

There was nothing that wasn't assuming good intentions in my original response to SteveA that you commented on. You could have taken your own advice and not acted otherwise or commented in the first place when the situation was already dealt with. You clearly didn't even read the original message. Your also the one attacking me by saying I need to "act like an adult" over a comment that was perfectly fine and by saying that I might not belong in this community just because I'm asking you to let me deal with my own problems. Saying things like that is needlessly confrontational and in direct opposition to exactly what your saying I should do. 

I'm sick of these types of slanted one sided discussions where things are put on me, especially by people who didn't even read the original message that they are complaining about because they don't have time to or because it's supposedly to long, Like I said, if you have specific feedback about the edit, feel free to voice it. Otherwise, I'm 100% done with this discussion.
SomeoneElse (2019-05-13 13:48:58+00:00): @iandees - (again) thanks.
@stevea and @Adamant1 - you both care about OSM.  We get that. However please do try and concentrate on the data, on on each other.  There is literally nothing to be gained from throwing 2k and 3k changeset discussion comments at each other.
ralley (2019-05-10 05:54:17+00:00): This changeset has added a church building inside the library building - can you please fix.  I have commented on a few of your changesets (http://resultmaps.neis-one.org/osm-discussion-comments?uid=8714835), can you please look into these comments.
CurlingMan13 (2023-09-19 23:47:27+00:00): Houses should not be named "House".  Instead they should get the tag "building=house"
Mateusz Konieczny (2024-02-04 08:45:12+00:00): why you added name=C to https://www.openstreetmap.org/way/689044837/history ?

Is this building really named C?
pitscheplatsch (2019-05-10 06:41:47+00:00): Hi mikebranca, welcome to OSM.

Could you please don't remove and redraw more or less the same objects? This deletes the history. Thanks. 
See https://wiki.openstreetmap.org/wiki/Good_practice#Keep_the_history

Furthermore, why did you remove elements, which are still visible in the satellite imagery? 

More information about your changeset: https://overpass-api.de/achavi/?changeset=70095467

#GolfMapping 
--- 
Detected by #SuspiciousOpenStreetMap
raito (2019-05-10 13:58:03+00:00): Hello and welcome to OSM. Firstly, pardon me if what I'm about to write is wrong in any way. Hope you read this message in a good way.

https://wiki.openstreetmap.org/wiki/Good_changeset_comments
Please write useful changeset comments. I think you understand something like "Updated 100519" is a useless comment. 

https://wiki.openstreetmap.org/wiki/Key:source
Please add the source of your information to the changeset source tag. Also make sure your source is good for OSM. 

https://wiki.openstreetmap.org/wiki/Key:highway
https://wiki.openstreetmap.org/wiki/Highway:International_equivalence
Highway type on OSM is not based solely on max speed. And what is your source of these max speeds anyway? I am a local, I don't remember all of them, but I see you got a few of them wrong I think, at least.

That's all for now. Cheers!
raito (2019-05-16 14:23:04+00:00): Hi, I reverted pretty much all of your changes, which was basically an import I think. I also think it is poor import with inaccurate data and you also removed a lot of valid oneway tags. Please refrain from making mass edits until you understand what OSM is all about. Thanks.
TagaSanPedroAko (2019-05-11 19:21:49+00:00): I'm wondering why this edit would have a very large bounding box.
Warin61 (2019-05-12 00:06:18+00:00): Hummm...

https://www.openstreetmap.org/way/173374039#map=16/53.9144/27.5320

Shakes head. 

I am attempting to correct actions by a school child ... not certain why changeset. But will check the way is reverted back to before the schoolchild changes. Check done - all back to where it was over in the north west of this changeset.
viloan (2019-05-10 05:42:08+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 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!
vorpalblade-kaart (2019-06-21 14:59:23+00:00): I've see that you added lanes, turn:lanes, and destination:lanes to a node. These are typically better expressed on the way itself.
In this case, it looks like you are trying to express the joining/leaving of lanes where the roundabout (which should be tagged as junction=roundabout) and an incoming way join.

That being said, Mapillary street-level imagery from 2019-02-22 does not support the roundabout having four lanes.

I would recommend attaching way 673217256 to node 5890332379 and expanding the roundabout to match the middle of the roundabout in aerial imagery. I would recommend using Maxar Premium Imagery (in iD, the editor you use, you can get it by going to the background icon (keyboard shortcut "b") and selecting "Maxar Premium Imagery (Beta)". Bing imagery tends to be out of date and poorly aligned.

Mapillary imagery: https://www.mapillary.com/app/?lat=40.87470752711111&lng=26.63457548866667&z=17.22655837864439&focus=photo&dateFrom=2017-01-01&pKey=AEjh2GXZ-nc2QFlQTs9Jag

Thank you for contributing, and have a good day,
vorpalblade77-kaart
abrensch (2019-08-18 13:20:59+00:00): Hallo 

laut Baustellenkalender ab morgen (19.8.) an Gimritzer Damm und Heideallee alles wieder frei (?)

weisst Du es genauer?
Carto'Cité (2019-05-17 11:01:56+00:00): Bonjour, 
Merci pour l'ajout de la piste cyclable le long de la Rue Gabriel Péri. Elle n'était pas reliée à la chaussée principale au sud, ce qui empêche les calculateurs d'itinéraires de la valoriser. 
Après visualisation de l'aménagement sur Mapillary, qui montre un simple séparateur,  j'ai préféré la remplacer par l'ajout du tag cycleway:right=track sur la chaussée. Il s'agit d'une variante proposée sur https://wiki.osm.org/wiki/FR:Bicycle qui me semble ici adaptée.
Cordialement,
Antoine de Carto’Cité, projet #CartoVeloIDF
hayes9 (2020-08-14 16:19:52+00:00): Hello naufalsyauqi,

While mapping in the region of Jakarta I noticed a pair of lift gates which were added by you in May 2019 (https://www.openstreetmap.org/node/6463610519). These gates are tagged with the access=private tag, however it appears that vehicles are traveling through the intersection without being stopped by the gate, according to this imagery: https://openstreetcam.org/details/2362750/572/track-info. Is it appropriate for these gates to remain marked as private access? Thanks for looking into this.
freebeer (2019-05-13 13:32:12+00:00): why are you adding obviously bogus and insulting names to these buildings?

osm is a place for adult behaviour and factual data.
dylan-sorg (2019-05-13 14:09:05+00:00): just an inside joke, think they will get verified?
freebeer (2019-05-13 19:03:31+00:00): osm is not the place for your so-called inside jokes.
iandees (2019-05-13 19:38:51+00:00): Reverted in https://www.openstreetmap.org/changeset/70206699
BCNorwich (2019-05-10 07:18:10+00:00): Hi, Welcome to OpenStreetMap.

You added the cafe name to the whole building outline. The cafe outline is mapped on the ground floor within the building and already has the name. So I've removed the duplicated name.

Regards Bernard.
mingo23 (2019-12-14 08:31:33+00:00): Dear user, I came across this changeset where you modified the road geometry introducing a number of mistakes, for example you moved the road on top of a building. 
If you want to make further edits, I recommend - in addition to being careful - to use PCN 2012 as the base orthophoto, since this is the reference in Italy. Thank you!
Constable (2019-05-13 16:16:24+00:00): Hi flevin, are you sure about this node location?
https://www.openstreetmap.org/node/1383687776

I'm quite sure that hikers/cyclists coming from the trail, going southbound do not really cross any gate, for that reason I think the trail should connect to this road just next to the top section of this parking area https://www.openstreetmap.org/way/627535597

Could you please confirm the gate location?
thanks
yaswap (2019-05-15 09:07:05+00:00): Hi Constable,

Thanks for looking into our edits. The edit was not completely done by our editor. The gate was added years ago by another user as lift_gate. In the aerial view it looks like it is the possible connection for the trail segment too.So It cannot be connected to the parking area that was mentioned in the comment. As per the resources the location of the gate is not available and the trail path was connected to it before our edit. 

Please let us know if there is anything that can improve the edit. We are always happy to engage with the OSM community.

Regards.
yaswap.
Constable (2019-05-16 06:22:44+00:00): I'm pretty sure you don't have to get across the gate in order to access the trail, I've been there quite some times this past winter so I'm moving the trail connection a bit to the south, so that it does reflect the "on the ground situation".
Thanks for your message!
abrensch (2019-07-21 19:52:03+00:00): Ist die Brücke noch gesperrt?
geri-oc (2019-09-23 06:39:33+00:00): Bitte bei Änderungen auch lastcheck=* Datum ändern - oder den Schlüssel entfernen. Seit mehreren CS wird das gleiche Datum mit geschliffen.
osmviborg (2019-05-10 08:10:44+00:00): Det er markeret på selve broen, med beskrivelse og access=no
eggie (2019-05-10 08:11:38+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privébericht.
eggie (2019-05-10 08:29:41+00:00): Dag Ivar.. lanes=2 zou ik niet gebruiken op reguliere wegen in wijken.
oneway=no alleen gebruiken als je bang bent dat een andere mapper oneway=yes gaat taggen. Bv bij parallelle fietspaden en fietsrotondes. 
MVG,
Eggie
eggie (2019-05-10 08:33:14+00:00): dag Ivar.. highway=pedestrian is meer voor voetgangersgebieden in winkelstraten e.d.
Gewone wandel/voetpaden beter taggen met highway=footway. Wanneer het een breed voetgangersgebied is kan het natuurlijk wel. Up to you.
MVG,
Eggie
saintam1 (2019-05-22 20:06:12+00:00): Привет, Ники

tag-ът place=hamlet е за малки села с по-малко от 100 жители: https://wiki.openstreetmap.org/wiki/Tag:place%3Dhamlet.

Предполагам, че Тези микрорайони са place=suburb като всички други райони на града.
niki88z (2019-05-23 05:58:32+00:00): Здрасти :) 
Идеята е, че постепенно големите комплекси в София се преструктурират и обобщават като един голям с основното име. Такъв е случаят с ж.к. Люлин - един цял мега-квартал. Оставих микрорайоните като по-малки населени места за да ги има на картата при търсене, а и като допълнителен ориентир.
В тези квартали няма повтарящи се адреси, например: няма блок 11 в ж.к. Люлин 1 и в ж.к. Люлин 10 и по тази причина спокойно може да бъде само блок 11 ж.к. Люлин. Нещо, което са направили от Общината.
Подобен е случая с Овча купел - там вече има само 2 части. Образно казано „старата“ и „новата“ - кв. Овча купел и ж.к. Овча купел. ЖК-то няма разделение на микрорайони.
Същото е и с ж.к. Дружба - там също вече е един мега-комплекс.
saintam1 (2019-07-01 06:45:11+00:00): Здрасти, Ники,

Подходящият таг е place=neighbourhood, ("an area within a place=suburb" -- https://wiki.openstreetmap.org/wiki/Tag:place%3Dneighbourhood)

Tag-ът place=hamlet е за села, не може да се използва за микрорайоните на Люлин.
DiogoBaptista98 (2019-05-13 17:48:24+00:00): theres not  a stop on this location.