The headers of the ride data are extended by obsDistanceLeft1,obsDistanceLeft2,obsDistanceRight1,obsDistanceRight2,obsClosePassEvent
and XL,YL,ZL,RX,RY,RZ,RC.
obsDistanceLeft1,obsDistanceLeft2,obsDistanceRight1,obsDistanceRight2: Usually, these are double values of the measured distances by the OpenBikeSensor on the left and right side respectively.
obsClosePassEvent usually contains whether the line has a near miss incident.
But OpenBikeSensor is not supported in the iOS version yet. To achieve consistent data across rides from iOS and Android, these fields still need to be added. However, their content should be empty (",,,,").
The full header as of now looks like this: lat,lon,X,Y,Z,timeStamp,acc,a,b,c,obsDistanceLeft1,obsDistanceLeft2,obsDistanceRight1,obsDistanceRight2,obsClosePassEvent,XL,YL,ZL,RX,RY,RZ,RC
The headers of the ride data are extended by
obsDistanceLeft1,obsDistanceLeft2,obsDistanceRight1,obsDistanceRight2,obsClosePassEventandXL,YL,ZL,RX,RY,RZ,RC.obsDistanceLeft1,obsDistanceLeft2,obsDistanceRight1,obsDistanceRight2: Usually, these are double values of the measured distances by the OpenBikeSensor on the left and right side respectively.obsClosePassEventusually contains whether the line has a near miss incident. But OpenBikeSensor is not supported in the iOS version yet. To achieve consistent data across rides from iOS and Android, these fields still need to be added. However, their content should be empty (",,,,").The full header as of now looks like this:
lat,lon,X,Y,Z,timeStamp,acc,a,b,c,obsDistanceLeft1,obsDistanceLeft2,obsDistanceRight1,obsDistanceRight2,obsClosePassEvent,XL,YL,ZL,RX,RY,RZ,RC