Hi, and welcome to OpenStreetMap!

Thanks for contributing the information that this shop is closed!

However, because there were also other tags on this node unrelated to the shop, like the address information, it's preferable to just remove the tags that no longer apply and not delete the node entirely.

I've "undeleted" it and updated its tags (Changeset: 150368720) so there's nothing you need to correct here - just keep the principle of "Keep the History" in mind in future edits!

Happy mapping!

Hi! Welcome to OpenStreetMap :D

Thanks for your contribution!

Welcome to OpenStreetMap! Thanks for your contribution - looking forward to see more in the future!

That solves it, then - I think I had used an Overpass filter to download a layer with only way["highway"] so it hadn't downloaded that relation. There's an option "File->Download Parent Ways/Relations" so I'll be sure to use that when making similar edits in the future. Thanks!

Hi! Thanks for catching and fixing my mistake!

So that I better understand how to avoid this error in the future, is it correct that I should have just kept the history on the left side of the split?

I'm used to JOSM just handling relation modification in the background during splits: for example, if a way is part of a route relation, JOSM automatically adds the newly-created way into that relation in the correct spot when the way is split, but I guess that doesn't apply to turn restrictions.

I'll keep an eye out for similar situations in the future. Thanks again!

Hi - thanks for catching this and fixing it! I'm not entirely sure how that tag ended up being created, but I definitely didn't intend for it to be there. Much appreciated!

Hi - thanks for your contribution!

OneBusAway no longer returns results for stops 25930 and 25060, so deleting these "highway=bus_stop" nodes is a good change.

Note that OSM also includes "public_transport=stop_position" nodes on the way which the bus travels (in this case, 35th Ave NE) as part of how bus stops are mapped - so I've gone ahead and deleted those nodes as well. (Changeset: 149634946)

I've recently been working on updating some of the transit infrastructure mapping in this area, and changes like yours make that process a lot less of a headache. Thank you, and happy mapping!

Hi! It looks like this is a good change, because the grass at this park is gone and it is now a construction area.

However, I've noticed that almost all of your changeset comments are just "aerial, knowledge, ,survey --". In the future, it would be very helpful and much appreciated to leave more descriptive changeset comments - for example, "Updated park to remove grass which is no longer present due to ongoing construction" or something similar!

Thanks for the feedback - I'll definitely include which imagery was used in future similar changesets' tags!

I was using the King County Orthoimagery as my "authoritative" alignment for a bit (and still use it very often, especially because the 2021 imagery was taken when many trees hadn't grown back their leaves) but received a message from another prolific Seattle-area mapper saying that it's better to use Bing as a reference and that is the local convention, so I've been following that since then.

In JOSM, I set the offset for the 2021 King King County Orthoimagery to "-1.7915,0.8959"

I also wanted to try recording some GPX tracks over time and figuring out a "perfect" alignment (but the hills make that impossible) however I only have my phone's GPS, which I can't really rely on for perfect accuracy.

Thank you for catching and fixing my spelling mistake! Much appreciated!

Hi! I had set "contact:text" because I didn't see anything better on the Key:contact:* OSM Wiki page (and contact:sms is not listed there) but OSM taginfo shows over 100 existing uses of contact:sms=* and none of contact:text=* so I agree that this is a good change.

Thanks so much for the fix! Much appreciated.

Hi! I just wanted to say that I appreciate the attention to detail of "keeping the history" on the original address nodes by preserving them as a node in the geometry of the new way that the tags are moved to. Great work on all of the new construction in the area!

Hey - thanks for catching and fixing my spelling error! Much appreciated!

The rainbow sign actually says "Maple Leaf Community Gardens" on the first row and "P-Patch" on the second. I took a bunch of photos of the area which I will upload to Mapillary soon and use to make a second pass at further micromapping the location.

I'm pretty sure the rainbow sign does say "Maple Leaf Community Park" and that's why I made the change, but I'll go double-check!

Hi! When I made this edit, I was walking by at night along 2nd Ave NE and could only see the surface (rooftop) parking area. From my desktop perspective, I can indeed see the lower (underground) entrances on the west side - so thank you very much for catching and fixing my mistake! Much appreciated!

Hi! I used the "survey_date" tag because I wanted to be more specific and indicate that I did indeed survey in person these opening hours at that date.

However, it's clear that "check_date" is the de-facto standard in OSM for indicating when something was last verified as up-to-date, and the detail that the source of the check date is a survey is also already indicated in my changeset tags.

So, thank you for making this correction! I have converted the rest of my "survey_date" tags to "check_date" (see Changeset: 149030812) and verified this changeset and your other earlier one (Changeset: 149012913) as good on OSMCha because I agree that this is a good change. Much appreciated!

I have reverted the parts of this changeset (see Changeset: 148988574) related to the residential landuse area edit (Way: 1221616810 and Way: 712371245) which mistakenly kept the wrong history, and re-added the intended fix (see Changeset: 148988646).

Thanks for catching and fixing my mistake! Much appreciated!

Accidentally uploaded without comment: "Added payment:cash=no to reflect posted signage"