My feeling is that Xensr is much closer to actual jump heights. I say feeling because we did not have "camera-horizon" rig to verify outcome. But 6-7m jumps I'd say are impossible on that wind with twintip.
Xensr log: https://my.xensr.com/session/#!e6265c34 ... 0203/1349/
Woo3 spot: https://leaderboards.woosports.com/kite ... 54118b45bd
EDIT: Edited Woo3 link..
--
The graphs have all data but to correlate better normal distribution (avg and stddev) I acknowledge that only jumps registered to both devices should have been used.
EDIT: Correlated data is on my answer..
--
Timestamp correlated jump height graph Normal distribution of above graph --
Excel data, I don't know why at least with me code-tag renders this wrong..
Code: Select all
Time Woo3 (m) Xensr (m) X-gps time Note
1:38 1,60 Lifting board from the ground
2:54 6,4 4,23 16:06:01
4:16 7,1 4,52 16:07:23
4:41 5,9 4,04 16:07:47
5:51 7,2 4,46 16:08:58
6:31 6,3 4,31 16:09:38
7:13 4,9 4,22 16:10:20
10:03 5,7 3,7 16:13:10
11:10 2,1 1,74 16:14:15
2,27 16:15:35 Not registered on Woo3 or Woo timestamp problem
13:57 4,2 Not registered on Xensr, could be same as prev. X-jump
17:39 4,3 3,64 16:20:45
38:43 3,2 2,29 16:41:46 Riku riding
39:17 2,1 1,59 16:42:21
42:38 4,8 4,03 16:45:42
45:52 5,3 3,96 16:48:55
49:36 4,3 3,67 16:52:49
51:24 4 3,04 16:54:27
51:44 2 Not registered on Xensr
53:25 6,1 3,96 16:56:28 Jori riding
54:10 4,5 3,26 16:57:13
55:18 3,5 2,72 16:58:21
56:20 5 3,61 16:59:23
62:00 4,5 2,42 17:05:02 Woo3 goes to minute timestamp
64:00 6 3,91 17:07:55
65:00 2,4 2,08 17:08:53
66:00 4,7 3,82 17:10:01
69:00 2,4 1,91 17:12:35
70:00 7,2 4,01 17:13:41
73:00 3,3 2,19 17:16:36
81:00 5,5 3,61 17:24:44
83:00 1,3 Not registered on Xensr
91:00 4,2 3,03 17:34:24
101:00 5,4 Xensr out of battery, not on track
Woo3 Xensr
AVG 4,47 3,32
STDDEV 1,644396669 0,882835261