The "name" field should only be used for actual names, not descriptions. For example, it's obvious that a walkway is a walkway because it's tagged as "highway=footway".

What are you trying to do that involves drawing large, untagged outlines?

Please don't abbreviate names. It's easy for a computer to decide it needs to shorten "Lane" to "Ln" if it needs space; it's much harder to decide if "St" should be expanded to "Street" or "Saint".

Looks to me like you got everything.

For situations like this, where you want to simply revert everything, the best tool is probably JOSM (https://josm.openstreetmap.de/). You'll need to activate the "Reverter" plugin, which will give you a "Revert changeset" menu option in the "Data" menu. Enter the number of the changeset you want to revert, make sure it's doing what you expected, and upload the resulting changes.

The "name" field should only be used for names, not for descriptions. Something like when a building was completed would go in the "start_date" field.

What are you testing, and since it pretty clearly didn't work, are you planning on reverting it?

What TIGER data have you deemed unnecessary here?

Additional imagery used: DigitalGlobe Standard and NAIP Washington 2015.

This isn't a park, it's a couple houses.

It looks like you're taking out far more nodes than you intend. For example, way/409571420 went from 72 nodes relatively evenly spaced over three miles, to just eight nodes, with a maximum gap between nodes of 2.25 miles.

On straight segments of ways, it's generally considered good practice to leave nodes at periodic intervals. Because of the way the OSM API works, if you download a region containing a way, but that way has no nodes in the area, the way isn't visible.

The Cabella's in Post Falls is already mapped (it's that big building to the southwest), so please stop adding it.

That doesn't look very park-like to me. It looks like somebody's house.

Looks good in both JOSM and the website map.

It's not clear what happened, but it looks like this edit may have broken the banks of the Spokane River.

Why did you delete a section of the Little Pend Oreille NWR boundary? According to the official map (https://www.fws.gov/refuge/Little_Pend_Oreille/map.html), that's an inholding in the refuge, presumably consisting of privately-owned land.

Navigation systems use the "name" and/or "ref" fields of roads when giving directions. Giving something a name that doesn't reflect the signs on the ground causes those systems to give bad directions.

Yes, the shortest route from eastbound WA-24 to westbound WA-26 is via Columbia Street, but that doesn't make Columbia Street part of WA-24. Calling that just serves to confuse people.

I drove this a few weeks ago. There are no markings to indicate that Columbia Street or Wahluke Street are part of WA-24, or that WA-24 starts north of the WA-26 underpass. There is, however, a very nice "End WA-24" sign just *south* of the underpass.

(It was somewhat disconcerting to have my GPS tell me to take a left turn on to a narrow, unlit road it called "WA-24".)

Or at the very least, use more dots. It's tricky to click on a changeset link that small.