POST /udl/emireport

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

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

The type of Electromagnetic Interference (EMI) being reported (GPS, SATCOM, TERRESTRIAL).

The reporting time of this EMI Report record, in ISO 8601 UTC format, with millisecond precision.

User generated report identifier. This ID should remain the same on subsequent updates to this report.

The reporting status (INITIAL, UPDATE, RESOLVED) of this EMI issue.

The type of EMI (i.e. BARRAGE, CARRIER WAVE, etc.), if known.

The specific type of activity affected by the reported EMI (e.g. UPLINK, DOWNLINK, HF COMM, etc.).

The EMI start time in ISO 8601 UTC format, with millisecond precision.

The EMI end time in ISO 8601 UTC format, with millisecond precision. The endTime may be excluded if EMI is ongoing.

The persistence status (e.g. CONTINUOUS, INTERMITTENT, RANDOM, etc.) of the EMI.

The Area Of Responsibility (AOR), Organization, or Combatant Command under which the reported EMI pertains (AFRICOM, CENTCOM, EUCOM, INDOPACOM, NORTHCOM, SOCOM, SOUTHCOM, SPACECOM, STRATCOM, TRANSCOM, UNKNOWN).

The responsible service branch under which this EMI falls (AIR FORCE, ARMY, COAST GUARD, MARINES, NAVY).

The band (EHF, SHF, UHF, etc.) affected by the EMI.

The affected frequency, in MHz.

The highest affected frequency, in MHz.

The affected GPS Frequency (L1, L2, etc.).

Flag indicating whether encryption is in use on the affected GPS frequency.

The channel affected by the EMI.

The affected antenna type (e.g. DISH, OMNI, PHASED ARRAY, etc.) experiencing the EMI.

The gain setting of the affected receiver, in decibels (dB).

The demodulation method (e.g. AM, FM, FSK, PSK, etc.) setting of the affected receiver.

The beam pattern in use.

Flag indicating whether the EMI is a decipherable intercept over the affected receiver. Additional information may be included in the description field content of this record.

The type of transmission being intercepted (e.g. VOICE, etc.). Applicable when intercept = TRUE.

The language heard over the intercepted source. Applicable when interceptType = VOICE.

Flag indicating whether the interfering source is encrypted.

The modulation method (e.g. AM, FM, FSK, PSK, etc.) of the interfering source, if known.

The center frequency, in MHz, of the interfering source, if known.

The bandwidth, in MHz, of the interfering source, if known.

The relative amplitude, in decibels (dB), of the interfering source, if known.

Flag indicating whether this interference appears to be illegally passing traffic over a known channel.

Description of the affected receiver location.

WGS-84 latitude of the affected receiver, represented as -90 to 90 degrees (negative values south of equator).

WGS-84 longitude of the affected receiver, represented as -180 to 180 degrees (negative values west of Prime Meridian).

Altitude of the affected receiver, expressed in meters above WGS-84 ellipsoid.

The Military Grid Reference System (MGRS) location of the affected receiver. The Military Grid Reference System is the geocoordinate standard used by NATO militaries for locating points on Earth. The MGRS is derived from the Universal Transverse Mercator (UTM) grid system and the Universal Polar Stereographic (UPS) grid system, but uses a different labeling convention. The MGRS is used as geocode for the entire Earth. Example of a milgrid coordinate, or grid reference, would be 4QFJ12345678, which consists of three parts:

4Q (grid zone designator, GZD) FJ (the 100,000-meter square identifier) 12345678 (numerical location; easting is 1234 and northing is 5678, in this case specifying a location with 10 m resolution).

The location of the affected receiver, reported as a kill box.

The country code in which the EMI occurred or is occurring. This value is typically the ISO 3166 Alpha-2 two-character country code, however it can also represent various consortiums that do not appear in the ISO document. The code must correspond to an existing country in the UDL’s country API. Call udl/country/{code} to get any associated FIPS code, ISO Alpha-3 code, or alternate code values that exist for the specified country code.

The alternate country identifier in which the EMI occurred or is occurring. Specifies an alternate country code if the data provider code is not part of an official Country Code standard such as ISO-3166 or FIPS.

The name or identifier of the affected platform.

The name or identifier of the affected system.

The name of the spacecraft whose link is being affected by the EMI.

Satellite/Catalog number of the affected OnOrbit object.

Unique identifier of the affected on-orbit object. For the public catalog, the idOnOrbit is typically the satellite number as a string, but may be a UUID for analyst or other unknown or untracked satellites.

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

The name or identifier of the affected link.

The name or identifier of the affected sat transponder.

The uplink frequency, in MHz, of the impacted link.

The uplink polarization e.g. H - (Horizontally Polarized), V - (Vertically Polarized), L - (Left Hand Circularly Polarized), R - (Right Hand Circularly Polarized).

The downlink frequency, in MHz, of the impacted link.

The downlink polarization e.g. H - (Horizontally Polarized), V - (Vertically Polarized), L - (Left Hand Circularly Polarized), R - (Right Hand Circularly Polarized).

The priority (LOW, MEDIUM, HIGH) of the affected SATCOM.

Text description of the EMI particulars and other supporting information which may be relevant to the cause and/or possible resolution of the issue.

Actions(s) taken to troubleshoot, mitigate, work-around, and/or resolve the EMI impacts.

Flag indicating whether assistance is being requested to address this EMI.

Flag indicating whether the affected mission is an ISR mission.

Flag indicating whether this EMI is impacting ISR collection.

The victim functional impacts (e.g. C2, COMM DATA LINK, ISR SENSOR, PNT, etc.).

The ISR role of the impacted asset.

The victim reaction (e.g. LOITER ORBIT, RETASK ASSET, RETURN TO BASE, TROUBLESHOOT, etc.).

Duration, Nature, Extent of impact.

The Point of Contact (POC) for this EMI Report.

The Unit or Organization of the reporting POC.

The phone number of the reporting POC, represented as digits only, no spaces or special characters.

The e-mail contact of the reporting POC.

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

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.

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.

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.