Thanks for cleaning this up.

I walked by here and I'm trying to figure out the nest way to map this. There is a barge close to the riverbank that stays permanently in place and supports the footbridge and may provide ancillary storage for the museum. Then there's the riverboat, which contains the museum. This is a working riverboat that takes 3-4 cruises per year. The rest of the time, it's either parked here or sometimes taken to dry dock for maintenance. Most tourist type maps of Portland show this museum and I think it makes sense to keep it in OSM.

I'm thinking maybe to remove the museum tag from the barge close to the riverbank since this is not really where the museum is and maybe adding a description to the riverboat noting that it is moored here for the vast majority of the time.

What exactly were you fixing with this roundabout?

Bus route 39 traverses portions of this roundabout and after this edit, the route relation for bus 39 from Hillsdale to Lewis & Clark College is no longer contiguous.

If you are doing extensive editing which involves splitting Ways, consider using JOSM instead of iD as if provides more complete support for Relations and will warn you when you introduce errors such as this into the data.

What's the intention of adding sidewalk_1=both where sidewalk=both already exists, such as: way/402292726 ?

I'm not sure what sidewalk_1 would actually be used for.

I'm not sure what's going on here, but there's a Node in the parking aisle that somehow connects from the Fred Meyer parking lot to NE Glisan St.

Very interesting. I see some of the Yelp reviews with pictures of both shops. Having a separate Node for Starbucks internal to the CLSB seems to make sense. The Starbucks website only lists one entity. Does that mean that both Starbucks have the same address, phone number, reference number, and opening hours? If you do a mobile phone order, which one do you pick it up at?
I may have to embark on a caffeine-fueled expedition to get to the bottom of this.

Thanks for clarifying. I didn't poke around extensively by the rec center. I did see a sign for http://www.oak-hills.net/ posted prominently. I've left the access=private tags on these trails and closed note/446787

I walked around here and there aren't any signs indicating that these trails are private. They appear to be part of a public park. How do you know they are private?

Why did you add a node for Starbucks here?
node/3742183360
This seems like a duplicate of
way/330994261

Thanks for fixing this

26 of these name tags with "Portland" in other languages are just "Portland". Seems redundant?

I'm thinking we don't want to trace the outline of a boat as a building in OSM. Especially not a boat that still travels along the river and is not permanently at this location. I'd say put it in OSM if it was permanently parked here, but that's not the case.

http://www.oregonmaritimemuseum.org/

Yes, thank you for preserving the tags for each of the stores.

By converting Areas into Nodes you lose information about the size of each store. The way I modeled it, you could see that the Wells Fargo bank takes up more space than the other stores in the building. In this particular example, the difference in sizes of the stores is not that pronounced, but in other strip malls you often have "big box" stores that are considerably bigger than say a hair salon adjacent to them.

You get into philosophical territory pretty quickly when trying to figure out exactly where one building starts and another starts, especially in urban areas where everything is build right next, or on top of, each other.

By making a separate Area for each store, you can also see more clearly if there are any vacant stores. Suppose that 2 of the 4 stores were vacant and then we just have 2 Nodes inside the building Area. In that case, it's not obvious that there are 2 empty stores.

That being said, OSM does not deal well with objects directly on top of other objects. In some shopping malls, you can literally have stores on top of stores. I that case, splitting up the building into an Area for each store would result in having Areas on top of each other and would make it a pain to edit and most renderers wouldn't know how to display that.

In any case, we should continue this discussion, either here or on some other medium so that we don't end up undoing each other's work.

I had previously split the building at 1972 West Burnside Street into 4 separate buildings, one for each store. You combined the buildings into one object and then placed data for the stores as Nodes inside the building. It seems like the way you have it captures less information than I had.

I went through and cleaned a bunch of the JOSM warnings and made various improvements to the data based on what I remember from this area.

Andy Allen confirmed that there was a bug in the rendering of the transport layer. It looks to have been recently fixed based on the updated rendering of local bus routes.

I split out the Portland-area public transport routes into it's own wiki page:
osm.wiki/Portland,_Oregon/Transit_Route_Relations
I added placeholder for various bus routes for surrounding transit agencies.

Please stop using highway=living_street for these minor roads. Please replace highway=living_street with highway=service and service=driveway.

I've mentioned this before and you did not respond and continue to prolifically make these changes. Why do you keep doing this?

What are you trying to represent with the highway=track inside of a parking lot?

It was me that was confused about the mailbox location. There is a mailbox here.

I just walked by here and can't see a mailbox here. If I can't figure out where the node was meant to be placed, I'll delete it. As far as tagging in general goes though, I prefer to omit the name tag on mailboxes, but use the operator tag with a value of "United States Postal Service"