This repository has been archived by the owner on Aug 28, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 32
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #333 from Esri/dev
June 2018 Release
- Loading branch information
Showing
459 changed files
with
116,058 additions
and
16 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,6 +13,7 @@ arc.dir | |
*.original | ||
*.mdb | ||
*.sav | ||
*.gdb | ||
|
||
############# | ||
## Python | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,83 @@ | ||
# app6d schema | ||
========================================= | ||
|
||
# Purpose | ||
|
||
This folder contains the Military Features Core Geodatabase Schema format and an empty geodatabase (in .zip format) and layer packages conforming to the current Military Features schema. | ||
|
||
## Schema Information | ||
|
||
The following information is intended to capture the format of the Military Overlay Schema for other applications that may depend upon this format. | ||
|
||
## Graphic Display Amplifiers | ||
|
||
The following fields control the display of symbols. | ||
|
||
| Attribute Name | 2525 D Field ID | Data Type | Range of Values | Default Value/Meaning | Sample Name | Sample Value/Meaning | Explanatory Notes | | ||
| -------------- | --------- | --------- | --------------- | ----------- | -------------------- | ----------------- | ----------------- | | ||
| symbolset | A/E/AC | short int | 00-99 | (per feature class) | "Air" | 01 ("air") | **REQUIRED** | | ||
| entity | A | long int | N/A | (per feature class) | "Military (Air) : Fixed-Wing" | "110100" | **REQUIRED** | | ||
| modifier1 | A | long int | 00-99 | 00 (None) | "Mobility : Air Mobile/Air Assault" | Modifier "01" for Modifier 1 | Optional | | ||
| modifier2 | A | long int | 00-99 | 00 (None) | "Close Range and Support : Casualty Staging" | Modifier "05" for Modifier 2 | Optional | | ||
| echelon | B | long int | 0-26 | 0 (None) | Squad | Squad=12 | Optional | | ||
| indicator | D/S/AB | long int | 0-7 | 0 (None) | Headquarters | Headquarters=2 | Optional (="HQ/TF/FD") | | ||
| identity | E | long int | 0-9 | 1 (Unknown) | "Friend" | 3 ("friend") | **REQUIRED** | | ||
| context | E | short int | 0-2 | 0 (Reality) | "Reality" | 0 ("reality") | Optional | | ||
| mobility | R | long int | 0,31-52 (None) | 0 | Rail | Rail=36 | Optional | | ||
| array | AG | long int | 0,61-62 | 0 (None) | Short Towed Array | Short Towed Array=61 | Optional | | ||
| operationalcondition | AL | long int | 0-5 | 0 (Present) | Planned | Planned=1 | Optional | | ||
| sidc | | string/TEXT | string length(8 or 20) | N/A | "01100110" | SymbolSet:"Air"/"01" + Entity:"100110" | Optional-allows len=20 or len=8(identity=unknown) SIDC format | | ||
|
||
## Text Amplifiers | ||
|
||
The following table lists the Modifier definitions from 2525D and their corresponding attributes in the symbol dictionary. | ||
|
||
| Attribute Name | 2525 D Field ID | Field Title | Notes | | ||
| ------------- | --- | ----------------- | ----- | | ||
| quantity | C | Quantity | | | ||
| reinforced | F | Reinforced or Reduced | | | ||
| staffcomment | G | Staff Comments | | | ||
| additionalinformation | H | Additional Information | | | ||
| additionalinformation2 | H1 | Additional Information 2 | Used in the Convoys and Airspace Coordination Area tactical graphics. | | ||
| credibility | J | Evaluation Rating | Credibility rating is second character of Evaluation Rating (J) field. | | ||
| reliability | J1 | Evaluation Rating | Reliability rating is first character of Evaluation Rating (J) field. | | ||
| combateffectiveness | K | Combat Effectiveness | | | ||
| signatureequipment | L | Signature Equipment | | | ||
| higherformation | M | Higher Formation | | | ||
| hostile | N | Hostile | | | ||
| idmode | P | IFF/SIF/AIS | | | ||
| direction | Q | Direction of Movement Indicator | | | ||
| sigintmobility | R2 | SIGINT Mobility Indicator | | | ||
| uniquedesignation | T | Unique Designation | | | ||
| uniquedesignation2 | T1 | Unique Designation 2 | Used as an additional field for Fire Support Lines tactical graphics. | | ||
| type | V | Type | | | ||
| datetimevalid | W | Date-Time Group (DTG) | First half of Date-Time Group (DTG) (W) field. | | ||
| datetimeexpired | W1 | Date-Time Group (DTG) | Second half of Date-Time Group (DTG) (W) field. Many systems use W1 as a trigger to delete symbol from map. | | ||
| z | X | Altitude/Depth | Maximum altitude for aviation tactical graphics. | | ||
| z2 | X1 | Altitude/Depth 2 | Minimum altitude for aviation tactical graphics. | | ||
| x | Y | Location | Longitude in degrees. | | ||
| x2 | Y1 | Location | Longitude in degrees 2. | | ||
| y | Y | Location | Latitude in degrees. | | ||
| y2 | Y1 | Location | Latitude in degrees 2. | | ||
| speed | Z | Speed | | | ||
| specialheadquarters | AA | Special C2 Headquarters | | | ||
| platformtype | AD | Platform Type | | | ||
| equipmentteardowntime | AE | Equipment Teardown Time | | | ||
| commonidentifier | AF | Common Identifier | | | ||
| distance | AM | Distance | | | ||
| distance2 | AM1 | Distance 2 | | | ||
| azimuth | AN | Azimuth | | | ||
| targetdesignator | AP | Target Designator | | ||
| guardedunit | AQ | Guarded Unit | | | ||
| specialdesignator | AR | Special Designator | | | ||
| country | AS | Country Code | | | ||
|
||
## Other/Special Cases | ||
|
||
| Attribute Name | 2525 D Field ID | Field Title | Notes | | ||
| ------------- | --- | ----------------- | ----- | | ||
| radius | AM | Distance | For special polygon symbols defined by attributes | | ||
| length | AM1 | Length | For special polygon symbols defined by attributes | | ||
| width | AM | Width | For special polygon symbols defined by attributes | | ||
| orientation | AN | Azimuth/Attitude | For special polygon symbols defined by attributes | | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# Ignore so the GDB can be unzipped and inspected here | ||
|
||
*.gdb |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# Ignore so the GDB can be unzipped and inspected here | ||
|
||
*.gdb |
Binary file modified
BIN
+18.5 KB
(110%)
military-overlay/mil2525b2/lpkx/MilitaryOverlay2525BChange2.lpkx
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# Ignore so the GDB can be unzipped and inspected here | ||
|
||
*.gdb |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# Ignore so the GDB can be unzipped and inspected here | ||
|
||
*.gdb |
Binary file not shown.
51 changes: 51 additions & 0 deletions
51
...tary-overlay/utils-source-and-test-data/comprehensive-test-generation/README.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,51 @@ | ||
# military-overlay / utils-and-source-data / comprehensive-test-generation | ||
========================== | ||
|
||
# Purpose | ||
|
||
The steps in this folder are used to create comprehensive (one symbol of each desired type) test datasets for military symbol data. | ||
|
||
# General Instructions | ||
|
||
## Source Data, Scripts, Models for Creating Comprehensive Test Datasets | ||
|
||
* The source or "truth data" is tabular data (in a .csv file) containing verified information about symbols from the standard: symbol code, name, etc. This data is located in the repo at: | ||
* [mil2525d](../../../military-symbology-styles/test-data/mil2525d/truth-data) | ||
* [mil2525c](../../../military-symbology-styles/test-data/mil2525c/truth-data) | ||
* [mil2525b2](../../../military-symbology-styles/test-data/mil2525b2/truth-data) | ||
* [app6b](../../../military-symbology-styles/test-data/app6b/truth-data) | ||
* This [link](../pairwise-test-generation/Complete_test_scripts) will take you to the location of a script and a model that automates the manual process outlined below. | ||
|
||
## Steps to create a Comprehensive Test Dataset (Manual) | ||
|
||
This is the manual workflow for test dataset creation for MIL-STD-2525 Projects (This workflow is the same for D, C, BC2 and App6 symbol sets). | ||
|
||
1. Open Microsoft Excel. | ||
2. Open a Master Excel file, containing information about all of the symbols in a particular version of the standard. | ||
3. Create a filter on Appendix, Affiliation, and Geometry. | ||
4. Sort on each field in the order above. | ||
5. Copy the results to a new tab in Excel. | ||
6. Rename the Count field to OID. | ||
7. In the OID field, create a sequential number for the first 3 records, then drag your cursor down, this will autopopulate the field (Ex. 1, 2, 3, ...) | ||
8. Save this as document as a .csv. | ||
9. Repeat steps until all desired appendices have been derived. | ||
10. Open ArcGIS Pro and create a new map. | ||
11. Add the csv files to the project using "add data." The tables will be added to your contents pane" | ||
12. Under Analysis, search for the Create Fishnet GP tool. | ||
* The output feature class will be the feature class you want to create for a particular appendix. | ||
* Change the template extent to "Current Display" | ||
* Use the attached spreadsheet for the appendix you want to test to figure out the number of rows and columns. | ||
For example, if there are 100 symbols in an appendix, you could create a fishnet with 10 rows and 10 columns. | ||
* Select "Create Label Points" | ||
13. Run the Create Fishnet tool. | ||
* the only output that is pertinent to this workflow are the label points. | ||
14. Join the .csv of your desired appendix to the Fishnet output. | ||
* right-click on the Fishnet output and "Add Join" | ||
* The input and output join fields will both be OID | ||
* The join table will be the corresponding appendix .csv. | ||
* Run to execute tool and check to make sure that all of the .csv fields were properly joined to the fishnet points. | ||
15. Use the Copy Features tool to create a new feature class from the join output. This will ensure that the attributes are editable in the future. | ||
* Right click the feature layer and select "Data, Export Features." | ||
16. Symbolize the points using the dictionary renderer | ||
* Under the symbology pane for the fishnet feature layer, select your desired dictionary renderer and ensure the fields are properly matched up. | ||
17. Share/package the resulting dataset. |
Binary file added
BIN
+2.89 MB
...tary-overlay/utils-source-and-test-data/layer-package-utilities/LayerPackageUtilities.tbx
Binary file not shown.
21 changes: 21 additions & 0 deletions
21
military-overlay/utils-source-and-test-data/layer-package-utilities/README.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
### Tools for creating Pro Layer Packages (lpkx) | ||
|
||
These steps/tools are used to create a Schema-Only layer package for Military Overlay. | ||
|
||
A layer package is a file that includes the layer properties (ex. drawing settings, renderer, etc.) and data. A schema-only layer package has an empty geodatabase (no data entries). | ||
|
||
To create the layer packages: | ||
|
||
1. Download the latest version of the Military Overlay solution: http://solutions.arcgis.com/defense/help/military-overlay/ | ||
2. Create a Pro project, this will have 2 maps, one for each standard | ||
3. For each map/standard share the Military Overlay layer as a schema-only layer package after performing the workaround below. | ||
|
||
**Spatial Index Layer Packaging Workaround** | ||
|
||
There is currently a workaround to address an error "Spatial Index Invalid" (See: https://github.com/Esri/military-features-data/issues/287 ) | ||
|
||
Run the following tools from the LayerPackageUtilities toolbox on each geodatabase being packaged. These tools/models should be run immediately before packaging the (schema only) Military Overlay Layer Packages in ArcGIS Pro: | ||
|
||
1. Delete All Features From Workspace | ||
2. Remove Spatial Index | ||
a. This is a model that will add a blank spatial index to a layer package |
1 change: 1 addition & 0 deletions
1
...airwise-source-data/mil2525b2/extendedfunctioncodesBc2/ExtendedFunctionCodeActivities.csv
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
OFIP------,OFIPD-----,OFIPF-----,OFIPG-----,OFIPI-----,OFIPR-----,OFIPS-----,OFIPV-----,OFLP------,OFLPB-----,OFLPG-----,OFLPM-----,OFLPW-----,OFOP------,OFOPA-----,OFOPD-----,OFOPE-----,OFOPF-----,OFOPH-----,OFOPHA----,OFOPHT----,OFOPHV----,OFOPK-----,OFOPM-----,OFOPO-----,OFOPP-----,OFOPR-----,OFOPRC----,OFOPRW----,OFOPS-----,OFOPU-----,OFOPY-----,OFOPYH----,OFOPYT----,OFOPYW----,OFVP------,OFVPA-----,OFVPB-----,OFVPD-----,OFVPM-----,OFVPMA----,OFVPMB----,OFVPMC----,OFVPP-----,OFVPS-----,OFVPY-----,OHVPEI----,OHPPF----- |
1 change: 1 addition & 0 deletions
1
...ta/pairwise-source-data/mil2525b2/extendedfunctioncodesBc2/ExtendedFunctionCodeSIGINT.csv
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
IFAP------,IFAPS-----,IFAPSC----,IFAPSCC---,IFAPSCO---,IFAPSCP---,IFAPSCS---,IFAPSR----,IFAPSRAI--,IFAPSRAS--,IFAPSRC---,IFAPSRD---,IFAPSRE---,IFAPSRF---,IFAPSRI---,IFAPSRMA--,IFAPSRMD--,IFAPSRMF--,IFAPSRMG--,IFAPSRMT--,IFAPSRTA--,IFAPSRTI--,IFAPSRTT--,IFAPSRU---,IFGP------,IFGPS-----,IFGPSC----,IFGPSCC---,IFGPSCO---,IFGPSCP---,IFGPSCS---,IFGPSCT---,IFGPSR----,IFGPSRAA--,IFGPSRAT--,IFGPSRB---,IFGPSRCA--,IFGPSRCS--,IFGPSRD---,IFGPSRE---,IFGPSRF---,IFGPSRH---,IFGPSRI---,IFGPSRMA--,IFGPSRMF--,IFGPSRMG--,IFGPSRMM--,IFGPSRMT--,IFGPSRS---,IFGPSRTA--,IFGPSRTI--,IFGPSRTT--,IFGPSRU---,IFPP------,IFPP------,IFPPS-----,IFPPSC----,IFPPSCD---,IFPPSR----,IFPPSRD---,IFPPSRE---,IFPPSRI---,IFPPSRM---,IFPPSRS---,IFPPSRT---,IFPPSRU---,IFSP------,IFSPS-----,IFSPSC----,IFSPSCC---,IFSPSCO---,IFSPSCP---,IFSPSCS---,IFSPSR----,IFSPSRAA--,IFSPSRAT--,IFSPSRCA--,IFSPSRCI--,IFSPSRD---,IFSPSRE---,IFSPSRF---,IFSPSRH---,IFSPSRI---,IFSPSRMA--,IFSPSRMF--,IFSPSRMG--,IFSPSRMM--,IFSPSRMT--,IFSPSRS---,IFSPSRTA--,IFSPSRTI--,IFSPSRTT--,IFSPSRU---,IFUP------,IFUPS-----,IFUPSC----,IFUPSCO---,IFUPSCP---,IFUPSCS---,IFUPSR----,IFUPSRD---,IFUPSRE---,IFUPSRM---,IFUPSRS---,IFUPSRT---,IFUPSRU--- |
Oops, something went wrong.