GET /udl/diffofarrival/tuple

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

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

Ob detection time in ISO 8601 UTC with microsecond precision.

Unique identifier of the target on-orbit object, if correlated.

Sensor ID of the primary/1st sensor used for this measurement.

Sensor ID of the secondary/2nd sensor used for this measurement.

Catalog number of the target on-orbit object.

Optional identifier to indicate the specific tasking which produced this observation.

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

Optional identifier provided by DOA source to indicate the primary/1st sensor identifier used for this measurement. This may be an internal identifier and not necessarily a valid sensor ID.

Optional identifier provided by DOA source to indicate the secondary/2nd sensor identifier used for this this observation. This may be an internal identifier and not necessarily a valid sensor ID.

Boolean indicating this observation is part of an uncorrelated track or was unable to be correlated to a known object. This flag should only be set to true by data providers after an attempt to correlate to an on-orbit object was made and failed. If unable to correlate, the 'origObjectId' field may be populated with an internal data provider specific identifier.

The signal arrival delay relative to sensor 1, in seconds.

The signal arrival delay relative to sensor 2, in seconds.

Sensor WGS84 latitude at obTime (if mobile/onorbit), in degrees. If null, can be obtained from sensor info. -90 to 90 degrees (negative values south of equator).

Sensor WGS84 longitude at obTime (if mobile/onorbit), in degrees. If null, can be obtained from sensor info. -180 to 180 degrees (negative values west of Prime Meridian).

Sensor altitude at obTime (if mobile/onorbit), in kilometers. If null, can be obtained from sensor info.

Line of sight azimuth angle for sensor 1, in degrees and topocentric frame. Azimuth ranges from 0 to 360 degrees.

Line of sight elevation angle for sensor 1, in degrees and topocentric frame. Elevation ranges from -90 to 90 degrees.

Sensor 2 WGS84 latitude at obTime (if mobile/onorbit), in degrees. If null, can be obtained from sensor info. -90 to 90 degrees (negative values south of equator).

Sensor 2 WGS84 longitude at obTime (if mobile/onorbit), in degrees. If null, can be obtained from sensor info. -180 to 180 degrees (negative values west of Prime Meridian).

Sensor 2 altitude at obTime (if mobile/onorbit), in kilometers. If null, can be obtained from sensor info.

Line of sight azimuth angle for sensor 2, in degrees and topocentric frame. Azimuth ranges from 0 to 360 degrees.

Line of sight elevation angle for sensor 2, in degrees and topocentric frame. Elevation ranges from -90 to 90 degrees.

Center frequency of the collect, in hertz.

Bandwidth of the signal, in hertz.

Delta range, in kilometers. Delta range calculation convention is (sensor2 - sensor1).

One sigma uncertainty in delta range, in kilometers.

Delta range rate, in kilometers per second. Delta range rate calculation convention is (sensor2 - sensor1).

One sigma uncertainty in the delta range rate, in kilometers per second.

Signal to noise ratio, in decibels.

Transponder polarization e.g. H - (Horizontally Polarized) Perpendicular to Earth's surface, V - (Vertically Polarized) Parallel to Earth's surface, L - (Left Hand Circularly Polarized) Rotating left relative to the earth's surface, R - (Right Hand Circularly Polarized) Rotating right relative to the earth's surface.

Time difference of arrival of the center frequency signal, in seconds. TDOA calculation convention is (sensor2 - sensor1).

One sigma uncertainty in time difference of arrival of the center frequency signal, in seconds.

The number of full signal cycles the time difference of arrival measurement could be shifted due to repeating patterns in the signal (0 = no ambiguity, +1 = one positive cycle ambiguity, -1 = one negative cycle ambiguity).

Frequency difference of arrival of the center frequency signal, in hertz. FDOA calculation convention is (sensor2 - sensor1).

One sigma uncertainty in frequency difference of arrival of the center frequency signal, in hertz.

Collection mode (e.g., DIRECTED_SEARCH, MANUAL, NEIGHBORHOOD_WATCH, SPOT_SEARCH, SURVEY, etc.).

Optional URI location in the document repository of the raw file parsed by the system to produce this record. To download the raw file, prepend https://udl-hostname/scs/download?id= to this value. This field should not be used unless coordinated with the UDL onboarding team.

Source of the data.

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.

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.

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.

Optional source-provided and searchable metadata or descriptor of the data.

Optional identifier to track a commercial or marketplace transaction executed to produce this data.

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

The source data library from which this record was received. This could be a remote or tactical UDL or another data library. If null, the record should be assumed to have originated from the primary Enterprise UDL.