All but the oldest imagery shows this as being used for RV storage. When it comes to mapping land use, "who owns it" doesn't matter as much as "what it's used for".

When you're building landuse multipolygons, please don't include city-limit lines as part of those multipolygons. It makes it very difficult to adjust things if the usage changes, or if a mistake was made.

This was still closed last Sunday when I drove by. Has that changed?

#WatchYourNodeDrags

Seriously. In addition to whatever you were doing in Africa, you moved an administrative boundary in Ireland and dragged an intersection in San Francisco to a point several blocks away.

You did a couple of what are called "node drags" here: you accidentally pulled an intersection across the map, leaving a tangle of roads behind. I've fixed them, but it's something to watch out for in the future.

The general principle of OpenStreetMap is that we map what is there, not what used to be there, what is going to be there, or what someone wishes was there. If the jetty is there but the railroad used to build it isn't, we map the jetty but not the railroad.

The main exception to this is if something has left obvious traces. For example, in one of the areas I hike, there's a strip of decaying asphalt and two bridge abutments. Since it's still obvious where a road used to run, I've mapped it as an abandoned road and a demolished bridge.

When you're adding a grid of ways (such as the parking aisles you added to the La Grande Wallmart), make sure there's an intersection (a grey dot) at each point where they cross. Computers are, as I noted, rather literal-minded, and they'll have you driving around in spirals trying to get out of the parking lot otherwise.

When you need to change the attributes of part of a road, don't draw another road over the original like you've done here. Computers are rather literal-minded, and they'll treat it as a bridge, or an embankment, or whatever, stacked on top of another road.

The correct way to do this is to split the road into two or three pieces, and then make the changes to the appropriate part:
1) Click on the road to highlight it.
2) If there isn't already a node (a white circle) in the correct place, click on a nearby white triangle and drag it to create one.
3) Right-click on the node and select "split" (the scissors icon) to split the road in two at that point.
4) Repeat if needed to get a third piece.
5) Click on the part of the road you want to change and change it.

Welcome to OpenStreetMap! I've got some questions about the changes you've made, as well as some tips for better editing.

1. Are you sure the stream you added as "Sanderson Creek" is called that? The USGS topo map has it as "Mill Creek".

2. Is thre a reason why you re-tagged a stretch of demolished railway through Post Falls from "razed" to "abandoned"? "Abandoned" should only be used when there's still evidence of the track, such as the gravel railbed.

3. There's an easy way to make square-cornered buildings: once you've drawn and tagged the building, highlight it and hit the "s" key or right-click and select "square" from the menu. This even works (usually) for 45-degree angles.

4. "Ruins" is only intended for things of historic interest. For things that have simply been demolished or fallen out of use, the "lifecycle prefix" tagging system is prefered: osm.wiki/Lifecycle_prefix

5. Have you considered editing in smaller pieces at a time? Editing in large chunks like this makes your edits show up in the history for most of Washington and Oregon, and makes it hard to ask you about just one aspect of your work at a time.

"Living street" is pretty much purely a European thing. In the US, anything that seems to match the description of a "living street" should be tagged as either a driveway or a residential road.

Please don't attach areas such as parks or landuses to roads. Sure, it makes the map look a little nicer at extreme zoom levels, but it also makes it much harder to adjust the area or the road in the future.

I've reverted this: the original version was correct. The western section of the Marina Drive link is two-way, to provide access to the parking lots to the north of the road.

A couple of tips for making better-looking building outlines:

First, it's easier to trace the actual building if you zoom in quite a ways.

And second, once you've got the basic outline done, you can square up the corners by selecting the building and hitting the "S" key.

Are you sure the location and/or address for "Good Deeds Mortgage" is correct? "State Street" looks like it's a block away.

When you say this is "for assignment", do you mean that someone gave you the task of deliberately adding false data to the map?

Did you not notice that "sensor garage door repair" is a) glued to the middle of a road, b) misplaced (the "401" addresses are about a half-block to the west), and c) probably spam?

If you're going to be correcting errors, please check for other mistakes while you're at it.

The correct way to deal with a private drive isn't to delete it, but to mark it as "private" -- which is exactly what Leif Nelson did four years ago.

In case you haven't already noticed, in Spokane County, the "Esri World Imagery" option is far sharper than Bing imagery, and nearly as new. It's good enough to let you tell adjacent buildings apart, distinguish garden sheds from parked travel trailers, or map the individual shingles on a roof.

Is there a reason why you consider Hoerner/Colton/Jay to be tertiary roads? They didn't feel very arterial-like the last time I drove through, and they're lacking most of the usual indications, such as an elevated speed limit. (Jay is also lacking lane markings.)

Could you do your updates in smaller pieces? It's hard to check for possible mistakes when a changeset is scattered across half a continent.