Messages

[@tapio]

Hi guys,

@tapio Crash with some tracks? If reproducible, send me GPX track to test please, thanks.

My Garmin imports now crash reliably. But when I export and re-import, they work. Will need to look for the source gpx files.

[@tapio]

@tapio
what about saving the track from route planner in fullscreen mode in the latest version? Better?

Yes, buttons are there, looks like solved.

Will send gpx if definitely reproducible.

Thanks! I've found out: Locus does not like my Vista hcx tracks any more, crashes on any of them. Anyone having old, imported Garmin tracks in Locus? Will try to find out more...
I'm under the impression it happens on imported gpx files. My workflow is to import and correct elevation data on import.

Crash since a few versions ago.

- Display like 20+ tracks
- Enter whatever track details screen
- Crash

Anyone else? Maybe because I have older hardware, a Sony Z1?

So both GraphHopper and BRouter should return computed ETA times and the app should only modify these values little bit based on previous user activities.

I'm not sure about "the app should only modify these values little bit".  There is no absolute truth in calculated ETAs, looking at the users tracks will not help, our actions may be too versatile. You add unnecessary complexity.

The light version of an app? No chance, sorry.

Here I fully agree. It would be something else. People can already have something else. Locus is complex, has to be learnt no matter what. But we want it. We want the features it has.

I cannot save tracks from route planner any more. Buttons at the bottom are missing. In fullscreen mode, old story.

I need to bring the keyboard (SwiftKey) up, then the buttons appear.

I've read about the swiss formula; looks like we need a realistic example here. I've searched quite a lot and did not find what those magic constants are.

[@tapio]

@tapio
setup of "climbing/descending/flat speeds" is overkill

OK! Hey, Locus already does calculate decent ETAs internally for the temporary track... and also offers it in route planner (Menu -> Travel time) - There is "Bergwandern (mountain hiking)" which would be more appropriate for me for display in the bottom bar.

BTW as you probably know, Germany has a norm for this (DIN 33466):

Code Select Expand

Up: <u> meters
Down: <d> meters
Horizontal: <h> meters

Conservative assumption - the hiker walks per hour:
300m up
500m down
4km horizontal

Calculation:
a = u/300 + d/500
b = h/4
c = greater value of a and b
d = smaller value of a and b

Walking time: (0.5*c + d) hours

A good time for reminding of poutnikls ETA calc proposal: http://forum.locusmap.eu/index.php?topic=5176.msg45502#msg45502

Ok. Average speed from my tracks is not perfect. I was in the mountains recently, with very low average speeds, because we had at max. 1400m elevation change per day and 1-2 km/h speed at times.

I think you just let us define climbing/descending/flat speeds. You already know the different ETA formulas, because it always has been in the track options... Thanks for your hard work!

I cannot save tracks from route planner any more. Buttons at the bottom are missing. In fullscreen mode, old story.

Test of Locus Pro+BRouter Route Planner ETA: quite good result in my first test. Well done @menion.

Du you have an example? What brf files do you use, maybe you can upload one? I get good results for 90 year old people. 3 km/h in flat areas. Is the ETA depending from something inside the brouter brf files maybe?

From: 51.351619,7.699465
To: 51.344583,7.740034

Graphhopper: 42m
Loc/Graphhopper: 1h14

Edit: Maybe hiking profile = walking profile.

17km in 6 hrs is still unrealistic ETA. Thx for the update btw.

Yes, the filesystem message makes me very nervous, I don't want to spend time setting anything up again.