Supported Data Formats

KlvInjector supports the following metadata source formats.

Supported Sources

Offline Sources

• Binary MISB 0601.x files
• JSON files
• CSV files

note

One practical way to create compliant metadata files is to use the StExporter application.

Live Sources

• Binary MISB 0601.x packets
• JSON packets

Binary MISB 0601.x Files

Binary MISB 0601.x files are parsed directly. KlvInjector uses Tag 2, UNIX_TIME_STAMP, as the timing reference for injection. A file may contain multiple packets without delimiters.

JSON MISB 0601.x Files

JSON MISB 0601.x files are parsed directly, and Tag 2 is again used as the timing reference.

In JSON, keys correspond to MISB 0601, MISB 0102, and MISB 0903 tags. Example:

{
  "2": 1571297393442000,
  "3": "Test Mission",
  "4": "24",
  "10": "Test platform",
  "11": "EO",
  "12": "WGS84",
  "13": 41.093574735,
  "14": -104.868920271,
  "15": 2932.7,
  "16": 3.065,
  "17": 1.722,
  "18": 258.015625146,
  "19": -14.039062529,
  "20": 0,
  "21": 2283.61,
  "22": 0,
  "23": 41.105721789,
  "24": -104.851011161,
  "25": 1870.2,
  "26": 0.000879,
  "27": 0.000174,
  "28": 0.000034,
  "29": 0.001174,
  "30": -0.000829,
  "31": -0.000163,
  "32": -0.00003,
  "33": -0.001106,
  "47": 0,
  "48": {
    "1": 1,
    "2": 1,
    "3": "//IL",
    "4": "Impleotv test",
    "12": 2,
    "22": 9
  },
  "65": 9
}

JSON Formatted KLV

JSON-formatted KLV is a JSON object containing tag-value pairs. Nested standards such as MISB 0102 and MISB 0903 appear as nested JSON objects.

For offline processing, Tag 2 must be present so KlvInjector knows where to inject each packet.

[
  {
    "2": 1283400392599311,
    "3": "Frame 0, 00:00:000",
    "13": 32.155127061,
    "14": 34.834800006,
    "15": 0.0,
    "48": {
      "1": 1,
      "2": 1,
      "4": "ImpleoTV Test Mission",
      "12": 2,
      "22": 9
    },
    "65": 9,
    "72": 1490987362175778
  },
  {
    "2": 1283400392957660,
    "3": "Frame 1, 00:00:033",
    "13": 32.155127061,
    "14": 34.834800006,
    "15": 0.0,
    "48": {
      "1": 1,
      "2": 1,
      "4": "ImpleoTV Test Mission",
      "12": 2,
      "22": 9
    },
    "65": 9,
    "72": 1490987362175778
  }
]

Complex Types

Most tags map to numbers, strings, or arrays, but some tags use more structured JSON.

Tag 94. MIIS Core Identifier

"94": {
  "Version": 1,
  "SensorID": {
    "Quality": "Physical",
    "UUID": "F592-F023-7336-4AF8-AA91-62C0-0F2E-B2DA"
  },
  "PlatformID": {
    "Quality": "Virtual",
    "UUID": "16B7-4341-0008-41A0-BE36-5B5A-B96A-3645"
  }
}

Tag 115. Control Command

"115": [5, "Fly to Waypoint 1", "2008-10-24T00:13:29.913"]

The last time element is optional.

Tag 115 can also contain an array of commands:

"115": [
  [5, "Fly to Waypoint 1", "2022-04-24T00:13:29.913"],
  [6, "Fly to Waypoint 2"]
]

Tag 128. Wavelengths List

"128": [
  [21, 1000, 2000, "NNIR"]
]

Tag 130. Airbase Locations

"130": {
  "TakeOff": [38.841859, -77.036784, 3],
  "Recovery": [38.939353, -77.459811, 95]
}

CSV Files

CSV input is detected by parsing the first line, which is expected to contain the column descriptions.

MISB 0601.x CSV

The header contains either the MISB tag number or the official tag description. Example:

Checksum,UNIX Time Stamp,Mission ID,Platform Tail Number

Figure: Example MISB 0601 CSV file.

Unused columns may be omitted if no data is present for those tags.

Figure: Example partial MISB 0601 CSV file.

note

Nested standards such as MISB 0102 and MISB 0903 are not supported in CSV. Use JSON instead.

Generic MISB 0601.x CSV Legacy Format

The first line contains tag number plus description, for example:

1. Checksum,2. UNIX Time Stamp,3. Mission ID

Figure: Legacy MISB 0601 CSV format.

All MISB 0601 columns are expected to be present, though fields may be left empty.

Security Metadata Set In CSV

Security Local Set content can be provided in column 48 using this format:

• MISB 0102 tag number followed by .
• items separated by |

Figure: Security Local Set encoded in CSV.

Image Horizon Pixel Pack In CSV

Image Horizon Pixel Pack data in column 81 uses labeled integer fields such as Start X0, Start Y0, End X1, and End Y1, with optional latitude and longitude values. Items are separated by |.

Figure: Image Horizon Pixel Pack encoded in CSV.

RVT And VMTI In CSV

RVT Local Data Set, Tag 73, and VMTI Local Data Set, Tag 74, can be imported as Base64-encoded strings in their corresponding columns.