This feature request is similar to how /tracking/<user_id>/json supports a last_update parameter to only fetch the latest points... but a bit different.
The idea is to be able to request the updates for a group of pilots from a given time so last_update should be a timestamp (number of seconds since January 1, 1970 12:00:00 AM).
The way last_update is implemented in /tracking/<user_id>/json would not work.
That's because in this case last_update is the number of seconds since prior midnight UTC of the first track point.
Let's say pilotA starts flying at 23:30 UTC and pilotB starts flying at 00:30 UTC then their reference day would be different and there is no one last_update value that is common to both. Making last_update a timestamp for the /tracking/<user_ids> endpoint would solve this.
Context: I am revamping the SkyLines tracker support into flyxc.app.
Thanks !
This feature request is similar to how
/tracking/<user_id>/jsonsupports alast_updateparameter to only fetch the latest points... but a bit different.The idea is to be able to request the updates for a group of pilots from a given time so
last_updateshould be a timestamp (number of seconds since January 1, 1970 12:00:00 AM).The way
last_updateis implemented in/tracking/<user_id>/jsonwould not work.That's because in this case
last_updateis the number of seconds since prior midnight UTC of the first track point.Let's say pilotA starts flying at 23:30 UTC and pilotB starts flying at 00:30 UTC then their reference day would be different and there is no one
last_updatevalue that is common to both. Makinglast_updatea timestamp for the/tracking/<user_ids>endpoint would solve this.Context: I am revamping the SkyLines tracker support into flyxc.app.
Thanks !