Dear marwa_khalid01, in this changeset you have added a number of "building=yes" objects but when looking at aerial imagery I can see that the actual buildings are much smaller; please use the "building" tag only on the actual building and not on the plot boundary.

Dear marwa_khalid01, please don't add land parcels to OSM. Instead, group neighbouring parcels into one large landuse=residential polygon. We are not interested in parcel boundaries as these are not verifiable on the ground.

I have reverted this edit, it appears to be a mistake and the changeset comment "편집" does not sufficiently explain why these facilities should have ceased to exist.

You are free to do that (providing you are using a source that is not subject to copyright!) but unless you are uploading new data within the next couple of hours, we should restore the old trails until you actually replace them.

Agreed - you will have to explain your deletions if you want them to stand. "Green Trail" is not a suffcient explanation for deleting data that has bee in OSM for over 12 years. Has the area been bulldozed? Have the trails been replaced to build a mine?

Hallo, ich habe die Löschungen zunächst einmal rückgängig gemacht. Das heisst nicht, dass sie falsch sind, allerdings ist das mit den Wildruhezonen und Schonungen eine häufige Schutzbehauptung in der Forstwirtschaft, um das allgemeine Waldbetretungsrecht auszuhebeln. Daher schauen wir in diesen Fällen gern selbst vor Ort genauer hin und erkundigen uns bei Bedarf bei der zuständigen Unteren Naturschutzbehörde, ob in den betr. Gebieten tatsächlich Sperrungen genehmigt sind, und löschen die Wege erst dann (oder markieren sie als gesperrt). Ich habe die Sache unserer Community zur Beurteilung vorgelegt: https://community.openstreetmap.org/t/ruckegassen-bei-warstein-kr-soest-nrw/140028

I have reverted all of Sparko000's deletions. I encourage Sparko000 to use access=private tags or similar, as explained in the link above. (DWG Ticket#2026010310000131)

Dear Jobigutenburg, when adding Arabic (or other) names to features, please keep in mind that we do not use the name:xx tags to add translations. For example, if you add an Arabic name to an entity called "Region Nordjylland" then you need to have a source where this Arabic name is actually used (for example: a web site operated by the government and offered in Arabic). It is *not* ok to simply translate the term into Arabic and add that to OSM - if you add an Arabic name it must be one that is actually (and provably) used. In the future when adding Arabic names please cite a source.

Please link to the required import documentation in your changeset uploads to avoid your edits being reverted as undiscussed imports!

I am having second thoughts about the *names* of these trails. I wonder if they are surveyable on the ground. If not, maybe the names need removing. If they are surveyable, some abbreviations might need expanding ("McQueen Lk Blue XC Tr").

The DWG is tracking this in Ticket#2025121810000281. The deletions are against OSM's rules and have been rightfully reverted. Repeated deletion of these tracks violates our terms and will be considered vandalism.

looks legit

These are mobile to a certain degree, right? And what you have mapped here is their configuration on whichever date the aerial imagery has been taken? Does that make sense? Is that not like mapping the location of an airport bus?

Instead of deleting buildings and then re-drawing them, you might use the JOSM "modify geometry" tool to move them to the right place.

Dear BrianKarani, in this changeset you have deleted a lot of buildings and then re-drawn them. The JOSM editor that you are using has an edit mode that allows you to correct the geometry of existing objects, rather than deleting them. That way, the history (Object initially created by user X, then improved by user Y) remains intact. Please consider using that in the future.

Also, please write changeset comments that are understandable by the average OSM community member - nobody outside a small circle of people knows what "#hotosm-project-37527" is supposed to mean ;)

Dear Torgeir123, I have reverted your recent edits because they seem to have accidentally deleted some data.

Dear Nguyen Quang 12178, there are a couple of problems with your contributions to OSM:
1. Instead of putting a "." in the changeset comment field, please add a meaningful sentence that describes to other humans what you have done.
2. Also please fill out the source field - you have named schools across the country so it seems unlikely that you simply happen to know them all.
3. When adding a school please use the "amenity=school" tag, not (just) "building=school".
4. The name of the school should be JUST the name of the school. The number of stories or the word "school" do not belong in the name field. Put the number of stories in the "Levels" field which appears just below the name field in the editor.
5. If the school as an interior courtyard like this one, you have to construct a "multipolygon" object in the editor to put the hole into the building.
Thank you for your attention and happy mapping!

reverted

Hello Rdeipenau, in this changeset you have deleted 200 roads and the only comment you offered about this was "05/12/25". This is not sufficient; a deletion like that requires an explanation why these features have gone (for example "the whole area has been bulldozed to make room for a spaceport" or so). You can't just delete that amount of data without saying why. I have reverted the deletion. (DWG Ticket#2025120510000304)

PeterK2003, there is no legal basis for you to request the deletion of accurate data from our database. You might just as well request your driveway be deleted from Google imagery or from your county's GIS database. The fact that your driveway is private doesn't impact our right to record it (as a private driveway). Please stop trying to intimidate us with your cease-and-desist antics. I have reverted your latest deletions because they violate our terms of use which you accepted when signing up, and I have blocked your account to prevent you from further breaches of our terms. If you would like to know more about our mapping of private property, see osm.wiki/Why_can%27t_I_delete_this_trail%3F