Messages

hi Andrew, thanks for a precise bug report. I'm playing with it on quite old SGS2, but unfortunately except certain slowness, I'm unable to simulate any crash or ANR (Application Not Responding).
I've anyway discovered that there is again a problem after editing track style and return back to map. There is some stuck of Locus for quite a long time, sometimes. Weird, still unsolvable problem for me, damn.

@menion - only single instance of ANR for me too but thought I'd mention it just in case it helped at all.

3.27.1.7 on Android 5.1: Analyze Track caused Locus to crash with 200km recorded track. To reproduce:

• tap track from list
• observe it seems to take longer to open track details since last version?
• tap ^
• tap More
• tap Analyze
• track is displayed on map but UI not responsive for ~20s
• when UI finally responds Locus stops with "Locus Map is not responding"
• retest (for this post) and now no crash, grrr

Question re Analyze Track UX: tap on "tick" icon - I see is possible to change track style; I change to +/-5% Manual Slope, but where is this new track style displayed? When I return to the map the track section is lost. It would be great if Analyze Track style could be sticky rather than plain dark blue line.

I then installed 3.27.1.27 on older Android 4.2 tablet: when I try Analyze Track for 1st time the 2 or 3? introductory pages about splitting and merging tracks is displayed which is for Track Editor not Analyze Track. Of course there is only one chance to test this because these "introductory pages" are only displayed once.

A little bit ... common stupid limitation on 1 MB for transfering content between screens. And this your track is so huge, that it's a little more then 1 MB so app crash.

@menion - longer tracks are entirely possible and not unreasonable, so maybe there is msgbox saying "This track is too large to edit this track in Route Planner; suggest split and edit each section?"

nice crash, thanks .

@menion - great - interesting reason?

The long press is handy, thanks I didn't know about the shortcut.

how to "discover" these often very useful shortcuts though? long tap every possible object and see whether there is hidden gem inside?

Newest Beta: "About app/Support" still not working...

Me too.

And more serious bug which occurs in 3.17.1 Pro and 3.27.1.5 beta: open the attached GPX with Route Planner: silent crash & restart of Locus. This file was originally created with RWGPS. Imported into Locus. GPX is exported from Locus. If more specific instructions useful: display track, tap track on map, select Route Planner, display goes blank, Locus is restarted.

[NO]

from: menion on September 27, 2017, 10:29:57
Export of shaping points into GPX is currently not implemented. Still not sure, if this is needed at all ... we will see
Usefull ?
Shaping Point: Has informative <name>and <description> NO <sym> !

export of shaping point would allow round-trip (export/ re-import) of a route? Quite useful.

[@balloni55]

@balloni55:
this is interesting. Other options in main menu works? Mainly add-ons and co-apps, that are made with exactly same system. exactly, behavior is identical on both of my devices

@balloni55 same problem for me

+1
maybe someone can create a help topic for voting?

Good day Andrew,
thank you for a precise description of a problem.

@menion - many more thanks to @0709 for the detailed analysis than to me (just reporting his work).

Hi Menione, in Beta there is a great way to re-calculate the route by long pressing the profile selection button. This is very good if you want to try different profiles. Would not it be possible to activate this feature in the PRO version?

@Žajdlík Josef - please vote +1 for my identical suggestion here - 5 votes so far.

Our hard working friend @0709 has created a very interesting and insightful test track to expose some current shortcomings with Locus slope filtering. What it shows is a smearing of track slope resulting a deceptively lower % at places where the slope is changing. Because SRTM elevation data is only every 30 x 40 metres it may not be possible to improve the situation much but I thought I'd ask...

Does this really matter? Well say there is a short sharp upcoming hill, say +20% slope, but only for 300 metres. Locus may only show this tortuous climb as +10%.

As shown here in Garmin Basecamp (also similar in Gps Visualizer) the attached test track has precise transitions
from 0% to 25%

Basecamp displays the slope accurately as 0%, +25% and -25%.

Locus on the other hand has quite aggressive filtering. The first +25% 'hill' starts at exactly 1.9km but the Locus chart shows the slope slowing increasing at 1.5km and only reaches the proper +25% at 2.3km.


If the track style is set to manual slope coloring -25% to +25% you would expect the color to be green from 0km to 1.9km then dark red/ brown after 1.9km. But instead the color starts changing thru various shades over a distance of 500 metres, starting before the hill even begins:


One real-world shortcoming is when a steep slope is less than 500m long. For example below the 25% slope is 200m long, then flat again. Locus calculates the slope as only 15%. And the track color is pale green/ orange for only 100m.

Hi @Menion - agreed the elevation is known and constant while stopped. So constant elevation = 0% gradient over that period of time. But I think even better is blank like speed.

Nice. That makes it very clear to see where no movement.

Probably odd combination to have in the chart - but I notice even with 3.27.1.2 beta that gradient on 2nd Y axis is still non-zero during places of no movement. Should be zero or not visible too.

ensure settings > tap on track: popup, not screen

tap on track > track info > tap on greater than > menu popup > tap on Show on elevation chart > 1st tab of track info is displayed and chart tab should then be selected/ chart displayed, but isn't.