GitLab

• Add current target waypoint
• Change coordinates to GeoJSON references
• Use oneOf to allow either target_waypoint:geojson.Point or target_waypoint_latitude/longitude:float to maintain backwards compatibility
• Add simulated type and simulation run id Figure out simulations later

(simulation outcomes could be a set of platform status messages - if that were the case we would need to be able to separate them from real status messages and re-compose them into a track per simulation run)

My main concern with doing it this way is we would have to read and parse x000 messages to show a single campaign simulation result whereas if we create a new simulated_track message (name and schema TBD) or even a single simulation_outcome message then we parse fewer messages.

One question to answer is how we want to store and use the simulations at our end.

I wonder if we store those simulated tracks as a timebound specification primitive which we show to the users but don't include in the planning_configuration sent to the backbone.