no?
(http://tapatalk.imageshack.com/v2/14/11/28/61dc1c543fc5eafc2b2dc61b56c9b803.jpg)
yes
(http://tapatalk.imageshack.com/v2/14/11/28/7633cdf057a92b07f5b0902437a4ba28.jpg) (http://tapatalk.imageshack.com/v2/14/11/28/a75948a67f51ba27ed2657858a2cf4e5.jpg)
no again?
(http://tapatalk.imageshack.com/v2/14/11/28/bd4d93b59aaf3cb5f3cdaa566159541c.jpg)
it only works for zoom levels 10 / 11 ?
I did discuse about it but i think i was not understood:
http://help.locusmap.eu/topic/track-is-changing-colours-when-zooming
@ulmus
Quote from: ulmus on November 28, 2014, 12:21:49
I did discuse about it but i think i was not understood:
http://help.locusmap.eu/topic/track-is-changing-colours-when-zooming
topic from link was "altitude changes" - but
ohgood talk about "color coding by speed"...
@ohgood
please attach your track
once you have it please delete my post that carried the attachment. thank you
@gynta: what the difference? input data only, algorithm is the same... i think it should be, shouldn't it? Min is blue, max is red, thats all, what's the difference if input data is named 'speed' or 'altitude changes'? Something is wrong with coloring and zooming, that's all.
Quote from: ohgood on November 28, 2014, 19:36:59
once you have it please delete my post that carried the attachment. thank you
sure
'think you've changed the source manually and something went wrong
After delete this part (line 25687 to 25717) all works fine (here).
(http://s3.postimg.org/a8228k4cf/image.jpg) (http://postimg.org/image/a8228k4cf/) (http://s3.postimg.org/u3y1o3ldr/image.jpg) (http://postimg.org/image/u3y1o3ldr/) (http://s3.postimg.org/bd0prog73/image.jpg) (http://postimg.org/image/bd0prog73/) (http://s3.postimg.org/cgku3n0u7/image.jpg) (http://postimg.org/image/cgku3n0u7/)
wrong things in next post...
(http://s10.postimg.org/e242r7uk5/2014_11_28_200252.jpg) (http://postimg.org/image/e242r7uk5/) (http://s10.postimg.org/ltkspryph/2014_11_28_203751.jpg) (http://postimg.org/image/ltkspryph/) (http://s10.postimg.org/rkaz3i6ph/2014_11_28_204951.jpg) (http://postimg.org/image/rkaz3i6ph/)
Quote from: gynta on November 28, 2014, 21:01:38
Quote from: ohgood on November 28, 2014, 19:36:59
once you have it please delete my post that carried the attachment. thank you
sure
'think you've changed the source manually and something went wrong
After delete this part (line 25678 to 25717) all works fine (here).
(http://s3.postimg.org/a8228k4cf/image.jpg) (http://postimg.org/image/a8228k4cf/) (http://s3.postimg.org/u3y1o3ldr/image.jpg) (http://postimg.org/image/u3y1o3ldr/) (http://s3.postimg.org/bd0prog73/image.jpg) (http://postimg.org/image/bd0prog73/) (http://s3.postimg.org/cgku3n0u7/image.jpg) (http://postimg.org/image/cgku3n0u7/)
wrong things in next post...
ohhhhhhhhh now I know why !
I've been editing tracks (in locus) and everyone with basecamp has complained the tracks were broken. I couldn't find a reason, so I told them basecamp sucked.
oops
Thanks gynta for your help.
@ohgood: if you find an exact steps that cause mess in track, let me know, so I can simulate same issue on my device and fix it. Thanks!
Quote from: menion on December 01, 2014, 06:57:40
Thanks gynta for your help.
@ohgood: if you find an exact steps that cause mess in track, let me know, so I can simulate same issue on my device and fix it. Thanks!
so far I think it's my own doing. tracks have been edited after the fact to fix the over laps and double crosses. I Didn't realize this until I started looking at which ones were problematic.