Skip to content

Topological links waterway=flowline and waterway=link should not show when using underlay imagery #24340

@adamfranco

Description

@adamfranco

Description

It seems that waterway=flowline and waterway=link were added to the OsmAnd data to support boat routing in #22512. As described in the OSM wiki,, waterway=flowline is a topological connection between inlets and outlets of lakes and reservoirs. Similarly, waterway=link is a topological connection for canoe routes and similar. While these are useful for boat routing purposes, waterway=flowline in particular does not have precise alignment to physical features (like a deep channel) in the same way that waterway=fairway does. The precise placement of both waterway=flowline and waterway=link are arbitrary and these ways are not a features that make sense to display to users.

Because the inclusion of water areas in the default vector rendering obscures waterway=flowline, these features are not really visible with vector backgrounds. However, when raster underlays are enabled these waterway=flowline and waterway=link get shown, resulting in many unneeded and confusing lines.

Steps to reproduce

  1. Use the Default rendering style in OsmAnd
  2. Browse to a location where waterway=flowline and waterway=link are mapped: https://osmand.net/map?pin=44.60363,-73.41319#13/44.60363/-73.41319
  3. Zoom in to around z=13 or greater
    Without underlay
  4. Enable an underlay like Microsoft Earth satellite imagery
  5. Note that without water areas being displayed, the flowlines are visible.
    With underlay

Actual result

waterway=flowline are unexpectedly rendering on top of the underlay raster imagery:
With underlay

Expected result

waterway=flowline should be hidden from display:
With underlay, no waterway=flowline or waterway=link

Your Environment (required)

OsmAnd Version: OsmAnd+ 5.2.13
Android version: 16
Device model: Pixel 8
Crash-Logs: n/a

Metadata

Metadata

Assignees

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions