Footpod pace as data field

string = "GPS Qual = " + Position.getInfo().accuracy;
string = "GPS SPD = " + posnInfo.speed.toString();
string = "ActInfo SPD = " + Act.getActivityInfo().currentSpeed;
string = "OnSnsr SPD = " + Speed;

string = "ActInfo CAD = " + Act.getActivityInfo().currentCadence;
string = "OnSnsr CAD = " + Cad;

string = " Timer = " + computeTimerTime();



I altered the SDK Position sample a little last time I was playing w/ the sensor.
basically the code above gets the output in the pic. Everything is the same. however, from the simulator, I do notice that between the 3 speed fields (GPS / ActivityInfo / OnSnr) I see that OnSnsnr is usually mili/1 seconds slower to update compared the GPS and ActInfo data - I do not however know what that means or it's significance)


I have even tested this "app" by using the footpod and the internal accelerometer. The test is simple
1) put watch on table
2) shake the footpod and see the data output

3) put footpod on table
3) shake the watch and see the data output

in both circumstances, the data output is duplicated between the OnSnsr and ActInfo - which basically tells me that the data is duplicated (tho I have no idea which one takes precedence - but I believe it should be footpod as priority then fallback to accelerometer as the 2ndary.



I also looked at the FIT file and this footpod calibration tool.
1) w/o any good algorithm, just using the "calibrated" footpod stride length can also not be as good I expect. One can't be entirely sure of the accuracy of one's footsteps and/or one's stride length for a long period of time.
2) It's all just another level of approximation I believe.

what are users expectations anyways?