Thanks for fixing these!

Hi,
What is way/1202040190 supposed to represent in relation to the blue line? There's already the platform way/429360418

I get where you're coming from on the routing part. That's actually why I switched to the conditional access tags. A lot of OSM-based maps and routers only update their data every month at best, so a 2-day closure can turn into a month+ closure in downstream apps.

I think the lack of access more accurately reflects that this section wasn't under construction. It was temporarily closed for construction on the overpass bridge. I'll discuss before next time

Thanks for mapping the closure. The wiki guidance for short-term closures is to add a conditional restriction like access:conditional=no @ (2026 Aug 25-2026 Aug 27)

Cool, thanks!

Hi, what's your intention with splitting these road sections when both parts have the same tags?

hey, was node/13722544345 supposed to be a water fountain?

No, no issue here and I see how splitting could be better for routing in this case. Just checking that you're not planning to split every path at every trail intersection

Hey Huong, What's the reason for splitting segments when both sections have the same tags?

The default assumption in OSM is public access, so the legal easement detail doesn't actually need different tagging from what a normal public indoor corridor would get. A ground-floor hallway isn't typically signed as "Saint Paul Skyway", which is what indicates something should have a name tag.

1. right, so what is the meaning of layer=0;1? If it's not crossing another way, it probably doesn't need layer at all. layer=1 isn't intended to mean what level something is on, that's what the level tag is for

Hey Jaacob,
I have a couple questions about your changes
- what is the intended meaning of a path with multiple values for the layer tag? The layer tag is for sorting ways vertically, not describing which floor something is on
- are the footways that have multiple level values ramps connecting two levels within the building?

Hi Jaacob,
I'm not sure something like way/1548635718 should be tagged with name=Saint Paul Skyway. If it's on the ground floor, it's just an indoor corridor that happens to connect to the skyway among other things

Hi,
Welcome to OSM. Just wanted to let you know not everything has or needs a name tag. See osm.wiki/Names#Names_are_not_for_descriptions

Reverted changeset/187009760

Is this trail new? I don't see it in imagery and I don't remember seeing it in person

Hi,
I saw couple of validation issues here: a couple buildings cross the alley, and there's a duplicate building directly on top of another. Rapid flags both of these in the issues panel before upload, so please check that panel and resolve flagged issues before submitting. Thanks.

Hi,
Thanks for adding these buildings. One small note: a lot of the new building outlines have angles that are a bit off from square. Going forward, it'd help a lot if you could run the "Square" tool (Q hotkey) on each building before uploading: it snaps the corners to 90 degrees and makes the footprints much cleaner.
Thanks again!

Hi gvwaal,
I have a couple of concerns about this change:

1. The Minneapolis OpenData source cited says it was last updated in 2022, and Boom Island was remodeled last year. More importantly, even a current dataset not showing a path there isn't strong evidence to remove an existing cycleway designation. There's no guarantee the dataset is a complete inventory of bike infrastructure.

2. Several footways were tagged footway=sidewalk. Per the wiki (footway=sidewalk#What_is_considered_a_sidewalk), that tag is meant for paths that run alongside and are associated with a road. These paths aren't adjacent to a street, so footway=sidewalk doesn't apply.

To be clear, I'm not saying I think all of these should be cycleway. I think at least around the Memorial to Survivors and Pioneer Monument, footway is correct.

Hey Huong,
Thanks for your change. FYI, you can encode an expected (re)opening date in the opening_date tag. I've gone ahead and done so in changeset/186126607