Neat tool! Thanks for the info. To explain, I have been removing `whitewater=hazard` from dams and weirs because these should always be considered hazards to paddlers. We can add access tags like `canoe=yes` if a weir happens to be runnable. Relying only on `whitewater=hazard` runs the risk of missing any dams and weirs that have not been tagged this way. However, I will defer to the local community if that's how you want to tag things in this area :)

Hi Tomas, thanks for the feedback. Are you talking about whitewater=hazard specifically or also my other whitewater edits? Frankly I did not realize that anyone was using these tags in earnest. What's the name of the tool? I'd be very interested to get your perspective. We're discussing this over at: https://community.openstreetmap.org/t/new-tagging-scheme-for-portages-and-rapids/

Hi, I've been standardizing rapids and canoe tags. The `whitewater` schema has some issues. See discussion here: https://community.openstreetmap.org/t/new-tagging-scheme-for-portages-and-rapids/111814

No worries at all! I am sorry for the confusion. Thanks for talking this through with me.

Hi creabaluti. Yes, there have been many different tags used for tagging whitewater features and I am working to standardize them so they are useful to consumers. I will update the wiki at some point if no one else does. More discussion here: https://community.openstreetmap.org/t/new-tagging-scheme-for-portages-and-rapids/111814

Thanks, I don't intend to revert my changes because I did not remove any information, and because no one appears to be relying on the prior pattern. As I've already said, the length and position are still available on the river segment, which avoids redundancy and the other issues I mentioned.

Feel free to revert this changeset if you're not convinced by my arguments. I don't live in Sweden and will defer to local mappers there. Alternatively I can map this rapid as an area if that would resolve the geometry issue for you.

Btw, there are thousands of `waterway=rapids` ways mapped along the width of the river in OSM, the example I sent is not an outlier. Check out Canada.

Anyone can write anything on the wiki, it's not necessarily good advice. The sentence "draw a linear way along the centre line" doesn't specify if the axis is with the flow or tangential to the flow, which apparently has led to different interpretations. Please let me know if there are any applications expecting the data to be mapped in the manner it was before. If I inadvertently broke something then I am happy to fix it.

Hi AndersAndersson, sorry to change you edits but no info was lost here. Mapping rapids as linear ways in the direction of flow has some issues. It's redundant to putting rapids attributes on `waterway=river` segments (where you can easily calculate length). Boat routers are the ones needing this info anyway. In some cases mappers have made `waterway=rapids` colinear with rivers, which is hard to maintain. In other cases mappers use `waterway=rapids` instead of `waterway=river`, which is unexpected (a river with rapids is still a river). The pattern is also ambiguous since many mappers use `waterway=rapids` to tag individual rapids parallel to the flow, akin to `waterway=weir` (e.g. way/511163824), thus we couldn't be sure if measuring a rapids way gives us width or length. Having a POI with a `name` tag is still useful for rendering and geocoding, so I left a point. Future work could convert this to an area matching the bounds of the section of named rapids.

Hi AndersAndersson, you can join the discussion here: https://community.openstreetmap.org/t/new-tagging-scheme-for-portages-and-rapids/111814

Hi sbre! Changes were not discussed, happy to revert if needed. I'm trying to standardize whitewater tagging—it's so fragmented and archaic to the point of being unusable. The whitewater wikiproject appears to be abandoned. Trying to kickstart canoe mapping.

Happy to! nwsr=*

Hi Mashin 👋
I see you're removing trail names from ways that are already present on trail relations. I fear this is a nonstandard pattern with spotty support. Most maps and routing engines will not show labels for these trails, including the default osm-carto style. As such, I recommend reverting your changes to save future mappers from needing to fill in the missing data again (unless the trails are truly unnamed). Thanks!

I don't think there was a reason, just incidental.

Hi rainsinsfried, sorry to ruffle any feathers. I admit I'm not a local but was attempting to standardize the data. OpenTrailMap is a Q/A tool I'm developing to help visualize and improve trail data, and it helped me find this apparent outlier city. `footway=sidewalk` is widely used to tag footpaths along roads even if there is some space between the road and the path. Apologies if I included places with considerable distance, I was using a relatively broad brush. Many cities allow biking on sidewalks, in which case you can add `bicycle=yes`. If the sidewalks is wide and intended for bikes it should be `highway=cycleway` + `foot=yes`. Happy to discuss this more. -Quincy

osm.wiki/Sidewalks
https://github.com/osmus/OpenTrailMap

Hi there! Yep, I’ve been mapping water trails in the northeast and started using the waterway=link tag to represent a type of feature that there didn’t seem to be a tag for. canoe=portage is for use on highway features while canoe=put_in is a poi (typically for nodes) for minor canoe access points where leisure=slipway doesn’t apply. The purpose of waterway=link is to connect up waterways to highways to support routing. This allows the canoe tag to be used for access, alongside the tags for boat, motorboat, sailboat, etc. I’m open to discussing this design further if desired.

Thanks! I was surprised how messy the NYC-area ferries were considering how prominent they are cartographically. I was able to clean them up considerably in a series of changesets

Hi wambag, thanks for your response.

I didn't end up reverting this and I'll leave it alone for the time being The area is complex and there's probably more than one way to map it in OSM. I was initially annoyed since the changes were vast and took my by surprise, but it doesn't seem like such a big deal now.

Thank you for your numerous edits. Happy mapping!

Hi wambag,

You appear to have removed the tunnel tags from the Schuylkill Expressway around 30th Street Station and tagged many of the ground level streets as bridges instead. As a local, I consider this an incorrect representation and will be reverting most of the changes. I encourage you to leave changeset comments explaining why you made such changes and to consider trying an editor like iD or JOSM that will warn you about potential issues you're creating.

Thanks,
Quincy

Hi Kent,
Unfortunately this changeset turned the Wissahickon Creek boundary into a road route. I've reversed that change. Please make sure that any routes you were editing weren't affected. Thanks!
- Quincy

Hello. The highway=pedestrian tag was present prior to my changes. I agree with your assessment and will make your suggested changes. Thank you for the tip, I'm fairly new at this and appreciate the help!