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. https://www.openstreetmap.org/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.