The LuciadLightspeed Military Symbology API uses Symbol IDentification Codes (SIDC), such as "GFCPMOLAM------", to uniquely define and identify a military symbol. The APP-6A, APP-6B, MIL-STD-2525b and MIL-STD-2525c symbology standards also define a unique hierarchy code for each symbol in addition to the SIDC, the code "1.X.2.1.2.8.2" for example. The hierarchy code indicates the position of the symbol in a tree structure. Each hierarchy code maps to exactly one SIDC. For your convenience, this article provides a set of hierarchy-SIDC mapping property files to support your mapping use cases.

Why use symbol hierarchy codes?

In some cases, you may need to map hierarchy codes to SIDC and the other way around. You may need to integrate new software with an older service for example.

Why is there no symbol code conversion API in LuciadLightspeed?

To convert MIL-STD-2525B/C SIDC codes to hierarchy codes and the other way around, you can use the legacy class TLcdMS2525bCode2HierarchyMap. There is no counterpart for this class for the APP-6 standards, however.

The main reason for not offering a complete API for the conversion is that the newer symbology standards (APP-6C and MIL-STD-2525D) do not use the hierarchy codes anymore. Consequently, the addition of new conversion API might result in confusion, and the API would become legacy fairly quickly. Instead, you can use the properties files below, and implement your own mapping logic. The files contain the mappings between hierarchy codes and SIDC.

Table 1. Mapping property files
Standard File

MIL-STD-2525B

ms2525b.prop

MIL-STD-2525C

ms2525c.prop

APP6A

app6a.prop

APP6B

app6b.prop