Need to know more about the use-case the user has in mind, do they want the actual coordinates for max/min (so an actual lat/lon pair) or are they simply interested in extracting the maximum/minimum recorded latitude - essentially meaning those stats properties will simply be decimal.
One option might be to make the relevant stats property an object in itself, so we'd have something like
The user has said they need square bounds on a per-file, per-track and per-segment basis. Makes sense, it'd allow you (for example) to easily extract the bounds to pass into Google Maps to ensure it's correctly centred around the track you're displaying.
Activity
2016-02-20 19:37:11
One option might be to make the relevant stats property an object in itself, so we'd have something like
Which would give the option of either, but then when retrieving it you'd have to do something like
Which feels a bit ugly and un-necessary
2016-02-20 19:40:32
2016-02-20 19:49:57
2016-02-20 19:51:08
2016-02-20 20:17:09
2016-02-20 20:17:17
2016-02-20 20:17:30
Webhook User-Agent
View Commit
2016-02-20 20:17:32
2016-02-20 20:31:50
- the entire file
- each track
- each segment
Running a print_r() on each gives
2016-02-20 20:32:57
2016-02-20 20:33:29
Webhook User-Agent
View Commit
2016-02-20 20:53:18
2016-02-20 20:53:31
2016-02-20 20:53:31
2016-02-20 20:53:35