Show Navigation
|
Hide Navigation
You are here:
Extensions > Military Overlay Editor > The MOLE geodatabase schema
Extensions > Military Overlay Editor > The MOLE geodatabase schema
Attribute data field descriptions |
|
|
Release 9.2
Last modified February 27, 2008 |
Print all topics in : "The MOLE geodatabase schema" |
Related Topics
This topic provides the schema, or data dictionary, for MOLE 9.2. It includes detailed field descriptions, valid values, and other requirements for all fields in the MOLE schema as well as some fields you can add for special circumstances.
Although all MOLE fields (attribute data) are described in this topic, they are not all required. For information on which fields MOLE requires, see Overview of MOLE data.
MOLE attribute data is similar to ArcGIS attribute data in how it is stored in attribute tables and can be accessed for editing (for example, in ArcMap right-click a feature layer in the table of contents, then click Open Attribute Table). However, unlike ArcGIS attribute data, MOLE attribute data adheres to the military specification you chose and can be edited with the MOLE Symbol Editor.
With a few exceptions, the fields that make up the MOLE schema are used to display labels around a MOLE graphic.
If you create MOLE layers from scratch using the first two methods described at Create MOLE data outside of ArcMap and if you are familiar with the military specification you chose, you will likely not need to refer to this topic. This topic is geared toward users who need to create data feeds and/or import existing string, tabular, spreadsheet, or table data into ESRI products for use with MOLE.
NOTE: You can use your existing attribute data as MOLE labels.
Tips for reading the tables below
- Default character limits - When creating new MOLE feature classes in a geodatabase, MOLE creates attribute fields, each of which has a default maximum number of characters you can specify for its value until MOLE truncates the value. For example, if you type an entry in a field in the MOLE Symbol Editor that exceeds the character limit for that field, MOLE truncates the entry and, as a result, does not store the removed characters in the source data upon save. The MOLE Symbol Editor indicates via message boxes whether or not an entry exceeds this limit. Default character limits are also known as length.
Field descriptions for force element attributes
The fields in the following table are used by MOLE for force elements. Each force element in the layer (or feature class) will have the following fields that you can populate to help define it according to the military specification you chose.
| Attribute field name | Description | Type | Default character limit |
| Symbol_ID | This is a required field. It is an identifier that provides the information necessary to display or transmit a military symbol between MIL-STD-2525B-Change-1 compliant systems or between APP-6A-compliant systems. Also see Symbol_ID field valid values. | Text | 15 |
| Name | A MOLE label used to distinguish this force element from others. It identifies the acquisition number when used with SIGINT symbology. Also known as track number and unique designation. | Text | 20 |
| Parent | This is a required field for force elements; it must be present in the dataset, but it does not have to be populated. It is a MOLE label that indicates the number or title of the force element's higher echelon command (corps are designated by Roman numerals).
If the feature is a point feature and this field and the Symbol_ID field is present, MOLE identifies the feature as a force element (instead of a point tactical graphic). Also known as higher formation. |
Text | 20 |
| SComment | A MOLE label that can be used for notes or comments about this force element. Also known as comment or staff comments. | Text | 50 |
| Info | A MOLE label that can be used for notes or comments about this force element. Also known as additional information. | Text | 50 |
| Strength | A MOLE label that indicates the degree to which a force element is strong: (+) indicates reinforced, (-) indicates reduced, and (+/-) indicates reinforced and reduced. Also known as reinforced or detached. | Text | 5 |
| EvalRating | A MOLE label that consists of a one-letter reliability rating and a one-number credibility rating for the force element.
Valid values for the reliability ratings: A—completely reliable B—usually reliable C—fairly reliable D—not usually reliable E—unreliable F—reliability cannot be judged Valid values for the credibility ratings: 1—confirmed by other sources 2—probably true 3—possibly true 4—doubtfully true 5—improbable 6—truth cannot be judged Also known as evaluation rating. |
Text | 2 |
| Location | A MOLE label that gives a force element's location in degrees, minutes, and seconds values (or in UTM or other applicable display format). | Text | 20 |
| Alt_Depth | A MOLE label that gives the altitude portion of GPS, flight level for aircraft, depth for submerged objects, height in feet of equipment or structures on the ground. Also known as alt/depth and altitude/depth. | Text | 10 |
| Speed | A MOLE label that gives the value for velocity as described in Military Standard 6040. | Text | 10 |
| DTG | A MOLE label that gives the traditional military Date/Time Group (DTG) format:
DDHHMMSSZMONYY. |
Text | 20 |
| HQ | A MOLE label that gives the name of the special C2 headquarters.
Unlike most other MOLE labels, this one displays inside the force element frame. Also known as special C2 headquarters. |
Text | 10 |
| Quantity | A MOLE label that gives the number of items present. | Text | 10 |
| EType | Type of equipment (used for equipment force elements) | Text | 20 |
| Effective | A MOLE label that indicates capability. Also known as combat effectiveness. | Text | 10 |
| Signature | A MOLE label for hostile equipment; “!” indicates detectable
electronic signatures. Also known as signature equipment. |
Text | 10 |
| IFFSIF | A MOLE label that indicates IFF/SIF identification modes and codes. | Text | 10 |
| Direction | A value that indicates in degrees (0–360) the direction of movement of the force element. MOLE uses this value to draw the force element's direction of movement indicator. Also known as a graphic modifier. | Double | n/a |
| DirectVis | Tells whether the direction of movement indicator for this force element should display or not.
0 = don't display (default) 1 = do display |
Short integer | 1 |
Fields for special circumstances
MOLE supports a set of fields that are not in the MOLE schema—that is—they are not in the MOLE feature classes available with ArcCatalog, so they do not get created for you automatically when you create a MOLE geodatabase or feature class in ArcCatalog. However, you can add and define these fields yourself.
| You can use optional MOLE fields to | For more information and field descriptions, see |
| Add a sphere(s) to a force element | Using spheres |
|
|
|
Field descriptions for tactical graphic attributes
Descriptions of fields that are the same for force elements are not given here. See the table above for those descriptions, replacing "tactical graphic" for instances of "force element". For descriptions that differ for force elements and descriptions for fields not used for force elements, see the table below named Field descriptions for point, line, and area tactical graphics.
| Field name | Has a different description than its force element counterpart? (force element descriptions are above) | Type | Default character limit |
| Symbol_ID | No, but has different valid values. Also see Symbol_ID field valid values. | Text | 15 |
| Name | Yes. See below. | Text | 20 |
| Name1 | Yes. This field doesn't exist in the schema for force elements. See below. | Text | 20 |
| Info | No | Text | 50 |
| Info1 | Yes. This field doesn't exist in the schema for force elements. See below. | Text | 50 |
| Info2 | Yes. This field doesn't exist in the schema for force elements. See below. | Text | 50 |
| Location | No | Text | 20 |
| DTG | No | Text | 20 |
| DTG1 | Yes. This field doesn't exist in the schema for force elements. See below. | Text | 20 |
| EType | Yes. See below. | Text | 10 |
| Quantity | Yes. See below. | Text | 10 |
| Direction | Yes. See below. | Double | n/a |
| Speed | Yes. This field can be used to create a wind barb, also known as a wind plot. This value determines wind strength (number of flags on the wind barb). It is required, along with the Direction field, for wind barbs. For more information, see Updating MOLE datasets. | Text | 10 |
| DirectVis | No | Short integer | 1 |
| Field name | Has a different description than its force element counterpart? (force element descriptions are above) | Type | Default character limit |
| Symbol_ID | No, but has different valid values. Also see Symbol_ID field valid values. | Text | 15 |
| Name | Yes. See below. | Text | 20 |
| Name1 | Yes. This field doesn't exist in the schema for force elements. See below. | Text | 20 |
| Location | No | Text | 20 |
| DTG | No | Text | 20 |
| DTG1 | Yes. This field doesn't exist in the schema for force elements. See below. | Text | 20 |
| Info | No | Text | 20 |
| Info1 | Yes. This field doesn't exist in the schema for force elements. See below. | Text | 20 |
| Info2 | Yes. This field doesn't exist in the schema for force elements. See below. | Text | 20 |
| Direction | Yes. See below. | Double | n/a |
| EType | Yes. See below. | Text | 20 |
| Field name | Has a different description than its force element counterpart? (force element descriptions are above) | Type | Default character limit |
| Symbol_ID | No, but has different valid values. Also see Symbol_ID field valid values. | Text | 15 |
| Name | Yes. See below. | Text | 20 |
| Name1 | Yes. This field doesn't exist in the schema for force elements. See below. | Text | 20 |
| Info | No | Text | 50 |
| Info1 | Yes. This field doesn't exist in the schema for force elements. See below. | Text | 50 |
| Info2 | Yes. This field doesn't exist in the schema for force elements. See below. | Text | 50 |
| Location | No | Text | 20 |
| DTG | No | Text | 20 |
| DTG1 | Yes. This field doesn't exist in the schema for force elements. See below. | Text | 20 |
| EType | Yes. See below. | Text | 10 |
Field descriptions for point, line, and area tactical graphics
| Field name(s) | Description |
| Name | A MOLE label used to distinguish this tactical graphic from others. Also known as track number. Nuclear: delivery unit (missile, aircraft, satellite). |
| Name 1 | A MOLE label used to distinguish this tactical graphic from others. Nuclear: delivery unit (missile, aircraft, satellite, and so on). Also known as track number. For air corridors, a populated Name1 field and Direction field indicates a three-line air corridor. |
| Info1, Info2 | A MOLE label that can be used for notes or comments about this tactical graphic. |
| DTG1 | A MOLE label with traditional military Date/Time Group (DTG) format:
DDHHMMSSZMONYY. |
| EType | Indicates type of tactical graphic, primarily for these tactical graphics: mines, minefields, final protective fire line, nuclear points, and nuclear areas.
Mines and nuclear points are point tactical graphics. Minefields can be point tactical graphics or area tactical graphics. Fire lines are line tactical graphics. Nuclear areas are area tactical graphics. For more information, see Using the EType field for tactical graphics (values for mines). For more information on feature class types, see MOLE feature class categories. |
| Quantity | In a nuclear tactical graphic, a MOLE label with a value that identifes the detonation in kilotons; yield (can be displayed in decimals). |
| Direction |
|
Symbol_ID field valid values
The Symbol_ID field has hundreds of possible valid values, all of which are listed in the military specification you chose.
Nearly all of the valid values are supported by MOLE. If you are new to the military specification, you may want to view the tables in the Symbol ID code section of this help system to get an idea of how the valid values work and how they are grouped by force element or tactical graphic.
Using the EType field for tactical graphics (values for mines)
EType versus Type
Even though "EType" is the field name MOLE gives by default 1 for the field that indicates mine/minefield type, MOLE actually uses (looks for) a name of "Type" to be the field name or alias name when MOLE works with this field in any way.
This handling differs from the way MOLE handles all other MOLE fields 2 . For the other MOLE fields, when it needs to use a field, MOLE uses (looks for) either:
- The field name MOLE gives by default
- The name you have mapped to the MOLE field name
or
As long as the field you want to use to indicate mine/minefield type has either a field name or alias name of "Type", MOLE will recognize it and use it. So unlike other MOLE fields, you may want to think twice before renaming this field's alias. By default, MOLE uses this field's alias to perform its functions. MOLE never looks for a field or alias of "EType".
This special handling of the EType field is required to stay backward compatible with some relational database systems.
About the role of the EType field
The way the EType field (Type field) is used differs from the way other fields in the Modifiers area (Area 1) of the MOLE Symbol Editor are used. The Etype field is a graphical property for specific military symbols: tactical graphic areas/minefields/dynamic depiction (symbol ID G*M*OFD) and tactical graphic points/minefields/static depiction (symbol ID G*M*OFS).
The following table contains the valid values, which are not case sensitive, for the possible mine types. If any other value is entered or if the EType field is blank, MOLE displays unspecified mines by default.
| Mine type | Valid values |
| Antipersonnel mine | OMP, OMP---, ANTIPERSONNEL, AP |
| Antitank mine | OMT, OMT---, ANTITANK, AT |
| Antitank mine + antihandling device | OMD, OMD---, ANTITANK ANTIHANDLING, ANTIHANDLING ANTITANK, AT AH, AH AT, AHAT, ATH, HAT |
| Directional antitank mine | OME, OME---, ANTITANK DIRECTIONAL, DIRECTIONAL ANTITANK, AT D, D AT, ATD, DAT |
| Unspecified mine | OMU, OMU---, UNSPECIFIED |
| Wide area mine | OMW, OMW---, WIDE AREA MINES, WIDE, WIDE AREA, W, WA, WAM |
Notes:
- Values entered for the EType field do not appear as labels around the symbol but, instead, change the symbol's appearance.
- Fields in shapefiles can't have aliases, so their field names must be called "Type" in order for mines to work.
- Mines are point tactical graphics. Minefields can be point tactical graphics or area tactical graphics.
- Minefields have a static depiction, a rectangle filled with a mine symbol that is centered over a point feature. While this depiction may suggest that a minefield is in a given area, its actual perimeter is unknown.
1 MOLE gives the field the name of "EType" by default when you create MOLE data using the step-by-step instructions in Creating MOLE data in ArcCatalog.
2 Except SComment. MOLE handles SComment the same way it handles EType. SComment is to EType as Comment is to Type; MOLE never looks for "SComment" in the field name or alias name, only "Comment".
AOU and dynamic modifiers
Area of uncertainty (AOU) modifiers and dynamic modifiers are not part of the MOLE schema this release. However, you can use existing ArcGIS symbol drawing capabilities to create them.