Allow adjust "estimated travel time" parameters

Marius Moldovan shared this idea 7 years ago
Gathering feedback

Because there are only 3 types of walk in Route planning screen ...none of them matches my speed when hiking/mountaineering ..Also the resting time calculated by it is more then needed for my use.

So I think it would be usefull if these orizontal/vertical speeds and resting time/km would be adjustable by the user

Also for the bike.. Not everyone is the same and this would result in much accurate estimated travel time for the route planned.

Replies (22)

photo
1

Good day Marius,

I've changed your question to idea, so other may votes if interested in this modification of Locus.

photo
1

Thanks, Menion


I wouldn't mind the setting to be even in config.cfg

photo
2

refer to this forum topic for recent discussion - http://forum.locusmap.eu/index.php?topic=6071.msg51113#msg51113. I count 29 (!) possible activities in the drop list at present. None really meet my cycling profile. I'd prefer just one or two custom (user edit) profiles.


PS. is this forum engine link button broken (-). Some times I try to create a link the URL text is just deleted.

http://forum.locusmap.eu/index.php?topic=6071.msg51113#msg51113

photo
1

Also not possible to estimate travel time for a motorized vehicle (nothing in the list) although Route Planner allows for them.

photo
photo
1

I agree

photo
1

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.

photo
1

@Rotko - once you start navigation Locus already bases displayed arrival time on average speed. I think the point of this suggestion from @Marius are to allow adjustment of the predefined "profiles" parameters before navigation has started.

photo
1

Yes, that is the whole point.. these profile need to be user-configurable

Why is that hard to implement??

photo
2

Because I just do not know what to do sooner, that's all ...

photo
1

Andrew Heard, You did not understand. Average speed and average ground speed are different values. You are talking about the first. I'm talking about the second.

photo
1

Rotko - Sorry I do misunderstand your point. You haven't mentioned "ground speed" elsewhere?

My understanding (I hope) of Marius idea is for the user to define their own activity "profile" with name (eg cycling), icon, average speed, average stop minutes per hour, maybe flag hide|show, other values?? At present there are 29 fixed profiles where Menion has tried very hard to provide good representative selection of activities. Of course there are clear limitations with this simplistic model for calculating an accurate estimate which have been discussed in other parts of the forum. Personally, although I vote for the idea, there are higher priority areas of Locus where more benefit per programmer-hour can be gained.

photo
1

Yes, sorry .. I had to post the update here in this topic .

But being in the rain and hiking, I cannot think of a mental calculation to do in order to estimate travel time when total ascent is X meters and total distance is Y km ..

photo
photo
1

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.

photo
1

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 ;-)

photo
1

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.

photo
1

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.

photo
1

Much agree

photo
3

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)

photo
2

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.

photo
2

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.....)

photo
2

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...

photo
2

Sounds like a good idea. 

photo
1

Which bit, training with the SAS or getting custom profiles... 🤣🤣👍

photo
2

A few custom activity profiles could replace the 38 different existing ones.

photo
2

Hi guys,

give us a few weeks. We are on a good way to improve it!

photo
2

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)

photo
2

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.

photo
1

To calculate the arrival time more accurately, it is enough to use your average speed on the current trip as a speed parameter.

photo
1

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.

photo
1

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.

photo
1

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.

photo
2

I am sure that in a flat universe, or constantly uphill or downhill, this approach gives magnificent results, but I think it happens not only to me: starting from the bottom to get to the top of a mountain and then going back down to the starting point.
Simplifying, the route is therefore divided into two parts, the first all uphill, therefore slower, the second downhill, generally faster.
If I check the ETA when I am about to reach the top, my average pace would be high due to all the climbing done and it would indicate a higher time than the correct one to return to the valley, because I will cover the downhill section faster.
The problem is therefore more complex than solving everything on the basis of average speed. Also, the original post was referring to planning, not navigating a track.
When you plan an excursion you want to understand how many hours you need to cover the route that you will perhaps do the following week, so you don't have an average speed other than that of your sofa.

photo
1

For the case of uphill and then only downhill, 2 specifications would make sense: one average speed in the ratio of altitude meters and one average speed in the ratio of depth meters.
So that this idea was intended only for planning I have not seen. But it is needed in the navigation just as.
I must be back at a certain time (train, appointment....). Is the time enough ? Do I have to shorten ? Do I have to drive faster ? Is it enough to take a break or visit a highlight.

photo
2

In fact, I agree with what you write, and I also agree with the parameters you suggested previously.
I replied in the discussion only because too many times the average speed alone was taken as a parameter for the best possible solutions. Also, the original post was about planning where there is no average speed.
I believe that the Locus team will have to find a solution for both planning and navigation. Planning will probably only be based on fixed parameters entered by the user according to his abilities, while in navigation he will be able to make use of speed in addition to these average for the route traveled compared to the planned average speed id based on the difference increase or decrease the ETA.

photo
Leave a Comment
 
Attach a file