OpenStreetMap logo OpenStreetMap

Changeset When Comment
163093492

Hi! I see that you requested a review on this changeset.

I took a look and followed up in Changeset: 163141372 with a few very minor changes - just dropped the "addr:county" and "source:addr" tags and made some slight geometry updates.

No real issues with your changeset - thank you for your contribution!

162167758

Hi - in the future, please do not add "*=unknown" tags - just leave those blank. Happy mapping!

162123579

I appreciate the initiative to find instances of `building=yes` that can likely be updated based on their POI type, but please individually review these changes using aerial or street-level imagery to make sure that they are correct.

As @Sakari_N correctly points out, it is not always the case that a POI is at a building which was originally constructed in the design of that POI type.

Please also keep changesets localized (rather than scattered around the world)! This makes things easier for others to understand and review your changes.

I suggest also using a different editor (such as iD or Rapid) for these types of changes, as to not unintentionally mislead others when SCEE automatically adds the `source=survey` tag to your changesets.

161553957

Hi, and welcome to OpenStreetMap!

I see that you requested a review of this changeset - looks good for the most part, though I'll note that OSM is generally not the place for advertise-y business descriptions.

I've removed that description and made a few other minor tag edits in changeset/161584165 - Thanks for your contribution, and happy mapping!

160988376

That has been made abundantly clear in these discussions. Undoing - especially by simplifying - the work that has been put in by other mappers is disrespectful. As others have said, you are of course free to (and welcome to!) map unmapped things in your preferred level of detail, leaving them up for others to iteratively refine, but please do not downgrade the detail added by others.

159223767

Don't worry - essentially everyone (myself definitely included!) makes some minor mistakes as they learn to map.

There's two approaches you could take to find the waste baskets you previously mapped as nodes on sidewalks:

By Overpass: Overpass Turbo (or Ultra) is a very powerful tool and a query like this should help:

https://overpass-turbo.eu/s/1V1z
Click "Run" at the top left and wait (it will take a bit!)
I did my best to annotate and explain what each line does. (I'm not a software dev)

By changesets: OSMCha is a great resource and a query like this may help you find those earlier changesets:

https://osmcha.org/filters?aoi=914b9552-813c-4360-baa2-5a6a8c211759

Do let me know if you need any further help or have any additional questions. :)

159794614

Changeset comment correction: Horseshoe Lake, not Hatchet Lake

159677775

Thanks for your contribution!
Local knowledge is a valid source, so feel free to add "name=Maple Park".
Happy mapping!

159261138

Corrected changeset comment:
[Fix: bin QA] "bin=n" → "bin=no"

159223767

Hi, and welcome to OpenStreetMap! Thank you for your recent additions - trash cans are great to have mapped!

Do note that the "amenity=waste_basket" node shouldn't be made a part of a way such as a sidewalk (unless it's serving as an obstacle) - the node should be placed at the location of the bin. I've touched up this one in Changeset: 159226900 already, so no need to do anything more!

Let me know if you have any questions. Happy mapping!

159185554

Correct changeset comment is "Update building geometry and tags; add benches".

159113904

Hi! I see that you requested a review of this changeset - I've verified using the King County iMap that the address point you deleted is indeed no longer associated with this location, so everything looks good!

Thanks for your contribution, and happy mapping!

158953471

"crossing:markings=*" + "crossing:signals=*" allows for all combinations of these features (and their details, such as "crossing:markings:colour=*") to be tagged, based entirely on observable on-the-ground information, under one coherent schema. "crossing=*" does not.

Adding "crossing=*" in line with the documentation on the Wiki is fine, though I'd expect those tags to eventually be removed in the future. Removing "crossing:signals=*" is not. "footway=*" is irrelevant here.

158953471

I'll also voice my strong support for "crossing:markings=*" and "crossing:signals=*" as useful and well-documented tags (and my distaste for "crossing=*", which has 912 different values currently!)

158762881

Hi, and welcome to OpenStreetMap!

It's great to see businesses adding their locations!

Unfortunately, there's a couple of minor formatting errors in your edits I wanted to make you aware of!

Street names in addresses should be fully expanded - for example, "addr:street=146th PL SE" should be "addr:street=146th Place Southeast".

Additionally, Suite/Unit numbers go in a separate key; for example, in your Changeset: 158762694, "addr:street=17th Avenue Northwest Suite 1842" should be "addr:street=17th Avenue Northwest" + "addr:unit=1842".

And you may consider adding tags describing the business in order to make it easier to find; for example, "craft=cleaning".

TagFinder (https://tagfinder.osm.ch/) and the OSM Wiki (osm.wiki/Main_Page) are good resources, and feel free to reply here or send me a message if you have any further questions!

Again, thanks for taking the initiative to add your businesses to OpenStreetMap - your contributions are appreciated! Happy mapping!

158710536

Welcome to OSM, and thanks for your contribution!

Happy mapping! :)

158702617

Thanks for your contribution, and I'm impressed by the specific SMC citation! Happy mapping :)

158513015

Hi! While I'm aware of that practice as it applies to street names (and I've unabbreviated plenty myself!) I didn't think it would apply to the name of a school, if that's its official name 🤔 But I do see articles referring to it as "Saint Agatha" so I've fixed it in changeset/158563283 🙂

158543604

Hi, two small errors were introduced by this changeset: conflicting information was added (crossing=unmarked + crossing:markings=zebra:paired) to the crossing nodes on the south and west of this intersection.

I've since mapped this intersection in greater detail and fixed this error: changeset/158554867

Otherwise, I've reviewed most of your other recent changes in the Seattle area and everything is looking good :)

Thanks for your contributions! Happy mapping!

156067166

Hi - the Community Transit route updates don't happen until 2024-09-14, right? The existing routes should not be deleted until then.

https://www.communitytransit.org/buses/service-changes