Thanks.

Sorry about that.

It looked like you were doing this remotely because the changeset boundaries enclose the entire state of Oregon -- exactly the sort of thing I'd expect from a state-by-state armchair cleanup.

Please don't do this. Many of these "name_1"s are the result of bad TIGER data, and have no basis in reality. For others, the "name=" tag is incorrect, and it's the "name_1" tag that has the correct name. It's not something you can fix remotely.

Are you sure the buildings you added to Sammamis Village are correct? I think you might have been working off of outdated imagery, deleting new buildings and replacing them with old ones.

An orphaned node isn't always a "delete this" situation. In this case, it was a mis-formatted address node (information in the name= tag rather than the addr:*= tags). I've restored and fixed it.

Where did you get the name "Riverside" from?

Is there a reason why you deleted the Whispering Hills apartment complex? "Updated street information" doesn't explain much.

"Living street" is pretty much a purely European concept. If you find yourself looking at something in the US that you think might be a living street, it's probably something like a low-speed residential road or a shared driveway.

If you check the Bing Streetside imagery for this area, you'll see that the parking aisle you deleted because it intersected the Mountain Valley Inn does, in fact, exist, and it passes through the building just as the tags on it indicated.

When you fixed the outline of the Tamarack Brewing building, you also deleted a "Tamarack Brewing" restaurant node, leaving Tamarack Brewing as simply a "building=yes". Was this intentional?

If you're going to do a MapRoulette task, please actually *do* the task. Leaving a non-existent road around but marking it as "I've reviewed this road" doesn't count.

Is there a reason why you removed the speed limits from the westbound side of I-84 here?

A quick spot-check shows that many of the "Wendy's" you've touched in this edit aren't the fast-food chain -- they include a demolished building, a bus stop, two driveways, and a non-chain restaurant.

Is there a reason why you moved the Dairy Queen across the map here? There's a very fast-food-looking building at the original location, while the new location looks like a bank's parking lot.

There appears to be a bug in JOSM. The changeset comment for this should be "Extend driveway to road".

There appears to be a bug in JOSM. The changeset comment for this should be "Merge duplicate POIs and improve outline".

If you're going to be editing in the Spokane area, I recommend using Esri World Imagery rather than DigitalGlobe Premium. It's slightly newer and better aligned.

It's not always a mistake to map the stores of a strip mall as a collection of buildings.

As a general rule, if the parts are structurally independent (you can take one out and the others won't fall down), they can be mapped as separate buildings. This sort of situation is very common in small towns and the older parts of cities.

That said, I don't know if that's the case here or not. It's hard to judge from aerial imagery, and much easier if you're looking at the buildings on the ground.

Is "Columbia Basin Oral and Maxilofacial" better described as a physician, or a dentist?

In the western United States, it's common to raise the "place=" level of an urban area above what the population alone would call for if it's of regional importance.

St. George, for example, is the largest city for a hundred miles in any direction (200 miles in any direction that isn't towards Las Vegas). It's got all the things you'd expect from a city: a university, a regional hospital, a regional airport, cultural facilities such as museums and theaters, and so on.