What I entered for the changeset comment was “Add detail to business” but it changed to this when I tapped Commit. 🤷

It also missed the reconnection of crossing nodes 6902505427 and 9938424611.

This change applied sidewalk=left to the missing section, but it previously (way/1064471021) had sidewalk=right.

Looks like this inadvertently deleted way/1064471021. It was recreated in changeset/152628981.

Yeah I thought JOSM handled these as well and testing now it appears to, so it’s not clear to me how the break happened. In general this can happen if JOSM hasn’t downloaded the relation and so doesn’t know to update it, though that should be an unusual situation. I’ve encountered it when sparse editing or occasionally due to bugs in the continuous download plugin.

FYI this broke a turn restriction on NE 100th St; after splitting the street the relation needed to be updated to reference the new segment.

relation/7702579

I just noticed it in Osmose and made the update.

Ah that’s reasonable, thanks for the explanation.

I did get as far as acquiring a slightly more precise GPS device but got lost going down the rabbit hole of identifying survey markers and interpreting government control point datasets.

Thanks for working on this!

For this kind of change I think it’s important to document which imagery you used as a reference since the various options aren’t all in agreement. You can do this with the source and/or imagery_used tags on the changeset.

Much of Seattle’s building alignment issues appear to have originated with the 2013 import and it would be nice to come to a broader consensus on what to do about it.

In this case it looks like you aligned to the current Bing aerial imagery. If you haven’t yet, do also consider King County orthoimagery which seems to be of high quality but differs in alignment from Bing. I’ve been meaning to do a more thorough comparison but haven’t personally gotten to it yet.

Thank you!

Misclick due to lagging phone UI inadvertently reused previous changeset comment.

See changeset/110697397 and more recently Bing aerial imagery. Your first clue should be the construction site already on the map here.

The buildings you added to Viewlands Elementary do not exist.

I think this might be on the wrong building. This building looks like it’s in the same lot as 417 N 87th St.

Hi, and welcome to OSM! It’s not clear to me what change you were trying to make to 9824 Lake City Way NE. In this changeset the way has been converted from a building with a liquor store into empty retail land, but still has the detailed shape of the building and contact information of the liquor store:

https://osmlab.github.io/osm-deep-history/#/way/221293960

Is the building actually gone? Or did you mean to tag the surrounding land (osm.wiki/Land_use) as retail?
---

Published using OSMCha: https://osmcha.org/changesets/133537543

Oh yep, thanks, also reverted now. And that one contains the real Corliss Ave so probably the beginning of the problem.

Yikes, I must have accidentally copied and pasted the tags somehow. I think I’ve reverted it now. Thank you!

Ah, I didn’t download the relations so JOSM never knew I was breaking them. I’ll see about repairing the splits…

Hmm, thanks. I used JOSM’s split way function which I thought preserved relations, but perhaps I’m misinformed about that.

Is the outdoor seating area at Jellyfish Brewing gone?

Several of these were wildly misplaced and already existed in the correct location. I’ve deleted them.
---

Published using OSMCha: https://osmcha.org/changesets/103204536