Run peak prominence / topographic isolation algorithm to display only prominent mountain peaks #9190

Open
opened 2024-09-01 15:01:04 +00:00 by hiddewie · 0 comments
hiddewie commented 2024-09-01 15:01:04 +00:00 (Migrated from github.com)

Is your feature request related to a problem? Please describe.

Currently, mountain peaks are shown from the first zoom level where downloaded country details are shown.

Every mountain peak is shown on the map, irrespective of its elevation.

(see screenshot)

Having fewer but more important mountain peaks on the map ensures the map is less cluttered, and more targeted. Especially together with contour lines, this creates a nice overview visualization of a region for the lower zoom levels.

The main OSM carto visualization has the same problem, see https://github.com/gravitystorm/openstreetmap-carto/issues/3722. However, that data has to be updatable dynamically without reprocessing the entire world when a single mountain peak changes. The OrganicMaps OSM data can be post-processed with algorithms before visualizing it because it is not updated every minute.

Describe the ideal solution

Run the prominence / topographic isolation algorithm on the mountain peak data. This produces a number for each peak, how prominent it is in the direct area.

The map can display peaks of a certain prominence depending on the zoom level.

Related documentation and implementations:

Describe alternatives you have considered

Other maps also use this solution, if the resources are available to recalculate the peak prominence when the data changes. For example OpenTopoMap.

Additional context

If this feature is not worth the processing or complexity, feel free to close this issue.

image

**Is your feature request related to a problem? Please describe.** Currently, mountain peaks are shown from the first zoom level where downloaded country details are shown. Every mountain peak is shown on the map, irrespective of its elevation. (see screenshot) Having fewer but more important mountain peaks on the map ensures the map is less cluttered, and more targeted. Especially together with contour lines, this creates a nice overview visualization of a region for the lower zoom levels. The main OSM carto visualization has the same problem, see https://github.com/gravitystorm/openstreetmap-carto/issues/3722. However, that data has to be updatable dynamically without reprocessing the entire world when a single mountain peak changes. The OrganicMaps OSM data can be post-processed with algorithms before visualizing it because it is not updated every minute. **Describe the ideal solution** Run the prominence / topographic isolation algorithm on the mountain peak data. This produces a number for each peak, how prominent it is in the direct area. The map can display peaks of a certain prominence depending on the zoom level. Related documentation and implementations: - https://osm2pgsql.org/doc/manual.html#strategy-discrete-isolation - https://github.com/MathiasGroebe/discrete_isolation - https://wiki.openstreetmap.org/wiki/User:Maxbe/Dominanz_von_Gipfeln (in German) - C implementation https://github.com/der-stefan/OpenTopoMap/blob/e4467cfc2064afc379b0f8e8360db1740099cca3/mapnik/tools/isolation.c **Describe alternatives you have considered** Other maps also use this solution, if the resources are available to recalculate the peak prominence when the data changes. For example OpenTopoMap. **Additional context** If this feature is not worth the processing or complexity, feel free to close this issue. ![image](https://github.com/user-attachments/assets/03c41fd0-8421-4eff-adb2-f35e325fc50a)
This repo is archived. You cannot comment on issues.
No labels
Accessibility
Accessibility
Address
Address
Android
Android
Android Auto
Android Auto
Android Automotive (AAOS)
Android Automotive (AAOS)
API
API
AppGallery
AppGallery
AppStore
AppStore
Battery and Performance
Battery and Performance
Blocker
Blocker
Bookmarks and Tracks
Bookmarks and Tracks
Borders
Borders
Bug
Bug
Build
Build
CarPlay
CarPlay
Classificator
Classificator
Community
Community
Core
Core
CrashReports
CrashReports
Cycling
Cycling
Desktop
Desktop
DevEx
DevEx
DevOps
DevOps
dev_sandbox
dev_sandbox
Directions
Directions
Documentation
Documentation
Downloader
Downloader
Drape
Drape
Driving
Driving
Duplicate
Duplicate
Editor
Editor
Elevation
Elevation
Enhancement
Enhancement
Epic
Epic
External Map Datasets
External Map Datasets
F-Droid
F-Droid
Fonts
Fonts
Frequently User Reported
Frequently User Reported
Fund
Fund
Generator
Generator
Good first issue
Good first issue
Google Play
Google Play
GPS
GPS
GSoC
GSoC
iCloud
iCloud
Icons
Icons
iOS
iOS
Legal
Legal
Linux Desktop
Linux Desktop
Linux packaging
Linux packaging
Linux Phone
Linux Phone
Mac OS
Mac OS
Map Data
Map Data
Metro
Metro
Navigation
Navigation
Need Feedback
Need Feedback
Night Mode
Night Mode
NLnet 2024-06-281
NLnet 2024-06-281
No Feature Parity
No Feature Parity
Opening Hours
Opening Hours
Outdoors
Outdoors
POI Info
POI Info
Privacy
Privacy
Public Transport
Public Transport
Raw Idea
Raw Idea
Refactoring
Refactoring
Regional
Regional
Regression
Regression
Releases
Releases
RoboTest
RoboTest
Route Planning
Route Planning
Routing
Routing
Ruler
Ruler
Search
Search
Security
Security
Styles
Styles
Tests
Tests
Track Recording
Track Recording
Translations
Translations
TTS
TTS
UI
UI
UX
UX
Walk Navigation
Walk Navigation
Watches
Watches
Web
Web
Wikipedia
Wikipedia
Windows
Windows
Won't fix
Won't fix
World Map
World Map
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: organicmaps/organicmaps-tmp#9190
No description provided.