This object is in archive!
Artificial Laps in My track/laps and statistic not displayed correctly when . tcx imported .
Solved
Hallo,
As seen on screenshots, when I import .tcx file in My tracks, it displays correctly in all tabs if the file does NOT contain any coursepoints. If it does, Track time (all) in Statistics displays incorect values as well as in Laps. Great visualisation of coursepoints in charts works flawlessly. I had this issue with files generated with javawa tool, bikeRideToasted, SportsTracks3 as well as with files created by my own application. Everything fine when I generate no coursepoints. Sample files I may provide. Best Regards, Radim.
Locus Pro 3.16.0
The same problem 
Good day Radim,
"Brandýs", like "Brandýs nad Labem"? :) Then we are maybe neighbours.
Anyway sample file is needed, so attach is here please. (maybe you will have to pack it to zip or just change extension to txt).
Thanks.
Good day Radim,
"Brandýs", like "Brandýs nad Labem"? :) Then we are maybe neighbours.
Anyway sample file is needed, so attach is here please. (maybe you will have to pack it to zip or just change extension to txt).
Thanks.
Hallo Menion!
Some description attached too!
Hallo Menion!
Some description attached too!
@Menion.
See attachment.
@Menion.
See attachment.
@Radim, thanks for a files. issue fixed!
@0709: "koko_vr_locus_out.gxp" has incorrect time at first point, not an issue in Locus. Second file seems to be fine.
@Radim, thanks for a files. issue fixed!
@0709: "koko_vr_locus_out.gxp" has incorrect time at first point, not an issue in Locus. Second file seems to be fine.
not an issue in Locus ?
The input tcx file (correctly timestamped) was converted by Locus. Result: false timestamped gpx output trackfile. All (tcx) associated coursepoints/trackpoints (trkpt) timestamps in the gpx (trkpt) track out -> false.
Result: Locus normal tcx input speed (18kmh) converted into a gpx track 'snail course" (0 kmh) speed. (statistics)
Convert to gpx was only used to show the timestamps problem. I used pc "gpx editor" for the screenshots.
Input correct tcx track (by Radim) -> Locus statistic -> Loooong tracktime !
I notice above message "fixed" ;-) = fine.
(In second gpx file, all false trkpt's timestamps from locus gpx out, corrected by a manual reedit ! )
Fixed ? ok.
not an issue in Locus ?
The input tcx file (correctly timestamped) was converted by Locus. Result: false timestamped gpx output trackfile. All (tcx) associated coursepoints/trackpoints (trkpt) timestamps in the gpx (trkpt) track out -> false.
Result: Locus normal tcx input speed (18kmh) converted into a gpx track 'snail course" (0 kmh) speed. (statistics)
Convert to gpx was only used to show the timestamps problem. I used pc "gpx editor" for the screenshots.
Input correct tcx track (by Radim) -> Locus statistic -> Loooong tracktime !
I notice above message "fixed" ;-) = fine.
(In second gpx file, all false trkpt's timestamps from locus gpx out, corrected by a manual reedit ! )
Fixed ? ok.
Thanks! Interesting.
Thanks! Interesting.
Replies have been locked on this page!