DescriptionThis may have a severe performance impact (potentially), but it'd be pretty awesome if we could calculate the distance travelled using Greater Circle on the lat/lons.
GPX track files normally contain a capture every 5 seconds or so, the usual inaccuracy with using greater circle shouldn't apply quite as dramatically here.
Activity
2013-11-17 20:16:09
2013-11-17 20:19:08
2013-11-17 20:19:08
2015-01-13 10:27:06
2015-01-13 10:27:06
2015-01-13 10:27:06
2015-01-13 10:27:06
2015-01-13 10:29:58
2015-01-13 10:50:02
2015-01-13 11:08:36
2015-01-13 11:33:12
The returned distance travelled was then calculated manually and using online calculators. Looks like the calculations are correct.
Commit 0312b20 refers.
Still need to push the distance out to an array of some form so that stats can be used/updated for each Segment/Track.
If the functionality is not enabled, the method calculateTravelledDistance will return _0_ which might get confusing somewhere down the line - it's probably worth having a list of which experimental features are enabled pushed to the metadata (have raised GPXIN-18 for implementation).
2015-01-13 11:37:10
Webhook User-Agent
View Commit
2015-01-13 12:52:56
It also incorporates a minor bugfix - when the location hadn't moved, the distance calculations were returning NAN. Have added a check so that 0 is returned in this instance.
2015-01-13 12:55:10
Webhook User-Agent
View Commit
2015-01-14 23:08:34
The resources required for the calculations aren't as high as originally expected either, so once stable and tested, this can be moved out of experimental features.
2015-04-15 10:07:05
Other than that, seems to work OK so closing FR.
2015-04-15 10:07:18
2015-04-15 10:07:18
2015-04-15 10:07:28