GitLab

• Update enum for status_source to include "simulated"
• Remove position as a required field
• Add a no_position_reason enum field to explain why the position has not been included

changed milestone to %CB-2024W37

added Partner::NOC Project::MAS-DT labels

changed the description

I'm still a bit uncomfortable with the idea of using a platform_status message to send something that isn't a platform status.

What we could do is create a simulated_waypoint message with the same data structure as the platform_status but different required fields.

That way positions receives 2 message types but passes them both through the same parser and ORI don't have to filter the platform_status messages. You could still add simulated to the status source enum as we might want simulated platform_status messages

So platform_status would still require position/latitude+longitude

..whereas simulated_waypoint would require waypoint/waypoint_latitude+waypoint_longitude. status_source enum = [simulated]

@ashmorr @owanes @trishna - Are you happy with my alternative approach to this ^?

unassigned @danjon

assigned to @danjon

Also if the real platform_status contains the real current waypoint and the plan is for the positions service to just do one thing then does that mean the real waypoint will get added to positions from every platform_status?

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

mentioned in merge request !49 (merged)

marked the task Update enum for status_source to include "simulated" as completed

marked the task Remove position as a required field as completed

changed the description

assigned to @trishna and unassigned @danjon

assigned to @danjon and unassigned @trishna

added Status::In Review label

closed