MAS-DT refactor region and exclusion zones into primitives in planning_configuration
Closed
MAS-DT refactor region and exclusion zones into primitives in planning_configuration
-
Decide on
types
language we want bothfeature.type
(human and flexible) andprimitive.type
(machine processable and fixed) -
Remove
region_of_interest
-
Remove
exclusion_zones
-
Define
primitive
schema-
feature
: GeoJSON:Feature -
instruction
(orrole
?) -enum
: [stay_inside
|stay_outside
|navigate_to
] (+ [follow
|repeat
|cover
..])
-
-
Add
primitives
array - Update test fixtures
-
GeoJSON properties is an object with no specific requirements
- Do we need to define required properties or do we add more properties to the parent primitive?
changed milestone to %CB-2024W35
added Partner::NOC Project::MAS-DT Status::Sprint Priority Weight::3 labels
@ashmorr : Are we also going to make the changes to the hydrogen UI to understand these new message definitions. I think for this project at least it's a useful debugging tool.
created merge request !38 (merged) to address this issue
mentioned in merge request !38 (merged)
added Status::In Progress label and removed Status::Sprint Priority label
assigned to @danjon
added Status::In Review label and removed Status::In Progress label
I considered using a
oneOf
to keep this backwards compatible in the same way as theplatform_status
but in the interests of moving forward decided against it.We can use the tagged version for any SoAR demos. We don't need the old
planning_configuration
to support existing implementations like we do with theplatform_status
. Hydrosurv don't implement it and our existing adapters don't implement it either. It's only hydrogen. I might do the work to make hydrogen understand both v1 and v2planning_configurations
so we don't have to worry about the hydrogen version.mentioned in issue #48 (closed)
mentioned in issue #41 (closed)
mentioned in issue #68