Display estimated time when creating route

Alan Budden shared this idea 4 years ago
Completed

The fabulous "Add new route & measure" feature of Locus shows a total distance counter in the top-left of the screen. If I plan a route with Google Maps, it also gives a (not especially accurate, but still indicative) idea of the time to do the journey in a car. I realise this is a bit messy with the ability to do mixed "routed" and "non-routed" routes (i.e. with and without the direction button highlighted), but it would be really useful to have this information when planning a car or motorcycle journey.

Comments (5)

photo
1

If you "navigate" the track you have just created you can set a field with remaining time to destination. Maybe that will help?

photo
1

What Alan wants is something, I miss a lot and I'm glad someone bring it here. When you use "add new route" feature, you firstly needs to save it and then start navigation, to get time estimate, how long the route will take. So to know this value also during a creating, should be more then welcome I believe.


Happy voting :)

photo
1

I do a lot of hill walking and it would be really useful when plotting a route to get an estimate of the likely time that the walk will take. I tend to use Naismith's rule which is an hour for every 5km and an hour for every 600m of ascent although many people including myself use an hour for every 4km and an hour for every 600m of ascent which allows for rests! There are modifications to the rules such as increasing the time based on the gradient of the descent but it would be really useful to get the basic settings of walking rate and ascent rate available with a estimated time based on the route and those parameters.

photo
1

Similarly, I use for a bicycle either 20 km/h + 500 m/h, or simplified just 15 km/h for 60-140 km routes.

For foot trips with children, or if you want to travel with enough time for POIs and relax, I use even down to 3 km/h.

I used on Symbian Nokia phone a great and small J2ME application GPSMid with OSM vector maps (!!), where it was hardcoded 4 km/h for foot and 15 km/h for bike trips, what was quite good statistical estimation. OSMAnd uses for Brouter routes or GPX 20 km/h what is too optimistic.

I guess it could be configurable in Locus if to display


20 km or 5 hours for foot, resp.

60 km or 4 hours for bike.

Elevstion could be processed for the estimation as well.

photo
photo
1

As far as I see, the required feature is already existing ("Estimated travel time", see http://docs.locusmap.eu/doku.php?id=manual:user_guide:tracks:planning&s[]=route#estimated_travel_time) but is "just" not available during route planning, but only after route planning has been finished. I'd love to have the feature avaible also during planning.

photo
1

The supposed screenshot bike vertical upspeeds are not realistic, wrt abilities of sustained mechanical power of human body. Cyclists do not have 4times bigger lungs nor hearts than hikers.

photo
1

As none in our team is experienced in this type of computes, we gladly accepts any suggestions to current values ;)

photo
1

A nice illustrative chart of the sustainable human mechanical power over given time interval is below.


In a steep climbing, the majority of the power is spent by gaining potential energy by climbing. The needed power P[watts] = m[kg] . g[m/s/s] . v[m/hod] / 3600. Let the cyclist mass is 65 kg, a bike mass 15 kg, g = 9.8 m/s/s, v = 500 m/h. Then P =80 . 9.8 . 400 / 3600 = cca 110 W just for lifting the weight of the biker and the bike.

Some next 15W or so is spent on rolling tyres friction. Another power is spent on air drag, if the slope is mild and speed still high. It could be typically 100*( v/20 )^3 Watts for v in km/h. ( Air drag is proportional to then3rd power of speed ).

So, I would advice as a first shot e.g. 350 / 500 / 700 m/hod as low/medium/high effort.


OTOH, descent rate in m/hod does not make any sense for the bike. While a pedestrian need to spent some extra effort via "knee brakes" going down, the bike ride down is not only effortless, but speeds up the route.

Long_term_human_power_capability

photo
1

P.S.> but I can see now, that LocusMap has those values already reasonable.


It is just the online manual, that has too high values yet.

photo
1

the screenshot displays "old" settings... will be replaced when the whole feature is fine-tuned

photo
photo
2

Hi Alan, Georg, others. ..

as Georg wrote, this feature is already available in track screen for single track, but not during planning. Georg has a good idea, so direct display of track time estimates was now added into bottom tools menu when you plan a route.

photo
1

Works fine in Locus 3.16.0 - thank you :)

photo