Milsymbol Mapping: Difference between revisions

Latest revision as of 19:40, 15 November 2025

Milsymbol Mapping

The "MilSymMapper" class provides methods for mapping draw object SIDC between the milsymbol versions: APP6D and APP6C. The result contains the result and status of the result. If the mapping is ambiguous, additional results are contained in the result (result.AdditionalResults).

Examples of Usage

var resources= new DrawObjectCommonResources(...);

// Get APP6D sidc from 15 character MIL-STD-2525C sidc
var result_d = resources.MilSymMapper.MapAPP6CToAPP6D("SUGPUSTA--A----");
var code = result_d.Code;

// Get APP6D sidc from APP6C hierarchy code.
var result_d = MapAPP6CHierarchyCodeToAPP6D("TACGRP.CSS.PNT.SPT.GNL");
var code = result_d.Code;

// Get 15 character MIL-STD-2525C sidc from APP6D sidc 
var result_c = resources.MilSymMapper.MapAPP6DToAPP6C("100301000011010400000000000000");
var code = result_c.Code;

// Get APP6C hierarchy code from APP6D sid.
var result_c = MapAPP6DToAPP6CHierarchyCode("100025000032050000000000000000");
var code = result_c.Code;

The MilSymMapper can also be created without using the DrawObjectCommonResources:

var milsymMapper = new MilSymMapper();

For compatible mapping between draw objects in MARIA GDK 4 and MARIA GDK 5 the following API can be used:

// Get GDK 4 compliant hierarchy code from APP6D sidc.
var id_c = GetGDK4CompliantSIDC("100025000032050000000000000000");

// Get GDK 5 compliant sidc from MIL-STD2525C hierarchy code.
var id_d = GetGDK5CompliantSIDC("TACGRP.CSS.PNT.SPT.GNL);

How to Update Mapping Between APP6D and APP6C

There are two files handeling mapping between APP6C and APP6D:

C2DMapping.csv, handels mapping from APP6C to APP6D
D2CMapping.csv, handels mapping from APP6D to APP6C

Each file contains one line per mapping and is a comma separated list of values. The first line in each file contains a descriptive name of each "column".

The File C2DMapping.csv

C_SymbolCode,D_Sidc,C_HierarchyCode,Status
S*A*M-----*****,100001000011000000000000000000,WAR.AIRTRK.MIL,

The File D2CMapping.csv

D_Sidc,C_SymbolCode,C_HierarchyCode,Status
100001000011000000000000000000,S*A*M-----*****,WAR.AIRTRK.MIL,

@@ Line 1: / Line 1: @@
 == Milsymbol Mapping ==
-The "MilSymMapper" class provides methods for mapping draw object SIDC and TypeId between the milsymbol versions: APP6D, MIL-STD-2525D, and MIL-STD-2525C.
+The "MilSymMapper" class provides methods for mapping draw object SIDC between the milsymbol versions: APP6D and APP6C.
+The result contains the result and status of the result. If the mapping is ambiguous, additional results are contained in the result (result.AdditionalResults).
 === Examples of Usage ===
@@ Line 8: / Line 9: @@
 // Get APP6D sidc from 15 character MIL-STD-2525C sidc
-var id_d = resources.MilSymMapper.MapAPP6CToAPP6D("SUGPUSTA--A----");
+var result_d = resources.MilSymMapper.MapAPP6CToAPP6D("SUGPUSTA--A----");
+var code = result_d.Code;
 // Get APP6D sidc from APP6C hierarchy code.
-var id_d = MapAPP6CHierarchyCodeToAPP6D("TACGRP.CSS.PNT.SPT.GNL");
+var result_d = MapAPP6CHierarchyCodeToAPP6D("TACGRP.CSS.PNT.SPT.GNL");
+var code = result_d.Code;
 // Get 15 character MIL-STD-2525C sidc from APP6D sidc
-var id_c = resources.MilSymMapper.MapAPP6DToAPP6C("100301000011010400000000000000");
+var result_c = resources.MilSymMapper.MapAPP6DToAPP6C("100301000011010400000000000000");
+var code = result_c.Code;
 // Get APP6C hierarchy code from APP6D sid.
-var id_c = MapAPP6DToAPP6CHierarchyCode("100025000032050000000000000000");
+var result_c = MapAPP6DToAPP6CHierarchyCode("100025000032050000000000000000");
+var code = result_c.Code;
 </source>
@@ Line 29: / Line 34: @@
 </source>
-=== Handling Mismatches Between APP6D and MIL-STD2525C ===
+For compatible mapping between draw objects in MARIA GDK 4 and MARIA GDK 5 the following API can be used:
-There are two files handeling mapping between APP6C and APP6D.....
+<source>
+// Get GDK 4 compliant hierarchy code from APP6D sidc.
+var id_c = GetGDK4CompliantSIDC("100025000032050000000000000000");
+// Get GDK 5 compliant sidc from MIL-STD2525C hierarchy code.
+var id_d = GetGDK5CompliantSIDC("TACGRP.CSS.PNT.SPT.GNL);
-Some objects cannot be mapped directly between APP6D and MIL-STD2525C. Either because the primitive representation of the objects are not compatible or because the objects are not present in both versions.
+</source>
-To handle this, the configuration file MilSymVersionMappings.json (located in the Data folder of the application output), sets up how these objects (SIDCs) should be mapped.
-The file is divided into two sections:
+=== How to Update Mapping Between APP6D and APP6C ===
-*HierarchyCodeMappings, for mapping a 20 digit APP6D SIDC to a MARIA GDK 4 draw object (MIL-STD2525C) hierarchy code, and vice versa
+There are two files handeling mapping between APP6C and APP6D:
-*SymbolCodeMappings, for mapping a 20 digit APP6D SIDC to a 15 character MIL-STD2525C SIDC, and vice versa
-Entries in each section of the configuration file looks like this:
+* C2DMapping.csv, handels mapping from APP6C to APP6D
+* D2CMapping.csv, handels mapping from APP6D to APP6C
+Each file contains one line per mapping and is a comma separated list of values. The first line in each file contains a descriptive name of each "column".
+==== The File C2DMapping.csv ====
+<syntaxhighlight lang="csharp">
+C_SymbolCode,D_Sidc,C_HierarchyCode,Status
+S*A*M-----*****,100001000011000000000000000000,WAR.AIRTRK.MIL,
+</syntaxhighlight>
+==== The File D2CMapping.csv ====
+<syntaxhighlight lang="csharp">
+D_Sidc,C_SymbolCode,C_HierarchyCode,Status
+100001000011000000000000000000,S*A*M-----*****,WAR.AIRTRK.MIL,
+</syntaxhighlight>
 [[Category:GDK5]]

Milsymbol Mapping: Difference between revisions

Latest revision as of 19:40, 15 November 2025

Contents