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.

changed the description

created merge request !41 (merged) to address this issue

mentioned in merge request !41 (merged)

changed the description

marked the task Add current target waypoint as completed

marked the task Change coordinates to GeoJSON references as completed

marked the task Use oneOf to allow either target_waypoint:geojson.Point or target_waypoint_latitude/longitude:float to maintain backwards compatibility as completed

I think we should be able to keep the formats backwards compatible by using a oneOf to allow either geojson features or the existing geography properties.

changed milestone to %CB-2024W35

added Partner::NOC Project::MAS-DT Status::In Review Weight::2 labels

mentioned in issue #60 (closed)

assigned to @danjon

mentioned in merge request !45 (merged)

changed milestone to %CB-2024W37

closed

mentioned in issue #68