1     Definition 2     Functional Requirements 3     Syntax
4     Semantics 5    Conformance Testing 6     Performance Assessment

1      Definition

The sequence of Spatial Attitudes SA (SA1, SA2,…, SAi) and corresponding Times t (t1, t2, tj) planned to reach a Goal.

2      Functional Requirements

A Trajectory is composed of Segments. Each Segment is described by:

  1. The expected starting Spatial Attitude and Time (assigned only for the initial segment)
  2. The expected end Spatial Attitude and Time.

3      Syntax

https://schemas.mpai.community/OSD/V1.2/data/Trajectory.json

4      Semantics

Label Size Description
Header N1 Bytes Trajectory Header
– Standard-Trajectory 9 Bytes The characters “CAV-TRJ-V”
– Version N2 Bytes Major version – 1 or 2 Bytes
– Dot-separator 1 Byte The character “.”
– Subversion N3 Bytes Minor version – 1 or 2 Bytes
TrajectoryID N4 Bytes Identifier of Trajectory.
TrajectoryData[] 2 Bytes Data in the Trajectory
– StartSA N5 Bytes Spatial Attitude at StartTime
– EndSA N6 Bytes Spatial Attitude at EndTime
– Duration N7 Bytes Prescribed or expected Duration of Trajectory from start to destination.
DescrMetadata N8 Bytes Descriptive Metadata

5     Conformance Testing

A Data instance Conforms with Trajectory (OSD-TRJ) V1.2 if:

  1. The Data validates against the Trajectory ’s JSON Schema.
  2. All Data in the  Trajectory ’s JSON Schema
    1. Have the specified type
    2. Validate against JSON Schemas.
    3. Conform with their Data Qualifiers if present.

6     Performance Assessment