piebro/osm-data huggingface dataset:
eireidium (2021-11-03 17:15:50+00:00): I am actually attempting to determine tree crowns in those areas - Am sorry if they appear random. one of my students is exploring tree cover in DK, IRL and CA using a few samples and so best attempts at identifying individual trunks has proved fruitful for her. Apologies if they appear random. They are placed based on perceived colour differentiation as a means to find the individual trees. Using natural=wood is useful for some means but in this instance skewed calculations - especially when there is a higher probability of using the imagery to pinpoint accuracy at a tree by tree level and overpass-turbo. Appreciate your attention to detail and the varied uses of OSM data
Discostu36 (2021-11-03 09:55:42+00:00): Bitte keine überflüssigen Daten hinzufügen. Bei Straßen und Wegen kann man davon ausgehen, dass diese normalerweise nicht überdacht sind.
user_11418917 (2021-11-05 04:15:24+00:00): Hello ፑሲ ፊከር,   
 Thank you for your edit in Iraq, but your edit made the monument not showing on the 2D map, here is a before and after screenshot: https://i.ibb.co/mHT21KF/image.png            
Is this meant to be or not?           
Thank you.    
Best Regards.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/113322574
user_11418917 (2021-11-05 04:23:21+00:00): if the answer is yes then I believe will fix lots of similar buildings in Baghdad like: https://www.openstreetmap.org/#map=18/33.31152/44.34981      
Just want a confirmation to just make sure before replacing the building tags with building parts tags.        
Thanks again sir.
Lee Carré (2021-11-03 20:16:31+00:00): Smaller changeset areas, please: http://wiki.osm.org/wiki/Changeset#Geographical_size_of_changesets
CRCulver (2022-04-26 20:22:27+00:00): Is there actually a sidewalk along the road at coordinates 51.9074006, 22.366938? Geoportal imagery does not show any sidewalk there.
pitscheplatsch (2021-11-04 06:47:18+00:00): Hi BlueSwiss, welcome to OSM.

You mapped a carport and added a housenumber. See https://www.openstreetmap.org/way/998705319

What's the source of your mapping activity? Thanks.

--
Detected by #SuspiciousOpenStreetMap
https://resultmaps.neis-one.org/osm-suspicious
Sheila Job (2021-11-05 09:44:09+00:00): Hello Cascafico, we have some problems here i think that you use bing instead of using Maxar to map, so please use maxar imagery when you are mapping, because a lot of retangular draw here is just a draw without house. please review and thanks for mapping
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/113323602
osmviborg (2021-11-03 11:08:12+00:00): Nu er jeg ikke lokalkendt; men ser man på terrænskyggekortet, så var dammen korrekt tegnet.
b-holdet (2021-11-03 11:35:24+00:00): Det ser ud til at området er tørret en del ind, så mosen kun er i den nordlige del.

http://kortsalg.sollerodok.dk/wp-content/uploads/2020/04/Rude-skov-S-1.png
osmviborg (2021-11-03 12:09:43+00:00): OK, tjek lige nederste venstre hjørne af din ref.
b-holdet (2021-11-03 13:36:49+00:00): Jeps, det ved jeg godt.
Det var nu også for at vise at stedet er tørret ud i forhold til Terrænvisningen.
Har løbet o-løb i området og har været gennem det. Nordlig del skulle man holde sig fra.
Sebastian Røysland Maltby (2021-11-03 13:46:48+00:00): Jeg har selv løbet o-løb her mange gange og den sydlige del er helt fin at løbe igennem; åben skov med enkelte grøfter. Delen øst for den store sti er lidt mindre gemmenløbeligt men bestemt ikke mose. Det område som jeg har tegnet som mose nu er meget tæt og vådt. Så vidt jeg mindes har der aldrig været mose i hele det område som før var tegnet som sådan.
Mordechai23 (2021-11-03 13:38:15+00:00): Cześć, taki park tagujemy jako leisure=dog_park ;)

staraj się unikać dodawania opisów w name=* https://wiki.openstreetmap.org/wiki/Pl:Nazwy#Nazwa_jest_tylko_nazw.C4.85
maraf24 (2021-11-03 17:27:59+00:00): Mój błąd, sprawdziłem zdjęcia i faktycznie wybieg dla psów, nawet ma regulamin wybiegu dla psów na tablicy :)
gitouche (2021-11-03 10:06:20+00:00): Modification envoyée sans commentaire ni sources.
Caméras de surveillance, source = survey (aussi sur mapillary/kartaview)
eggie (2021-11-03 10:40:41+00:00): Dag G vd W  
Best lastig al die verschillende manieren van wegklassen. 
Hier heb ik het nog even naar steeg aangepast.  Dan klopt ook die maxspeed van 10.
Op een woonerf is het wettelijk 15.
en het Jasmijnpad zelf veranderd in woonerf met maxspeed 15 
Het voetpad vanaf de Crocusstraat ook maar op private gezet. 
'k Denk dat het nu allemaal klopt.
MVG
eggie
afgb1977 (2025-02-17 06:22:24+00:00): Hello.
You added a lot of wikipedia=en:xxx about Colombia, a country where the official language is Spanish, not English.
At any point did you notify the Colombian OSM community about the data you were going to add?
So, you made an official inquiry about entering a language other than Spanish in a large number of OSM elements and you received an acceptance to add that type of key=value?
If not, why do you force the English language on data whose coverage corresponds to a country where the official language is Spanish?
borovac (2025-02-17 20:03:26+00:00): I used the Wkipedia plugin, which is set to English by default. I will make some changes and replace the Wiki links in the next few days. I would like to ask you to send me the language for which countries you want me to put. Thanks for the suggestions.
eggie (2021-11-03 10:57:37+00:00): Ook een lastige...
access=permissive is algemeen. Dat dus beter weghalen en alleen specifiek taggen. Dus vehicle=no foot=permissive
MVG
eggie
eggie (2021-11-03 11:17:36+00:00): Ik pas even wat aan zodat de paden goed liggen.
access=permissive zal ik verwijderen.. Dat conflicteert met de andere accesstags 
MVG
eggie
DressyPear4 (2021-11-03 10:44:28+00:00): Olá, vias não devem ser sobrepostas, sempre adicione um nó nos cruzamentos.
Não ignore os avisos do editor sempre resolva antes de fazer o upload
ovruni (2021-11-03 20:28:17+00:00): Hola, en este conjunto de cambios se ha quitado el sentido de la vía a la entrada del estacionamiento sin ninguna justificación. La salida del estacionamiento es solamente por la avenida punta del este, revierto su conjunto de cambios.
Saludos
eggie (2021-11-03 11:13:12+00:00): Dag GvdW  In het begin wordt wel meegekeken.
Uiteraard om te helpen.
Dit geeft een foutmelding, want er loopt nu een wandelpad door het water.
Een steiger map je met man_made=pier  Het voetpad kun je weglaten.
name=Zwemsteiger veranderen in description=zwemsteiger.
gr eggie
eggie (2021-11-03 11:38:08+00:00): name=Openbare Vlonders hoort niet op de kaart thuis
Haal je die naam weg of vervang deze door description=...
Maak er man_made=pier van ipv highway=footway.
Mapse
eggie
SomeoneElse_Revert (2021-11-03 10:39:36+00:00): This changeset reverts some or all edits made in changesets 101626547, 102566008, 102570015, 102796201, 102797613, 102914449, 102914908, 103043707, 103183486, 103324542, 103324967, 103335461, 103395305, 103473696, 103758879, 105083254, 105403066, 105475313, 106080931, 106383984, 106516137, 106896131, 107257843, 107425664, 107539891, 107616147, 107685347, 107888909, 107905919, 107909413, 108239557, 108475863, 108806925, 109390344, 109735933, 110274876, 110662780, 110663105, 110665275, 110782734, 110782834, 110840618, 110846445, 110898993, 111183088, 111278833, 111287622, 111288332, 111439846, 111636766, 111636796, 112362222, 112731762, 112935175, 113069781, 113220950, 113227891, 98354664, 98635686.
tonyf1 (2021-11-03 10:39:13+00:00): correction 106663088
surveyor54 (2021-11-03 18:14:18+00:00): Hi Tobias83,
es wäre hilfreich, wenn du auch die Quelle deiner Änderungen angeben würdest. (survey, georeferenzierte Fotos u. ä.)
Du hast hier einen Pfad und eine Furt eingetragen und als Quelle Bing angegeben. Ich kann beim besten Willen hier keinen Weg u. keine Furt auf dem Luftbild erkennen.

Gruß
surveyor54
Tobias83 (2021-11-03 18:18:03+00:00): Hallo surveyor54,
Die Quelle ist nicht Bing, sondern eine offizielle Wanderroute des Spessart. Eine Furt ist es in der Tat nicht, sondern eine Bachüberquerung mittels Trittsteinen. Diese Option konnte ich in OSM aber leider nicht finden. Hast du mir dazu vielleicht einen Tipp? Danke :)
surveyor54 (2021-11-04 08:29:49+00:00): Hi,
schön, dass du dich meldest. :)
Dann schreib doch als Quelle "Ortskenntnis; GPS" hin, da wissen alle bescheid.
Hier ein Link für Trittsteine:
https://wiki.openstreetmap.org/wiki/DE:Tag:ford%3Dstepping_stones

Ich nehme an du bist die neue "Roßbacher Biebertal-Fährte" gelaufen und hast die Route mit dem GPS aufgezeichnet. Bist du in der Lage so eine Route in OSM als Routen-Relation einzutragen?

Weiterhin frohes Mappen und Gruß
surveyor54
Tobias83 (2021-11-05 12:46:00+00:00): Hi surveyor54,
danke für den Tipp. Hab die Furt jetzt auf stepping_stones geändert.
Gruß Tobi
marc__marc (2024-08-30 10:26:26+00:00): Hello,
amenity=clubhouse without a _ :)
Regards,
Marc
SomeoneElse_Revert (2021-12-28 00:51:09+00:00): This changeset has been reverted fully or in part by changeset 115447422 where the changeset comment is: Reverting some changes that removed 'unexpected' values from surface tags.  See comments on https://www.openstreetmap.org/changeset/113316313 .
gurglypipe (2021-11-03 11:20:15+00:00): Smaller changeset areas please: https://wiki.openstreetmap.org/wiki/Changeset#Geographical_size_of_changesets
grin (2021-11-03 11:33:10+00:00): It is not possible.
gurglypipe (2021-11-03 11:50:58+00:00): Yes it is. In JOSM, select the modified objects in a single country (https://help.openstreetmap.org/questions/41728/in-josm-can-one-select-objects-within-a-given-country-outline, or just do it manually), then ‘Upload selection’
grin (2021-11-03 11:58:41+00:00): It is not possible, what you say is not related to the changeset. Please examine carefully what happens there: it fixes _global_ problems, not country specific ones. (Or, in other words, it may contain 100+ countries in one change, or "one change in every country".)
Please do not send out warnings without actually examining the changeset since it is possible that the changeset is right and you are wrong. Global changes may be unusual for you but it doesn't mean they're not valid.
gurglypipe (2021-11-03 12:50:11+00:00): What I say definitely is related to the changeset. I have examined the changeset. You’ve fixed weird values of surface= all over the world. That’s a good change, but it doesn’t need to be done in one changeset. Submitting these changes in multiple changesets, one per country, is possible and many other people manage to do so with their edits using JOSM.

Did you read the wiki page’s reasons for why submitting changesets over large geographical areas is not great? This changeset will be showing up in many, many people’s osmcha feeds. That means that either tens of people will spend time reviewing this changeset even though it’s probably unrelated to their editing area; or *nobody* will review it because it’s too big and they all think someone else will review it.

If problems are found with your changes in one country, you risk the rest of the valid changes in the changeset being reverted as a result.
grin (2021-11-03 13:52:44+00:00): Try to tell me how *practically* you imagine "multiple changeset" in this case. 

I tell you that right now it takes time to find the problem (that's the longest part, usually), then get all the problematic objects in one turn (from overpass), then select all problem object (at once), fix up the tag, this last phase takes about 30 seconds; then verify multiple ways and visually check a few times and places (2-3 minutes unless it's broken), then upload. 

Now I wonder how you plan to do it when, say 50 countries are involved, and I do not even know which ones, since I do not download boundaries. I guess it would take few hours(!) to do what you propose and you don't realistically expect me do to that. Or anyone. Also it would create separate changesets for _related_ changes, which is exactly the opposite of why changesets exist in the first place.

You see it also correctly that if my changeset would have a problem it would be reverted _globally_, quite right, since if I screwed it up in Timbuktu then it'd be problem in Niue too. :-)

I am very familar with the wiki (as you may have seen on my HDYC page), also with global sized changesets, osmcha and other QA tools. When I say that I am aware *and* I am sure this is the correct way then I really mean it. It is rarely a good thing - this is the case when it is.
gurglypipe (2021-11-03 14:15:09+00:00): > Try to tell me how *practically* you imagine "multiple changeset" in this case. 

A significant number of the changes in this changeset are in the US, so that could be one changeset. There are other clusters in Chile, South Africa, Vietnam and central Europe; so one changeset each for those.

Or you do one global changeset and make it clear exactly what mechanical edit has been made, i.e. document “Removed invalid surface=[0-9]+ tag, only mechanical edits”. The fact that your changeset comment also said “small local updates” means that nobody can trust the changes are all uniform, and hence the only way to review the changeset is to look at every single node/way it touches and use OSM deep history on them.

Note that a changeset of this size is too big to load in osmcha or achavi successfully, so changes have to be manually reviewed node by node.
Lee Carré (2021-11-03 20:38:43+00:00): I have to concur entirely with gurglypipe.

@grin

Why should anyone tolerate their local list of changesets being spammed with globe-spanning bounding-box CSs when said sets make exactly zero changes in the mapper's own country?

Especially when count of said globe-spanning sets EXCEEDS the count of locally-relevant sets?(!)

Explaining that quality work takes effort … well, yeah, of course it does (I say that as an on-foot surveyor, who has sometimes spent multiple hours at the same site). That's not an excuse to be lax or cause other members of the community to suffer the externality of your convenience.
fghj753 (2021-11-03 22:58:45+00:00): Dear Mr/Mrs Grin,

As you may have noticed by now, making large changesets in OSM attracts angry comments made by mappers, who are demanding you to create changesets with smaller bounding boxes. Such mappers are often located in Western and/or Central Europe. Therefore i agree with Gurgly Pipe on the matter that either size or positioning of your changeset is not optimal considering it's content and advise you to split future changesets bit smaller.

As a user from rather small country, i strongly disagree with suggestion of splitting changesets by country's borders, because in Europe such actions could lead to unreasonably small changesets (often 1-3 changes per country). Instead, i would suggest splitting changesets by continents while keeping in mind mapper density (latter means splitting Western Europe). For example in your case there could be 3 changesets: changes in Usa, southern hemisphere (incl Vietnam) and in Europe.

As for other two users. I have noticed under different global changesets, how some people (not necessarily you, don't take this personally) have voiced complaints over too large changesets breaking their review workflow. I would like to hereby encourage you to refrain yourself from such retroactive behaviour and focus on being proactive instead. If you are using a review tool that doesn't open large changesets, what is long-term benefit of announcing it in most changeset discussions? Why not think ahead and address the cause (tool doesn't support large changesets) instead of effect (tool crashes when opening large changeset)? Presuming the tool used is open source, please do open a pull request or at least issue on on tool's git/website and at least attempt to fix the bug yourself.
For example: if Lee Carre doesn't want to see large changesets in their OSM changes feed, they could simply create plugin for the feed analyser, which could filter out all changesets with three-digit longitudinal width or encompassing equator, such as this one.
MxxCon (2021-11-04 04:56:03+00:00): You should be able to augment your overpass query to filter only for specific area(s), be it a country, relation, continent or just bbox.
grin (2021-11-04 10:46:49+00:00): @gurlypipe: some changes may be in some countries, others may not. What you say may be true for one change and false for others. Most aren't.

@lee: the word "spamming" means something else you think it does. I wonder if you attack people accidentally putting unrelated changes in a changeset with the same vehemence...
grin (2021-11-04 11:09:41+00:00): Dear Mr./Mrs./Ms. @fghj753! :)
Thanks for actually responding related to the changeset. :-) 

One problem is that some people are indeed using defected methods to filter for local changes, since bounding-box based filtering hasn't been useful for a decade now. Many tools are intelligent enough to actually filter by content instead of the box, and other tools can filter boxes with corners the active area. If all else fails it's pretty obvious even visually to see if a bbox is larger than target area, and leave it for people with higher tolerance of bbox sizes. :-)

Other problem is that the fellows commenting here can't decide whether they absolutely want specific changesets (and resulting dozens of global changesets) or they want one merged changeset (global with lot of unrelated changes), apart from the ideas that the work shall take 100 times longer, which is pretty easy to give out as an advice (and I could have replied "why don't YOU do that then?" but QA doesn't work that way), but clearly unfeasible.

These kinds of changesets always will be global, simply because these kinds of problems are not restricted to areas, more often either to mappers making same mistakes all over or people making the same typical typo everywhere scattered (example to see: people counting on autocomplete and giving "surface=u" instead of "surface=unpaved"). 

What I can do is that I try to upload mechanical change and manual changes separately, but it means uploading errors which I do not quite like: some mechanical fixes reveal mapping/tagging problems. I'll see whether it's feasible.

The method/tools are nothing magical: go to taginfo, find obvious problem tagging, send over to JOSM, select all, fix all, verify, upload. (@MxxCon: any such idea would mean N-times amount of work for nothing; peopel complaining should rather use better filtering.)

One can open any changeset for viewing/editing in JOSM: File»Open location»insert changeset URL.
MxxCon (2021-11-04 14:10:23+00:00): Do share what better filtering there is. in Osmcha I have an area designed strictly around 5 NYC boroughs, yet I'm getting your changeset. So please do tell how to filter only for changes inside of the area of my interest.
grin (2021-11-04 14:40:18+00:00): @MxxCon: find "BBox size bound" in filtering. Giving "2" filters out anything larger than twice of yor selected target bbox.
grin (2021-11-04 14:45:23+00:00): @MxxCon: find "BBox size bound" in filtering. Giving "2" filters out anything larger than twice of yor selected target bbox.
MxxCon (2021-11-05 05:55:57+00:00): That will just filter out big bboxes, including the ones that actually do contain changes within my area of interest. That's not a solution.
grin (2021-11-05 07:04:18+00:00): @MxxCon: yes, it is the solution for those who get _annoyed_ by large bboxes. They definitely shall skip those.

For everyone else there are various QA tools around, and I do not say I know them all. As an example I am using WhoDidIt (https://simon04.dev.openstreetmap.org/whodidit/) which filters on real chhange coverage. I have collected a large amount of tools on https://wiki.openstreetmap.org/wiki/User:Grin/bookmarks#QA but I shall probably review/extend the list again.
MxxCon (2021-11-05 07:16:52+00:00): No, that's not workable solution. whodidit doesn't present me with data in a way that's easy for me to observe the map for changes in my area of interest.
grin (2021-11-05 07:38:34+00:00): @MxxCon: Unfortunately I cannot provide a personalised solution for everyone. You could check the QA tools and choose which is best for you, or convince tool authors to make changes according to your needs. There are various realtime or history browsers, you may find one of your liking.
MxxCon (2021-11-05 07:47:18+00:00): I did check all the QA tools I know of and for the way I do things, OSMCha works best.
grin (2021-11-05 11:11:12+00:00): @MxxCon: https://github.com/mapbox/osmcha-frontend/issues/572 may be the one helping you, provided someone from the developers implement it. Unfortunately I do not have the time to implement it by myself.
In the meantime achavi can handle these if you press "cancel", select your actual local bbox and press "load" again; the reason is that overpass API does not like huge bbox queries.
Lee Carré (2021-11-06 21:38:03+00:00): From http://www.osm.org/changeset/110409629

“Tool co-author here.

Today there's no workable solution available to analyze large changesets.

…”
grin (2021-11-07 10:17:57+00:00): @Lee Carré I see people already told you in the linked discussion how to filter these changesets, so you really should do that. I also have linked the related issue above, since the solution for your problem is not stopping QA edits but fixing the tools you use.
Lee Carré (2021-11-21 14:30:12+00:00): “the solution for your problem is not stopping QA edits”

Ignoring the projection & presumption over what the problem is; by ‘QA edits’ do you mean edits made in order to remedy tagging problems (like the ones you're doing), or edits made as a result of reviewing changes made by others?

I ask, because I'm going somewhere with this, but it depends on what you meant in your original.
eggie (2021-11-03 11:32:59+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privebericht. 
Feedback.. Wanneer het echt een bezoekadres is dan is het oke.
Format phone is +31....  in OSM 
https://wiki.openstreetmap.org/wiki/Tag:craft%3Dgardener


MVG, 

Eggie 

Namens de OSM Community
gurglypipe (2021-11-03 11:20:22+00:00): Smaller changeset areas please: https://wiki.openstreetmap.org/wiki/Changeset#Geographical_size_of_changesets
grin (2021-11-03 11:32:24+00:00): It is not possible. This is a global change.
Mordechai23 (2021-11-03 12:57:12+00:00): Nothing stopped you from uploading one fixed value at a time - so it was possible. Please don't do such big bboxes again
grin (2021-11-03 13:11:11+00:00): @mordechai23: if I uploaded one fixed value a time there would have been 10 times *more* global bboxed changesets. Is that what you mean?

Please also realise that I am very well aware what a bbox is, how it's working and why the large box is proper in this case. Repeating a wrong claim does not make it more valid and does not help the discussion. Also see my other changesets for parallel discussions, as well as contradicting advices from various people, which is normal in cases where all their advices are improper.
Lee Carré (2021-11-03 20:40:47+00:00): Great, another [un]Friendly_Ghost 🙄🤦‍♂️.
Friendly_Ghost (2021-11-03 21:33:30+00:00): Love you too, Lee <3

Anyway, grin, you can select a cluster of objects and upload only the selection. If you do that a couple of times you can make regional boundary boxes, which might save you some unfriendly comments from Lee Carré here.

Thank you for taking your time to fix these tags :)
Zaneo (2021-11-03 23:42:23+00:00): Thanks for being a valuable member of OSM grin. Good to see that some people can see the forest despite the trees :)
RaccoonFederation (2021-11-04 00:06:35+00:00): Only edit one tree at a time please, no large forest edits, thanks
glglgl (2021-11-04 10:59:16+00:00): It annoys people in all parts of the world which are not affected.
grin (2021-11-04 13:43:16+00:00): @Friendly_Ghost, @Zaneo: thanks.
grin (2021-11-04 13:44:39+00:00): @glglgl: you should avoid letting yourself annoyed. If you know a large bbox annoys you then try to skip those.