Idea/future work: Upgrade the features finding along the track (mountain passes for example)

[JulesL2]

See the possibility to pass to overpass API the full gpx track and to do an around request. Then it would be possible to enhance the speed of Mountain map processing. https://help.openstreetmap.org/questions/65796/querying-the-osm-data-for-peaks-or-other-features-which-are-nearby-a-gpx-track?page=1&focusedAnswerId=65904#65904

[ThomasParistech]

This sounds promising, but in practice the current solution that requests overpass data over the bounding box and then compare with the GPX track is already quite fast! Roughly 1-2s for a large mountain scene like UTMB.

When we look at the UTMB profiling, we notice two parts that take much longer:

• Elevation Data Download: hard to improve it as we're already using an allegedly optimized wrapper (https://github.com/ACCESS-Cloud-Based-InSAR/dem-stitcher
• Optimal Text Allocation: I've already submitted a few PRs to tailor textalloc to pretty-gpx usecase, e.g. allow to drastically reduce the number of candidates (https://github.com/ckjellson/textalloc/pull/22). We can probably still improve it