Using military symbology and symbol-based graphics

In this topic

• Creating MOLE graphics
• Force elements and tactical graphics
• MOLE symbols
• Symbol ID code
• Terminology

Creating MOLE graphics

• Symbol-based approach
• Feature-based approach

Force elements and tactical graphics

• Force elements, also known as tactical symbols or force units, are points that represent military units, installations, and equipment. MIL-STD-2525B Change 2 and APP-6A define force elements as point objects that present information that can be pinpointed in one location at a particular time. Military specifications dictate the following:
• A force element is composed of an icon, frame (shape), and fill and can include additional components that provide information about the symbol's affiliation, battle dimension, echelon, mobility, status, and mission.
• Echelon and mobility indicators are positioned outside the frame. The shape and color of the frame change according to the force element's affiliation.
• In the case of friendly-affiliated graphics and, to a lesser extent, hostile-affiliated, unknown, and pending graphics, the shape is also determined by the battle dimension of the graphic being represented.
• In addition to components, you can use the MOLE application programming interface (API) to add or edit labels (modifiers), such as parent name, altitude/depth, or the direction of movement indicator. Labels are also known as attributes in the feature-based approach for creating graphics because they are stored as data fields in an attribute table.
• Tactical graphics, also known as military operations graphics, can be point, line, or polygons and represent command/control and mission planning and operations features. MIL-STD-2525B Change 2 and APP-6A define tactical graphics as point, line, and area objects that are necessary for battlefield planning and management but cannot be presented as force elements alone. As the military specifications dictate:
• A tactical graphic is composed of an icon and may include additional components. The size and shape of the point graphics remain fixed, while the size and shape of the line and area graphics are determined by drawing parameters provided by the user and the scale of the background on which the graphic is placed.
• Tactical graphics can signify responsibilities and activities critical to supporting mission planning and battlefield management. They can represent military bases, facilities, mission guidance, control measures, and obstacles.

Using the feature-based approach to creating MOLE graphics, you can apply leadering rules to force elements to group them onto lines (leader lines). The following illustration shows four leaders:

MOLE symbols

Symbol ID code

• For example, the Symbol ID code SHGPUCIGD--H*** can be translated into the following symbol attributes:
• S = war fighting
• H = hostile
• G = ground
• P = present
• UCIGD = internal security force
• H = brigade
• ** = country
• * = order of battle; for example, air, maritime, and so on

Terminology

• Why MOLE graphics and not MOLE symbols—MOLE graphics refers to MOLE graphics and symbols that are standard ArcGIS symbols (symbol-based graphics). Because many objects and documents are applicable to both types of graphics (symbol-based and feature-based), it is necessary to refer to them collectively. Shifting from graphic to symbol only for symbol-based objects is impractical and may be confusing; therefore, MOLE graphics refers to both types collectively and is used to maintain consistency throughout the documentation.
• Why MOLE labels are called attributes—Attribute refers to MOLE labels or what the military specifications often refer to as modifiers. Attribute is used to stay consistent with ArcGIS terminology. In ArcGIS, attribute refers to a table field (a field in a feature class) that stores data. When using a feature-based method of graphics management, MOLE labels are stored in an attribute table; therefore, when you use the symbol-based method, attribute can sound off-putting because symbol-based does not use attribute fields to store data.

See Also: