Closed damjanev closed 4 years ago
Same here, I am using ROX6.0 and most of the time , data can't be merged , due to different reasons : Stops at red light , pauses to sort out mechanical issues and so on. At the time I use python script which attempts to adjust timing based on markers with type =='l' , thus I have some errors to iron out, so I won't be posting it here yet.
Have you tried to use Edit > Fix Gaps to remove the gaps before merging? It is documented in https://github.com/GoldenCheetah/GoldenCheetah/wiki/UG_Special-Topics_Activity-Processing#edit-tool-fix-gaps-in-recording
I run into the same problem and created a python-script. You can find it in https://github.com/grmpl/Sigma_SLF_Pythonscripts
Hi there.
I'm trying to use GoldenCheetah to combine the positioning data from a smartphone app (GPX/TCX) with a HR, cadence and temperature data from my Sigma ROX 5.0 cyclocomputer. The "combine activity" feature seems to be the one to go but i have issue when the activity has stops (and they almost always have stops). The Sigma ROX device stops recording, while the exports from the GPS/sports apps that i use (all of them) still record the breaks. Time ticking with zero speed. This makes the two recordings unmergable :-(
By briefly analyzing the possible export formats from Sigma DATACENTER application, i have concluded that, when exporting to SLF, there are tags at the end of the document that indicate lap markings and breaks that are not imported into GoldenCheetah. There is a tags for each lap and/or break. If GoldenCheetah can process the type="p" markers (pause) an insert them into the activity as stopped time (clock keeps ticking, speed is zero, cadence is zero, HR and temperature can be either zero or interpolate with last recorded value), then there will be no issue with merging the activities. Type="l" markers are lap markers. It's a nice feature to have, but not necessary.
<Markers>
section after the<Entries>
section withSample:
`<?xml version="1.0" encoding="utf-8"?>