Allow adjust "estimated travel time" parameters

Marius Moldovan shared this idea 6 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 (11)

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
2

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
1

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
1

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

Leave a Comment
 
Attach a file