v4.13 router profile for cross country skiing: Assumtions for calculated time?

Georg D shared this question 42 days ago
Need Answer

In v4.13 a router profile for cross country skiing has been added. The calculated travel time is way too high for most routes I looked at, so I'd like to ask: What are your assumptions for time calculation? 🙂 Maybe you're including breaks. Or you always assume ungroomed pistes, thus I do expect lower times on pistes that have grooming information in OSM data.

For example, for https://link.locusmap.app/r/hko7fp the router tells 2h30 and I need around 1h40 in classic style (so the slower one and usually depicted with the icon used in LoRouter ski profile) and I am not at all in a rush; time is same for varying conditions but it's groomed. Similar, for https://link.locusmap.app/r/udm4t2 I need 1h15, calculation is 2h03.

But on an ungroomed track during snowfall (=bad vision), I needed 1h52 for https://link.locusmap.app/r/qamwn5 while calculation is 1h48. So here, it is quite accurate.



BTW, https://help.locusmap.eu/topic/23106-how-can-i-plan-cross-country-skiing-route and https://help.locusmap.eu/topic/route-planning-winter-slopes-lomaps are locked, so I can't add a comment on new feature but maybe Locus team can 🙂

Replies (3)

photo
2

I think these support questions will occur again & again until profiles can be added/ edited by the user to suit their own preferences. There are many other related help & forum topics.

photo
1

Hello Georg. Thanks for this report. We haven't got much feedback for nordic skiing routing yet, so yes, time estimates looks high. I will fix it, but what Andrew says will always be the case here. There is no single settings that suits all skiers / conditions. Customization is being debated.

photo
2

I count 15 travel-time profiles, none of which really suit my use. And although I mostly cycle, I do occasionally use a car & other transport too but there are no vehicle profiles, which is inconsistent given there are car/ motorcycle/ bus routing profiles. Locus could actually create it's own optimized travel-time profiles by analyzing a selected & representative set of track recordings - wouldn't that be clever (& accurate)! The user then just selects an icon & name.

photo
1

Great idea as it is convenient, quick, easy yet highly customized & accurate 🙂 IMHO you shall create an idea on itself for it, so it can be discuessed – e.g. which aspects of the tracks shall be considered during analysis (distance, elevation gain/loss, surface, time/daylight/night, density of traffic lights and crossings,...)

photo
Leave a Comment
 
Attach a file