Messages

I think the both Locus ETA systems ( routing service ETA for the planner + Locus usage profiles for track statistics)  should be unified.

It would be nice to have the routing and the custom settings as the 2 extra options in addition to Locus ones.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

[@tapio]

@tapio
it rarely happens that any settings change by itself. App struggle with this problem for some time and I've also some time ago discovered the possible cause. It's because of the huge amount of settings Locus Map has an Android system that was not created for such amount. So ... another task on long evenings ...

@slarti76
I'll try to improve "toasts" next time, I'll add some new. At least some small "code" at the bottom that may help to identify from where comes, should be useful, agree.

@neatwheat
the difference in times is currently most probably caused by the difference of track segment: in case, the segment is computed by the router, the time comes from this router, otherwise, time is estimated by the app based on few internal variables. I can't improve this now, but it is definitely something that needs to be "fixed" as soon as possible.

---

And new Beta version 3.46.1.1 on Google Play for weekend testing.

Thanks for the hint, I'll try the template too!

If experimenting with the template and if a little familiar with Linux, you may find the use for the sedbatch bash script in Brouter-profiles, that can be run in Android termux Linux console, generating profiles directly from the local or GitHub template. You may want to taylor it for your own modifications.

There is also the original Windows batch sedbatch.bat, but rather obsolete and much less sophisticated.



Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

(Note: To view gpx tracks I do not use services that calculate gpx altitude data from their own terrain model, so this should not be a source of error)

It is also possible if the altitudes are (partially) GPS based ( even if optimized ), the online service internally filters noisy data. If altitudes are SRTM based, there is nothing to filter, as it is smooth.



Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

[immediately]

Everything you set in "Altitude manager" is applied immediately after the GPS location is received. After that, an updated location (in this case with updated altitude value) is sent to other services like track recording. So all recorded points already contain this updated altitude. Original altitude is lost.

Why you have feeling that SRTM data are not exported? If you use the "Replace" option in "SRTM data" settings (Altitude manager), you should get quite a fluent elevation profile, exactly the same as with the "Fill elevation" option (in track detail).

Hello,

basic information may be found here: https://docs.locusmap.eu/doku.php?id=manual:user_guide:tools:altitude#srtm_data . LIDAR data in HGT format (SRTM-1, SRTM-3) are supported and you may use custom data by placing files into Locus/data/srtm directory.
Hope this helps.