Labeling military operations features
All labels are turned on by default for military operations features. It is often hard to distinguish one line from another, or an area from another, without labels. For example, a present boundary and present phase line have the same symbol, a black solid line. It is the labels that distinguish one of these military operations line features from another. The placement of text for military operations points, lines and areas is derived from military symbol specifications supported by ArcGIS.
Like UEI features, label classes are used to label a single military operations feature with multiple labels. For example, boundary line features are labeled using three label classes. Label classes are also used to label a subset of military operations features in a single layer by using a SQL query. For example, unique designation is labeled for both the boundary feature (2ID) and the phase line feature (ALPHA), but it is labeled in different positions. The field the SQL query is based on depends on if you are labeling military operations point features or line and area features.
Labeling military operations point features
The label classes are named for the type of military operations point features they are labeling. For example, the Decision Point label class is used to label decision points. The SQL query for labeling military operations point features is based on the SymbolName field. Using the same attribute (Unique Designation), one point feature, such as a decision point, can be labeled differently than another point feature, such as a check point. An explanation for how the Decision Point label class is used, along with a SQL query, to label a set of features in the map is described for each of the numbered items identified in this graphic.
Using a label class to label features from the same layer differently
- The Decision Point label class is selected in the Label Classes box.
- The SQL Querydialog is used to select which features will get labeled based on the text properties, label expression and position for the Decision Point label class. Here the label class was named for the symbol name.
- Decision Point features are labeled using the Unique Designation field attribute.
As with the UEI features, label classes are also used to label the same military operations point feature multiple times based on different attribute fields. The following table is an example of how different features are labeled based on label classes, SQL queries, and label expressions.
Label Class | SQL Query | Label Field or Expression |
|---|---|---|
Decision Point | "SymbolName" = 'Decision Point' | [UniqueDesignation] |
Action Points - Unique Designation | "SymbolName" in ( 'Action Points (general)', 'Amnesty Point', 'Check Point', 'Linkup Point', 'Passage Point', 'Rally Point', 'Release Point', 'Start Point') | [UniqueDesignation] |
Action Points - Additional Information | "SymbolName" in ( 'Action Points (general)', 'Amnesty Point', 'Check Point', 'Linkup Point', 'Passage Point', 'Rally Point', 'Release Point', 'Start Point') | [AdditionalInformation] |
Action Points - DTG | "SymbolName" in ( 'Action Points (general)', 'Amnesty Point', 'Check Point', 'Linkup Point', 'Passage Point', 'Rally Point', 'Release Point', 'Start Point') | [DateTimeValid] & " -" & vbnewline & [DateTimeExpired] |
The image below shows two military operations points labeled using the same attribute field but in different positions.
- Label classes are used to label the same attribute field differently.
- Unique Designation is labeled centered on point for decision points
- Unique Designation is labeled horizontal and northeast of point for check points, rally points and other action points
- Label classes are used to label a subset of features from the same layer. A SQL query is used to select the subset of features to be labeled.
- Action points (general), amnesty points, check points, linkup points, passage points, rally points, release points and start points are labeled using the same three label classes.
- Label classes are used to label the same feature multiple times based on different attributes. For example, there are three label classes used to label a set of action point features.
- Action Points - Unique Designation
- Action Points - Additional Information
- Action Points - DTG
Labeling military operations line and area features
Labeling military operations line and area features is similar to labeling UEI features except for the field the SQL query is based on. It is the representation rules, denoted by RuleID, that the SQL query uses to filter which line or area is labeled by a specific label class. This is because military operations line and area layers are symbolized using representations. The line and area feature class representations contain many representation rules to categorize the features. For more information about military operations line and area features and how they are constructed, see Using military operations features.
Learn more about representation rules
The following table is an example of how military operations areas are labeled based on label classes.
Label Class | SQL Query | Label Field or Expression | Text Symbol |
|---|---|---|---|
Objective | RuleID = 7 | "OBJ " & [UniqueDesignation] | Arial, 8pt |
Area of Operations | RuleID = 74 | "AO " & [UniqueDesignation] | Arial, 8pt |
Battle Position | RuleID in (9, 80) | [UniqueDesignation] | Arial, 8pt |
Echelon | RuleID in (9, 24, 80, 81) | [Echelon] | ESRI Mil2525C Modifiers, 8pt |
- Label classes are used to label a group of features from the same layer. A SQL query, based on the representation RuleID, is used to select the subset of features to be labeled.
- Objective features (RuleID = 7) are labeled using the Objective label class
- Battle position (RuleID = 9), strong point (RuleID = 24), planned battle position (RuleID = 80) and battle position prepared but not occupied (RuleID = 81) features are labeled using the Echelon label class
- Label classes are used to label the same feature multiple times based on different attributes. For example, there are two label classes, Battle Position and Echelon, that are used to label battle position (RuleID = 9) features and planned battle position (RuleID = 80) features.
- Label classes are used to label the same attribute field differently. They allow you to use a different text symbol to label different types of features in the same layer. For example, Arial font is used to label objective features and the ESRI Mil2525C Modifers font is used to label the four sets of features that use the Echelon label class.
The Echelon label class uses the ESRI Mil2525C Modifiers font to label a set of features based on the attribute selected in the Echelon field. There are coded values defined for the Echelon field. For example, when you choose Brigade for the echelon, the label is X and when you choose Division, the label is XX. All of the attribute domains associated with the feature classes in your geodatabase can be viewed by browsing_the_attribute_domains_of_a_geodatabase_Br.