KLV Metadata Insertion
You can define a small set of static KLV objects (i.e., mission IDs and security classification) for KLV and CoT metadata sources. This allows customers to modify erroneous or insert missing metadata within outbound TS steams. These options are available:
- Configure a mission ID string of up to 127 characters: When the mission ID is configured, any received UAS KLV dataset will be processed in order to modify the existing mission ID or add a mission ID element if not there with the configured value.
- Enable or disable the update/generation of the security data set in UAS messages: When this feature is enabled, you then specify the classification (Unclassified, Restricted, Confidential, Secret, or Top Secret), the classifying country, and the object country/ies (up to 6) (using the proper ISO 3-letter country code).
In both cases, the mission ID or security data will get replaced or inserted with the ones created by the Makito X based on the configuration.
Example
To define a mission ID (up to 127 characters long):
# metadata 1 set missionid="XYZ" |
To unconfigure the insertion/modification of the mission ID element:
# metadata 1 set missionid=none |
To enable security modification/insertion:
# metadata 1 set reclassify=on classification=confidential objcountry=afg |
To disable the insertion and modification of the security data set:
# metadata 1 set reclassify=off |
Related Topics