Skip to content
Marek Szeles edited this page Jan 20, 2021 · 39 revisions

Milsymbol generator wiki

The pages on this wiki describe the functionality and content of the Milsymbol generator as extended by the Military Tactical Graphics Czechia. Some information is valid for the original Milsymbol generator created by spatialillusions as well.

Documentation of used standards

In this project, we are using the MIL-STD-2525C standard for military symbols, specifically the Military Operation Tactical Graphics section. The relevant specification of this standard can be found on pages 329 - 761 in the following document: http://www.mapsymbs.com/ms2525c.pdf

Symbol generation

The generator uses a form which prompts the user to input necessary attributes. Here are some examples of GeoJSON and the corresponding symbols they generate:

Table of sample symbols

Image JSON file Description Parametres
GFGPGPRS---- Special point A single placed point to map using GeoJson.
Specifically, it is a "Special point" created in the unitgenerator,
with FunctionID: GENERAL - POINTS - REFERENCE POINT - SPECIAL POINT
  • Parameters
    • "sidc": ID specifying diagram type
    • "distance": the size of the space on the map
  • Coordinates
    • Longitude
    • Latitude
GFGPGPUYA--- Under sea S single placed point to map using GeoJson. Specifically, it is an "ANM" created in the unitgenerator,
FunctionID: GENERAL - POINTS - UNDER SEA WARFARE - SONOBUOY
  • Parameters
    • "sidc": ID specifying diagram type
    • "distance": the size of the space on the map
  • Coordinates
    • Longitude
    • Latitude
GFGPGPWG---- Ground zero / ambush Combination of two objects, point Ground zero and ambush. Used just as example, not as a real visualization. Multiple coordinations are used for specification anchor points described in Nato Documentation,
FunctionID: GENERAL - POINTS - WEAPON - GROUND ZERO
  • Parameters
    • "sidc": ID specifying diagram type
    • "size": attribute specifying the size of the marker on the map
  • Coordinates
    • Longitude
    • Latitude
GFMPBCB----- Canalize / bridge Combination of two objects, point Bridge and LineString Canalize. Used just as example, not as a real visualization. Multiple coordinations are used for specification anchor points described in Nato Documentation,
FunctionID: CROSSING SITE/WATER CROSSING - BRIDGE OR GAP
  • Parameters
    • "sidc": ID specifying diagram type
    • "size": attribute specifying the size of the marker on the map
  • Coordinates
    • Longitude
    • Latitude
GFTPD------- CFF zone / destroy Combination of two objects, point Call for fire zine and destroy. Used just as example, not as a real visualization. Multiple coordinations are used for specification anchor points described in Nato Documentation,
FunctionID: DESTROY
  • Parameters
    • "sidc": ID specifying diagram type
    • "distance": the size of the space on the map
    • "uniqueDestination": ID specifying exact location on the map
  • Coordinates
    • Longitude
    • Latitude

SIDC ("sidc") ID code specification

The SIDC codes are 12 character long identifiers of each feature in the generated diagrams. Detailed information on the codes is available in the relevant documentation, but the general classifications may be abstracted using the keys in the following table:

Character number Type Value
1 en: Coding scheme
cz: Druh operace
S - Warfighting
I - Intelligence
O - Stability Operations
E - Emergency
2 en: Affiliation
cz: Příslušnost
P - Pending
U - Unknown
A - Assumed Friend
F - Friend
N - Neutral
S - Suspect
H - Hostile
G - Exercise Pending
W - Exercise Unknown
D - Exercise Friend
L - Exercise Neutral
M - Exercise Assumed Friend
J - Joker
K - Faker
O - None Specified
3 en: Battle Dimension
cz: Druh sil
If Coding scheme is S or I:
P - Space
A - Air
G - Ground
S - Sea Surface
U - Sea SubsurfaceF - Special Operations Forces

If Coding scheme is O:
V - Violent Activities
L - Locations
O - OperationsI - Items
P - Individual
G - Nonmilitary Group or Organization
R – Rape

If Coding scheme is E:
I - Incident
N - Natural Events
O - Operations
F - Infrastructure
4 en: Status
cz: Status
A - Anticipated/Planned
P - Present
C - Present/Fully Capable
D - Present/Damaged
X - Present/Destroyed
F - Present/Full to Capacity
5-10 en: Function ID
cz: Druh vojska
(Hundreds of options)
11 en: Symbol Modifier 1
cz: Bližší upřesnění typu
A - Headquarters
B - Task Force HQ
C - Feint Dummy HQ
D - Feint Dummy/Task Force HQ
E - Task Force
F - Feint Dummy
G - Feint Dummy/Task Force
H - InstallationM - Mobility
N - Towed Array
12 en: Symbol Modifier 2
cz: Úroveň C2
A - Team/Crew
B - Squad
C - Section
D - Platoon/Detachment
E - Company/Battery/Troop
F - Battalion/Squadron
G - Regiment/Group
H - Brigade
I - Division
J - Corps/Mef
K - Army
L - Army Group/Front
M - Region
N – Command

If Symbol Modifier 1 is M:
O - Wheeled/Limited
P - Wheeled
Q - Tracked
R - Wheeled and Tracked
S - Towed
T - Rail
U - Over the Snow
V - Sled
W - Pack Animals
Y - Barge
Z – Amphibious

If Symbol Modifier 1 is N:
S - Towed Array (Short)
L - Towed Array (Long)

General GeoJSON syntax

The outermost tag for all diagrams is a FeatureCollection, which contains individual features with properties and geometry. A Feature collection may include only one feature, as seen on this abstract example:

{
    "type": "FeatureCollection",
    "features": [
        {
            "type": "Feature",
            "properties": {
                "sidc": xxxxxxxxxxxx,
                "property 1": xxx,
                "property 2": xxx,
                ...
            },
            "geometry": {
                "type": "Point",
                "coordinates": [
                        longitude,
                        latitude
                ]
            }
        }
    ]
}

Or it could be a combination of several features, like in this abstract example with two features:

    "type": "FeatureCollection",
    "features": 
    [
            {
            "type": "Feature",
            "properties": {
                "sidc": xxxxxxxxxxxx,
                "property 1": xxx,
                "property 2": xxx,
                ...
            },
            "geometry": {
                    "type": "LineString",
                    "coordinates": [
                        [
                            longitude,
                            latitude
                        ],
                        [
                            longitude,
                            latitude
                        ],
                        [
                            longitude,
                            latitude
                        ]
                    ]
                }
            },
            {
                "type": "Feature",
                "properties": {
                    "sidc": xxxxxxxxxxxx,
                    "property 1": xxx,
                    "property 2": xxx,
                    ...
                },
                "geometry": {
                    "type": "Point",
                    "coordinates": [
                            longitude,
                            latitude
                    ]
                }
            }
        

    ]
}