Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Andrew Heard

Pages: [1] 2 3 ... 30
Versions / Re: [APP] - version 3.27.+ ( 8. 11. 2017 )
« on: Today at 23:05:26 »
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.

Troubles & Questions / Can slope filtering be improved?
« on: Yesterday at 11:13:09 »
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 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.

I normally set chart X axis to distance, but today needed to accurately measure time stopped (3 places). To my surprise these times @ 78, 106 and 281 minutes show non-zero speed! All 3 times the line is perfectly straight over periods of many minutes (5, 14, 4 minutes respectively), clearly unlikely for a cyclist of my ability. It appears the speed at beginning of the stop is displayed as last non-zero speed, and straight line is then drawn to first non-zero speed once riding again.

Black vertical lines show period while speed should be 0km/h:

Versions / Re: [APP] - version 3.27.+ ( 8. 11. 2017 )
« on: November 12, 2017, 22:37:14 »
3.27.1 Pro: @menion:
  • ANR - fixed
  • icons in slope coloring - even spacing and excellent

Versions / Re: [APP] - version 3.27.+ ( 8. 11. 2017 )
« on: November 12, 2017, 03:29:09 »
@Andrew Heard:
ANR means "application not responding". This happen when app do too much work on background (longer then 5 seconds). Then you see dialog "Application is not responding" with option "wait" or "close". This should be your case here and log is not useful, because app did not crash, it just do something ... if you leave app for some time, it should start working again.
@menion - only for my interest I tapped ANR Wait 10+ times with quite long wait in between but Locus never responded. So looking forward to next release :D

Versions / Re: [APP] - version 3.27.+ ( 8. 11. 2017 )
« on: November 11, 2017, 21:53:42 »
@Andrew Heard:
hmm thanks. No useful in logs, but I think I was able to simulate this problem. Not sure why this happen, but one small change seems to fixed it, so next version as well ... (probably tomorrow).
@menion - "No useful in logs" - that's a shame because it generates huge (15MB) file and was lots of effort (long story) getting it emailed. Is there something I could do better next time? I waited until Locus crash then created the log as quickly as possible.

Versions / Re: [APP] - version 3.27.+ ( 8. 11. 2017 )
« on: November 11, 2017, 03:28:30 »
@Andrew Heard:
2. "crashed"? Like real force close of app? Then I'll need a log. Otherwise as I mentioned in help desk topic > improved.
Map screen freezes. Very repeatable - display track on map, tap on track, return to map, repeat a few times. Android says Locus Map is not responding etc. I have emailed log direct (15MB). Attached is GPX. It seems related to the manual slope track style. I have never seen this before, even in last beta.

@Andrew Heard:
4. this is caused by very old problem in BRouter ( expect that other sources do not have this problem, right?), that I've fixed by this ugly hack. Should be improved, agree ...
I hadn't seen a direct line at start and end of track.

Versions / Re: [APP] - version 3.27.+ ( 8. 11. 2017 )
« on: November 08, 2017, 23:01:00 »
3.27: great release, as usual.
  • @menion recall a recent discussion & change in 2 screens to not use auto-display keyboard? One was track export. I notice for Track Folder the keyboard is auto displayed with track name field selected, whereas it is just as likely or more likely the user may want to edit the track style.
  • Locus crashed with track slope mode+Arrows #3. Not for many many months has there been a crash. There was big variation of spacing of the arrow icons along track. Some places arrows merged into solid line, other places there was much bigger (and sensible) gap. See also (related but not the same issue)

  • Release notes screen - tap More Info button - bad URL. Even the copyright is 2014.

  • Route planner: is incorrectly using direct line at start and end of route. Behavior has changed since I have selected Car for routing. This route is impossible and incorrect. There is no OSM way at the start/ end as drawn. I have attached v1.1 exported GPX. I'll have to use RWGPS route planner until this is fixed.
PS - reopened 3.27.0 which had above track displayed. Completely frozen. After a few attempts was able to hide this track. Now Locus is usable again.

Versions / Re: [APP] - version 3.26.+ ( 11. 10. 2017 )
« on: November 02, 2017, 01:11:57 »
@menion: track style screen is now much more responsive on older tablet. Thanks.

Versions / Re: [APP] - version 3.26.+ ( 11. 10. 2017 )
« on: October 30, 2017, 02:43:46 »
5. I have settings > Maps > Points & Tracks > Tap on track=Screen. However tap on track on map briefly shows track popup before track screen. Is it now slower displaying this track screen too? When I return to map this popup is again displayed.
@menion - actually this behavior is in 3.26.2 Pro release as well, not just beta.

Versions / Re: [APP] - version 3.26.+ ( 11. 10. 2017 )
« on: October 29, 2017, 00:12:42 »
    @Andrew Heard:
    2) not sure here. I was thinking about it a lot and for me cancel/save at bottom should confirm whole style edit screen. Also from practical point of view, you usually set colors etc. and then you try set limits on this altitude or slope colors and then? You wants to return to map as fast as possible, right?[/li][/list]
    @menion the user may be changing any number of style settings. I see no reason for special quick return from min/max limits screen - the pencil icon has other settings below - width/ outline/ close line. Why would you expect settings limits be the last change before return to map? To me tapping Save on limits screen is just to save min/ max settings, not to confirm all other settings.

    I've for now only reduced dynamic palette from 40 to 20 colors, but I'll look at it closer. I'm anyway surprised that green is so dominant. You are coloring some faked track to achieve this? May you share it with me? Thanks
    I have attached GPX thanks to @0709 - so track below is latest with, and green quite dominant:


    Versions / Re: [APP] - version 3.26.+ ( 11. 10. 2017 )
    « on: October 28, 2017, 00:07:18 » Line/ track/ route styles general comment: from my initial testing the new functionality is a fantastic advance. Well done @Menion. I have done a comparison of certain tracks pre/ version with 0..6% slope. Now the new color is mostly red and exactly how my body remembers how hard the cycling actually was. Bravo!
    • the new track style UI is slower to respond - very slow on older tablet, a little slower on Xperia Z1 phone
    • tapping Save button from new Slope or Altitude min/max screen returns to track info screen but should return to track style screen
    • I suggest the new Slope screen Manual "min value" should allow minus values, at present only >= 0% is possible but I may for example want slope color palette range +/-10%
    • therefore at present all -ve slope % is only blue, I guess because blue is below current min 0% value?
    • I have settings > Maps > Points & Tracks > Tap on track=Screen. However tap on track on map briefly shows track popup before track screen. Is it now slower displaying this track screen too? When I return to map this popup is again displayed.

    @0709 & others have done a lot of work with color palette suggestions. The current Locus palette is very dominated by green, with very uneven transition between colors. :

    I really like 0709's proposed 9 color palette:

    Because there is no blending of colors, or maybe just less colors, if I saw a particular color (slope %) on a map I would be confident I would know what % slope this color represents.

    There is also a 15 color version, but for me, more colors with only subtle differences, means it becomes harder to tell which color represents a specific band of slope or altitude.

    Pages: [1] 2 3 ... 30