I agree with the observation in #19 that as we have "lat" and "lon", "ele" probably makes more sense.
However, "elevation" has been used in tracks for quite some time, so simply changing it would break backwards-compatability (no matter how limited the size of the user base). So need to take that into account too.
Although the documentation is behind in plenty of other ways, I've updated it to refer to "ele" instead of "elevation" (and added a note to explain the latter is deprecated) so that if anyone does follow it they don't wind up using the older attribute.
Activity
2017-07-04 10:18:05
However, "elevation" has been used in tracks for quite some time, so simply changing it would break backwards-compatability (no matter how limited the size of the user base). So need to take that into account too.
2017-07-04 10:29:30
Webhook User-Agent
View Commit
2017-07-04 10:36:52
2017-07-04 10:37:44
2017-07-04 12:19:06
- lat
- lon
- ele
So marking this as complete for now. Will raise a new issue if I find any I've missed.
2017-07-04 12:19:11
2017-07-04 12:19:11
2017-07-04 12:19:15