Hello Dartmouthmapmaker,

yet again you have imported data into OSM without following established procedure, and your imports had to be reverted. The procedure is there for a reason - it helps avoid mistakes like osm.org/node/8570284935/history where your botched process led to having four versions of the node in the database instead of just one.

I have also noticed that you make extensive use of OpenData to add boundaries and in doing so, you are occasionally leaving behind bits and pieces of boundary ways that have unnecessary tags.

The “land_area” tag that you are adamant to use does not really make any sense.

I have also noticed that you are prone to using “boundary=historic_lot” which does not seem to have any documented meaning. I commented on that here osm.org/changeset/100004094 - I am not reverting this because I lack local knowledge but be advised that information that is not verifiable on the ground needs a very good reason to be in OSM. This is usually assumed to be the case for current administrative boundaries, but other sorts of boundaries should only be added with explicit community consent.

Please refrain from doing any undiscussed imports in the future as otherwise we would block your account for longer.

Best regards
Frederik Ramm
OSMF Data Working Group
Ticket#2021032910000141