GET /udl/attitudeset/history

Unique identifier of the record, auto-generated by the system.

Classification marking of the data in IC/CAPCO Portion-marked format.

Unique identifier of the on-orbit satellite to which this attitude set applies.

Satellite/catalog number of the on-orbit object to which this attitude set applies.

Optional identifier provided by the record source to indicate the target object of this attitude set. This may be an internal identifier and not necessarily map to a valid satellite number.

The type of attitude message or messages associated with this set.

AEM = Attitude Ephemeris Message, specifying the attitude state of a single object at multiple epochs.

APM = Attitude Parameters Message, specifying the attitude state of a single object at a single epoch.

Unique identifier of the parent (positional) Ephemeris Set, if this data is correlated with an Ephemeris.

Unique identifier of the sensor to which this attitude set applies IF this set is reporting a single sensor orientation.

Optional identifier provided by the record source to indicate the sensor identifier to which this attitude set applies IF this set is reporting a single sensor orientation. This may be an internal identifier and not necessarily a valid sensor ID.

The epoch or start time of the attitude parameter or attitude ephemeris, in ISO 8601 UTC format, with microsecond precision. If this set is constituted by a single attitude parameter message then startTime is the epoch.

The end time of the attitude ephemeris, in ISO 8601 UTC format, with microsecond precision. If this set is constituted by a single epoch attitude message then endTime should match the startTime.

Reference frame 1 of the quaternion or Euler angle transformation utilized in this attitude parameter or attitude ephemeris. The UDL convention is that transformations occur FROM frame1 TO frame2. A specific spacecraft frame or instrument name may be provided with the assumption the consumer understands the location of these frames (ex. SC BODY, J2000, LVLH, ICRF, INSTRUMENTx, THRUSTERx, etc.).

Reference frame 2 of the quaternion or Euler angle transformation utilized in this attitude parameter or attitude ephemeris. The UDL convention is that transformations occur FROM frame1 TO frame2. A specific spacecraft frame or instrument name may be provided with the assumption the consumer understands the location of these frames (ex. SC BODY, J2000, LVLH, ICRF, INSTRUMENTx, THRUSTERx, etc.).

Number of attitude records contained in this set.

Attitude ephemeris step size, in seconds. This applies to Attitude Ephemeris Messages (AEM) that employ a fixed step size.

Initial precession angle (ECI J2000 frame) in degrees.

Initial spin angle (ECI J2000 frame) in degrees.

The rotation sequence of the Euler angles in which attitude reference frame transformation occurs (from left to right). One, two, or three axis rotations are supported and are represented by one, two, or three characters respectively. Repeated axis rotations are also supported, however, these rotations should not be sequential. The numeric sequence values correspond to the body angles/rates as follows: 1 - xAngle/xRate, 2 - yAngle/yRate, and 3 - zAngle/zRate. Valid sequences are: 123, 132, 213, 231, 312, 321, 121, 131, 212, 232, 313, 323, 12, 13, 21, 23, 31, 32, 1, 2, and 3.

The following represent examples of possible rotation sequences: A single rotation about the Y-axis can be expressed as '2', a double rotation with X-Z sequence can be expressed as '13', and a triple rotation with Z-X-Y sequence can be expressed as '312'.

Recommended interpolation method for estimating attitude ephemeris data.

Recommended polynomial interpolation degree.

Optional notes/comments for this attitude set.

Time the row was created in the database, auto-populated by the system.

Application user who created the row in the database, auto-populated by the system.

Source of the data.

Originating system or organization which produced the data, if different from the source. The origin may be different than the source if the source was a mediating system which forwarded the data on behalf of the origin system. If null, the source may be assumed to be the origin.

Indicator of whether the data is REAL, TEST, EXERCISE, or SIMULATED data:

REAL: Data collected or produced that pertains to real-world objects, events, and analysis.

TEST: Specific datasets used to evaluate compliance with specifications and requirements, and for validating technical, functional, and performance characteristics.

EXERCISE: Data pertaining to a government or military exercise. The data may include both real and simulated data.

SIMULATED: Synthetic data generated by a model to mimic real-world datasets.

The originating source network on which this record was created, auto-populated by the system.