Are there any news regarding implementing a more accurate ETA (Travel time)on navigating new created routes?
Which take into consideration profile elevation at least
I suggested some time ago that at least fixed profiles which are already in locus(mountain hiker,Take a walk, MTBtrail ride etc) should be user configurable regarding speed on flat/ vertical speed, rest time
I had a problem this weekend when I was hiking to a mountain chalet and the navigation said there were only 5 kilometers till destination and I was at almost the same height as the chalet.The ETA was aprox 1 hour and I thought I will make it till night has began
I began hiking and it was raining but I arrived after aprox 3 hours...walking on the crest in the night and rain.
I forgot to look on the altitude chart and there were many peaks in between these 5 kilometers and so ascent was significant.
Because I had a good speed on the last 15 minutes before making the new route to the chalet I was given a shorter ETA to destination, not taking into account total ascent of the new route
Had a rough time :)
I like this idea 
Good day Marius,
I've changed your question to idea, so other may votes if interested in this modification of Locus.
Good day Marius,
I've changed your question to idea, so other may votes if interested in this modification of Locus.
I agree
I agree
It seems to me correct to calculate the arrival time based on the average speed. This method is used in the OrusMaps program and fully justifies itself. And it will not matter if you go on foot, ride a bicycle or a car. Also, all your stops along the route will be taken into account.
It seems to me correct to calculate the arrival time based on the average speed. This method is used in the OrusMaps program and fully justifies itself. And it will not matter if you go on foot, ride a bicycle or a car. Also, all your stops along the route will be taken into account.
Is it still not possible to set a customize and personalize speed to calculate righter ETA. It seems the minimum walking speed is 4km/h and not possible to change it. Is it right? If you walk at 5000mt or on snow or carrying 25kg speed cannot be this, and ETA it will be hardly wrong.
Is it still not possible to set a customize and personalize speed to calculate righter ETA. It seems the minimum walking speed is 4km/h and not possible to change it. Is it right? If you walk at 5000mt or on snow or carrying 25kg speed cannot be this, and ETA it will be hardly wrong.
I'd also like to adjust the speed for each routing profile, so routing gives a more accurate ETA for my personal walking/driving speeds.
A value "+/- x km/h" would do for me (as it is implemented in the PC software of a sometimes rather ignorant US navigation company ;-)
I'd also like to adjust the speed for each routing profile, so routing gives a more accurate ETA for my personal walking/driving speeds.
A value "+/- x km/h" would do for me (as it is implemented in the PC software of a sometimes rather ignorant US navigation company ;-)
That would be very useful to me. In the wintertime my avarage speed is 1.5-2km/h. I wish there was a way to adjust that parameters.
That would be very useful to me. In the wintertime my avarage speed is 1.5-2km/h. I wish there was a way to adjust that parameters.
The travel time is currently being adjusted based on the user's past speed. That is not always optimal. The user should be able to set the speed himself. Locus could suggest the speed. This is suggested based on the behavior since then. But then the user decides which time to enter.
The travel time is currently being adjusted based on the user's past speed. That is not always optimal. The user should be able to set the speed himself. Locus could suggest the speed. This is suggested based on the behavior since then. But then the user decides which time to enter.
Much agree
Much agree
Any news on this? Walked 2 days with heavy backpack and the average speed was waaay slower as calculated speed. Would be great to change avg speed to something lower (or higher in case of cyclo)
Any news on this? Walked 2 days with heavy backpack and the average speed was waaay slower as calculated speed. Would be great to change avg speed to something lower (or higher in case of cyclo)
Any updates on this? I also need to be able to create custom profiles for speed and time per elevation gain / loss. Ski mountaineering, with different profiles for slow, avg, and fast partners.
Any updates on this? I also need to be able to create custom profiles for speed and time per elevation gain / loss. Ski mountaineering, with different profiles for slow, avg, and fast partners.
In an ideal (complicated) world I'd like at least 3 settings
- Average speed when going up
- average speed when going down
- average rest time per hour
of course we could add to be more precise
- average speed when going up or down on steep area
complementary Idea : why not a way to compute these values baseed on previous tracks ?
My hiking folder has 100+ tracks recorded.. it should be more than enough to compute precise averages (yes, I know, 'precise' and 'average' in same phrase is weird.....)
In an ideal (complicated) world I'd like at least 3 settings
- Average speed when going up
- average speed when going down
- average rest time per hour
of course we could add to be more precise
- average speed when going up or down on steep area
complementary Idea : why not a way to compute these values baseed on previous tracks ?
My hiking folder has 100+ tracks recorded.. it should be more than enough to compute precise averages (yes, I know, 'precise' and 'average' in same phrase is weird.....)
I think this is definitely needed. I based my walking on this in Snowdonia, it's way out, some sheer climbs are running my hiking in to 1.6mph, camera equipment loaded rucksack,where Locus map is saying I can do the route at an average of 3.5mph! I think I may have to start training with the SAS...
I think this is definitely needed. I based my walking on this in Snowdonia, it's way out, some sheer climbs are running my hiking in to 1.6mph, camera equipment loaded rucksack,where Locus map is saying I can do the route at an average of 3.5mph! I think I may have to start training with the SAS...
Sounds like a good idea.
Sounds like a good idea.
Which bit, training with the SAS or getting custom profiles... 🤣🤣👍
Which bit, training with the SAS or getting custom profiles... 🤣🤣👍
A few custom activity profiles could replace the 38 different existing ones.
A few custom activity profiles could replace the 38 different existing ones.
Hi guys,
give us a few weeks. We are on a good way to improve it!
Hi guys,
give us a few weeks. We are on a good way to improve it!
Coulsd it be possible to used previous recorded tracks ?
I have 100+ tracks recorded when hiking.. strucured in variopus folders. It should be somewhat possible to compute average speeds (going up or down or more detailed as suggested above) and also average rest time (almost always lunch break at summits)
Coulsd it be possible to used previous recorded tracks ?
I have 100+ tracks recorded when hiking.. strucured in variopus folders. It should be somewhat possible to compute average speeds (going up or down or more detailed as suggested above) and also average rest time (almost always lunch break at summits)
I will be very happy when dashboard will show me the reliable arrivaltime. I nearly missed train on the last walk, though I know time is not correct in dashboard. I use for carridings the FreewareApp "MapFactor Navigator" and there I always have a reliable arrival time shown in dashboard, I only had to adjust my driving style in preadjustments first. I suppose that only personally made preadjustments give me a reliable arrival time. Thanks to the developers and editors of LocusMap.
I will be very happy when dashboard will show me the reliable arrivaltime. I nearly missed train on the last walk, though I know time is not correct in dashboard. I use for carridings the FreewareApp "MapFactor Navigator" and there I always have a reliable arrival time shown in dashboard, I only had to adjust my driving style in preadjustments first. I suppose that only personally made preadjustments give me a reliable arrival time. Thanks to the developers and editors of LocusMap.
To calculate the arrival time more accurately, it is enough to use your average speed on the current trip as a speed parameter.
To calculate the arrival time more accurately, it is enough to use your average speed on the current trip as a speed parameter.
It's not that simple. This is only true if the boundary conditions remain the same. The biggest factor for errors are altitude meters. Since then, only a few have been there. In the last area of the tour, there are very many. Therefore, one must always put the average speed in relation to the altitude meters.
With the MTB come then still difficulty of the terrain in addition. But this is very difficult with automatic calculations. user 1 makes little difference, because he can ride very well. User 2 makes a big difference.
Therefore, it is important to make user-defined defaults for the calculation.
But always based on average in relation to the altitude meters.
Most users will first take the standard calculation of Locus. The users who choose their own default, it would be helpful to see the default calculated by Locus to get a feeling. This could be an info field when I long click on calculated time.
In this field I could also adjust the own default and it will be recalculated.
It's not that simple. This is only true if the boundary conditions remain the same. The biggest factor for errors are altitude meters. Since then, only a few have been there. In the last area of the tour, there are very many. Therefore, one must always put the average speed in relation to the altitude meters.
With the MTB come then still difficulty of the terrain in addition. But this is very difficult with automatic calculations. user 1 makes little difference, because he can ride very well. User 2 makes a big difference.
Therefore, it is important to make user-defined defaults for the calculation.
But always based on average in relation to the altitude meters.
Most users will first take the standard calculation of Locus. The users who choose their own default, it would be helpful to see the default calculated by Locus to get a feeling. This could be an info field when I long click on calculated time.
In this field I could also adjust the own default and it will be recalculated.
Possible specification in the info field:
If Locus default is used:
Specification of current default Km/h // hm calculated by Locus and calculated time.
A field to make user defined default.
If own default is used:
Specification of current default Km/h // hm calculated by Locus and calculated time.
Specify current custom default Km/h // hm. and calculated time.
A field to change user-defined default.
Possible specification in the info field:
If Locus default is used:
Specification of current default Km/h // hm calculated by Locus and calculated time.
A field to make user defined default.
If own default is used:
Specification of current default Km/h // hm calculated by Locus and calculated time.
Specify current custom default Km/h // hm. and calculated time.
A field to change user-defined default.
There is a program called Oruxmaps. This program implements the arrival calculation based on the average speed of the current track. I used it a lot. It works great. And it is very simple to implement it.
This solution takes into account all the individual characteristics of the user at once.
There is a program called Oruxmaps. This program implements the arrival calculation based on the average speed of the current track. I used it a lot. It works great. And it is very simple to implement it.
This solution takes into account all the individual characteristics of the user at once.
Replies have been locked on this page!