4aiman
0dd4a67e7b
Track 22 May showed 31km instead of 12.6km because 4 points had wrong seq order — native service and WebView GPS interleaved. Sorting by seq placed them wrong, creating 2km+ teleport jumps. Fixes: - All sort calls now use timestamp only (seq was unreliable) - computeStats skips segments > 180 km/h (GPS teleportation) - After recalculate: 22 May track should show ~12.6 km |
||
|---|---|---|
| .. | ||
| css | ||
| data | ||
| js | ||
| lib | ||
| index.html | ||