Waypoint ID Tracking

[i25052i]

Mission

• When servicing a GET /queue request we refresh the queue using info from MissionPlanner, so as to provide the most up-to-date information.
• In the process, however, we lose the waypoint IDs sent to us by GCOM, because MissionPlanner does not track IDs and we are not storing them anywhere else.
• Wherever possible, we must restore these IDs before sending the queue back to the caller.

Execution

Some considerations:

• If the current mission we are executing was received through a previous POST /queue request, we should be able to compare the saved mission waypoints from that request with the waypoints returned from mission planner, pair waypoints together, and thus associate them back with their IDs.
• We should take care to support the IDs of waypoints sent through /prepend and /append, as well as sequential GET /queue requests.
• Waypoints/missions created from endpoints where the caller does not specify waypoints (for example, /takeoff overwrites the queue with a takeoff mission` will necessarily not have an ID. What sort of default value/signal should we return to the caller?
• Consider adding a parameter to GET /queue for users that don't wish to trigger this update (e.g. GET /queue?refresh=false)