No problem. Better to make sure than to have to clean up a mess later.

Most of the changesets in Oregon are just deleting orphan nodes with no tags or info. I try to spend some of my editing time on clean up. Not much fun but it's easy when my brain is tired.

Jerry

I am not deleting the names. I am just following the wiki that the "name" key should not be followed by a number. This is the area where I live and I know most, if not all, of the correct names. If it's something I'm not sure about I can check the Coos County GIS map for the official name.
As for tiger data, I am well aware of the many errors in it and am correcting them as I check the area where I live. I have divided my home area in the coastal area of Coos County into about 15 bookmarked sections and am methodically eliminating errors. So this is not something I am doing "remotely."

You have applied several tags to the entire area of the parks you edited. This is contrary the wiki and should be corrected. Some of the tags themselves would not be appropriate for a park too.
For example: You applied "greenfield" to the entire area of the parks but greenfield on Wikipedia describes "land scheduled for new development where there have been no buildings before. A greenfield is scheduled to turn into a construction site."
Are the parks you edited scheduled for new housing developments? If you had reviewed the wiki pages I suggested you would know "greenfield" is not appropriate for the parks.

Please review your edits and the messages I sent you and reconsider your response that all the tags apply to the entire parks.

Thanks for your message. I am not aware of any buildings being deleted, and certainly that was not my intention. JOSM validation found many duplicate building nodes and that was what should have been deleted. If the changeset caused a problem for you please revert it.

Sorry for any problem it caused for you. Jerry

Almost all of the orphan nodes I deleted this morning in southern Portugal originated on March 3-5, 2018 so I guessed that it was a failed import or some other glitch in the system.

I'm not sure where all the orphan nodes cam from, but this was not a revert. I'm using Osmoscope to identify areas with large numbers of orphan nodes and then using JOSM validation to scan that area and fix the problems that JOSM can fix. If I am causing a problem please let me know.

Pascal, thanks for all your work with neis-one.org.

I apologize if any of my edits caused a problem for you. However, all the edits were problems identified by and fixed by JOSM validation. The only tags it changes are deprecated tags, unneeded tags and a couple of others. This is programmed into validation so the data can be improved. I did no edits manually, so the "generic text" accurately describes the upload. If you can give me an example of a change that caused a problem for you I'll be happy to take a look and see if I need to change something. Thanks, Jerry

Hi northtron, sounds like you've done your homework and that's great. Keep up the good work!
Jerry

The streetview imagery you are using is off-limits for OSM. However Bing streetview is not. Take a look at the same site with Bing Streetview and look at the date on Bing's imagery.

Check the dates of the imagery you are using. Which is newer - the satellite view or the other?