Thank you, I appreciate the quick update!

Hi there, it seems you've added some bicycle restrictions on ways that also have cycleway tags. These seem to contradict each other, would you be able to clarify one way or the other?

Congrats on your first changeset! Since you requested a review I have taken a look and the content looks accurate, nice job. The only thing I'll mention is that it is useful to include the "source" field on changesets so others can know how you determined the edit was warranted.

Forgot to add source before submitting changeset: local knowledge

I had read that previously and just re-read it, I don't think the blurb on the Wiki is very definitive one way or the other. I agree the speed limits aren't as low as they could be, but seeing as these streets allow pedestrians to walk throughout the right of way and motor vehicles must yield to them, this is effectively achieving the same goal. My experience living a block from a Healthy Street is that there is much less traffic on them and more pedestrians and cyclists.

Hello, I think many of the streets you've reclassified from living_street to residential are in fact "living streets," as they are closed to through motor vehicle traffic and motor vehicles must yield to pedestrians and bicycles.

https://www.seattle.gov/transportation/projects-and-programs/programs/stay-healthy-streets

May want to reroute the Interurban Trail relation to use this ramp rather than the crosswalks, not sure what the more accepted route is.

Hi there, when the features I'm mapping appear in both Bing and King County imagery I tend to swap between them while I'm aligning things. Typically whichever one the existing objects in an area better align with I'll use for reference. As for a particular offset value, rather than use a set value I find that I have to shift the imagery bit by bit to match existing object alignments as I move further in one direction. Hope that helps, happy to discuss further if you like!

Hi, "lut" is the ISO 639-3 code for Lushootseed.

Great thanks, updated in changeset/135708158

Hi there, I think it would be more consistent with how other honorary street names are tagged to do this:
name=Alaskan Way
name:en=Alaskan Way
alt_name=Dzidzilalich
alt_name:lut=Dzidzilalich

Does this change seem okay? I think it's worthwhile because Dzidzilalich is not a translation of Alaskan or Elliott Ways but rather has a separate meaning (unlike the streets in the CID which are have signposted translations).

Hi there, what's your source for this closure? I just checked the Seattle DOT's traffic camera at Alaskan Way and Wall Street and it appears to be open to traffic.

No worries, mistakes happen! I'll plan on undeleting it, just wanted to double check if there was a reason for it so I didn't trample anything. Thanks!

Hi there, did you intentionally delete part of Olive Way (between 9th Ave and Boren Ave)?

Will do, thanks for the feedback!

I've seen a mix of city documentation for how the name of this park is typeset, but I think written Lushootseed doesn't typically include the spaces between letters seen here. Thoughts on changing the "name" tag to "ƛ̕ax̌ʷadis" (and would recommend adding it as "name:lut" too)?

Didn't manage to get over there until today, but you were correct. It appeared not to be a bus-only road so I removed the "access=no" in changeset/121448111

Ah, I must have missed that signage, thanks! I thought I recalled seeing a "Do not enter except buses" sign but I'll go double check this weekend.

Forgot to include changeset source:
Aerial imagery, street-level imagery (personal), Local knowledge

And for your 2nd comment: I do find JOSM easier for working with larger relations, but I think this is fine as-is right now. As far as I am aware there's no way to transfer the history of a relation object to a way object. If you want to you could cut and paste the tags from the relation to the way to clean it up but I don't think that's all that necessary!