Thanks, I added the traffic signal that has also been added here are described and diagrammed the turn restriction.

Yeah, I think meant it as a description. If I made the edit now I would only add a name if it were a formal name of a feature. I removed the name, but since there are two sections to the playground with a path, it made sense to merge the two playground sections into one multipolygon.

I reverted it to a footway. The platforms drawn as areas and then the footway making connections to other adjacent ways makes more sense. Thanks for pointing it out.

Hello, I saw this update to CPR extension and while it does perhaps capture better the exact current physical nature of the project and AKS's description of current gravel road as just an access road. I feel like the previous mapping of just having a single way and just calling it CPR under construction was simpler as it's the same right of way and would make future updates once segments are paved easier as the mapper would just need to edit the tagging from construction status.

Just my thoughts on this. Thanks for your work in South Hillsboro and the region. Between you ArchPDX and I, there is a lot of interest in mapping the rapidly evolving changes in the area which I think benefits the map quality overall very much.

@archpdx I used photoshop to combine wireframe outlines in this doc, and then I made a ratified overly on mapwarper.net

https://apps2.beavertonoregon.gov/DevelopmentProjects/ApplicantMaterials/SCM%20Blackbird%20Farms-18485%20SW%20Scholls%20Ferry%20Rd-Plans%20Civil-.pdf

Just bad syntax. I must have thought I was overwriting the old tag but just put it in front of it. Fixed now. Thanks @dDuga.

…Continued from changelog: Naming sidewalks causes visual clutter with multiple instances of the road name causing confusion: https://drive.google.com/file/d/1cc14SScjubHFakF439OKMdXaU3hsNysH/view?usp=sharing
---

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

Hey there, I made some modifications to your Waterhouse Trail additions along Bronson Rd and Bethany Blvd and felt they were significant enough to give you a heads up. I see you’re a new mapper and hope to maybe offer some insight.

While I know the path is a little wider than a typical sidewalk, It doesn’t really meet the standards of a shared multiuser path so I’ve changed the highway type to sidewalk, but have added notes and the Waterhouse Trail walking relation to it while keeping the cycling relation on the road lanes. This should make the map and specifically hiking and cycling app routing more accurate.

If you’re not sure what a relation is, it’s seperate overlayed data to an area or way that is typically non-physical in nature such as a turn restriction or bus route on a road, or association of a trail route to multiple different roads/paths along its way. If you view the open cycle map layer in regular map view you’ll see the route relations as purple lines on trails for example.

Thanks, and keep on mapping!

FYI, my child attends this school. Area not used for sports, but instead the school marching band uses this area to practice formation maneuvers they will use during football games. Re-tagged as pedestrian area as there isn't anything as specific as actual use.
---

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

A better schema for this would be to place nodes at the beginning and end of the steps. split each node so there is a new way segment between the nodes and tag the way "highway=steps", then you can notate surface, # of steps etc.
---

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

surface=*

This looks ok. surface=paved is fine, but if you know the specific paving material (asphalt, concrete, paving stone, etc), that's more descriptive.