ADAPT - Guidance / GpsSource Discussion

Note: How do we want to use north & east offsets? When someone shifts a guidance line, should we modify the guidance line, record an event with the documentation / logged data, or clone the guidance line into a new object with different offsets? Is the operator nudging a guidance line something worth recording, or is it a non-repeatable event?

Decision to ignore nudge events pending additional input or use cases documenting a relevant need.

20150915: ISO handles this by capturing the nudge as a guidance offset element (tag GuidanceShift, GST) that is recorded as an event. It includes shift (2-D translation) and Offset (translation perpendicular to the track, which can involve a radius change.)

20150915: Q: Should we add GST elements for the purposes of ISO11783 conformance test compatibility?

A: The agreement is that we are inserting this for the strict purposes of passing AEF conformance tests, as opposed to scope creep. This would entail a) Creating the equivalent of the GST class. b) Creating the mechanism to insert it in the context of LoggedData, akin to an ASP.

Note: Decided to remove AdaptiveCurve guidance types in favor of creating a guidance group containing multiple AB Curve objects. Noted that AdaptiveCurve is a setting for the steering and guidance system rather than a valid type of predefined guidance line.

GuidanceAllocation

GuidanceGroup

 GuidanceShift

 GuidancePattern

GpsSource

GuidancePatternTypeEnum

GuidanceExtensionEnum

GpsSourceEnum

Sub-classes of GuidancePattern

APlus

AbLine

MultiAbLine

AbCurve

CenterPivot [Not Implemented]

Spiral

PivotGuidancePattern

PivotGuidanceDefinitionEnum