related: https://www.clearwaterconservancy.org/article/2019/09/19/clearwater-conservancy-awarded-grant-to-conserve-windy-hill-farm

that was fast! was going to add these and you beat me to it -- well done

This is awesome, adding the trails to the skills park had been on my list and glad you beat me to it! Kudos

I've made a few additional edits, creating what I believe to be the most elegant solution -- let me know if agree with mapping as per osm.org/changeset/146601870

I might be looking at stale imagery though, if that's the case please let me know!

I think turn lane taggings should be added and the dual carriageway should not start so far south because the divided part of the road (physical concrete barrier) is farther north than mapping at present indicates

on way #1061223434 -- I'm not seeing an unpaved service road anywhere in aerial imagery going through a yard. it appears this was created using outdated USGS imagery. While useful for historical context, I suggest checking fresher imagery before adding data from it to the map

I've moved addr tags to the school building in changeset 144488966. Thanks for calling this to my attention and the helpful dialogue!

well put and thank you

helpful callout, will remove fixme. thank you

Generally my belief is that adding granularity adds value to the map, and to that end -- mondo is definitely a different surface (feels different underfoot) than Tartan, as previously mapped. Also at least per wikipedia, Tartan is trademarked too. https://en.wikipedia.org/wiki/Tartan_track

Gotcha, thanks for the reply! I think access=permissive is a more precise tag in such instances (osm.wiki/Key:access). To the point of Community Field thank you for edits to improve the schoolyard perimeter. One thought there and potentially more broadly is to map what's "on the ground" in the most accurate way possible without worrying about how it renders on the default map (osm.wiki/Tagging_for_the_renderer). Since the public recreation area that is Community Field indeed exists on school property, I think two overlapping areas are justified.

thanks!

Helpful context; I've updated the tag removing is_in=*"

Oh dang this is great, thanks for the tip!

could you explain why this was added? There is no water here

awesome thanks for the reply here! I went and retagged using your convention. I've opted to tag pitch:net:material=steel, to preserve fidelity. Let me know if you think this is ok but my thought is that the specific material could potentially be useful for some user (in this case, maybe a skateboarder as the manufacturer of that specific outdoor ping pong table suggests) see "prism net" approx 1/2 down the page: https://hengetable.com/the-table

Hi dufekin,
Also, is there a compelling reason you removed the area for Commmunity Field and replaced it with a node?
Thanks!

interesting, might have been an artifact of previous tagging but great callout. thanks and fixed - osm.org/changeset/123481547

Hi dufekin,
Just wondering, why did you change the parking aisles at Westerly Parkway Plaza to be private in this changeset?