/** Recommended interpolation method for attitude ephemeris data. */
INTERPOLATION_METHOD,
// ----------------------------------------------
// Tracking Data Messages (TDM) specific keywords
// ----------------------------------------------
// TDM Header section
// ------------------
/** Header: TDM format version in the form of ‘x.y’, where ‘y’ shall be incremented for
* corrections and minor changes, and ‘x’ shall be incremented for major changes.
* <p>Obligatory: YES
*/
CCSDS_TDM_VERS,
// TDM meta-data section
// ---------------------
/** Meta-data: PARTICIPANT_n, n = {1, 2, 3, 4, 5}.<p>
* Participants in a tracking data sessions (spacecraft(s), ground station(s)...)
* <p>Obligatory: YES (at least 1)
*/
PARTICIPANT_1,
/** Participant 2. */
PARTICIPANT_2,
/** Participant 3. */
PARTICIPANT_3,
/** Participant 4. */
PARTICIPANT_4,
/** Participant 5. */
PARTICIPANT_5,
/** Meta-data: Tracking mode associated with data section of the segment.<p>
* - SEQUENTIAL: Applies only for range, Doppler, angles, and LOS ionosphere calibrations.
* The name implies a sequential signal path between tracking participants;<p>
* - SINGLE_DIFF: Applies for differenced data;<p>
* - In other cases, such as troposphere, weather, clocks, etc., use of the MODE keyword does not apply.
* <p>Obligatory: NO
*/
MODE,
/** Meta-data: The PATH keywords shall reflect the signal path by listing the index of each PARTICIPANT
* in order, separated by commas, with no inserted white space.<p>
* The first entry in the PATH shall be the transmit participant.<p>
* The non-indexed ‘PATH’ keyword shall be used if the MODE is SEQUENTIAL.<p>
* The indexed ‘PATH_1’ and ‘PATH_2’ keywords shall be used where the MODE is SINGLE_DIFF.<p>
* Examples:<p>
* - 1,2 = one-way;<p>
* - 2,1,2 = two-way;<p>
* - 3,2,1 = three-way;<p>
* - 1,2,3,4 = four-way;<p>
* - 1,2,3,2,1 = turn-around range with 1=primary station, 2=satellite, 3=secondary station.
* <p>Obligatory: NO
*/
PATH,
/** Path 1. */
PATH_1,
/** Path 2. */
PATH_2,
/** Frequency band for transmitted frequencies.
* <p>Obligatory: NO
*/
TRANSMIT_BAND,
/** Meta-data: Frequency band for received frequencies.
* <p>Obligatory: NO
*/
RECEIVE_BAND,
/** Meta-data: Turn-around ratio numerator. <p>
* Numerator of the turn-around ratio that is necessary to calculate the coherent downlink from the uplink frequency.
* <p>Obligatory: NO
*/
TURNAROUND_NUMERATOR,
/** Meta-data: Turn-around ratio denominator.
* <p>Obligatory: NO
*/
TURNAROUND_DENOMINATOR,
/** Meta-data: Timetag reference.<p>
* Provides a reference for time tags in the tracking data.<p>
* It indicates whether the timetag associated with the data is the transmit time or the receive time.
* <p>Obligatory: NO
*/
TIMETAG_REF,
/** Meta-data: Integration interval.<p>
* Provides the Doppler count time in seconds for Doppler data or for the creation
* of normal points.
* <p>Obligatory: NO
*/
INTEGRATION_INTERVAL,
/** Meta-data: Integration reference.<p>
* Used in conjunction with timetag reference and integration interval.<p>
* Indicates whether the timetag represents the start, middle or end of the integration interval.
* <p>Obligatory: NO
*/
INTEGRATION_REF,
/** Meta-data: Frequency offset.<p>
* A frequency in Hz that must be added to every RECEIVE_FREQ to reconstruct it.
* <p>Obligatory: NO
*/
FREQ_OFFSET,
/** Meta-data: Range mode.<p>
* COHERENT, CONSTANT or ONE_WAY.
* <p>Obligatory: NO
*/
RANGE_MODE,
/** Meta-data: Range modulus.<p>
* Modulus of the range observable in the units as specified by the RANGE_UNITS keyword.
* <p>Obligatory: NO
*/
RANGE_MODULUS,
/** Meta-data: The RANGE_UNITS keyword specifies the units for the range observable.<p>
* ‘km’ shall be used if the range is measured in kilometers.<p>
* ‘s’ shall be used if the range is measured in seconds.<p>
* 'RU' for "range units'
* <p>Obligatory: NO
*/
RANGE_UNITS,
/** Meta-data: The ANGLE_TYPE keyword shall indicate the type of antenna geometry represented in the angle data (ANGLE_1 and ANGLE_2 keywords).<p>
* The value shall be one of the following:<p>
* - AZEL for azimuth, elevation (local horizontal);<p>
* - RADEC for right ascension, declination or hour angle, declination (needs to be referenced to an inertial frame);<p>
* - XEYN for x-east, y-north;<p>
* - XSYE for x-south, y-east.
* <p>Obligatory: NO
*/
ANGLE_TYPE,
/** Reference frame in which data are given: used in combination with ANGLE_TYPE=RADEC.
* <p>Obligatory: NO
*/
REFERENCE_FRAME,
/** Meta-data: Transmit delays list (up to 5).<p>
* Specifies a fixed interval of time, in seconds, for the signal to travel from the transmitting
* electronics to the transmit point. Each item in the list corresponds to the each participants.
* <p>Obligatory: NO
*/
TRANSMIT_DELAY_1,
/** Second. */
TRANSMIT_DELAY_2,
/** Second. */
TRANSMIT_DELAY_3,
/** Second. */
TRANSMIT_DELAY_4,
/** Second. */
TRANSMIT_DELAY_5,
/** Meta-data: Receive delays list.<p>
* Specifies a fixed interval of time, in seconds, for the signal to travel from the tracking
* point to the receiving electronics. Each item in the list corresponds to the each participants.
* <p>Obligatory: NO
*/
RECEIVE_DELAY_1,
/** Second. */
RECEIVE_DELAY_2,
/** Second. */
RECEIVE_DELAY_3,
/** Second. */
RECEIVE_DELAY_4,
/** Second. */
RECEIVE_DELAY_5,
/** Meta-data: Data quality.<p>
* Estimate of the quality of the data: RAW, DEGRADED or VALIDATED.
* <p>Obligatory: NO
*/
DATA_QUALITY,
/** Meta-data: Correction angle 1.<p>
* Angle correction that has been added or should be added to the ANGLE_1 data.
* <p>Obligatory: NO
*/
CORRECTION_ANGLE_1,
/** Meta-data: Correction angle 2.<p>
* Angle correction that has been added or should be added to the ANGLE_2 data.
* <p>Obligatory: NO
*/
CORRECTION_ANGLE_2,
/** Meta-data: Correction Doppler.<p>
* Doppler correction that has been added or should be added to the DOPPLER data.
* <p>Obligatory: NO
*/
CORRECTION_DOPPLER,
/** Meta-data: Correction Range.<p>
* Range correction that has been added or should be added to the RANGE data.
* <p>Obligatory: NO
*/
CORRECTION_RANGE,
/** Meta-data: Correction receive.<p>
* Receive correction that has been added or should be added to the RECEIVE data.
* <p>Obligatory: NO
*/
CORRECTION_RECEIVE,
/** Meta-data: Correction transmit.<p>
* Transmit correction that has been added or should be added to the TRANSMIT data.
* <p>Obligatory: NO
*/
CORRECTION_TRANSMIT,
/** Meta-data: Correction applied ? YES/NO<p>
* Indicate whethers or not the values associated with the CORRECTION_* keywords have been
* applied to the tracking data.
* <p>Obligatory: NO
*/
CORRECTIONS_APPLIED,
// TDM Data section
// ----------------
// Signal related keywords.
/** Data: Carrier power [dBW].<p>
* Strength of the radio signal transmitted by the spacecraft as received at the ground station or at another spacecraft.
*/
CARRIER_POWER,
/** Data: Doppler instantaneous [km/s].<p>
* Instantaneous range rate of the spacecraft.
*/
DOPPLER_INSTANTANEOUS,
/** Data: Doppler integrated [km/s].<p>
* Mean range rate of the spacecraft over the INTEGRATION_INTERVAL specified in the meta-data section.
*/
DOPPLER_INTEGRATED,
/** Data: Carrier power to noise spectral density ratio (Pc/No) [dBHz]. */
PC_N0,
/** Data: Ranging power to noise spectral density ratio (Pr/No) [dBHz]. */
PR_N0,
/** Data: Range value [km, s or RU].
* @see #RANGE_UNITS
*/
RANGE,
/** Data: Received frequencies [Hz].<p>
* The RECEIVE_FREQ keyword shall be used to indicate that the values represent measurements of the received frequency.<p>
* The keyword is indexed to accommodate a scenario in which multiple downlinks are used.<p>
* RECEIVE_FREQ_n (n = 1, 2, 3, 4, 5)
*/
RECEIVE_FREQ_1,
/** Received frequency 2. */
RECEIVE_FREQ_2,
/** Received frequency 3. */
RECEIVE_FREQ_3,
/** Received frequency 4. */
RECEIVE_FREQ_4,
/** Received frequency 5. */
RECEIVE_FREQ_5,
/** Data: Received frequency [Hz].<p>
* Case without an index; where the frequency cannot be associated with a particular participant.
*/
RECEIVE_FREQ,
/** Data: Transmitted frequencies [Hz].<p>
* The TRANSMIT_FREQ keyword shall be used to indicate that the values represent measurements of a transmitted frequency, e.g., from an uplink operation.<p>
* The TRANSMIT_FREQ keyword is indexed to accommodate scenarios in which multiple transmitters are used.<p>
