Messages

It is also possible to display the heart rate on the LocusMap dashboard, possibly transparent over the map.

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

I have installed the recent theme update, after adviced  deletion of the 1st version. It works fine as far as I can tell for V4 maps.

But when I long tap the OS Map V4 theme icon in the theme list of LM4 beta and press validate, it shows a list of missing files in os_res/SVG and os_res/patterns subfolders.

Missing theme files often lead to a tile drawing failure, if it happens there is a POI or  pattern with such a missing file.

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

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

Well, the IT is in the 2nd part only. :-) I have posted it for general audience, as some may take it as useful info, others not so much.

Yes, the BRouter servers take from OSM the daily difference files, process them and make the related daily BRouter differential and full updates.

You can check yourself:
http://brouter.de/brouter/segments4/

For usual users nothing changes, they just notice in BRouter download manager less of data downloading and more of data processing.

The daily/frequent  updating makes sense mainly on the current data square only a/o if one impatiently waits for OSM update propagation.

Or, if one wants/needs to cut down the updating network data for whatever reason.

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

ETA in route planner:

If I use BRouter bicycle profiles in the route planner, it is my understanding the stats bar uses the ETA ( estimated time of arrival ) provided by Brouter, or by some internal defaults.

But if I make LocusMap calculate ETA by ETA estimation from the planner menu, none of ETA estimation profiles fits the stats ETA.

I think it could be good to optionally allow binding a particular ETA estimation profile to a particular Locus transportation mode.

Eventual votes at https://help.locusmap.eu/topic/consistence-of-eta-in-the-route-planner


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

Consider adding a regular routed segment as typing a letter on a keyboard, while adding a straight segment as a CAPITAL one.

Consider explicit profile switching to straight line as CAPS LOCK activation.

Consider long pressing route or + button as using SHIFTed letter to type just 1 or 2 CAPITALS.

What is wrong with SHIFT key ?

I see just 1 issue, why to use right SHIFT and not left, if right one is already taken ?


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

until this discussion I wasn't aware long-tap on + did anything, probably many Locus hidden gems in same category, but now I know the extra function I think its useful & consistent

Hi Andrew,

I have been trained by various  applications  and electronic devices to try long presses on control elements ...  "what if it does something ?" . Especially if I am not able to invoke a feature that is there.

I have discovered the long press "+" does what it does, without prior knowledge it should be somehow possible.

Similarly, long press "-" clears the planner (after confirmation).

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

I got it the same, as I have expressed above, which I see as quite nice.

( * = "long press routing button" )

+   = routing segment(via currently selected profile)
+   = another routing segment
*    = straight segment
+   = routing segment
*    = straight segment
*    = another straight segment
+   = routing segment

I do not use such approach often, but I understand for heavy off-road hikers it would be useful feature. It is not only a workaround for missing/wrong OSM mapping, but also for the true lack of OSM ways to be passed, or their intentional avoiding.

And LocusMap is for heavy off-road hikers more than most of other applications.

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

I remember something like a mentioned design or coding flaw in round trip generator in history logs, so perhaps @menion  has withdrawn it to put better one later.

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

It was fixed for LM4 alpha and LM3 beta. Stable LM3 free/pro have the bug yet, in my understanding.

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

For completeness, here are my bicycle and foot profiles, locally generated, named and packed in Android by Linux/bash script sedbatch (my GitHub repo) in termux Linux console.

Skilled users can do it any time to fetch up-to-date profiles, as the script is able to pull profile templates master and develop branches from my GitHub repository.

http://cloud.tapatalk.com/s/5e9072dd6f74e/BR-Bike-Profiles-develop-locus.zip


http://cloud.tapatalk.com/s/5e9072e94e6a4/BR-Bike-Profiles-master-locus.zip


http://cloud.tapatalk.com/s/5e907319904c2/BR-Foot-Profiles-master-locus.zip

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

I confirm the new Arndt's car profiles do have switches present if the switch defaults within the  profile are changed from false to 0.

In fact I did know it, noticing this issue earlier, when I was playing with generating car variants from Arndt's profiles, or combining my dry/wet bicycle profile variants into a single profile via my Linux/bash script on Android/termux.

But I have completely forgot about that.

There were originally available just 0/1 values for BRouter profile logical expressions. True/false values were implemented later and are currently preferred in newer profiles for explicit clarity. So it would definitely good to support them.

Note that uploaded Trekking-dry does work on BRouter 1.6.1, I use it all the time, exactly the copy I have provided.

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

It seems I am tracking the stats issue down..

I was playing with the planner, having set the start and setting/unsetting the shaping point in various directions and distances.

I have noticed that at the moment I set the shaping point, it often, but not always, immediately displays straight line statistics bar when the route computation begins. But it seems does not affect the issue occurance, that happen in both cases.

But I have also realized, that for the particular direction and distance, the issue REPRODUCIBLY occurs above a critical straight distance, but does not occur below  a critical distance.

For short enough segments, the stats reproducibly displays ( or updates itself to ) the true route stats.

For long enough segments, the stats reproducibly  display ( or remain )  the straight line stats.

The critical straight distance value varies for my device and region typically between 70-90 km,  so it may be related rather to the route computation time. For sparse road network it may be more.

If I add a short segment after the segment with wrong stats, it correctly updates the 1st segment partial stats for the totals. So e.g if I add 10 km long segment after (straight ) 100 km segment with wrong stats, the total distance stats may jump by e.g. 40 km.

So the work around is, after adding a long route segment, add ( and remove if not needed) a short segment to be sure stats are OK.

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

I miss the upper status bar. And I agree with "too white".

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