- Military Symbology Styles is a solution for creating style files used by the Dictionary Renderer to render Military Symbols.
- A solution using a style file with a complex attribute renderer (the Dictionary Renderer) included with ArcGIS Pro, Runtime, and Server
- The stand-alone style files used by the Dictionary Renderer included with ArcGIS Pro, Runtime, and Server to render Military Symbols
- Data included with the Military Symbology Styles solution
- ArcGIS Pro 1.4+
- ArcGIS Runtime 100.0+
- ArcGIS Server 10.5+
- For more information see the Military Symbology Styles solution.
Includes:
- Styles for each version of the standard
- mil2525d
- mil2525c_b2 - a style used to draw both C and B Change 2 versions of the standard
- app6b
- Note: requires ArcGIS Runtime 100.1+ or Pro 2.1+
- These files are generated from source images and icon specification files from this repo
- This auto-generated file is then merged with the .stylx below that is edited/maintained in Pro
- This version is intended for end-users
- mil2525d-lines-areas-labels-base-template.stylx - a separate version of the military symbols .stylx that has only the Label Placement Definitions, Point, Line, Polygon, and Text Symbols that are manually created and maintained in ArcGIS Pro
- This version is intended only for use by the Product Engineers or maintainers of this repo/data
- Utilities and source data for creating the Military Symbology Styles
This is done with the file: mil2525d-lines-areas-labels-base-template.stylx
- In Pro, Add Style to project
- You may edit/correct the symbols and associated meta data in this file in Pro, update this repo with this file as needed (for repo Product Engineers or others making edits in Pro only)
- Before you edit this file in Pro, please read the Runtime Compatibility Warning section of the style-utilities README.md
- Once you have completed making any desired edits/changes, you will need to merge this file using the steps/process outlined in merge-stylx-utilities
Additional Usage Notes:
- When editing these files, ensure that the CIM version used by ArcGIS Pro is compatible with the product you are targeting.
- These files are intended to be viewed and edited in ArcGIS Pro but may be viewed with a SQLite viewer also.
The following version data is captured in the stylx "meta" table.
| Key | Current value/format/example | Description/Usage | Application Used By |
|---|---|---|---|
| version | 1.0 | Indicates the database schema for stylx files. | Pro |
| content | json | Indicates the content type of stylx. | Pro |
| cim_version | 1.1.0 | Indicates the version of CIM specification that is used/supported. | Pro/Runtime |
| forceRGB | true | CIM format option. This must be true to be compatible with ArcGIS Runtime. | Pro |
| vectorizeCM | true | CIM format option. This must be true to be compatible with ArcGIS Runtime. | Pro |
| densifyCurves | true | CIM format option. This must be true to be compatible with ArcGIS Runtime. | Pro |
| runtime_version | 1.0.0 | Indicates the version of the CIM Plugin API. | CIM Rule Engine Plugin Manager |
| rule_engine_plugin_version | 1.0.0 | Indicates the version of the CIM Rule Engine plugin dll. Note: this should match the "version" in the manifest/metadata file. | CIM Rule Engine Plugin Manager |
| pro_version | 1.1.0 | mil2525d plugin administrative entry. Version of ArcGIS Pro. | mil2525d plugin |
| milstylx_version | 1.1.0 | mil2525d plugin administrative entry. Version of the mil2525.stylx. | mil2525d plugin |
| milstd_version | 2525D-0.1 | mil2525d plugin administrative entry. Version of MIL-STD-2525. | mil2525d plugin |
| jmsml_version | 1.0.1 | mil2525d plugin administrative entry. Version of the JMSML used | mil2525d plugin |
You may view the style file with any SQLite viewer. Note: some viewers have difficulties showing multi-line text data such as the label drawing rules so you should pick a viewer that supports this if you need to view the label rules.
While in general we strongly discourage editing the style file, we recognize that special needs and requirements may arise. Please be advised that these edits aren't supported and that use or modification of this data remains governed by the Apache V2 license.
Example: Suppose you would like to replace the Friendly Blue icons with Lime Green ones, you might run an update query:
UPDATE SymbolInfo SET Json = REPLACE(Json, '128,224,255,255', '224,255,128,255') WHERE (Json LIKE '%128,224,255,255%')
The control measure line/area symbols that have unique point ordering and/or transformation rules defined in 2525C are captured in the symbol dictionary table "LnAExceptions." Use this table to determine at a glance which symbols have these special drawing rules. If you do not require these rules/transformations, you may be able to edit/modify this table to meet your specific needs. More information on these exception lines/areas can be found documented here.
If you view the table "LnAExceptions" (see above) you will see 2 particular columns of interest "Significant8Chars" and "GCT." "Significant8Chars" defines the middle (characters 3-10) part of the symbol ID that is significant for control measure lines/areas. These are the defined exception rules/enumerations in the "GCT" column: GCT_INDETERMINATE, GCT_ARROW, GCT_ARROWWITHOFFSET, GCT_ARROWWITHTAIL, GCT_CIRCLE, GCT_CIRCULAR, GCT_FREEHANDARROW, GCT_FREEHANDLINE, GCT_FREEHANDREVERSEARROW, GCT_FREEHANDU, GCT_HOOK, GCT_HORNS, GCT_OPENTRIANGLE, GCT_PARALLELLINES, GCT_PARALLELLINESMIDLINE, GCT_PARALLELLINESWITHTICKS, GCT_RECTANGULAR, GCT_RECTANGULAR1PT, GCT_T, GCT_TRIPLEARROW, GCT_TWOLINE, GCT_TWOLINE3OR4PT, GCT_UORTSHAPE There are 3 additional enumerations: GCT_POINT, GCT_POLYLINE, GCT_POLYGON that indicate no transformation is required. For more infomation on these rules consult the particular symbol in the standard. There is also a python class here that implements these transformations if you prefer to see them in code.
To modify this table (after you re-consult the warning here), in a SQLite viewer/editor of your choice, edit either the "Significant8Chars" column to change the symbol ID, the "GCT" column to change the transformation rule (for instance to "GCT_POLYLINE" to disable a special transformation), or remove the row(s) altogether (ex: delete from LnAExceptions where 1 = delete all rows, but doesn't remove the table).