Got it, thanks for the additional details and sorry to hear about your property damage. I removed the tags that specify these as Flock cameras or ALPRs, so they should no longer show up as Flock devices in apps and websites that use OpenStreetMap data (though note that apps and websites sometimes take a while to pull the latest data from OpenStreetMap, so it could be a few weeks depending on what app you look at). Thanks for understanding and please reach out if you have any questions!

Thanks for the contribution. Did the footprint of the building also change during construction? If so, we should re-draw its shape in OpenStreetMap (though, if the construction was recent, there might not yet be aerial imagery available for use in OpenStreetMap that we could use to trace the footprint).

Thanks again for your contributions and welcome to OpenStreetMap!

I reviewed your changes and they look good. Thanks for contributing, and welcome to OpenStreetMap! Please feel free to reach out at any time if you have questions. I also have found the OSM-US Slack workspace a helpful space to discuss how to map things, or talk about things in the OpenStreetMap and open data space. If you want, you can join at https://slack.openstreetmap.us/

Happy mapping!

>so it is the median sidewalk that functions as the other side of both

So does that mean both oneways of Beacon Ave *are* sidewalk:both=separate because the median path?

Thanks

Oops, missed a leading zero in way/1137406320/history/6 - Fixed!

Hello,

In the future, please take the time do document the rationale behind your edits using a real changeset comment. It is not acceptable to type gibberish into the changeset comment box: other humans review your work and need to know what you're trying to do.

osm.wiki/Good_changeset_comments has lots of good pointers and is worth a read-through, or feel free to reach out with any questions and I'll do my best to help. Thanks for understanding.

Happy mapping!

That looks like an incorrect opening_hours=*. If it's closed, shouldn't the relevant features just get removed? Or is is now just access=private?

Hey, I noticed that you added footway=sidewalk tags along the foot path down the median of Beacon Ave S (way/330262659 etc.) Do you believe this should be considered a sidewalk een though it's shared between the two directions of Beacon Ave? How would you tag sidewalk presence (sidewalk:left=* etc.) on the segments of road that cross through the median, where there aren't matching sidewalks to cross between the "far-side" sidewalks on the right of each one-way road? For example, how would you tag sidewalk:left on the segment of way/6342677/history/13 that crosses between the directions on Beacon?

Oh, right, you got unit 300 put on the therapy business. Presumably the real estate is then at unit 100, but it would need a survey to confirm.

Thanks for confirming. If these have different unit numbers, you could also add those. Happy mapping!

Is the office really open on Saturday and Sunday too? or by "daily" did you mean Monday thru Friday?

Thanks. Did this business replace the real estate company that was mapped here? or do the two businesses share the building?

Looks good, thanks!

It looks like you added the name to a building several blocks away from where you put the main office point. Did you mean to edit the building that's at 7225 170th Avenue Northeast or is that a mistake?

Thanks for the contributions. Usually, buildings are made of rectangular parts, so it's good practice to "square" buildings so that near-right angles become perfect right angles. This looks better, and, more importantly, is more accurate to the footprint of the building in the real world.

Most editing programs support squaring lines and areas. In iD, the in-browser editor you used, you can select an object and press Q on your keyboard, or right-click and find the "square" option.

Do you want to try squaring the buildings you've added, or should I take care of it?

Thanks again for your contributions, and welcome to OpenStreetMap! Feel free to reach out anytime with questions.

Hello, and thanks for the contribution. Did you really mean that these lanes are marked with a through (a.k.a. straight) arrow? If there are no pavement markings, it can be left empty (as it was mapped) or written out as "none", like turn:lanes:backward=left|none|none. See turn=*#Values for more information.

In King County 2025 aerial imagery, I don't see markings on the road that say you can only go straight in lanes 2 and 3 (the rightmost lanes). Is there really a turning restriction from southbound 116th to westbound 128th? If you can't turn right, there are also other steps we should take to indicate a no-right-turn restriction.

Thanks again for your contributions and welcome to OpenStreetMap! Please let me know if you have questions about my feedback.

As you map out sidewalks, you can/should also add sidewalk presence tags in the form of sidewalk:left=*, sidewalk:right=*, and sidewalk:both=*. For example, the long segment of 134th Pl should be sidewalk:both=separate, and the circle at the end should be sidewalk:left=no + sidewalk:right=separate

I think you're missing barrier=kerb nodes at the edns of the crossing. Check out osm.wiki/Foundation/Local_Chapters/United_States/Pedestrian_Working_Group/Guide for some examples of best practices for pedestrian infrastructure in the US.

If you're mapping out lots of sidewalks and crossings, I reccomend looking at JOSM's Sidewalks plugin. See https://community.openstreetmap.org/t/josm-sidewalk-plugin-tutorial/134088 for more info. I recommend aligning roads (e.g. by using the Improve Way Accuracy tool, https://josm.openstreetmap.de/wiki/Help/Action/ImproveWayAccuracy) before adding pedestrian infrastructure, though, because it's a lot easier to neatly clean up roads before there are lots of extra crossing nodes.

See changeset/187314921#c1643719. Thanks!

See changeset/187314921#c1643719. Thanks!