protomaps / protomaps/basemaps
Missing parts on rivers
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 740
- Forks
- 104
- Avg merge
- 26m
- Merged PRs (30d)
- 2
Description
Impacted Features/Layers
Long rivers like the "Elbe" or "Danupe" are kind of cluttered on low zooms (~7). This also happens in various other places/rivers.
Screenshots
High Zoom (~8)
Low Zoom (~7)
My thoughts on the issue/solution:
I suspect that the reason for this issue comes from the complex relations within OSM dataset, which splits it into multiple polygons. I am not really into the planetiler framework, but I think it would make sense to add some relation management for rivers/streams/canals/riverbanks and combine into MultiPolygons in post-process.
I would appreciate it if someone could me give me some feedback on my thoughts and a brief overview of how the relations should be implemented. I would be happy to implement this, but I failed so far.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the missing or cluttered river parts around zoom levels 7–8 using the Elbe or Danupe examples and then investigate how Planetiler handles the related OpenStreetMap river, stream, canal, and riverbank data. Done means the affected long rivers render continuously and without the reported clutter at low zooms, with relation handling validated against comparable cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100