Sorry for the delay, I got a little busy!

In terms of bike route relations, the standard is if it's part of a larger system of bike routes like neighborhood greenways/bike boulevards in Portland and Seattle for instance. Multi-use paths/trails are good candidates for relations as well.

If it's just sharrows or bike distance signage, simply bicycle=designated on the way will do, as that's a perfect indicator of a bike route as well.

I have no idea if it's an official bike route but there are sharrows on the west end by the railroad tracks. That's all I know.

There is a "WA 14 Business Loop" designation in Washougal at least. https://www.bing.com/maps?toWww=1&redig=AF0702F13E544318A5E8591F8E6FB5E9&cp=45.570332%7E-122.294749&lvl=16.6&pi=-1.4&style=x&dir=345.9

S 45th Ave in Ridgefield is still tangled up btw

Hi everyone,

Jeffrey is correct on interpreting the meaning of mini-roundabout. Since these islands can't be traversed by vehicles (in other words, going straight through a painted island) and instead are physical islands, mini-roundabout is not appropriate. I suggest restoring the circular ways and tagging them with junction=circular (junction=circular) instead, so it can be shown as a circular junction without calling it a roundabout. (solution stolen from (changeset/102013909), I'm not the only one here). Hope this helps.

It's permanently closed.
https://www.reddit.com/r/Portland/comments/cqe4na/sb_naito_to_eb_steel_bridge_ramp_permanently/
https://www.oregonlive.com/commuting/2019/08/bus-only-lane-coming-to-northwest-everett-street-on-approach-to-steel-bridge.html

If you're still working on it, that's fine, but ideally you should get it done soon. When you're done I have a tool that can revert this set of edits with one go so you shouldn't have to worry about it. Let me know on here when you're done.

Do you still need the building tags on the sports pitches? It isn't appropriate for them to have building tags if they're not buildings.

Please be careful when merging streets, you've broken a relation with this edit (relation/8274000). The ways that were split were used to represent a boundary. Since it's broken now the merged streets go all over the place.

Hey thanks for stopping by in Vancouver. My concern with the Clark County speed limit dataset is some portions of it aren't accurate, specifically with 20 mph speed limits when they're actually 25. I believe an earlier import of this data resulted in a similar situation, and I've been fixing this and related speed errors for some time now. I see 25 mph signs around Vancouver much of the time with 20 mph signs a rarity (I've noticed only 2 streets in downtown have them).

This specific changeset, the streets have posted 25 mph speed limits, but you've added them as 20 mph. This is what I'm concerned, the dataset doesn't match up with on-the-ground reality, and OSM aims to reflect what's on the ground. Given that you work for TriMet, I don't know what they'll have to say about this, but as a local volunteer mapper, I'm giving you a heads-up and a warning about potential conflicts.

*adjust

Just letting you know that the 7-11 gas station you mapped is actually a truck in the Maxar imagery and there's no such gas station at the site, so I removed it.

Do you have proof the ramps are signed with the speed limit values you specified? Last time I checked there were no speed limit signs on those ramps.

We already have a Bonneville Dam Historic District relation: way/553340971

The NRHP info you're adding is already available on OSM in this relation: relation/8366500. The relation you edited is the neighborhood, not the historic district (which do not have the same boundaries).

*non-existent slip lanes

Do you have any proof that the road in question is named "Pastarru Road"?

Hi, the Columbia River Crossing refers to the proposed replacement for the currently existing Interstate Bridge. This is the wrong name to use. I reverted this changeset on local knowledge grounds.

This is the second time someone from Telenav removed new roads that exist on the ground but not in aerial imagery. First time was at changeset/59174974. Please add back the roads and ensure that Telenav won't remove these roads again.

I noticed SE Washington between SW Dennis and S 1st is still tagged as highway=service. I think that section might be worthy as residential too, but can you check the RLIS classifications to confirm my suspicion?