POST /udl/collectrequest

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

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

The unique ID of the collect request record from which this request originated. This may be used for cases of sensor-to-sensor tasking, such as tip/cue operations.

The type of external message from which this request originated.

The timestamp of the external message from which this request originated, if applicable, in ISO8601 UTC format with millisecond precision.

The type of this collect or contact request (DIRECTED SEARCH, DWELL, OBJECT, POL, RATE TRACK, SEARCH, SOI, STARE, TTC, VOLUME SEARCH, etc.).

Unique identifier of the parent plan or schedule associated with this request. If null, this request is assumed not associated with a plan or schedule.

Index number (integer) for records within a collection plan or schedule.

Task ID associated with this request. A task ID may be associated with a single collect request or may be used to tie together the sub-requests of a full collect, for example a DWELL consisting of many dwell points.

The dwell ID associated with this request. A dwell ID is dwell point specific and a DWELL request consist of many dwell point requests.

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.

Unique identifier of the requested/scheduled/planned sensor associated with this request. If both idSensor and origSensorId are null then the request is assumed to be a general request for observations or contact on an object, if specified, or an area/volume. In this case, the requester may specify a desired obType.

Optional identifier provided by the source to indicate the sensor identifier requested/scheduled/planned for this request. This may be an internal identifier and not necessarily a valid sensor ID. If both idSensor and origSensorId are null then the request is assumed to be a general request for observations or contact on an object, if specified, or an area/volume. In this case, the requester may specify a desired obType.

Optional type of observation (EO, IR, RADAR, RF-ACTIVE, RF-PASSIVE, OTHER) requested. This field may correspond to a request of a specific sensor, or to a general non sensor specific request.

The priority of the collect request (EMERGENCY, FLASH, IMMEDIATE, PRIORITY, ROUTINE).

The (SSN) tasking category (1-5) associated with this request. The tasking category defines the priority of gathering and transmitting the requested observational data. Note that category definitions are sensor type specific.

The (SSN) tasking suffix (A-Z) associated with this request. The suffix defines the amount of observational data and the frequency of collection. Note that suffix definitions are sensor type specific.

Boolean indicating that this collect request is UCT follow-up.

The start time or earliest time of the collect or contact request window, in ISO 8601 UTC format.

The end time of the collect or contact request window, in ISO 8601 UTC format. If no endTime or duration is provided it is assumed the request is either ongoing or that the request is for a specified number of tracks (numTracks). If both duration and endTime are provided, the endTime is assumed to take precedence.

Unique identifier of the target on-orbit object for this request.

Satellite/catalog number of the target on-orbit object for this request.

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

The tasking group to which the target object is assigned.

Inter-Range Operations Number. Four-digit identifier used to schedule and identify AFSCN contact support for booster, launch, and on-orbit operations.

The orbit regime of the target (GEO, HEO, LAUNCH, LEO, MEO, OTHER).

The minimum object (diameter) size, in meters, to be reported.

The minimum Radar Cross-Section of the target, in m^2. If only minimum RCS is provided it is assumed to be minimum reportable RCS.

The Radar Cross-Section of the target, in m^2.

The maximum Radar Cross-Section of the target, in m^2.

The minimum frequency of interest, in MHz. If only minimum frequency is provided it is assumed to be minimum reportable frequency.

The estimated or expected emission frequency of the target, in MHz.

The maximum frequency of interest, in MHz.

The RF polarization (H, LHC, RHC, V).

The minimum estimated or expected visual magnitude of the target, in Magnitudes (M). If only minimum vismag is provided it is assumed to be minimum reportable vismag.

The estimated or expected visual magnitude of the target, in Magnitudes (M).

The maximum estimated or expected visual magnitude of the target, in Magnitudes (M).

The spectral model used for the irradiance calculation.

The fraction of solar energy reflected from target.

The target object irradiance value.

For optical sensors, the requested number of frames to capture at each sensor step.

For optical sensors, the frame rate of the camera, in Hz.

For optical sensors, the integration time per camera frame, in milliseconds.

The number of requested tracks on the target. If numTracks is not provided it is assumed to indicate all possible observations every pass over the request duration or within the request start/end window.

The number of requested observations on the target.

The duration of the collect request, in seconds. If both duration and endTime are provided, the endTime is assumed to take precedence.

The search pattern to be executed for this request (e.g. PICKET-FENCE, SCAN, etc.).

Pre-coordinated code, direction, or configuration to be executed by the sensor or site for this collect or contact.

ID of the UDL Elset of the object associated with this request.

ID of the UDL Manifold Elset of the object associated with this request. A Manifold Elset provides theoretical Keplerian orbital elements belonging to an object of interest's manifold describing a possible/theoretical orbit for an object of interest for tasking purposes.

ID of the UDL State Vector of the object or central vector associated with this request.

ID of the UDL Ephemeris Set of the object associated with this request.

Epoch time, in ISO 8601 UTC format, of the orbital elements.

The average of the periapsis and apoapsis distances, in kilometers. For circular orbits, the semimajor axis is the distance between the centers of the bodies.

The orbital eccentricity of an astronomical object is a parameter that determines the amount by which its orbit around another body deviates from a perfect circle.

The angle, in degrees, between the equator and the orbit plane when looking from the center of the Earth. Inclination ranges from 0-180 degrees, with 0-90 representing posigrade orbits and 90-180 representing retrograde orbits.

Right ascension of the ascending node, or RAAN is the angle as measured in degrees eastwards (or, as seen from the north, counterclockwise) from the First Point of Aries to the ascending node.

The argument of perigee is the angle, in degrees, formed between the perigee and the ascending node.

The true anomaly defines the angular position, in degrees, of the object on it's orbital path as measured from the orbit focal point at epoch. The true anomaly is referenced from perigee.

The expected or directed right ascension angle, in degrees, for search or target acquisition.

The expected or directed declination angle, in degrees, for search or target acquisition.

The expected or directed azimuth angle, in degrees, for search or target acquisition.

The expected or directed elevation angle, in degrees, for search or target acquisition.

The expected acquisition range or defined center range, in km.

The extent of the azimuth angle, in degrees, from center azimuth to define a spatial volume.

The extent of the elevation angle, in degrees, from center elevation to define a spatial volume.

The extent of the range, in km, from center range to define a spatial volume.

WGS-84 latitude, in degrees. -90 to 90 degrees (negative values south of equator). If an accompanying stopLat is provided, then the lat value can be assumed to be the starting latitude of a volume definition.

WGS-84 longitude, in degrees. -180 to 180 degrees (negative values west of Prime Meridian). If an accompanying stopLon is provided, then lon value can be assumed to be the starting longitude of a volume definition.

Height above WGS-84 ellipsoid (HAE), in kilometers. If an accompanying stopAlt is provided, then alt value can be assumed to be the starting altitude of a volume definition.

The stopping WGS-84 latitude of a volume definition, in degrees. -90 to 90 degrees (negative values south of equator). The stopLat value is only meaningful if a (starting) lat value is provided.

The stopping WGS-84 longitude of a volume definition, in degrees. -180 to 180 degrees (negative values west of Prime Meridian). The stopLon value is only meaningful if a (starting) lon value is provided.

The stopping HAE WGS-84 height above ellipsoid (HAE), of a volume definition, in kilometers. The stopAlt value is only meaningful if a (starting) alt value is provided.

The maximum inclination, in degrees, to be used in search operations.

The angular distance, in degrees, in the sensor-x direction from scan center defined by the central vector. The specification of xAngle and yAngle defines a rectangle of width 2xAngle and height 2yAngle centered about the central vector.

The angular distance, in degrees, in the sensor-y direction from scan center defined by the central vector. The specification of xAngle and yAngle defines a rectangle of width 2xAngle and height 2yAngle centered about the central vector.

The magnitude of rotation, in degrees, between the xAngle direction and locally defined equinoctial plane. A positive value indicates clockwise rotation about the sensor boresight vector.

The customer for this request.

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

Notes or comments associated with this request.

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.

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

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.