[Feature request] Indicate trail closure in trail planner

[Stancerz]

Sometimes trails are closed due to damage, construction, etc. I guess that this is stored as a trail attribute in osm. The wanderer trail planner seems to observe this attribute and disallow auto-route through trails that are closed. However, it does not indicate that the trail is closed (i.e., why auto-route is not working). Therefore, feature request 1 is that the map indicates trail closures. As a reference, komoot shows trail closures this way:

For testing, I created a trail that tries to use a closed trail in the demo instance: https://demo.wanderer.to/trail/view/0ee6257a3510946

It would be even more amazing (feature request 2) to have the option to ignore trail closures during planning (e.g., for planning journeys ahead of time and expect the trail to be open when visiting it).

[Flomp]

Hey there,

Anything routing related is a bit tricky. wanderer uses the valhalla routing engine. Routing is a very resource and storage space intensive endeavor. Currently there is no budget to provide our own routing data. So we use a public instance of valhalla in the standard installation: https://github.com/Flomp/wanderer/blob/98691dc31128b94ba21853604e6fe02683657168/docker-compose.yml#L60

As a result, we do not have any influence over which route gets calculated by the server. If you want to host your own valhalla instance you can do so by uncommenting the respective section in the docker-compose.yml.

[Stancerz]

Hi, thanks for your reply. I fully understand that there is no budget to run a dedicated routing server.

However, I just looked into valhalla and (at least the web interface) allows to configure the necessary settings by setting "use hills", "maximum hiking difficulty" and "shortest" (see link/screenshot at the bottom). Exposing these parameters as wanderer settings (best case general settings + possibility to override for specific route) is what #204 refers to. Does the public valhalla API not expose these parameters?

#202 is a bit different, as it is not referring to the routing or modifications to routing, but the visualization of trails being closed. Valhalla seems to be aware of these closures, but also does not display them. I wasn't able to figure out where this info is stored in osm, but will update if I find something.

Thanks for your work!

https://valhalla.openstreetmap.de/directions?profile=pedestrian&wps=9.528302396799939%2C48.57616458058214%2C9.5162862%2C48.5827773%2C9.5213107%2C48.5864087

[Flomp]

Oh sweet, I hadn't had a proper look at these settings. I'll do so next week and probably create a dedicated settings page for default values that can be fine tuned when drawing a route.

Thanks!

[Stancerz]

Perfect, thank you! :)

[Stancerz]

So, I just managed to take a closer look regarding closures. They are available through the "access" tag of the highway=path tag, see https://wiki.openstreetmap.org/wiki/Tag:highway%3Dpath Presumably, Valhalla will not route through a given path if the access tag is set to "no" (and maybe also "private"). I also did not find a way to tell Valhalla to ignore the "access" tag, so part of the initial feature request seems to indeed be not easily implementable. There may also be specific access tag depending on the means of transport one is using (e.g., foot, bicycle, horse). Example from the trail also mapped in the demo: https://www.openstreetmap.org/way/319593116#map=17/32.759959/-16.949201&layers=N Apparently, the "note" tag is typically used to add a note with regards to the reasons and duration of the closure.

Thus, the feature request is to A) Visualize closed trails with appropriate symbols (for example, the ones used by komoot, see https://github.com/Flomp/wanderer/issues/202#issue-2940283552) B) On mouse-over or on click of a trail-closed-symbol, display any note text (if available).

[Flomp]

v0.16.2 adds the aforementioned settings to the routing algorithm. The dedicated settings page will follow in a later update. I'll have a look at the trail closures.