search

AMSP-04 / NETN-ETR

NATO Education and Training Network (NETN) Entity Tasking and Reporting (ETR) Module
Other
2 stars 0 forks source link

Extra parameter MoveToLocation #65

Closed hendersonhc closed 8 months ago

hendersonhc commented 10 months ago

It should also be possible to define the optional path with a list of objects (uuid) instead of a list of locations or by an uuid of a path object.

In that case is is possible that the movement passes special waypoints or engineer bridges by using the location on which this objects are defined. So an extra optional parameters pathByObjects of type ArrayOfUuid is needed

lofstrandbjorn commented 10 months ago

This issue has already been discussed, and the conclusion was to limit the options on how to express locations (not only waypoints in the MoveToLocation task but on other tasks as well). The location of an object can be copied and put explicitly into the Move Task.

lofstrandbjorn commented 9 months ago

Investigate adding info on segments in a path e.g. bridge, road etc. + additional info on max weight, width etc. Might also solve the Formation issue when getting into a tight spot.

lofstrandbjorn commented 8 months ago

MoveByRoute task is updated to accommodate for more information on each segment.

lofstrandbjorn commented 8 months ago

Updated the Waypoint datatype to include SegmentMaxWidth in meters.