Started by Menion, July 31, 2018, 13:19:59
0 Members and 1 Guest are viewing this topic.
Quote from: Andrew Heard on August 05, 2018, 02:50:37Test of Locus Pro+BRouter Route Planner ETA: quite good result in my first test. Well done @menion.
Quote from: tapio on August 05, 2018, 07:36:29Du 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?
Quote from: lor74cas on August 05, 2018, 21:44:36Not a bug report just for information about power saving mode of my device.Today I tested the battery saving mode on the a5 2017 Samsung
Quote from: Andrew Heard on August 06, 2018, 02:09:00Quote from: lor74cas on August 05, 2018, 21:44:36Not a bug report just for information about power saving mode of my device.Today I tested the battery saving mode on the a5 2017 Samsung@lor74cas - thanks for report - I have just bought this phone so am hoping no power saving problems with Locus.I note has inbuilt barometer - do you find the ascent measurement more accurate than a phone without inbuilt barometer?
Quote from: menion on August 06, 2018, 09:18:45@lor74casbattery saving mode is always ... "wrong" for GPS usageAnyway I'll always suprised that my overcomplicated altitude system return quite good elevation values. Nice
Quote from: menion on August 06, 2018, 09:18:45@tapioevery BRouter profile is based on either car, bike or foot. Generally, every routing profile in every router belongs to one of these three categories. So no matter what custom profile you use, it will always be in one of three groups.
Quote from: menion on August 06, 2018, 09:18:45@tapiosetup of "climbing/descending/flat speeds" is overkill
Up: <u> metersDown: <d> metersHorizontal: <h> metersConservative assumption - the hiker walks per hour:300m up500m down4km horizontalCalculation:a = u/300 + d/500b = h/4c = greater value of a and bd = smaller value of a and bWalking time: (0.5*c + d) hours