Milsymbol Mapping: Difference between revisions

From Maria GDK Wiki
Jump to navigation Jump to search
(Created page with "== Milsymbol Mapping == With the "MilSymMapper" class you can map draw object sidc between the milsymbol versions: APP6D, MIL-STD-2525D, and MIL-STD-2525C. === Examples of Usage === Tese example maps the Battle Position type. === Examples of Usage - Get Mapped SIDC from SIDC === <source lang="c#"> var factory = new DrawObjectCommonFactory(); // Get APP6D sidc from MIL-STD-2525C SIDC var id_d = factory.MilSymMapper.GetMilSymSIDCFromMilSymSIDC("TACGRP.C2GM.DEF.ARS.BTLPS...")
 
 
(13 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Milsymbol Mapping ==
== Milsymbol Mapping ==
With the "MilSymMapper" class you can map draw object sidc between the milsymbol versions: APP6D, MIL-STD-2525D, and MIL-STD-2525C.
The "MilSymMapper" class provides methods for mapping draw object SIDC and TypeId between the milsymbol versions: APP6D, MIL-STD-2525D, and MIL-STD-2525C.


=== Examples of Usage ===
=== Examples of Usage ===
Tese example maps the Battle Position type.
These examples maps the Battle Position type.


=== Examples of Usage - Get Mapped SIDC from SIDC ===
=== Get Mapped SIDC from SIDC ===
<source lang="c#">
<source lang="c#">
var factory = new DrawObjectCommonFactory();
var factory = new DrawObjectCommonFactory();
Line 16: Line 16:
</source>
</source>


=== Examples of Usage - Get Mapped TypeId from SIDC ===
=== Get Mapped TypeId from SIDC ===
<source lang="c#">
<source lang="c#">
var factory = new DrawObjectCommonFactory();
var factory = new DrawObjectCommonFactory();


// Get APP6D TypeId from TypeId
// Get APP6D TypeId from MIL-STD-2525C sidc
  var typeId_d = factory.MilSymMapper.GetDrawObjectTypeId("TACGRP.C2GM.DEF.ARS.BTLPSN", Mapping.MilSymType.APP6D);
var typeId_d = factory.MilSymMapper.GetDrawObjectTypeId("TACGRP.C2GM.DEF.ARS.BTLPSN", Mapping.MilSymType.APP6D);


// Get MIL-STD-2525C TypeId from TypeId
// Get MIL-STD-2525C TypeId from APP6D sidc
var typeId_c = factory.MilSymMapper.GetDrawObjectTypeId("30002500001512000000", Mapping.MilSymType.MILSTD2525C);
var typeId_c = factory.MilSymMapper.GetDrawObjectTypeId("30002500001512000000", Mapping.MilSymType.MILSTD2525C);
</source>
</source>


=== Examples of Usage - Get Mapped SIDC from TypeId ===
=== Get Mapped SIDC from TypeId ===
<source lang="c#">
<source lang="c#">
var factory = new DrawObjectCommonFactory();
var factory = new DrawObjectCommonFactory();
Line 37: Line 37:
var id_c = factory.MilSymMapper.GetMilSymSIDCFromTypeId(new Guid("88784e27-c8d4-46d8-a72f-4fc433c759ee"), Mapping.MilSymType.MILSTD2525C);
var id_c = factory.MilSymMapper.GetMilSymSIDCFromTypeId(new Guid("88784e27-c8d4-46d8-a72f-4fc433c759ee"), Mapping.MilSymType.MILSTD2525C);
</source>
</source>
=== How to Create MilSymMapper Without Factory ===
<source lang="c#">
var mappingDrawObjectTypeXmlParser = new MappingDrawObjectTypeXmlParser();
var mappingDrawObjectTypeLoader = new MappingDrawObjectTypeLoader(mappingDrawObjectTypeXmlParser);
var activesymbolset = "APP6D";
var milSymMapper = new MilSymMapper(mappingDrawObjectTypeLoader, activesymbolset);
</source>
=== Handling Mismatches Between APP6D and MIL-STD2525C ===
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.
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.
Entries in the configuration file looks like this:
<source lang="json">
{
      "SourceVersion": "APP6D",
      "TargetVersion": "MILSTD2525C",
      "Name": "Minimum Safe Distance Zones",
      "Source": "30002500002721000000",
      "Target": "GENERIC.ELLIPSE",
      "ObjectType": "MultiFanArea"
}
</source>
The values in an entry are:
{| class="wikitable"
! Name
! Description
|-
| '''SourceVersion'''
| Version to map from.
|-
| '''TargetVersion'''
| Version to map to.
|-
| '''Name'''
| Name of object (for readability only, does not affect mapping).
|-
| '''Source'''
| SIDC to map from.
|-
| '''Target'''
| SIDC to map to.
|-
| '''ObjectType'''
| Primitive type of object (for readability only, does not affect mapping).
|}
The entries in the configuration file can be edited to whatever is the best match for the client application, as long as the primitive representation of the objects are compatible.
[[Category:GDK5]]

Latest revision as of 16:28, 11 March 2025

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.

Examples of Usage

These examples maps the Battle Position type.

Get Mapped SIDC from SIDC

var factory = new DrawObjectCommonFactory();

// Get APP6D sidc from MIL-STD-2525C SIDC
var id_d = factory.MilSymMapper.GetMilSymSIDCFromMilSymSIDC("TACGRP.C2GM.DEF.ARS.BTLPSN", Mapping.MilSymType.APP6D);

// Get MIL-STD-2525C sidc from APP6D sidc
var id_c = factory.MilSymMapper.GetMilSymSIDCFromMilSymSIDC("30002500001512000000", Mapping.MilSymType.MILSTD2525C);

Get Mapped TypeId from SIDC

var factory = new DrawObjectCommonFactory();

// Get APP6D TypeId from MIL-STD-2525C sidc
var typeId_d = factory.MilSymMapper.GetDrawObjectTypeId("TACGRP.C2GM.DEF.ARS.BTLPSN", Mapping.MilSymType.APP6D);

// Get MIL-STD-2525C TypeId from APP6D sidc
var typeId_c = factory.MilSymMapper.GetDrawObjectTypeId("30002500001512000000", Mapping.MilSymType.MILSTD2525C);

Get Mapped SIDC from TypeId

var factory = new DrawObjectCommonFactory();

// Get APP6D sidc from TypeId
var id_d = factory.MilSymMapper.GetMilSymSIDCFromTypeId(new Guid("88784e27-c8d4-46d8-a72f-4fc433c759ee"), Mapping.MilSymType.APP6D);

// Get MIL-STD-2525C sidc from TypeId
var id_c = factory.MilSymMapper.GetMilSymSIDCFromTypeId(new Guid("88784e27-c8d4-46d8-a72f-4fc433c759ee"), Mapping.MilSymType.MILSTD2525C);

How to Create MilSymMapper Without Factory

var mappingDrawObjectTypeXmlParser = new MappingDrawObjectTypeXmlParser();
var mappingDrawObjectTypeLoader = new MappingDrawObjectTypeLoader(mappingDrawObjectTypeXmlParser);
var activesymbolset = "APP6D";
var milSymMapper = new MilSymMapper(mappingDrawObjectTypeLoader, activesymbolset);

Handling Mismatches Between APP6D and MIL-STD2525C

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. 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.

Entries in the configuration file looks like this: 

{
      "SourceVersion": "APP6D",
      "TargetVersion": "MILSTD2525C",
      "Name": "Minimum Safe Distance Zones",
      "Source": "30002500002721000000",
      "Target": "GENERIC.ELLIPSE",
      "ObjectType": "MultiFanArea"
}

The values in an entry are:

Name Description
SourceVersion Version to map from.
TargetVersion Version to map to.
Name Name of object (for readability only, does not affect mapping).
Source SIDC to map from.
Target SIDC to map to.
ObjectType Primitive type of object (for readability only, does not affect mapping).

The entries in the configuration file can be edited to whatever is the best match for the client application, as long as the primitive representation of the objects are compatible.

Retrieved from "http://docs.maria.teleplanglobe.com/index.php?title=Milsymbol_Mapping&oldid=4699"