Even if you are mapping from imagery taken at oblique angles, you just need to make sure to align it to the building's footprint rather than its roof line. 👍
---

Published using OSMCha: https://osmcha.org/changesets/109033543

Yup, I added it back. Generally if one makes a mistake it's a common courtesy to other mappers to fix it.🙂

If you look at your changes, you'll see Flixbus 2683: Ithaca => New York City (10792460, v31)

It should be whatever is the most accurate, not more recognizable. 🙂
---

Published using OSMCha: https://osmcha.org/changesets/108905711

Hello.
Could you please elaborate what is this change based on?
---

Published using OSMCha: https://osmcha.org/changesets/108853786

Hello.
Why did you delete Flixbus relation?
---

Published using OSMCha: https://osmcha.org/changesets/108835028

Since I found nothing about this feature online and this user didn't respond in 4 days, I deleted that neighborhood. Perhaps their other changes should be reviewed as well.

Yup, I submitted fix and yesterday it was accepted 😁👍

Hello.
Do you have some supporting information that there's a neighborhood named Ravel there?
As far as I'm aware that area is referred to as Brooklyn Heights.
---

Published using OSMCha: https://osmcha.org/changesets/108714756

Hello.
2 right-most fields are not tennis courts but american handball.
---

Published using OSMCha: https://osmcha.org/changesets/108713328

Yup, it seems like that the template that new iD uses is not following OSM's own best practices.

Hello.
Could you please elaborate why did you rename operator from its full name to WMATA?
It is a well established practice not to abbreviate names as documented in osm.wiki/Names#Abbreviation_.28don.27t_do_it.29
---

Published using OSMCha: https://osmcha.org/changesets/108710508

Hello.
It's great that you found OSM and adding your business here. However, there are some standards that must be followed when adding data.
For example, "description" field must not contain any promotional or advertising messaging. This is explained in more details here: description=*
Additionally, business hours must follow a specifically defined syntax as documented in opening_hours=*
And overall, go easy on seo keyword stuffing. This map is watched for spam and will be corrected/deleted. 👍

San Marino embassy to Canada in NY?🤨 Is that a mistake?
---

Published using OSMCha: https://osmcha.org/changesets/108577532

Hello.
It appears that you drew a duplicate road segments. It already exists as way/276657609. As such I removed your duplicate road segment to avoid routing problems.👍
---

Published using OSMCha: https://osmcha.org/changesets/108575342

>Does it actually harm the map? No.
@snoozingnewt, but the issue at hand. Do you know for sure that every single one of these 3200 changes is correct for the situation it's in? That's why people monitor the map to spot any potential issues, intentional or not. It's very difficult to review a single changeset with 3200 changes.

> Does it inconvenience you in any way? Not with the right tools.

It does if you try to ensure that edits that go into OSM are of high quality. As an example, that archavi link posted earlier errors out with "osmDiff: runtime error: Query timed out in "query" at line 1 after 181 seconds."
Most tools are not designed to wrangle such huge changesets.

By state or last by general geographic regions. Best case I'd prefer it split up by major populated areas. Because your changeset is so huge, I can't even tell where most of your changes are...
And due to the nature of OSM, your bounding box also included a bunch of other countries which don't care seeing changes from USA.

Just because people don't comment on your changesets doesn't mean they completely approve of you making giant multi-continent bounding boxes. I too would appreciate if you limited your edits to smaller geographic regions so that each changeset could be evaluated to make sure there are no problems. Now reviewing almost 3200 changes in one commit is unreasonable.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/108548780

Hello.
Could you please elaborate what you edited here? "added features" is not really helpful in helping people understand your changes.
You can also take a look at osm.wiki/Good_changeset_comments for better explanation. 👍

Hello.
Please note that "name:az-Arab" is not a valid tag. Language names should be ISO 639-1 (alpha-2) or ISO 639-2/T (alpha-3) or ISO 639-3 (alpha-3) codes.
---

Published using OSMCha: https://osmcha.org/changesets/108506615