I do carefully check that imported buildings match overhead imagery, but height is a little bit harder to verify. I've removed the tag.

This change includes a number of duplicate addresses (including unit number, and without feature tags). Is there a way to clean that up or should they be left?

Reverted in changeset/104467927

Reverted in changeset/104467927

Reverted with changeset/104466858

Reverted with changeset/104466858

The bounding box was accurate before you changed it. Reverted in changeset/104150179.

Reverted in changeset/104150041 to restore alignment

Reverted in changeset/104149835

Please don't move buildings in this area to align to imagery. We have imported the building outlines from an authoritative source. The imagery is incorrect.

Here is the new area you made that encompasses the hotel's land area: way/935737076 You can see that since it is not a building, I removed the "building" tag from it. Buildings within the larger hotel area should keep the "building" tag.

This removes the name and contact information of an adjacent, unrelated hotel. Reverted in changeset/103714183

When drawing an area around a hotel campus, be sure to remove the "building" tag from the boundary, since the buildings are mapped separately. Fixed in changeset/103714039

When drawing an area around the campus of a hotel, be sure to delete the "building" tag. Also be careful not to connect it to unrelated things, like a post box or another building. Fixed in changeset/103713945

When using an area around the campus of a hotel, remove the "building" tag from the new area. Fixed in changeset/103713756

There's still a lot more work to be done. I mentioned in e.g. changeset/103265417 that I went through just a few Zartico edits, but there are so many that I've since given up.

Before I had fixed it, "addr:street" was "Odin Rd", with an abbreviation. The nearby road is named "Odin Road," with no abbreviation. "addr:street" should therefore be "Odin Road" without abbreviation.

No, I am suggesting the same thing. "One feature, one OSM element" means that there should not be both a building and a node tagged with "tourism=hotel", which is exactly my complaint. The methodology that Lyx suggests is what the iD editor does automatically when you use the "merge" command as I had suggested. Perhaps you are misunderstanding their instructions: "move the existing node to one corner of the building" does not mean to just position the node near the corner, but to use the node as a corner as a part of the new way. Again, you don't have to worry about this since iD does that automatically when you use the "merge" function.

This is not a bicycle path, it is a bike lane, which is already mapped with the "cycleway=lane" tag on the main roadway.

Sorry, to clarify: Instead of copying information from a node to an area, use the "merge" feature to automatically move the information without leaving a node behind. Also, I've gone through some of your mistakes and fixed them, but I don't have time to do it all myself. Please tell your team that they should be fixing previous mistakes as well as responding to feedback for future changes.