Military Tools for ArcGIS 3.0

What's new

New functionality for Military Tools for ArcGIS in this release is listed below.

  • Support has been added for the following:
    • ArcMap 10.3.1–10.6.1
    • ArcGIS Pro 2.1–2.2
    • Web AppBuilder for ArcGIS (Developer Edition) 2.4–2.8
  • Converted Military Tools toolbox to Python toolbox (.pyt) format.
  • Released Military Tools toolbox through the Python package manager.
  • Added Gridded Reference Graphic toolset to Military Tools toolbox.
  • Added support for Dark Theme in ArcGIS Pro.
  • Added support for Distance and Direction labels in ArcGIS Pro.
  • Added the Number Features tool to the Gridded Reference Graphic toolset.
  • Input coordinate parameters handle longitude latitude order.
  • Coordinate Conversion export functionality exports all coordinate types listed in the output section.
  • Coordinate Conversion supports pasting multiple coordinates to the list at one time.

Issues addressed in the June 2018 release

The Military Tools for ArcGIS June 2018 release fixes the issues below.

Coordinate Conversion

Issues addressed for Coordinate Conversion are described in the following table.

BugDescription

Ambiguous Coordinate dialog box appears for coordinates that are not ambiguous.

Column heading error when exporting to a .csv file.

Importing an open .csv file causes the application to crash.

Flash does not work on coordinates that were imported in ArcMap and ArcGIS Pro.

Inputting coordinates via keyboard does not populate the list function.

Distance and Direction

Issues addressed for Distance and Direction are described in the following table.

BugDescription

Using the Delete or Backspace key on the keyboard on the Circle tab removes all zeros if the leading nonzero digit is deleted.

Drawing line graphics across the International Date Line causes label issues in ArcMap.

ArcGIS Pro gives an error if the user does not explicitly name a feature class on Save As.

Create Circle from Radius/Diameter value entered is always radius.

Distance Calculator results are always labeled with radius in ArcMap.

Ellipse tool axis labels are incorrect in ArcMap with the Semi ellipse type.

Map Point Tool does not activate when relaunching ArcMap from an .mxd file saved with the Distance and Direction window open.

Cursor location does not match the circle diameter.

Crash when entering the same value for Starting Point and Ending Point.

Distance and Direction Ring and Ellipse tools cause ArcMap to go unresponsive when clicking outside the basemap extent.

Military Symbol Editor

Issue addressed for Military Symbol Editor is described in the following table.

BugDescription

Features from favorites tab do not add the military information model.

Military Tools toolbox

Issues addressed for the Military Tools toolbox are described in the following table.

BugDescription

In ArcGIS Pro, setting the Table To Polygon Line parameter causes the tool to fail.

Table To Polyline incorrectly re-adds first group point.

Known issues

Known limitations of Military Tools for ArcGIS are listed below.

ArcGIS Pro

Coordinate Conversion

  • Pasting a list that has an empty row results in duplication of the coordinate prior to the empty row.
  • Entering a coordinate in the input box with no map in the project causes a crash.
  • Does not provide an output MGRS or USNG coordinate in the polar regions.

Distance and Direction

  • When the Distance and Direction group layer is removed from the table of contents and Distance and Direction is used again, another feature dataset is created in the default geodatabase.
  • Distance unit in feature tables is not based on resource value.
  • New feature dataset is added to the default geodatabase if the layers are not present in the table of contents.
  • Range ring radials are distorted when they pass near the poles.

Military Symbol Editor

  • After removing the military symbology schema from the table of contents, there is no way to interact with Military Symbol Editor again within that project.
  • Symbol with the SIDC G*MPSE----**** X is titled Shelter in the Military Symbol Editor (MIL-STD-2525B w/CHANGE 2), not as Earthwork, Small Trench or Fortification (2.X.3.3.1).
  • Incorrect symbology for the Assault Position in the MIL-STD-2525B w/CHANGE 2 settings.
  • Line of Contact not implemented.
  • MIL-STD-2525B w/CHANGE 2 or MIL-STD-2525D does not have the echelon [B] for boundaries.
  • Command and Control Lines are not implemented according to MIL-STD-2525B w/CHANGE 2.
  • MIL-STD-2525B w/CHANGE 2 does not have the echelon [B] for Strong Point.
  • "Foxhole, Emplacement or Weapon Site" (2.X.3.3.4) is not implemented according to MIL-STD-2525B w/CHANGE 2.
  • Polygon and line symbols defined as 'Anticipated' with the Military Symbol Editor do not become dashed.
  • Labels that are set with a domain value cannot be cleared to an empty value once a value is set.

Visibility

  • Radial Line of Sight in 3D produces empty output results.
  • Radial Line of Sight is cut off when using a nonprojected data layer.
  • Radial Line of Sight does not utilize a layer file for symbology.
  • Radial Line of Sight in 3D input points have too much vertical exaggeration.

ArcMap

Coordinate Conversion

  • Pasting a list that has an empty row results in duplication of the coordinate prior to the empty row.
  • Exporting to CSV or KMZ locks the file type as your file type option until you restart the session.
  • Does not provide an output MGRS or USNG coordinate in the polar regions.
  • Diaeresis and double acute accent symbol for seconds mark.

Distance and Direction

  • Exporting to KMZ leaves a lock file in the folder, preventing the next KMZ export in the folder.
  • On the Line, Ellipse, and Rings tabs, deleting a nonzero digit removes all trailing zeros.
  • ConstructGeodesicCircle or ConstructGeodesicEllipse fails to return for some projections.
  • Retains the previous coordinate system.
  • Exported KMZ symbology does not match the source symbology.

Visibility

  • Add-in retains the previous data frame settings.
  • Changing the data frame after receiving a message that data must be projected causes the results to not be shown upon running.
Top