Looks like a pretty solid edit. Did SPR change the name of this place to "Park"? When I used to walk down here, the whole thing was called a P-Patch. The website seems to suggest that the official name is "Maple Leaf Community Garden P-Patch", but I'm curious to know what the rainbow sign says on the ground.

I think it's probably fine to tag the area surrounding the allotments as a park--just not sure about the name.

Hey there, thanks for all the mapping that you've been doing around here. This parking structure has two levels. I changed it back to a building in changeset/149070979. Let me know if you have any questions!

On the ground, the sign has a space between the words, too :)

Sorry, I commented from a work account by accident. Here's the changeset that I made from my personal account: changeset/143430861

Hey! I noticed that you align stuff to the KC imagery. Is it more accurate than Bing? I know feature alignment in Seattle is massively inconsistent, but Bing seems to line up with Mapillary/GPS traces pretty well. You might have seen that the OpenSidewalks folks snap all the pedestrian features back to Bing when they comb an area. I've been using "-1.73, 0.77" as an offset for KC 2021 so I'm consistent. What do you think?

Hello, what is the source of the name for this alley? There is no signage on the ground that I can find.

I was mistaken--the liquor store is indeed closed now. I swung by today. Signage is still up. I updated the feature in changeset/133877230. Sorry about that!

Andrew, that liquor store still exists as it did before this change. There are several other issues in this changeset that I haven't had time to look into.

JDillion, welcome to OSM! It looks like you're familiar with the area--thanks for the updates. Please try to upload your changes whenever you finish editing a particular feature on the map. It's difficult for other editors to review updates and offer help when several unrelated changes are batched together into one big upload. I see from your changeset comment that you're practicing for school. We can help you catch mistakes and provide tips and suggestions more easily if you upload closely-related changes in smaller batches. Thanks!

Hello! It looks like you're new to OSM. Welcome, and thanks for the recent edits. I'll address your review request:

This changeset appears to add a new park as a wooded area within a park that has already been mapped. The phrase "Green park" may describe what you see here, but it's not the actual name of the trees or of the park ("Victory Creek Park").

In OSM, we only enter the real names of features on the map. We use other "tags" to describe objects that don't have a name, such as the "natural=wood" tag that you used to represent these trees.

If you'd like to improve your changes here, remove the name "Green park" and redraw the woods as an area around the trees.

Let me know if you have any questions!

Hello, I noticed that this changes the tactile paving status on some curb ramps. The texture on these ramps are designed as grips for slippery weather conditions, but they're not compliant with ADA recommendations for a detectable warning surface. Does OpenSidewalks consider this type of surface as tactile paving?

Some mappers like to tag these as "tactile_paving=primitive" to indicate that the surface isn't smooth, but I don't think these count as "yes".

Ah, I figured out how to get the KC 2021 imagery into the tasking manager:

1. Open the background settings panel
2. Choose the "Custom" option
3. Paste this URL: https://gismaps.kingcounty.gov/arcgis/rest/services/BaseMaps/KingCo_Aerial_2021/MapServer/WMTS/tile/1.0.0/BaseMaps_KingCo_Aerial_2021/default/default028mm/{z}/{y}/{x}

Hope that helps!

To improve the representation of those wide curbs when using two nodes, we could connect both nodes with a way tagged with:

barrier=kerb
kerb=*
tactile_paving=yes

This way they're connected by a single feature for anyone who happens to want that data.

To access the imagery in the editor on openstreetmap.org, open the "Background Settings" panel on the right, and choose the "King County Orthoimagery (2021)" option. The imagery offset settings are at the bottom of the panel.

And good question about those newer "elbow macaroni" curbs... I've thought about this type of curb a lot. I used to draw those with a single curb node, but it often didn't feel right.

For the wider ones, I add two curb nodes now because I try to capture the natural path that a human would actually follow in the real world, and I want create more contrast between those straighter paths versus other crossings in which a person might have to follow the sharper angles of the small corner ramps that point into the center of an intersection.

This may result in better comprehension of directions for the blind. The sharp angle when using one node could provoke an unnecessary detour into the waiting area of the crossing and may cause a person reading a tactile map to spend extra time searching for things like beg buttons or guide ridges in the center of the curb edge when those assistive features are placed at the ends.

Using two nodes is also more friendly for typical map readers because we can reduce the zig-zag of the crossing center line that just adds noise to the visual representations for sighted people who often walk right over the curbs in a straight line.

I still haven't decided whether to classify these as "kerb=lowered" or "kerb=flush". Arguments could be made for each...

Oh...

Dr. Caspi introduced me to the OpenSidewalks Tasking manager today. I just noticed that the iD instance in this tool doesn't have the newer King County aerial imagery option. You may wish to cross-reference changes made through the tasking manager with KC 2021 imagery available in the official iD editor instance at openstreetmap.org or in JOSM. Use this offset to line it up with existing sidewalk data: -1.73, 0.77

It may be a simple upgrade to get this imagery into the tasking manager for your team. Hope this helps!

Hi 0wu, thanks for the reply. I'm referring to the angles of the curb ramps which changed after the construction. For example, this changeset moves some ramps back to the ~45 degree angle shown in the older Bing aerial imagery. However, the construction replaced a few of these with straight angles, and added a second ramp at 90 degrees on some corners.

The missing crossings I left out intentionally because N 80th St can be quite busy during the day (despite its tertiary status in OSM). I'm reluctant to draw unmarked crossings across dangerous roads until pedestrian routers mature. I'd rather emphasize the the safer marked/signalized crossings that exist nearby. Is this a problem for OpenSidewalks?

Hello! This changeset reverts the updated alignment of reconstructed curbs/bulbs on Green Lake Dr N. I've tried to align sidewalks very carefully south of 85th St to account for all of the new construction.

Hello! This changeset reverts the updated alignment of reconstructed curb ramps and crossings along N 80th St. This is one of the streets that I sent in the list that you asked for.

Please check the version history of an element before adjusting it with outdated imagery.

Thanks!

Hello, can you please elaborate on the reason for this change? As far as I can see, the original road configuration was correct.

NE 113th St is signed as "right turn only" both east and west of this intersection, and northbound traffic from Northgate Way and Lake City Way must not turn left onto that road. The segment added to connect this road across the intersection does not reflect these restrictions.

This changeset also removes a segment of the Lake City Way dual carriageway that enables southbound traffic to continue through to the road south of the intersection. With this change, southbound traffic will only be able to turn right onto Northgate Way.

This changeset adds a new traffic signal that does not exist on the ground. The west junction of NE 113th St and Lake City Way is controlled by a stop sign, and there is no signal for traffic turning right from Lake City Way onto Northgate Way.

I can fix these issues, but I'd like to understand the goal of these changes before reverting anything.

Thanks!

(Other mappers have been merging these back together as well).