piebro/osm-data huggingface dataset:
user_6110846 (2019-05-08 18:55:52+00:00): https://www.openstreetmap.org/changeset/70039286#map=11/50.8669/29.2859
(I did everything possible to protect the edits within the rules.


Creates wars of redagings and ignores arguments https://www.openstreetmap.org/changeset/69992214 
I wrote him a confirmation yesterday and made a reverse, today he deletes again
https://www.openstreetmap.org/changeset/70036488#map=11/50.8669/29.2859
https://www.openstreetmap.org/changeset/70039286#map=11/50.8669/29.2859 

Hamlet 101km https://www.openstreetmap.org/#map=20/50.754217737550164/29.339166250860696  is a remote part of the city of Malyn, KKS by its actions removes it from the relationship Malyn

Source =181300 Казарма 101 км вулиця Kazarma 101 km
https://drv.gov.ua/ords/portal/!cm_core.cm_index?option=ext_dvk&pid100=18&pf3001=190&prejim=2
This link shows (181300) that Казарма 101 км  вулиця (street () is Malуn
_______________________________________________
KKS suggested that I call the local government of Nedashky village and check the information.
https://www.openstreetmap.org/changeset/69891857#map=14/50.9770/29.2330
I draw the neighborhood Hnylyshche as a polygon, but KKS removes the polygon and puts the POI instead.
The point is wrong because then the render Nominatim in the search results will be a third of the village to write that it is a neighborhood Hnylyshche / Гнилище
Hnylyshche / Гнилище only Sadova Street


KKS refuses to call
KKS is not a local cartographer
I am a local cartographer, I live in the city of Malyn
________________________________
ma-rt-in (2019-05-09 09:57:39+00:00): Hallo,
hab da ne Frage zu Node 6459145272? Warum "may be 200" nicht auf das Schild geguckt? :)
vg
Enock4seth (2019-05-11 17:11:23+00:00): Awesome! Keep it up and welcome :)
miche101 (2019-05-29 06:29:09+00:00): Hi

bin nicht ganz glücklich mit dem tagging der Straße durch den Ebersberger Forst :-\ ... einteils ermöglicht es dem auto dort zu fahren, aber fuß und radfahrer weichen dadurch auf andere Wege aus.. was ich nicht optimal finde :-(

highway=unclassified ist bei Routing zu hoch eingestuft was auch meist zutreffend ist.. 


Ich finde Version besser:
https://www.openstreetmap.org/way/220100620

https://www.openstreetmap.org/directions?engine=fossgis_osrm_bike&route=48.1419%2C11.8646%3B48.1081%2C11.9324#map=14/48.1250/11.8985
miche101 (2019-05-29 06:29:24+00:00): Version #6
opendcc (2019-05-29 06:43:47+00:00): https://wiki.openstreetmap.org/wiki/DE:Tag:highway=unclassified?uselang=de benennt Regeln, wann unclassified zutreffend ist. Wenn Deine Routingsoftware da ausweicht (trotz gravel, maxspeed, maxweight), dann  sollte man vielleicht die Kostenfunktion der Routingsoftware verbessern. Auch meine Routingsoftware irrt leider - die geht auf unclassified drauf, obwohl der Untergrund nicht Rennrad tauglich ist.

Aber Du hast Recht, eine Kategorie unterhalb von unclassified fehlt in OSM.
Track wäre normalerweise falsch, da man eben normal durchfahren darf. Track mit motorcar=yes könnte ev. auch eine brauchbares Tagging sein.

Servus
PT-53 (2019-05-29 07:18:11+00:00): Bitte nicht - bewußt falsch - für das Routing taggen. Mit surface und smoothness gibt es geeignete Tags die Qualität des Weges und damit die Nutzbarkeit des Weges für Radfahrer anzugeben. BRouter wertet dies z.B. aus.
miche101 (2019-05-31 06:52:59+00:00): Darum ein highway=track bei dem das Fahren mit dem Auto usw. freigegeben ist trifft die Sache wesentlich bessern als highway=unclassified. Der Zustand die Breite usw. eingeschränkter Winterdienst.. es ist nicht zu emfehlen.. außer man will zur Forstwirtschaft

Wahrscheinlich wurde die Straße nur wegen der Forstwirtschaft freigegeben..
opendcc (2019-05-31 08:25:46+00:00): Nö, nicht nur Forst, sondern wegen den bewegungsfaulen Besuchern von Hubertus... und dort ist auch größerer Parkplatz. https://www.openstreetmap.org/way/41977716
miche101 (2019-05-31 08:46:57+00:00): Mit Forstwirtschaft... mein ich St. Hubertus ;-)
opendcc (2019-05-31 09:38:02+00:00): So gesehen wäre 'service' auch ein denkbares Tagging ...
miche101 (2019-05-31 12:09:54+00:00): service ist noch.. blöder vom tagging.. :-(
PT-53 (2019-05-31 13:20:30+00:00): Für eine Zufahrt (nur) zu "einer" Wirtschaft halte ich Servce sehr wohl für passend.
miche101 (2019-06-01 17:07:16+00:00): Also ich war jetzt dort: 

Beschildert ist dieser Weg nicht von der Zornedinger Str. her, was gegen highway=unclassified spricht also Ortsverbindungsstr. es gibt nur Fahrad Wegweiser und ein Ortsausgangsschild wo Ebersberg 10km drauf steht

Ein Schild ist das das auf 8km, Tempo 40 gilt und "Straßenschäden"

Ein weiters gleich dahinter:  max 3,5t außer Forstwirtschaftlicher Verkehr frei + "Kein Räum- und Steudienst"

Die Straße ist gekiest mit einer Fahrspur für beide Richtungen mit Schlaglöchern und die ganze Fahrbahn ist gewölbt, also zu beiden seiten abfallend..
miche101 (2019-06-01 17:09:10+00:00): also ich hab mich getäuscht... es gibt überhaupt keinen Winterdienst ;)
miche101 (2019-06-01 17:11:52+00:00): es gibt sogar einen Tag dafür :-)

https://wiki.openstreetmap.org/wiki/DE:Key:winter_service

winter_service=no
PT-53 (2019-06-01 17:19:03+00:00): Und was schließt Du daraus?
miche101 (2019-06-01 17:27:20+00:00): Auf was beziehst du dich??
PT-53 (2019-06-01 17:34:27+00:00): Welche Schlüsse Du bezügl. der Straßenklassifikation auf Grund Deiner Besichtigung ziehst.
miche101 (2019-06-01 18:12:42+00:00): Bin immer noch für track mit entsprechender Access
PT-53 (2019-06-02 05:40:50+00:00): Hoffnungslos!
eggie (2019-05-08 16:58:53+00:00): Hi Tjiwa.. Please leave the addressinfo intact. Just remove the shop info!
It's imported info fron the Dutch Kadaster to find an address in routeplanners!
Greetz, 
Eggie
eggie (2019-05-08 17:07:42+00:00): I noticed these removed  address-nodes come from the Bulgersteyn.  Funny.
eggie (2019-05-08 17:10:06+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privébericht.
eggie (2019-05-08 17:16:04+00:00): Het stuk langs de Omloop was al als construction ingetekend door medemapper 	A67-A67
Nu ontbreekt een tussenliggend stuk. Is dat misschien toch ook construction en kan als zodanig worden ingetekend?
highway=construction met construction = cycleway? 
Die edits langs de Omloop zijn van april 2019.
MVG,
Eggie
DaanGerard (2019-05-08 17:50:56+00:00): het is niet under construction, maar weg, en komt niet terug.
eggie (2019-05-08 21:55:59+00:00): Oke.,Duidelijk... maar ik heb het over het verloop van de highway=construction vanaf de omloop daar zit nu een gat in tot de Keutenberg. 
Wellicht is al bekend hoe dan de fietsers moeten rijden?
Gr eggie
mavl (2019-05-09 21:13:19+00:00): This changeset reverts some or all edits made in changesets 68059293, 68104729, 68105508, 68105633, 68105709, 68105756, 68105794, 68145959, 68146345, 68146553, 68146697, 68146985, 68160864, 68160965, 68161529, 68161721, 68162153, 68162234, 68162279, 68162376, 68162611, 68163568, 68163694, 68163739, 68163838, 68164041, 68164085, 68165740, 68165906, 68165940, 68185910, 68186173, 68186549, 68186818, 68187032, 68187125, 68187226, 68187443, 68187485, 68187666, 68188069, 68188313, 68188419, 68201429, 68201505, 68201819, 68202901, 68203003, 68203435, 68204155, 68209021, 68209301, 68219195, 68219574, 68219739, 68220172, 68220806, 68221103, 68222194, 68222809, 68223067, 68223182, 68223878, 68224030, 68224108, 68224674, 68224917, 68224941, 68225338, 68225802, 68226067, 68226507, 68227031, 68227887, 68229085, 68229569, 68229829, 68230512, 68236789, 68238522, 68239997, 68240230, 68247095, 68247157, 68254338, 68255431, 68256612, 68260729, 68261425, 68262633, 68264209, 68265323, 68266171, 68268335, 68270151, 68270836, 68271582, 68272302, 68274451, 68274945, 68275128, 68275866, 68276159, 68282116, 68283110, 68283717, 68284914, 68286819, 68289047, 68291105, 68294222, 68296422, 68297967, 68298794, 68299585, 68299677, 68301187, 68301547, 68302548, 68304679, 68320691, 68321801, 68324701, 68331931, 68334880, 68335937, 68339550, 68341880, 68347033, 68349262, 68352538, 68355370, 68355422, 68356009, 68356116, 68356294, 68356946, 68364052, 68366235, 68369850, 68371410, 68376470, 68378521, 68378950, 68379651, 68382412, 68383510, 68385700, 68398957, 68399291, 68399782, 68410999, 68415910, 68420221, 68423584, 68424323, 68424816, 68426829, 68429253, 68430393, 68431131, 68435575, 68436037, 68438609, 68440451, 68441506, 68445511, 68449963, 68451718, 68453195, 68453821, 68454265, 68454853, 68456313, 68457805, 68461972, 68461999, 68470135, 68472619, 68473840, 68474670, 68478553, 68479612, 68480583, 68480769, 68481059, 68482276, 68504512, 68508186, 68509217, 68509411, 68511594, 68512732, 68513256, 68522231, 68522792, 68543895, 68590317, 68622884, 68624896, 68625555, 68626317, 68632967, 68637600, 68667338, 68667792, 68671144, 68672198, 68676292, 68677578, 68699310, 68701260, 68701674, 68701804, 68715154, 68715560, 68716454, 68717330, 68726805, 68727988, 68757049, 68760622, 68761787, 68762697, 68790311, 68792530, 68794430, 68795279, 68831135, 68865085, 68865275, 68865601, 68869172, 68870281, 68870622, 68872458, 68872673, 68893573, 68894195, 68895155, 68958266, 68959415, 68966165, 68966428, 68966840, 68967075, 68967170, 68991977, 68995311, 69011097, 69046189, 69140482, 69150153, 69150744, 69170723, 69171419, 69177526, 69178135, 69182449, 69201587, 69203539, 69204391, 69205822, 69242042, 69242271, 69295064, 69296765, 69345956, 69349941, 69358348, 69369923, 69370472, 69372794, 69375281, 69379002, 69382150, 69385738, 69387010, 69395301, 69395710, 69402647, 69406490, 69409242, 69410903, 69416107, 69416729, 69422282, 69422845, 69424353, 69425609, 69427087, 69427817, 69438933, 69442833, 69445192, 69450587, 69452938, 69458491, 69460807, 69464815, 69476830, 69480051, 69501933, 69502957, 69503313, 69759396, 69759457, 69762413, 69841058, 69879265.
aharvey (2020-02-11 02:37:11+00:00): I see you added the fee value here, per https://wiki.openstreetmap.org/wiki/Key:fee I'd recommend using fee=yes (to say that a fee usually applies; the default) combined with fee:conditional=no @ (Tu-Fr 11:00-20:00; Sa-Su 10:00-20:00) to say that during these hours a fee doesn't apply.  This is more in line with how conditional restrictions generally work https://wiki.openstreetmap.org/wiki/Conditional_restrictions
Constable (2019-05-10 12:03:15+00:00): ciao, giusto per dovere di cronaca, il tag highway=cycleway implica bicycle=designated
https://wiki.openstreetmap.org/wiki/IT:Tag:highway=cycleway?uselang=it
Puoi quindi tranquillamente tralasciarlo
Dingo67 (2019-05-10 19:23:14+00:00): Hai ragione, però con la mappa che uso io assegnando anche il TAG specifico vengono inserite ulteriori varianti grafiche sulle linee. Per cui visto che di problemi non dovrebbe crearne (spero) essendo semplicemente un doppione del l'implicito, ho pensato di apportare tali modifiche sulle ciclabili che conosco e che solitamente frequento. Se ho sbagliato me ne scuso e correggo. Ciao.
Constable (2019-05-11 16:12:56+00:00): CIoa, grazie per la risposta. Essendo implicito direi che è ok, nessun problema, lo vedo alla pari di oneway=no su alcuni tratti di strada che magari possono sembrare (ma non essere) a doppio senso.
Importante è però non cadere nell'errore di mappare per il render https://wiki.openstreetmap.org/wiki/Tagging_for_the_renderer . Non è questo il caso comunque :)
Richard (2019-06-18 15:46:17+00:00): Hi Kyle,

Great to see the work you've been doing!

In a developed country like the US, we'd usually assume highway=secondary to be a paved road. Being able to judge the surface correctly is particularly important for vehicles (e.g. road bikes) which are unable to use non-paved roads. Here's an example of where it's important - https://www.crazyguyonabike.com/doc/page/?o=1mr&page_id=579972&v=5W where the cyclists had to walk for 2km because the surface wasn't tagged in OpenStreetMap!

So for a road like Stony Hollow Road (https://www.openstreetmap.org/way/15879615), the current mapping of highway=secondary is a bit misleading unless there's a surface tag.

Could I encourage you to add surface tags to unpaved roads you edit? surface=gravel or surface=dirt would be great, but you can be less specific with surface=unpaved if it's easier.

All the best
Richard
Kyle Gates (2019-06-18 16:13:09+00:00): Richard,
Yes, I wholeheartedly agree. Adding surface tags is on my list of things to work on.
In rural areas of the US there are many unpaved roads that do have relatively high traffic volumes and/or are direct routes between small populated places. I generally focus on routing for motorized vehicles but understand OSM is used for bicycles as well. I will try to keep the needs of cyclists in mind as well.
Thanks for the comments and your support of the mapping community.
Kyle
NunoCapeloCaldeira (2019-05-08 19:20:06+00:00): again, explain and fix the content you are adding. Or i will be forced to reverse.
TurtleDrake (2019-05-08 19:34:22+00:00): I did the trail yesterday and discovered serval passages that have minor climbing elements. Some of them looked like a simple ferratas to me.
Becaus the trail leads down from the Pico Ruivo and some folk will probably use the path, the entry should also warn them.
NunoCapeloCaldeira (2019-05-08 21:44:02+00:00): hi, we have a sac scale for the trails. https://wiki.openstreetmap.org/wiki/Key:sac_scale what you added and described does not fit into the "climbing" tag https://wiki.openstreetmap.org/wiki/Climbing
TurtleDrake (2019-05-08 22:19:11+00:00): Got it, I will have a look into this next week.
And thanks for your comments.
NunoCapeloCaldeira (2019-05-08 22:31:12+00:00): No worries. Enjoy your stay in Madeira.
viloan (2019-05-08 17:10:18+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!
gurglypipe (2019-05-08 19:17:45+00:00): Nice work. Did you mean to move the rubbish bin from Ullswater Road?
Casey_boy (2019-05-09 08:32:01+00:00): Bin moved back in https://www.openstreetmap.org/changeset/70063181
pitscheplatsch (2019-05-08 19:39:36+00:00): Hi Piet183, welcome to OSM.

Did you discuss this mass-edit of almost 50,000 with the local community? Thanks.

Second CS: https://www.openstreetmap.org/changeset/70039728

More information about this changeset: https://overpass-api.de/achavi/?changeset=70038896

--- 
Detected by #SuspiciousOpenStreetMap
Piet183 (2019-05-12 15:23:25+00:00): Hi pitscheplatsch, 
I have not discussed it with the community, but I could undo these changes
pitscheplatsch (2019-05-12 16:54:23+00:00): Thanks for your answer, but you should better discuss your mass-edit before any changes were made.
Mateusz Konieczny (2019-05-08 18:03:55+00:00): Small note - things like individual baseball fields we tag as pitches. I fixed https://www.openstreetmap.org/way/688703388
Martin Borsje (2019-05-13 19:03:13+00:00): OK heb er wel, net als voor de overige sporen 'preserved' van gemaakt :)
viloan (2019-05-08 17:28:36+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!
user_6110846 (2019-05-11 15:28:24+00:00): https://www.google.com.ua/maps/@50.7696644,29.2466732,3a,15y,150.87h,90.72t/data=!3m6!1e1!3m4!1sOuaPWMTdA1MfzCS3A5Dm6w!2e0!7i13312!8i6656?hl=uk тут перуканрня є 
шукати чи ти її видалив чи хтось інший  впадло
santamariense (2019-05-08 22:18:44+00:00): Segundo a convenção que adotamos atualmente, Itapuca deve ser place=village e não town por ter menos de 10k habitantes. town para as de 10k a 100k e city para as maiores
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/70039708
ricardopretto (2019-05-09 02:17:55+00:00): OK, amigo, obrigado por avisar. Vou corrigir isso agora mesmo.
viloan (2019-05-08 17:45:47+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!
Hjart (2019-05-09 06:21:32+00:00): https://www.openstreetmap.org/way/468364697 er da ellers defineret som sti? Ignoreres dette når den samtidig tagges som område (area)?
Bjørn Kristensen (2019-05-09 11:24:53+00:00): Du har ret, området fungerede som sti, så jeg har fjernet den jeg lavede.
maraf24 (2023-07-09 13:08:10+00:00): Dane były poprawne, w tej edycji zamieniłeś elektrownie miejscami.
LoboWinter (2019-05-08 18:07:02+00:00): https://wiki.openstreetmap.org/wiki/Key:barrier
muralito (2019-05-08 18:37:15+00:00): Hola LoboWinter.

Etiquetar barrier=wall en esos nodos no es la forma correcta de modelar eso, porque lo que hiciste hace que el muro este en la calle. Lo que podes hacer si queres es dibujar el muro con una o varias lineas y a esas si ponerle el barrier=wall.
muralito (2019-05-08 18:38:22+00:00): Al nodo de 532 Bonifacini me refiero....
LoboWinter (2019-05-09 14:20:59+00:00): Hola muralito, muchas gracias por el comentario. Me queda una duda, los nodos 319282326 y 6459340793 efectivamente están sobre la calle (sin espacio para vereda) y el nodo 314493367 (de bonifacini) no se junta con la pared sino que hay una vereda de por medio (La calle Jose Murias termina sobre la calle Bonifacini y no sobre el muro). Viendo el tile que genera osm creería que se corresponde con esa situacion, si estoy equivocado por favor confirmame que vuelvo a editar el nodo.
muralito (2019-05-09 22:16:34+00:00): Fijate como lo deje ahora, asi es como entiendo que debe quedar, en tres lados tocando el poligono barrier=wall y en el otro separado, para que se pueda rutear por Bonifacini, porque si pones un nodo barrier=wall en esa T, ese nodo hay que esquivarlo en los ruteos.
viloan (2019-05-08 18:18:29+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!
pitscheplatsch (2019-05-09 07:18:41+00:00): Hi imflynn13, 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

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

#GolfMapping 
--- 
Detected by #SuspiciousOpenStreetMap
Gabriel0322 (2019-05-09 15:23:42+00:00): Define badly POI?    People are entitled to added grass, separating townhomes since they have separate address.   Allowed to add parking.   What is the point of having all of the tags if you guys aren't allowing them to be utilized?
TravGW (2019-05-09 17:54:09+00:00): The poi were either: 1) Missed tagged [changing a building to landuse]  2)Not tagged at all [naming a bench as “Bench” is not the same as tagging it] 3)Tagged but not used correctly [using a parking lot tag for street side parking. 4)The poi does not exist [a footway that does not exist] 5)Maliciously added [the 40+ fishing spots you added to your private pier]

1)https://wiki.openstreetmap.org/wiki/Buildings
2)https://wiki.openstreetmap.org/wiki/Good_practice#Don.27t_use_name_tag_to_describe_things
3)https://wiki.openstreetmap.org/wiki/Key:parking:lane
4)https://wiki.openstreetmap.org/wiki/Good_practice#Map_what.27s_on_the_ground
5)No.
Gabriel0322 (2019-05-09 18:07:32+00:00): A footway that is designated as a ground tag, is a proper tag for a park that doesnt have actual sidewalk footways.   They were correct.   

Tagging a bench, it was done as a point of interest.   There shouldn't be anything wrong with using points of interest to label objects they do not have as area tags.  It is used for various things including a address number....   This is an idiotic remark.     

40 fishing spots.   It is a 85 foot pier with a 20ft by 14 feet L shape.   It isnt malicious it.  It allows for people to see how many spots they can use for fishing and crabbing.   

You guys are looking at things in a board range, when the map can handle more detail than you are willing to provide.  Doesn't mean others shouldn't be allowed to enter more information.
Gabriel0322 (2019-05-09 18:09:33+00:00): How about instead of wasting both of our times on a park.    Let me update, you chime in saying whats wrong.    Give me time to review and change.   Otherwise nothing will ever get updated and we will be in a stupid constant loop of nothing being updated.
Gabriel0322 (2019-05-09 18:10:37+00:00): Just because I may not have it thoroughly finished doesn't mean you should revert every si
Gabriel0322 (2019-05-09 18:10:52+00:00): single thing.
Mateusz Konieczny (2019-05-09 19:07:56+00:00): Dzięki za weryfikację i poprawkę!