GET /udl/rfsignal/{id}
Changed onService operation to get a single RFSignal record by its unique ID passed as a path parameter.
Request
- Base URLhttps://unifieddatalibrary.com
- URLhttps://unifieddatalibrary.com/udl/rfsignal/{id}
- Authnone declared
Path parameters
The ID of the RFSignal to retrieve.
Query parameters
Response
OK
Unique identifier of the record, auto-generated by the system.
Classification marking of the data in IC/CAPCO Portion-marked format.
The RFFileType of the stored samples in the dataset file (e.g. SigMF, etc.).
The filename of the internal .zip file.
The size, in bytes, of the internal .zip file contained within the outer .zip. This refers to the compressed size of the internal archive as stored inside the parent archive and includes all contents of that internal archive (the data file and any optional metadata file). If a POST is provided without an associated internal .zip file, or an invalid filesize, the record will be rejected.
A text description of the RFSignal recording.
Satellite/catalog number of the target on-orbit object if the RF signal originates from an on-orbit source.
Optional identifier provided by the source to indicate the source object from which this RF Signal was received. This may be an internal identifier of and not necessarily map to a valid satellite number or other ground or mobile source.
Unique identifier of the target satellite on-orbit object to which this observational data applies. This ID can be used to obtain additional information on an OnOrbit object using the 'get by ID' operation (e.g. /udl/onorbit/{id}). For example, the OnOrbit with idOnOrbit = 25544 would be queried as /udl/onorbit/25544.
Unique identifier of the sensor from which this observational data was collected. This ID can be used to obtain additional information on a sensor using the 'get by ID' operation (e.g. /udl/sensor/{id}). For example, the sensor with idSensor = abc would be queried as /udl/sensor/abc.
Optional identifier provided by observation source to indicate the sensor identifier which produced this observation. This may be an internal identifier and not necessarily a valid sensor ID.
Sensor WGS84 latitude at startTime (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 startTime (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 startTime (if mobile/onorbit), in kilometers.
Optional identifier to indicate the specific tasking which produced this observation.
The sample rate of the signal in samples per second.
The result of applying the specified hash algorithm to the entity.
Name of the algorithm used to generate the hash for this entity (e.g., SHA-256, SHA-512, etc.).
RFSignal detection start time in ISO 8601 UTC with microsecond precision.
RFSignal detection end time in ISO 8601 UTC with microsecond precision.
The detected signal frequency, in hertz.
Azimuth angle in degrees and topocentric coordinate frame.
Elevation in degrees and topocentric coordinate frame.
Antenna offset from the platform azimuth angle, in degrees.
Antenna offset from the platform elevation angle, in degrees.
Boolean if antenna is offset from object pointing azimuth/elevation angle. If yes, then use antenna platform azimuth and antenna platform elevation fields.
The reference frame of the cartesian orbital states. If the reference frame is null it is assumed to be J2000.
Three element array, expressing the spacecraft position components, in kilometers, at the startTime, in the specified referenceFrame. The array element order is [x, y, z]. If the referenceFrame is null it is assumed to be J2000.
Three element array, expressing the spacecraft velocity components, in kilometers per second, at the startTime, in the specified referenceFrame. The array element order is [x', y', z']. If the referenceFrame is null it is assumed to be J2000.
Three element array, expressing the spacecraft acceleration components, in kilometers per second squared, at the startTime, in the specified referenceFrame. The array element order is [x'', y'', z'']. If the referenceFrame is null it is assumed to be J2000.
The received signal polarization (e.g. HORIZONTAL, VERTICAL, LEFT_HAND_CIRCULAR, RIGHT_HAND_CIRCULAR).
Additional metadata comments, if needed.
Sample index of the start of the signal in the dataset.
Number of samples in the dataset.
Start carrier frequency, in hertz.
End carrier frequency, in hertz.
Optional ID from external systems. This field has no meaning within UDL and is provided as a convenience for systems that require tracking of an internal system generated ID.
Optional identifier to track a commercial or marketplace transaction executed to produce this data.
Optional array of provider/source specific tags for this data, where each element is no longer than 32 characters, used for implementing data owner conditional access controls to restrict access to the data. Should be left null by data providers unless conditional access controls are coordinated with the UDL team.
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.
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.
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.
Changes
- info
endpoint added
- info
Some revisions have not been checked yet.