--- title: "GET /udl/missiletrack" method: GET path: "/udl/missiletrack" tags: ["Track"] --- # GET /udl/missiletrack `GET /udl/missiletrack` ## Request - Base URL: `https://unifieddatalibrary.com` - URL: `https://unifieddatalibrary.com/udl/missiletrack` - Auth: none declared Service operation to dynamically query data by a variety of query parameters not specified in this API documentation. See the queryhelp operation (`/udl//queryhelp`) for more details on valid/required query parameter information. ## Query parameters - `ts` string, date-time, required - `firstResult` integer - `maxResults` integer ## Response `200` OK - MissileTrackAbridged[] - `id` string: Unique identifier of the record, auto-generated by the system if not provided on create operations. - `classificationMarking` string, required: Classification marking of the data in IC/CAPCO Portion-marked format. - `msgType` string: The type of external message from which this request originated. - `msgSubType` string: The message subtype is a finer grain categorization of message types as many messages can contain a variety of data content within the same structure. Examples include but are not limited to Initial, Final, Launch, Update, etc. Users should consult the appropriate documentation, based on the message type, for the definitions of the subtypes that apply to that message. - `msgCreateDate` string, date-time: The timestamp of the external message from which this request originated, if applicable, in ISO8601 UTC format with millisecond precision. - `env` 'AIR' | 'LAND' | 'SPACE' | 'SURFACE' | 'SUBSURFACE' | 'UNKNOWN': The track environment type (AIR, LAND, SPACE, SUBSURFACE, SURFACE, UNKNOWN): AIR: Between sea level and the Kármán line, which has an altitude of 100 kilometers (62 miles). LAND: On the surface of dry land. SPACE: Above the Kármán line, which has an altitude of 100 kilometers (62 miles). SURFACE: On the surface of a body of water. SUBSURFACE: Below the surface of a body of water. UNKNOWN: Environment is not known. - `objType` string: The type of object to which this record refers. The object type may be updated in later records based on assessment of additional data. - `objTypeConf` integer: Confidence of the object type, 0-100. - `objPlat` string: Space Platform field along with the Space Activity field further defines the identity of a Space track (examples: SATELLITE, WEAPON, PATROL). The object platform type. Intended as, but not constrained to, MIL-STD-6016 environment dependent platform type designations. The platform type can be reported as either a combination of the code and environment (e.g. 14/LAND) or as the descriptive representations (e.g. COMBAT VEHICLE), which are equivalent. - `objIdent` 'ASSUMED FRIEND' | 'FRIEND' | 'HOSTILE' | 'NEUTRAL' | 'PENDING' | 'SUSPECT' | 'UNKNOWN': The estimated identity of the track object (ASSUMED FRIEND, FRIEND, HOSTILE, NEUTRAL, PENDING, SUSPECT, UNKNOWN): ASSUMED FRIEND: Track assumed to be a friend due to the object characteristics, behavior, and/or origin. FRIEND: Track object supporting friendly forces and belonging to a declared friendly nation or entity. HOSTILE: Track object belonging to an opposing nation, party, group, or entity deemed to contribute to a threat to friendly forces or their mission due to its behavior, characteristics, nationality, or origin. NEUTRAL: Track object whose characteristics, behavior, nationality, and/or origin indicate that it is neither supporting nor opposing friendly forces or their mission. PENDING: Track object which has not been evaluated. SUSPECT: Track object deemed potentially hostile due to the object characteristics, behavior, nationality, and/or origin. UNKNOWN: Track object which has been evaluated and does not meet criteria for any standard identity. - `spaceAmp` string: Space amplification indicates additional information on the space environment being reported (examples: NUCLEAR WARHEAD, FUEL-AIR EXPLOSIVE WARHEAD, DEBRIS). - `objAct` string: Space activity (examples: RECONNAISSANCE, ANTISPACE WARFARE, TELEVISION). The activity in which the track object is engaged. Intended as, but not constrained to, MIL-STD-6016 environment dependent activity designations. The activity can be reported as either a combination of the code and environment (e.g. 65/AIR) or as the descriptive enumeration (e.g. DIVERTING), which are equivalent. - `spaceSpecType` string: Specific type of point or track with an environment of space. - `acftSubType` string: Subtype is a finer grain categorization of missile types. Examples include but are not limited to SRBM, MRBM, IRBM, LRBM, ICBM, SLBM. SRBM - Short-Range Ballistic Missile MRBM - Medium-Range Ballistic Missile IRBM - Intermediate-Range Ballistic Missile LRBM - Long-Range Ballistic Missile ICBM - Intercontinental Ballistic Missile SLBM - Submarine-Launched Ballistic Missile. - `name` string: Track name. - `callSign` string: The call sign currently assigned to the track object. - `lostTrkInd` boolean: Indicates whether or not the missile is considered lost. - `trackId` string: Track ID within the originating system. - `parentTrackId` string: Track ID of the parent track, within the originating system, from which the track was developed. - `muidSrcTrk` string: Track ID for the source of the missile-unique identifier. - `muidSrc` string: Source of the missile-unique identifier (MUID). - `alert` string: A track may be designated as a non-alert track or an alert track. Examples include but are not limited to: Non-alert tracks - choose None (Blank). Alert tracks - enter the proper alert classification: HIT - High Interest Track TGT - Target SUS - Suspect Carrier NSP - Cleared Suspect. - `mslStatus` string: Missile status enumeration examples include but are not limited to: AT LAUNCH AT OBSERVATION FLYING IMPACTED LOST STALE DEBRIS. - `ts` string, date-time, required: The receipt time of the data by the processing system, in ISO8601 UTC format with microsecond precision. - `aouRptType` string: The Area of Uncertainty (AoU) type (BEARING, ELLIPSE, OTHER) definition. This type defines the elements of the aouEllp array and is required if aouEllp is not null. See the aouEllp field definition for specific information. - `aouRptData` number[]: Three element array representing an Area of Uncertainty (AoU). The array element definitions and units are type specific depending on the aouType specified in this record: ``` ELLIPSE: brg - orientation in degrees of the ellipse a1 - semi-major axis in kilometers a2 - semi-minor axis in kilometers BEARING (BEARING BOX or MTST BEARING BOX): brg - orientation in degrees of the bearing box a1 - length of bearing box in kilometers a2 - half-width of bearing box in kilometers OTHER (All other type values): brg - line of bearing in degrees true a1 - bearing error in degrees a2 - estimated range in kilometers. ``` - `containment` number, double: The percentage of time that the estimated AoU will "cover" the true position of the track. - `trkConf` number, double: Overall track confidence estimate (not standardized, but typically a value between 0 and 1, with 0 indicating lowest confidence). - `trkQual` integer: Track Quality is reported as an integer from 0-15. Track Quality specifies the reliability of the positional information of a reported track, with higher values indicating higher track quality; i.e., lower errors in reported position. - `angElev` number, double: Angle of elevation/depression between observer and missile in degrees. - `senMode` string: Last report type received from the sensor (for example, OBSBO = observation burnout). - `infoSource` string: Source code for source of information used to detect track. - `boosting` boolean: Indicates whether or not the missile is currently in a state of boosting. - `polarSingLocLat` number, double: Azimuth corridor reference point latitude. - `polarSingLocLon` number, double: Azimuth corridor reference point longitude. - `emgInd` boolean: Indicates whether or not a track has an emergency. - `dropPtInd` boolean: The drop-point indicator setting. - `spaceAmpConf` integer: Confidence level of the amplifying characteristics. Values range from 0 to 6. - `launchTime` string, date-time: Missile launch timestamp in ISO8601 UTC format with microsecond precision. - `launchLat` number, double: WGS-84 latitude of the missile launch point, in degrees. -90 to 90 degrees (negative values south of equator). - `launchLon` number, double: WGS-84 longitude of the missile launch point, in degrees. -180 to 180 degrees (negative values west of Prime Meridian). - `launchAlt` number, double: Estimated launch point altitude relative to WGS-84 ellipsoid, in kilometers. - `launchAz` number, double: Angle between true north and the object's current position, with respect to the launch point, in degrees. 0 to 360 degrees. - `launchAzUnc` number, double: Uncertainty of the launch azimuth, in degrees. - `launchConf` number, double: Confidence level in the accuracy of the launch point estimate. 0 - 100 percent. - `azCorr` number, double: Missile azimuth corridor data. - `burnoutAlt` number, double: Track point burnout altitude relative to WGS-84 ellipsoid, in kilometers. - `launchAouType` string: The Area of Uncertainty (AoU) type (BEARING, ELLIPSE, OTHER) definition. This type defines the elements of the aouEllp array and is required if aouEllp is not null. See the aouEllp field definition for specific information. - `launchAouData` number[]: Three element array representing an Area of Uncertainty (AoU). The array element definitions and units are type specific depending on the aouType specified in this record: ``` ELLIPSE: brg - orientation in degrees of the ellipse a1 - semi-major axis in kilometers a2 - semi-minor axis in kilometers BEARING (BEARING BOX or MTST BEARING BOX): brg - orientation in degrees of the bearing box a1 - length of bearing box in kilometers a2 - half-width of bearing box in kilometers OTHER (All other type values): brg - line of bearing in degrees true a1 - bearing error in degrees a2 - estimated range in kilometers. ``` - `impactTime` string, date-time: Estimated time of impact timestamp in ISO8601 UTC format with microsecond precision. - `impactLat` number, double: WGS-84 latitude of the missile object impact point, in degrees. -90 to 90 degrees (negative values south of equator). - `impactLon` number, double: WGS-84 longitude of the missile object impact point, in degrees. -180 to 180 degrees (negative values west of Prime Meridian). - `impactAlt` number, double: Estimated impact point altitude relative to WGS-84 ellipsoid, in kilometers. - `impactAouType` string: The Area of Uncertainty (AoU) type (BEARING, ELLIPSE, OTHER) definition. This type defines the elements of the aouEllp array and is required if aouEllp is not null. See the aouEllp field definition for specific information. - `impactAouData` number[]: Three element array representing an Area of Uncertainty (AoU). The array element definitions and units are type specific depending on the aouType specified in this record: ``` ELLIPSE: brg - orientation in degrees of the ellipse a1 - semi-major axis in kilometers a2 - semi-minor axis in kilometers BEARING (BEARING BOX or MTST BEARING BOX): brg - orientation in degrees of the bearing box a1 - length of bearing box in kilometers a2 - half-width of bearing box in kilometers OTHER (All other type values): brg - line of bearing in degrees true a1 - bearing error in degrees a2 - estimated range in kilometers. ``` - `impactConf` number, double: Confidence level of the impact point estimate. 0 - 100 percent. - `maneuverStart` string, date-time: Maneuver start time, in ISO 8601 UTC format with microsecond precision. - `maneuverEnd` string, date-time: Maneuver end time, in ISO 8601 UTC format with microsecond precision. - `contextKeys` string[]: An optional string array containing additional data (keys) representing relevant items for context of fields not specifically defined in this schema. This array is paired with the contextValues string array and must contain the same number of items. Please note these fields are intended for contextual use only and do not pertain to core schema information. To ensure proper integration and avoid misuse, coordination of how these fields are populated and consumed is required during onboarding. - `contextValues` string[]: An optional string array containing the values associated with the contextKeys array. This array is paired with the contextKeys string array and must contain the same number of items. Please note these fields are intended for contextual use only and do not pertain to core schema information. To ensure proper integration and avoid misuse, coordination of how these fields are populated and consumed is required during onboarding. - `vectors` MissileTrackVectorAbridged[]: Array of MissileTrackVector objects. Missile track vectors are cartesian vectors of position, velocity, and acceleration that, together with their time, 'epoch', uniquely determine the trajectory of the missile. ECEF is the preferred coordinate frame but in some cases data may be in another frame as specified by 'referenceFrame', depending on the provider. - `type` string: Type of vector represented (e.g. LOS, PREDICTED, STATE). - `object` string: Object to which this vector applies. - `epoch` string, date-time, required: Vector timestamp in ISO8601 UTC format, with microsecond precision. - `idSensor` string: Unique identifier of the reporting sensor of the object. - `origSensorId` string: Optional identifier provided by the source to indicate the reporting sensor of the object. This may be an internal identifier and not necessarily a valid sensor ID. - `pos` number[]: Three element array, expressing the cartesian position vector of the target object, in kilometers, in the specified referenceFrame. If referenceFrame is null then ECEF should be assumed. The array element order is [x, y, z]. - `vel` number[]: Three element array, expressing the cartesian velocity vector of the target object, in kilometers/second, in the specified referenceFrame. If referenceFrame is null then ECEF should be assumed. The array element order is [x', y', z']. - `accel` number[]: Three element array, expressing the cartesian acceleration vector of the target object, in kilometers/second^2, in the specified referenceFrame. If referenceFrame is null then ECEF should be assumed. The array element order is [x'', y'', z'']. - `course` number, double: Track object course, in degrees clockwise from true north. - `spd` number, double: Track object speed, in kilometers/sec. - `referenceFrame` string: The reference frame of the cartesian vector (ECEF, J2000). If the referenceFrame is null it is assumed to be ECEF. - `cov` number[]: Covariance matrix, in kilometer and second based units, in the specified covReferenceFrame. If the covReferenceFrame is null it is assumed to be UVW. The array values (1-45) represent the upper triangular half of the position-velocity-acceleration covariance matrix. The covariance elements are position dependent within the array with values ordered as follows: ``` x y z x' y' z' x" y" z" x 1 2 3 4 5 6 7 8 9 y 10 11 12 13 14 15 16 17 z 18 19 20 21 22 23 24 x' 25 26 27 28 29 30 y' 31 32 33 34 35 z' 36 37 38 39 x" 40 41 42 y" 43 44 z" 45 ``` The cov array should contain only the upper right triangle values from top left down to bottom right, in order. - `covReferenceFrame` 'J2000' | 'UVW' | 'EFG/TDR' | 'ECR/ECEF' | 'TEME' | 'GCRF': The reference frame of the covariance elements (J2000, UVW, EFG/TDR, ECR/ECEF, TEME, GCRF). If the referenceFrame is null it is assumed to be UVW. - `vectorLat` number, double: WGS-84 object latitude subpoint at epoch, represented as -90 to 90 degrees (negative values south of equator). - `vectorLon` number, double: WGS-84 object longitude subpoint at epoch, represented as -180 to 180 degrees (negative values west of Prime Meridian). - `vectorAlt` number, double: Object altitude at epoch, expressed in kilometers above WGS-84 ellipsoid. - `confidence` integer: Confidence of the vector, 0-100. - `status` string: Status of the vector (e.g. INITIAL, UPDATE). - `propagated` boolean: Flag indicating whether the vector data was propagated. - `vectorTrackId` string: Vector track ID within the originating system or sensor. - `timeSource` string: Source of the epoch time. - `quat` number[]: The quaternion describing the attitude of the spacecraft with respect to the reference frame listed in the 'referenceFrame' field. The array element order convention is the three vector components, followed by the scalar component. - `flightAz` number, double: The flight azimuth associated with the current state vector (0-360 degrees). - `range` number, double: Range from the originating system or sensor to the object, in kilometers. - `contextKeys` string[]: An optional string array containing additional data (keys) representing relevant items for context of fields not specifically defined in this schema. This array is paired with the contextValues string array and must contain the same number of items. Please note these fields are intended for contextual use only and do not pertain to core schema information. To ensure proper integration and avoid misuse, coordination of how these fields are populated and consumed is required during onboarding. - `contextValues` string[]: An optional string array containing the values associated with the contextKeys array. This array is paired with the contextKeys string array and must contain the same number of items. Please note these fields are intended for contextual use only and do not pertain to core schema information. To ensure proper integration and avoid misuse, coordination of how these fields are populated and consumed is required during onboarding. - `origNetwork` string: The originating source network on which this record was created, auto-populated by the system. - `createdAt` string, date-time: Time the row was created in the database. - `createdBy` string: Application user who created the row in the database. - `source` string, required: Source of the data. - `origin` string: 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. - `dataMode` 'REAL' | 'TEST' | 'SIMULATED' | 'EXERCISE', required: 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. ## Other responses - `400`: Bad Request - `401`: Invalid/Missing User Credentials - `403`: User Is Not Authorized - `405`: Method Not Allowed - `406`: MediaType Not Accepted by Request Headers - `429`: Rate of Requests Exceeds Allowed Limit - `500`: Internal Server Error ## Changes > 12 revisions in range; 1 could not be searched. - **2026-03-25** `173e4aff893f`: 7 breaking - the `items/aouRptData` response property's minItems was decreased from `3` to `0` for the response status `200` - the `items/impactAouData` response property's minItems was decreased from `3` to `0` for the response status `200` - the `items/launchAouData` response property's minItems was decreased from `3` to `0` for the response status `200` - the `items/vectors/items/accel` response property's minItems was decreased from `3` to `0` for the response status `200` - …3 more - **2025-10-23** `09bd422d5ac1`: 1 warning, 1 info - added the new `ECR/ECEF` enum value to the `items/vectors/items/covReferenceFrame` response property for the response status `200` - removed the `ECEF` enum value from the `items/vectors/items/covReferenceFrame` response property for the response status `200` - **2025-09-26** `45631f9bb3f0`: 15 info - added the optional property `items/contextKeys` to the response with the `200` status - added the optional property `items/contextValues` to the response with the `200` status - added the optional property `items/impactAlt` to the response with the `200` status - added the optional property `items/impactConf` to the response with the `200` status - …11 more - …earlier changes not shown [Operation history](https://skmtc.dev/bluestaq/apis/unified-data-library-services-api/changes/udl/missiletrack/get.md) --- [API](https://skmtc.dev/bluestaq/apis/unified-data-library-services-api.md) - [All operations](https://skmtc.dev/bluestaq/apis/unified-data-library-services-api/llms.txt) - [OpenAPI document](https://skmtc.dev/bluestaq/apis/unified-data-library-services-api/revisions/bd17bc53681e?raw)