This object is in archive!
Locus and Turtle speed. Not a direct real problem, but o soo strange.
Solved
Link: http://forum.locusmap.eu/index.php?action=dlattach;topic=5066.0;attach=3730
Selketal.gpx In this track by brouter, trkpt's are not timestamped.
After corrections by Locus Edit on map: See the new created, now timestamped track.
http://forum.locusmap.eu/index.php?action=dlattach;topic=5066.0;attach=3733
The average speed it represent = 0,2kmh ! The proof that Locus is designed for Turtle races ?
The same problem 
Hello Willy,
in rare cases when track do not have time values, Locus needs to generate these values. For now, Locus use 1m/s value during this "time generation", without possibility to modify this value.
Is this value causing any troubles anywhere?
Hello Willy,
in rare cases when track do not have time values, Locus needs to generate these values. For now, Locus use 1m/s value during this "time generation", without possibility to modify this value.
Is this value causing any troubles anywhere?
As said it is only strange. Not causing a real problem.
You already said before: 1m/sec....is that not representing 3,6 kmh ?
I have no problem with 3,6 kmh ! = Excellent value !
But I notice slooow 0,2 kmh average speed in Track time (all) statistic reported ?
No ? Am I wrong somehow ?
As said it is only strange. Not causing a real problem.
You already said before: 1m/sec....is that not representing 3,6 kmh ?
I have no problem with 3,6 kmh ! = Excellent value !
But I notice slooow 0,2 kmh average speed in Track time (all) statistic reported ?
No ? Am I wrong somehow ?
Hmm value seems to be based on total distance (1.5 km) and time difference between first and last point ( 7 hod). Why this happen, don't know. I'll be watching it, thanks anyway 0.2 km/h is really not an intent.
Hmm value seems to be based on total distance (1.5 km) and time difference between first and last point ( 7 hod). Why this happen, don't know. I'll be watching it, thanks anyway 0.2 km/h is really not an intent.
Issue will be fixed in next version. Final speed of generated tracks will be based on selected track activity or, in case of online GraphHopper for example, on speeds supplied by this service.
Issue will be fixed in next version. Final speed of generated tracks will be based on selected track activity or, in case of online GraphHopper for example, on speeds supplied by this service.
Locus & Timestamps - No happy marriage.
Timestamps generation NOK.
Track (wpt) contains some loops back in time.
Example generated timestamps by gpx 1.1 attached.
Locus & Timestamps - No happy marriage.
Timestamps generation NOK.
Track (wpt) contains some loops back in time.
Example generated timestamps by gpx 1.1 attached.
Whuuaa ... what app you use to display such crazy charts? I tried it in GPX Track editor and directly reimport into Locus and all was looking correctly!
Whuuaa ... what app you use to display such crazy charts? I tried it in GPX Track editor and directly reimport into Locus and all was looking correctly!
Reimport into Locus: Sure = Looks ok. Because of the in gpx 1.1 used Locus extension ;-)
In point list view (trk+wpt) remove timestamps by deleting element <timestamp> using gpx track editor.
Test: Regenerate new timestamps by another new export by Locus app.
See and check the new generated timestamps/point.
Pictures: By (pc) gpx track editor. In lower pane select graph type: Altitude - Speed - Angle - Distance
Confirmed in point list view:
And confirmed by text editor: See pt 54 to pt 55
<time>2018-03-20T23:10:24.821Z</time>
</trkpt>
<trkpt
lat="51.055159"
lon="4.004214"
>
<ele>2.85</ele>
<time>2018-03-20T23:05:51.351Z</time>
</trkpt>
Reimport into Locus: Sure = Looks ok. Because of the in gpx 1.1 used Locus extension ;-)
In point list view (trk+wpt) remove timestamps by deleting element <timestamp> using gpx track editor.
Test: Regenerate new timestamps by another new export by Locus app.
See and check the new generated timestamps/point.
Pictures: By (pc) gpx track editor. In lower pane select graph type: Altitude - Speed - Angle - Distance
Confirmed in point list view:
And confirmed by text editor: See pt 54 to pt 55
<time>2018-03-20T23:10:24.821Z</time>
</trkpt>
<trkpt
lat="51.055159"
lon="4.004214"
>
<ele>2.85</ele>
<time>2018-03-20T23:05:51.351Z</time>
</trkpt>
Ohm, I'm stupid!! Thanks, I see a problem. Fixed! (finally, or am I cursed? :) )
Ohm, I'm stupid!! Thanks, I see a problem. Fixed! (finally, or am I cursed? :) )
Replies have been locked on this page!