army itam gis: developing a standard army training map ... · m. o’donnell, p. dubois / esri 2003...

M. O’Donnell, P. Dubois / ESRI 2003 International Conference 1

ARMY ITAM GIS: Developing a Standard Army Training Map Production Tool

Michael O’Donnell, ITAM Western Regional Support Center, Center for Environmental

Management of Military Lands1 Colorado State University, Fort Collins, CO

Paul Dubois, US Army Environmental Center, Aberdeen Proving Ground, MD

July 2003 The Integrated Training Area Management Program’s GIS Regional Support Centers (RSC) support production of military installation training maps for 115 Army installations. For smaller sites, this task requires data development and map layout, and the RSC are available for technical support to larger installations, which have onsite GIS operators. In order to streamline this production task, the RSC designed and implemented a standard process. A model personal geodatabase containing the majority of ITAM related feature datasets and feature classes was created using the CADD/GIS Technology Center's SDSFIE/FMSFIE Geodatabase Builder. An ITAM stylesheet was created using the Style Manager dialog. RSC developers created tools that create map elements such as conversion graphs, north arrows, scale bars, slope guides, projection parameters, and military grid reference system (MGRS) information using VBA.

This abstract was written by the Army Environmental Center and was not reviewed by the primary author.

1. Introduction 1.1 Background to ITAM and RSCs The Integrated Training Area Management2 (ITAM) program directs Army Department of Defense (DOD) land management decisions for optimization of maintaining sustainable military training lands while enhancing rapid unit deployment and concise combat scenarios in any range of environmental conditions (AR 350-4). DOD relies on four components of ITAM which assist in sustaining training requirements for decades on the same land while following US environmental and safety concerns, and conservation and land stewardship practices:

Land Condition Trend Analysis (LCTA), collecting and utilizing information concerning environmental condition and suitability; Training Requirements Integration (TRI), managing training requirements and land management; Land Rehabilitation and Maintenance (LRAM), reparation and maintenance of land while reducing long term impacts of military use; and Sustainable Range Awareness (SRA) (formerly known as Environmental Awareness (EA)), continual enhancement and distribution of educational requirements for the promotion of environmental stewardship and reduction of potential impacts for natural and cultural resources.

ITAM was first initiated under the Facilities Technology Application Test (FIAT) in 1983. The program was later tasked for development under the US Army Construction Engineering Research Laboratories (CERL), and finally an aggressive army-wide implementation for ITAM was initiated under the Office of the Deputy Chief of Staff for Operations and Plans (ODCSOPS) of 1993 (1995, Headquarters Department of Defense). ITAM later evolved to fully encompass the

1 Center for Environmental Management of Military Lands (CEMML). 2003. http://www.cemml.colostate.edu. (2003). 2 Integrated Training Area Management (ITAM). 2003. http://www.army-itam.com/home.jsp. (2003).

http://www.cemml.colostate.edu/

http://www.army-itam.com/home.jsp. (2003


management applications and directives discussed earlier. The Regional Support Centers3 (RSCs) are a component of ITAM which began in 1998 with the introduction of Geographic Information Systems (GIS) support for category three and four installations. The RSCs currently support all GIS applications aiding the ITAM components and directives for categories three and four installations as well as GIS technical support for categories one and two installations. Category one and two installations are larger training areas representing significant training resources for DOD while category three and four installations are typically smaller installations providing less training resources for DOD. The RSCs have rapidly evolved to keep current with new software developments and industry improvements within the GIS community. In prior years, the RSCs’ tasks first emphasized data development but recently they serve as a support team to aid the Army Environmental Center (AEC) and military installations with determining standards, producing technical guidelines and software tools; implementing analysis, map production, and visualization data procurement; and acting as a central data repository for ITAM. 1.2 Components of the Production Tool The RSCs developed the following components of the Army Training Map Production Tool: ArcMap template for coverages/shapefiles and personal/enterprise geodatabase, ITAM style sheet, documentation on available symbology of style sheet, map surround tools, documentation on how to create a Military Installation Map (MIM) using ArcMap, documentation on how map surround elements are derived and utilized, and a protocol for quality control/quality assurance of a MIM product. The tool is designed to produce MIMs resembling NIMA maps as well as permit entry-level GIS personnel to develop the maps in a timely and cost-effective manner. These tools will enable quick turn-around of maps for training needs or combat use within a dynamic environment. The software tools developed using Environmental Systems and Research Institute, Inc. (ESRI) and Microsoft Visual Basic 6.0 will permit standardizing the production of MIMs, increase efficiency and cost-effectiveness for product output, enhance the ability for frequent alterations of maps, increase quality and standardization of maps portrayed approximately in real time, improve training requirements, and assist in land stewardship applications. 1.3 History of the Military Installation Map (MIM) and the Dynamic Role the Army Now Requires MIMs were first developed by the National Imagery and Mapping Agency (NIMA), formerly known as Defense Mapping Agency (DMA), in 19724. MIMs are designed for military training tools of DOD land ownership and leasing that aid in a multitude of training requirements. The primary use of MIMs is for military personnel to gain the knowledge and skills of reading maps under diverse and challenging conditions resembling combat applications. Military personnel are required to learn all components of the maps so that tactical decisions can be made while engaging opponents. Therefore, utilizing MIMs during training procedures maintains high relevance for DOD’s ability for successful combat engagement. In addition to requirements of military personnel having the ability to read topographic maps, MIMs are now including land restriction use areas and dynamic training requirements. Therefore, the demand for readily developing MIMs with new training exercises and new environmental constraints lends to software products that do not demand a decade of experience and hundreds of thousands of dollars for map production. DOD and various training components of the Army also require additional training efforts such as Air Operation exercises and Combined Arms Live Fire Exercises (CALFEX) which often require information affecting air space, noise abatement 3 Regional Support Centers. 2003. http://www.army-itam.com/gis/page1.html. (2003). 4 Dudley Know Library. Map Collection. (2003). http://library.nps.navy.mil/home/mapcollection/htm#military. (2003).

http://www.army-itam.com/gis/page1.html

http://library.nps.navy.mil/home/mapcollection/htm


zones or a combination of ground and air components. MIMs are typically tailored for training on the ground and in the past were not easily updated and used dynamically. With new software applications designed by ESRI and map surround tools developed by the RSCs, mapping applications and land stewardship can be portrayed closer to real-time and allow alterations based on real-time training requirements. 1.4 Map Surround Elements and Their History NIMA includes numerous map surround elements on their MIMs that are not utilized on other published maps such as the United States Geological Survey (USGS) topographic series. The map surround tools developed in this application, which also resemble NIMA MIMs, will produce a Slope Guide, Military Grid Reference Guide, Magnetic North Arrow/Grid North Arrow/True North Arrow Guide, SI Conversion Guide, Map Definition Guide, and Scale Bars. Almost all maps today contain scale bars, north arrows, and map definitions but the other surround elements are not usually captured on topographic map series. Additionally, map surround elements located on MIMs usually deviate from those elements located on other topographic maps. Therefore, these tools will not only aid cartographers to include such elements on specials but also standardize how and where they are portrayed. Although the map surround elements are designed specific to military applications, these map surround elements are also practical for any topographic map being used for navigation. The Center for Environmental Management of Military Lands first developed an Arc Macro Language (AML) application that created the map surround elements using ArcPlot in 1997. These tools are now being carried over to an object oriented application allowing inclusion of various geodetic models and procedures that can be developed in ArcMap. The new programs will advocate more robust procedures, and therefore eliminate hard coding as well as enhance and standardize the output while following NIMA standards. Information gathered from geodetic models produced by various entities will avoid misuse of tools and decrease the level of efforts for determining inputs used in the construction of the map surround elements. The RSCs were tasked by the Army Environmental Center in 2002 to migrate the map tools developed in AML to Visual Basic for use in ArcMap. The RSCs will finalize the migration of these tools as well as enhance the tools and documentation during 2003. 1.5 Military Requirements Military personnel on the ground, water, and in the air all require mechanisms for navigating terrain and locating military targets. Rather than the RSCs reinventing what was once well established and orchestrated, they have followed the guidelines implemented by DMA and NIMA. However, due to inconsistencies of MIM products or at least alterations over time, the RSCs have elaborated, clarified, and adjusted guidelines to not only meet existing standards but also incorporate the enhancements brought forth with the integration of ESRI products. Due to increased requirements for updating maps produced by DMA/NIMA of military installations many years ago, the Army DOD is progressively acting to meet current mapping technologies while aiding ITAM Natural Resource Management requirements and sustaining military training. The primary Army stipulation is to develop MIMs for approximately half of the ITAM-supported installations and provide technical support and tools for the other half of the ITAM community so that their sites can also be mapped. Therefore, having a standardization procedure and tools that help automate the production of MIMs is not only a cost-effective action but also directly influences the ability for the military to improve land stewardship and improve their ability to properly train personnel. 2. Standardization and Integration of the Map Production Tool


Standards applying to each of the tools being developed are cited when applicable, but some circumstances require deviation from existing standards because either the standard is antiquated or has been altered for the ITAM program and new technological developments. 2.1 Template The ArcMap template and layout for creating Military specials is based on previous NIMA specials and/or documentations developed by NIMA, the Army and other recognized entities as referred to in these documents: PS/3AA/101; CADD/GIS Technology; FM101-5-1/MCRP 5-2A; FM 21-31; MIL-STD-240. All aspects of the ArcMap template reflect the layout, fonts and features standardized in NIMA MIMs. Map templates are created for two map scales - 1:25,000 and 1:50,000. The templates are based on, but not limited to, Spatial Data standards for Facilities Information and Environment5 (SDSFIE) data layers and attributing. The template is not designed for official publication and therefore certain NIMA standards for publication content are not incorporated; such contents include call numbers, reference numbers, product numbers, and location of publication. A document accompanying the template will address all technical aspects for creating military specials as they relate to ArcGIS software. Topics include stepwise procedures for developing MIMs, printing with regards to creating color separates, utilizing spot colors, capability of blue-green light readability and red light readability, procedure for adding data, utilizing symbols, rotation of main data frame with convergence angle, and adding graticules with no rotation. 2.1.1 Methodology for Developing Template To create your map document with a desired or required layout, develop a map document and then save as an ArcMap template. Creating an ArcMap template with data is not recommended; only the layout and location of data frames and surround elements should be included in the template. 2.2 Style Sheet The RSCs developed the majority of symbols affiliated with most installation specials in an ArcMap style sheet based on existing NIMA installation specials, Army DOD, and USGS standards. The symbols the RSCs assign to military layers will continue to be reviewed and amended in order to closely match existing standards (FM 21-31; FM 101-5-1; MIL-PRF-89045; MIL-HDBK-857) and any new standards. Although MIMs require red-light readability, such stipulations have not yet been integrated into the style sheet. Additionally, ArcMap v. 8.3 does not currently support spot colors or transparent fonts utilized for training area labels and therefore such requirements could also not be supported. The symbols have been tested and modified to work with 1:50,000 scale MIMs but may require size adjustments when working with various scales. Documentation on how symbols were developed, where symbols were mimicked, if used from a government agency, and all other relevant information will be noted. 2.2.1 Methodology for Developing Style Sheets/Symbols The features/symbols determined for inclusion in the style sheet are based on what typically is located on MIMs as well as how the features correlate to SDSFIE. 5 CADD/GIS Technological Center. Spatial Data Standards for Facilities Infrastructure and Environment. 2003. http://www.tsc.wes.army.mil. (2003).

http://www.tsc.wes.army.mil/


1. Navigate to Tools | Style Manager… 2. When the ‘Style Manager’ dialog opens, click on Styles (tab) | Create New…. 3. Navigate to location where the style is to be saved and name it as ‘file.style’ then

save. Note: folders in style will be yellow if symbols exist and white if no symbols exist. All folders created in a new style sheet will therefore be white.

4. To copy symbols from an existing style to your new style, navigate to an existing style in the style manager and select the desired element, copy, and then paste the element in your new style sheet. The elements transferred over must be of the same type (e.g. point, line, fill, et cetra). Change the name of symbol copied over if desired.

5. To edit the properties of a symbol, click on the folder containing the symbol, then double click on the symbol. Edit the symbol as desired and save.

6. When using text in your symbols, select ‘Type’ as ‘Character Marker Symbol’. Then select character and offset to spell out desired words or acronym. Each letter of a word will represent a different layer to the symbol. When using images in your symbol, select ‘Type’ as ‘Picture Marker Symbol’. Any combination outlined above may be used for creating desired symbols.

7. Hatches and line patters are very easy to modify through ESRI GUI and therefore will not be elaborated. For additional information read ESRI’s help documentation.

2.3 Dynamics of Map Surround Elements Refer to Appendix A for pictorials of both Graphical User Interfaces of the tools and output to be generated by the tools. Refer to Appendix B for constants used within the program development. Refer to Appendix C for MIM layout standards suggested by NIMA. 2.3.1 Slope Guide Definition The slope guide depicts the slope between any two adjacent intermediate contour intervals or between any two adjacent index contour intervals. The horizontal lines represent the slope increments and the vertical lines represent the distance between two adjacent contours for a specific slope. The information portrayed from the slope guide permits users in the field to determine whether terrain is suitable for walking, driving vehicles or whether the area is accessible at all. Considerations for Programming

• The user cannot specify a minimum slope of 0 because calculations will result with an undefined term.

• To adjust the slope guide height, reduce or increase the range of percent slopes. However, NIMA stipulates that 10 divisions will always be created.

• Produce an option for specifying contour intervals as feet or meters. • Only one slope guide can represent one contour interval. If multiple contour intervals

are depicted on a MIM, multiple slope guides with notation of contour intervals may be required. At the minimum, notation is required whenever more than one contour interval is present on the MIM.

Calculations Utilized in Programming The requirement for developing a slope guide is to determine the length of the horizontal line between each contour interval (CI) for a specified percent slope. The contour interval and map scale are the two primary components affecting the slope guide output. The last component is the equivocal value of percent slope but denoted as degree slope (Appendix A).


ratio slopeCI

.1) 10% (e.g. Guideon slopecurrent for ratioPercent Ratio Slopescale. mapcurrent on based interval,Contour CI

=∆∆

==

===

XY

runriseslope

X2 CI

5% X1

π180*)tan(

:slope degree toslopepercent of Conversion

factor scale map)12*((inches) contoursbetween inchesin distance Horizontal

factor scale map)370.39*((meters) contoursbetween inchesin distance Horizontal

(inches) distance ground(inches) distance mapdistance map factor to ratioor scale map Converting

)ratio slope(; )(Theoremn Pythagorea

2

2

222

22

slope

x

x

CIxbac

=

=

=

+=+==

2.3.2 True North/Magnetic North Arrow/Grid North Guide Definition The ‘north arrow’ on NIMA maps includes three components which are discussed individually below. Although not previously built into this tool, two north arrows are required if two UTM zones are crossed in the map data frame. The tool will permit this option and properly label the zone number above the north arrows (PS/3AA/101). NIMA standard PS/3AA/101 explains: “complete the grid reference box and the declination diagram(s) in accordance with DA TM 5-241-1, [Grids and Grid References]. When overlapping grid ticks are shown, show two declination diagrams (Arrangement B).” Refer to Appendix C for a pictorial distinguishing between arrangements. When a UTM zone is crossed, data developers should either redefine their central meridian or use another coordinate system. Such a scenario is not likely to be a frequent issue but the program will account for it. Also, two sizes of the ‘north arrow’ may be used depending on the map arrangement required. Considerations for Programming

• Values of grid north, true north, and magnetic north should be determined for the center of the map sheet as it relates to the center of the UTM zone (or central meridian of the UTM zone).

• If a different ellipsoid is used, different results for the magnetic and grid north will be developed, and one will be required to update their map to reflect this information.

• If more than one UTM zone is applied for a map, then more than one ‘north arrow’ is required for creation on the MIM.

• Meridian convergence only applies to planer coordinates. • Because true north is always placed perpendicular to your map layout, the graphics of

your data frame requires orientation to the angle of convergence. However, one does not want to change the orientation of the latitude and longitude tics.

• The rotation of a mapsheet is the angle of convergence, ‘C’, in decimal degrees. Latitude and longitude tics will not be rotated on the map however. Your text should be perpendicular to the paper and not rotated with the data frame. This will not include any


text splined to topographic features such as streams, contour lines, county lines or so forth. One should also not rotate point symbols used in the graphic. Further explanation on what should and should not be rotated is outlined in documentation for creating a map template (Creating Installation Special Map Using the ITAM Map Template – Draft).

Rather than the program rotating the data frame for the user, a message box will denote the convergence angle in decimal degrees so the data frame can be properly rotated at a later time. The reason for not having the program rotate the data frame automatically is because the graticule coordinates and tics must first be converted to a graphic so they will not rotate. This procedure is explained in the documentation for creating a map template. 2.3.2.1 True North Definition True north represents a line of longitude from any point on earth to the North Pole. It can also be referred to as a meridian which in turn represents the earth’s rotational axis. The orientation of true north on all maps is directly north or perpendicular to the orientation of the map layout. Considerations for Programming

• None Calculations Utilized in Programming

• None 2.3.2.2 Magnetic North Definition Magnetic north is based on the earth’s geomagnetic fields which fluctuate on a daily/annual frequency. Magnetic declination is the angle between true north and magnetic north. Therefore the tool will reflect an average change (positive or negative) of direction based on an annual rate. NIMA did not include such rates on their MIMs but with enhanced geodetic models and improved cartographic applications, the output created by the Military Production Tool will reflect such information. Conceptualizing magnetic declination is important for map users to comprehend. If the magnetic arrow slants east of true north, the mapped region is west of the agonic line. The agonic line is found running through the east-central part of the US and toward the Northwest Territories of Canada north of Bathurst Island where there is no declination. This location in NW territories is the actual North Pole of the earth’s magnetic pole. Because of this, the declination west of agonic line is eastern declination and everything to the east of declination has a western declination. Considerations for Programming

• The magnetic north for each installation currently uses one specific day for determining its value. The best way to do this, which is commonly done on maps produced today, is to find the average magnetic field and then accompany this value with the rate of change. For example, if the magnetic north is averaged at 6 degrees over the last 5 years and is increasing on average 1 degree per year, 6±1 degrees will be noted.

• Elevation or land masses also influence magnetic north. The current magnetic north arrow values assigned to each installation were not adjusted for large land mass anomalies; therefore, values will need to be adjusted for this as well as for the scenario above. For the time being, magnetic north calculations will be based on a mean elevation extracted from the elevation guide data frame included on the MIM. If a Digital Elevation Model (DEM) is not available, the user will have the option of defaulting to mean sea level or entering any desired value. Further investigation of the


actual impact for excluding the elevation value from the model will be fully discussed in HELP documentation but at this time the affect is not fully understood.

• The previous calculations for magnetic north were hard coded and did not take into consideration geomagnetic model updates. HELP documentation for the integration of models will include protocols so updates become relatively easy with future releases.

• The geomagnetic models compiled in C by various government agencies are called from VB while variables are passed to and from the C program.

Calculations Utilized in Programming Several different geomagnetic models have been developed by various agencies. The International Geomagnetic Reference Field – Epoch 2000 (IGRF-2000) was developed by the International Association of Geomagnetism and Aeronomy (IAGA). The model which will be applied in the Military Map Production Tool (MIMT) is the DOD World Magnetic Model. This model was produced by USGS and the British Geological Survey as contracted by DOD, which in turn is distributed by NOAA’s National Geophysical Data Center6 (NGDC) (WM/OO/17R). Because DOD supports WGS84 only (TR8350.2), the model is designed for this datum. Therefore, all maps will be produced for WGS84 datum only. If time permits, a second model will be included in the tool to allow users to produce magnetic north angles based on other datums. Magnetic models are viable for five year durations and therefore the program will be developed so that updated models can be easily integrated into the map production tool. The current DOD model was developed in 2000 and therefore the model built in the MIMT will require replacement in 2006. The models are provided by several federal government agencies and are compiled as C programs. The RSCs will create a DLL (Dynamic Link Library) of the program using C++ and link it from the visual basic program. 2.3.2.3 Grid North Definition Grid north is an artificial direction coinciding with the UTM grid lines. The convergence of the meridian derivation is an angle representing the difference between the map projection (grid azimuth) and geodetic azimuth. It is the angle between the projection of the meridian at a point on the map and the projection’s North axis (typically represented by the y-axis of the projection). Convergence of a meridian is positive in the clockwise direction. By definition, a UTM grid can only be oriented to a single meridian, and the grid declination is the angular difference between grid north and true north. In other words, the grid north represents the direction and angle between the true north (UTM central meridian) and the relative location of the map sheet center. The further the UTM central meridian is from the center of the map, the more deviation between true north and grid north. If the north-south (horizontal) UTM grid lines tilt to the east on a map, the region lies to the east of central meridian for the specific UTM zone. The angle described above is also commonly referred to as the convergence angle ‘C’. When the center of your mapsheet is to the left of the UTM central meridian, then ‘C’ will be negative. If the center of your mapsheet is to the right of the UTM central meridian, then ‘C’ is positive. Because the width of a UTM zone is 6°, except for 31X - 37X and 31V - 32V, the convergence angle will always fall within +/- 3°. The exceptions to zones are a result of military requirements (Table 1). Because evenly spaced parallels on the ellipsoid project to unevenly, spaced parallels on the projection, the convergence of meridian is required for translating ones location onto a map.

6 NOAA. Earth’s Magnetic Field Version 4.0. 2003. http://www.ngdc.gov/cgi-bin/seg/gmag/fldsnth1.pl. (2003).

http://www.ngdc.gov/cgi-bin/seg/gmag/fldsnth1.pl


Latitude LongitudeUTM Zone Lower Upper West East Central Meridian

31 56 deg N 64 deg N 0 deg E 3 deg E 3 deg E32 56 64 3 12 931 72 84 0 9 332 72 8433 72 84 9 21 1534 72 8435 72 84 21 33 2736 72 8437 72 84 33 42 39

Not Used

Not Used

Not Used

Table 1. Exceptions to UTM Zones (TEC-SR-7). Longitude, latitude, and elevation above sea level represent a geodetic coordinate. These are the coordinates used on maps or GPS units based on an ellipsoid or model to best fit the shape of the earth. The geodetic latitude does not precisely correspond to the angle (in polar coordinates) from the center of the earth, which the geocentric coordinate system does. Geocentric Cartesian coordinates define the position of a point with respect to the earth’s center of mass. For these reasons, one must account for the angle of convergence. Declination Angle and Ground Distance Discrepancy The ground distance Error due to compass reading errors increases with distance and declination value and therefore, documenting such errors and ascertaining the importance of understanding how these north arrow components are calculated becomes extremely relevant. For example, for a declination of 10 degrees, one traveling 1000 meters will have ground discrepancy of 174 meters; and for a declination of 1 degree, one traveling 1000 meters will have a ground discrepancy of 20 meters. Additionally, for a declination of 10 degrees, one traveling 5000 meters will have a ground discrepancy of 872 meters; and for a declination of 1 degree, one traveling 5000 meters will have a ground discrepancy of 100 meters. Converting Between Grid Azimuth and Magnetic Azimuth Do not confuse grid declination with convergence of meridian (COM), which is the difference between geodetic and magnetic north at the center of the map sheet. The magnetic north will be based on its relative position to the agonic line (zero declination). The Grid-Magnetic (GM) angle will be based on the relative position to the central meridian of the UTM zone. If you are using a compass and have a magnetic azimuth reading, you must first convert it to a grid azimuth. If you are using a grid azimuth from your map and you need a magnetic azimuth in the field, then you must convert to a magnetic azimuth. If magnetic azimuth is to the left of grid north then subtract the difference of these two angles from the magnetic azimuth, commonly referred to as the GM angle. To convert the grid azimuth to magnetic azimuth in the same scenario, add the GM angle. If magnetic azimuth is to the right of grid azimuth, then add the difference of these two angles from the magnetic azimuth. To convert the grid azimuth to magnetic azimuth in the same scenario, subtract the GM angle. Scale factor reduces the distance in a map projection to the actual distance on the reference ellipsoid. Two scale factors are required to distinguish from the calculations below. The Central Meridian (CM) scale factor is a constant that applies to only a location on the central meridian of the UTM zone or distance from pole with UPS. The point scale factor accounts for one’s position or distance deviating from the CM (Appendix B). The following concepts will help clarify the various components used in the calculations below. Geodetic coordinates are composed of latitude, longitude and height. Latitude is the angle between the plane of the equator and the plane through the ellipsoid position. Longitude is the


angle between meridian and prime meridian. Height (h) is the geodetic or ellipsoidal height, or the height between the ellipsoid and physical surface. Geoid separation (N) or height is the difference in distance between the geoid and mathematical reference ellipsoid, which can be thought of as the height between the ellipsoid and geoid. Geocentric Cartesian coordinates are those coordinates with an origin at the center of the Earth’s mass.

Calculations Utilized in Programming The following information was extracted from TEC-SR-7. For additional information and primary sources refer to:

1979. US Department of Commerce, Coast and Geodetic Survey, Special Publication. No. 251.

1989. Stem. State Plane Coordinate System of 1983. NOAA Report NOS NGS 5 (1989). Testing of the visual basic code within MIMT will be verified using software produced by Eagle Technology7.

A. Determine Zone and Central Meridian of the Zone. Consider non-standard zones.

radiansin expressed

30zfor ; 180

)1776(

31zfor ; 180

)1836(

o

o

o

z

z

λ

πλ

πλ

≤+=

≥−=

B. Compute Transverse Mercator coordinates from Universe Transverse Mercator

coordinates.

( )

( )

( )

( )UTMTM

UTMTM

UTMTM

UTMTM

YY

YX

YY

XX

9996.1

000,000,109996.

1HemisphereSouthern

9996.1

000,5009996.

1HemisphereNorthern

=

−=

=

−=

C. Go Through the following calculations for determining COM using transverse Mercator coordinates.

7 Eagle Technology. Geodetics Calculator for Transverse Mercator Projections. 2003. www.wherearewe.co.nz/geodetics.html. (2003).

http://www.wherearewe.co.nz/geodetics.html


( )

[ ]

radiansin meridian centralradiansin

131072315

3241

307235

12877

43

25615

4096455

12815

41

83

16384175

2565

643

411

8sin6sin4sin2sin

2

1'

cos'tan

sin1

o

88

866

8644

86422

8642

8642

2

22

2

22

22

=−=Λ

−=

−=

−+=

−++=

−−−−=

+−+−=

−=

−=

==

−=

λλλ

ε

εε

εεε

εεεε

εεεε

φφφφφ

ε

εεε

φεηφ

φε

φ

o

o

o

A

A

A

A

A

AAAAAaSaba

t

aN

Iteration End

]8cos86cos64cos42cos2['

S'y-S

-'

:IterationStart

IterationFirst ;

:iterationKrakiwsky using φ latitudefootpoint theCalculate

8642

1

φφφφ

φφ

φ

φ

φ

φ

AAAAAaS

ay

o +−+−=

=

=


( )

( )3122

2

1

1221

11

122

1

2

22

41

41

41

21

216

21

21

21

41

215

21

21

41

21

214

21

213

5

1

53

1

3

11

6

1

64

1

42

11

111

1

sin1

)1(

sin1

tan2cos'

1'

25245469061

8624285

9435

21

1206sec

7202421

RNt

-

:φ from λ),( Find

φε

ε

φε

φφεη

εεε

ηη

ηη

ηηη

η

φλλ

φφ

φ

−

−=

−=

==

−=

−+++=

++++=

−−++=

++=

+

−+=

+

−

=

aR

aN

t

tttB

tttB

ttB

tB

NxB

nxB

Nx

NxB

NxB

Nx

o

UPS. toapplicablenot is COM Therefore undefined. is and (pole) 90φ then 2πφ If

:nsapplicatio for UPS Note

1 λo±=±=

426

42224224

22

6

66

4

44

2

22

1614861

4828131445

1720cos

24cos

2cos1

:),(factor scalePoint

ttD

tttD

D

DDDK

+−=

−−++−=

+=

Λ+

Λ+

Λ+=

ηηηη

η

φφφ

λφ

426

42224224

422

66

6

44

4

22

2

22617

501535152

231

315cos

15cos

3cos1sin

:),( (COM)meridian of eConvergenc

ttF

tttF

F

FFF

+−=

−−++−=

++=

Λ+

Λ+

Λ+Λ=

ηηηη

ηη

φφφφγ

λφ

2.3.3 Military Grid Reference Guide


Definition The Military Grid Reference System (MGRS) is a system used by the United States as shorthand for reference to location (TE-SR-7). The MGRS requires a coordinate system with Universal Transverse Mercator (UTM) or Universe Polar Stereographic (UPS) and units of meters. In several geographic locations, the UTM zones have been altered to accommodate military uses and simplification of zone delineations as noted in the Grid North Discussion. Considerations for Programming

• MGRS designators have changed over time and this tool will only compute the values for the most recent designators.

• Ellipsoids used in the map determine MGRS values and therefore such differences must be accommodated.

• Testing of MGRS values will be verified with software produced by NIMA8. Calculations Utilized in Programming Two primary values are calculated as inputs into the Military Grid Reference Box. These values include the UTM zone number/UTM band as well as the MGRS alphabetic designator. The MGRS value is affected by several characteristics which are contingent on the mapsheet extent, ellipsoid, geodetic latitude, UTM zone, Easting, and Northing. The Easting and Northing can each have between one significant digit and five digits. An example of how the MGRS are written for UTM can be reviewed in Table 2. XX Y ZZ # # # # # # # # # #U

TM Zone #

UTM

Zone BandAlphabetical designator

Easting Coordinate

(UTM

or UPS)

Northing C

oordinate (U

TM or U

PS)

Table 2. Illustration of how to write MGRS designators for UTM. The alphabetic designator represents the 100,000 meter grid square. The Easting and Northing coordinates are relative to the lower left corner of the 100,000 meter designator. Therefore, their values always range from 0-100,000 meters. These values must have the same resolution and must include leading zeros (Table 3). Because UPS does not utilize zones, the method for delineating MGRS designators is different (Graph 1).

Grid Size (Meters) MGRS Example Accuracy1:1,000,000 16TCC 100,000

1: 500,000 - 1:100,000 16TCC07 10,0001:100,000 - 1:12,500 16TCC0571 1,0001:50,000 - 1:12,500 16TCC052715 100

NA 16TCC05237152 10NA 16TCC05237152 1

Table 3. Illustration of MGRS designator for various map scales.

8 National Imagery and Mapping Agency. Geotrans 2.23-Geographic Translator. 2001. http://164.214.2.59/GandG/geotrans/geotrans.html. (2003).

http://164.214.2.59/GandG/geotrans/geotrans.html


DOD uses two grid systems, UTM for features falling between 84° North and 80° South and UPS for features falling north of 84° and south of 80°. Both UTM and UPS have a 30-minute latitude overlap. Refer to TEC-SR-7 for additional reference to MGRS designators. UTM Characteristics Each zone origin is 500,000mE, 0mN in the northern hemisphere and 500,000mE, 10,000,000mN in the southern hemisphere. UTM has a false Northing (a.k.a. latitude of origin) of 0 and a false Easting of 500,000m with a scale factor of .9996. The longitude of origin is represented by UTM zone central meridian. UPS Characteristics UPS has a false Northing of 2,000,000m and a false Easting of 2,000,000m with a scale factor of .994. Zone numbers are not assigned to UPS and therefore are not designated in MGRS. All meridians project to straight lines radiating from a central point

Y XK # # # # # # # # # #UPS G

rid

100,000 square m

eter designator

Easting C

oordinate (U

PS)

Northing

Coordinate

(UPS)

180 North Pole UPS

Y Z

0

0

South Pole UPS

B A

180

Graph 1. Illustration for denoting MGRS designators of UPS. 2.3.4 SI Conversion Guide Definition The international system of units (SI) refers to metric units. UTM can be noted in either meters or feet for positional units, but the standard being meters, a conversion guide is made available. In the United States, elevation values for contour intervals are often noted in feet. Therefore, the SI conversion guide translates feet to meters or meters to feet for easy reference. This is the primary reason for inclusion of the SI conversion guide on MIMs since most map coordinates are depicted in UTM meters WGS84. Considerations for Programming

• NIMA standards PS/3AA/101 explain: “the conversion graph includes only the elevation range depicted on the map. The length of the graph is adjusted to the first 100 meters above the highest point on the sheet and to the first 100 meters below the lowest point on the sheet. The conversion graph should be shown full size if space permits. Otherwise, it may be reduced to not smaller than 75% of original size. Show two or more conversion graphs when the map elevation range exceeds 700 meters.”

Calculations Utilized in Programming


−

−

−

−

01.)elevationLowest elevationHighest (

scale map12*)elevationLowest elevationHighest (

:feetfor incrementsbetween inchesin Distance

01.)elevationLowest elevationHighest (

scale map37.39*)elevationLowest elevationHighest (

:metersfor incrementsbetween inchesin Distance

Note: .01 represents the standard 1% increment used on conversion graphs of MIMs. 2.3.5 Map Definition Frame The map definition describes the coordinate system of the map, MGRS gridline distance, vertical datum, horizontal datum, control (if one is used), the organization the map was prepared by, and the publisher. The production tool is designed to populate about half the information required. The cartographer is required to fill in graticule, vertical datum, control, prepared by, and produced by. The user is allowed to modify other information but such alterations are not recommended. Once the production tool form is initiated, most of the fields will be populated with information extracted from the data frame. According to NIMA’s standard PS/3AA/101, the central meridian and latitude of origin are not included; however, USGS typically includes this information. This same information is inferred in the UTM zone but, it can be helpful if the end user is not familiar with UTM zones. The RSCs have modified the output to correspond to both USGS and NIMA standards. 2.3.6 Scale Bars Definition The scale bar is a measurement tool based on the map’s current scale. The cartographer will have options for a few different units of measurements to include on their MIMs but for the most part the types and formats of scale bars are dictated by NIMA standards. Considerations for Programming

• A known problem with ArcMap occurs whenever the scale of the data frame is altered (even though it is actually fixed) - the scale bar dimensions change and then become misaligned. The RSCs will need to investigate this issue and ensure it will not arise in the map surround tool scale bar. One possibility is to make the scale bar not from a MapObject but by line components. The downside to handling the problem as such way is that if the scale is changed, the scale bar has to be recreated. Because most of the tools produce scale-dependent elements, how the RSCs handle this may not be an important decision.

Calculations Utilized in Programming The calculations for converting map units to page units for a specific ratio factor follow the same principals used for calculating the SI conversion graph. 3. Software Applications


The Map Production Tools began development in ESRI ArcGIS 8.2, Microsoft Visual Basic 6.0 (VB 6.0) and Arc-MapObjects NT 2.1. The finalization of tool development will be completed in ArcGIS 8.3 and VB 6.0 due to recent ESRI upgrades. There will also be some applications developed in Microsoft Visual C++ version 6.0 which include magnetic models developed by other organizations:

• Convert existing AML tools to VB, MapObjects, and ArcObjects. • Implement all existing standards in tools. • Integrate all calculations into VB using VB, C++, ArcObjects, and MapObjects. • Improve mechanisms and correct current issues for calculating COM. • Permit use of UTM and UPS. • Fully implement MGRS notation in MGRS reference box with inclusion of coordinates

where designators change. • Automate extraction of projection information for projection definition tool. • Modify reporting of contour intervals on slope guide. • Require +/- 100 meter buffer to maximum and minimum elevation values on SI

conversion guide. • Modify and enhance GUIs to improve application for user-friendly interfaces. • Create help documentation. • Render all graphic elements produced by the tool as non-resizable and non-scalable.

However, allow elements to be moved in layout. • A message needs to appear if the mapscale changes at any time. The message will

instruct users that because the map surround elements are scale dependent, one is required to regenerate the elements or change the scale back.

• Enhance error handling with VB coding. The key to successfully writing any type of program application starts with an implementation plan:

1. Identify what the program needs to do. 2. Determine what programs and applications are going to be required based on designer

and user requirements. 3. Create a schematic depicting how the tools will relate to each other, the language and

the user. 4. Document how each tool works. 5. List all exceptions to all tools and assure these are built into the program. 6. Examine each component then look at the whole picture. If certain procedures are

executed for more than one program, consider building standard modules or classes. 7. Examine the function of each tool and consider how the GUI will be designed. Be

consistent in your programming so users are not required to learn multiple icons or statements which may refer to the same concept.

8. Start programming. As you begin, the programmer should build in error-handling guidelines.

9. Integrate help documentation into the program. Several tools exist and will be discussed below.

10. Test your software application. 11. Prepare software for deployment and then package the software.

3.1. Software Documentation Help The following software tools will be used for implementation of help documentation of the Map Production Tool: Microsoft HTML Help Workshop Version 4.74.8702.0 and Teletech Systems, Inc VB HelpWriter Version 4.3.3.

• Identifying important controls. • Handling of graphic images and tables must be considered because they require

different protocols.


• Creating a glossary and definitions dictionary. • Creating an interface with system requirements and information about the software. • Considering multi-level keywords versus single keywords for searches. • Integrating What’s This? Key words. • Use ‘F1’ for selected text Help. • Compiling and testing Help documentation. • Displaying context-sensitive help command bar controls.

4. Accuracy and Credibility 4.1 Background The credibility of Map Production Tools is justified by testing for standardization based on existing requirements. The calculations for each tool are made available for any desiring parties to scrutinize and all documents used for creating the tools are referenced for outside referrals. 4.2 RSCS Testing Implementation A brief description of how the RSCs will test the Map Production Tools is outlined below:

The RSCs will test 15 installations scattered within the western US, one site in Hawaii, one site in South Korea, and one site in Japan. The RSCs will also test 10 installations scattered within the Eastern US, one site in Germany, and one site in Puerto Rico. The MGRS (NIMA Geotrans) and Convergence Angle (Eagle Technology) software tools will be used as an independent test for verifying the convergence angles and MGRS values. The purpose for scattering the test sites and including so many sites is twofold. First, the need to test multiple MGRS designators and multiple zones will assure fewer mistakes. Second, several sites were chosen to test for overlapping UTM zones. Currently no testing is occurring for UPS but this may be done at a later time. Two forms developed by the RSCs will address questions in regards to the accuracy of the map surround elements based on calculations, format and content, and these forms will be utilized for the testing phase for the development of this tool. Currently no sites have been selected for UPS projected systems and no sites in the southern hemisphere have been set aside to verify the accuracy of the tools.

The RSCs will also test ‘Creating Installation Special Map Using the ITAM Map Template’ by creating a MIM based solely on the content of the document as well as answer questions about legibility, ease of use, level of detail, and practicality. The RSCs will use students or least experienced personnel of ArcGIS/ArcMap applications to gain the greatest input for completeness of the document. All answers from the two forms mentioned above will be used to make changes to the software based on incorrect calculations, misuse of map surround elements, and all other comments so the tools can be improved before release. 5. Product Deployment The various components of the Army Training Map Production tool will be compiled into an executable program which will include all components of the Map Production Tool including Standard Base Modules, Class Objects, Icons, DLLs of C++ files, and Help Documentation. The tool will be made available sometime in the end of August 2003 on the ITAM GIS Geographic Information and Services (GI&S) which will be linked through the ITAM. Two documents will be produced. The Developer’s Guide will document the history of code, alterations to the tools, and any known unresolved issues for internal government use, and will


not accompany the deployed executable. The User’s Guide will document explanations of each tool, relevant geodetic rules, how to use the tools, and how each tool applies to an installation special and accompany the deployed executable. Some tools will have restrictions in regards to the data available and these limitations will be fully discussed. Each document will cite references that have been previously published and that are relevant to the tool development process. The User’s Guide will serve as a complete documentation for all tools available for download online. 6. Future Enhancements Two additional tools that will benefit the ITAM program, but have not been considered beyond the programmer include a spell check tool and a tool that develops the required map extent. The spell checker would allow cartographers to check all spellings of text elements used within the map against Microsoft’s dictionary. Whether the spell checker can actually verify attributes labeled for individual data layers is not yet known. Currently, the RSCs have determined the map extent by using the following procedure which describes how to calculate the area being mapped outside the installation boundary per installation. The calculations below were determined by the RSCs and compared to NIMA mapping products. Although NIMA does not have a known standard or method for obtaining map extents, the RSCs have compared the results calculated here to assure an approximation of values used on NIMA maps. However, the RSCs did not necessarily find NIMA to be consistent on distances from north-south or east-west of data developed outside installation boundaries. The RSCs believe the method described below is a less subjective protocol for calculating the map extents of MIMs and will hopefully reduce individual interpretation for deciding an appropriate map extent. Also be aware that if this were to be applied for a military air operations map, one would substitute the installation boundary with the military air-surface boundary, the latter usually encompassing the area of interest.

Procedure 1. Determine a new area of the military installation boundary by drawing an imaginary

box or rectangle around the boundary so that the extent of the new area is minimized or represents the smallest size in which the installation can fit within.

yxAIE *axis-y alongboundary on installatibetween distancey axis- xalongboundary on installatibetween distancex

===

2. Extend the boundary of the box drawn above so that you’re mapping an area

outside of the installation which is equivocal to 1/4 or 1/8, scale dependent, of the area falling inside the box.

4

50,000:1n larger tha scale Map

8

smalleror 50,000:1 scale Map

4

8

IEIE

IEIE

AA

AA

=

=


3. Apply a percentage in the x- and y-direction so that the symmetry of your mapped area is asthetically pleasing.

44

44

88

88

*)(

*)(

50,000:1n larger tha scale Map

*)(

*)(

smalleror 50,000:1 scale Map

IEIE

IE

IEIE

IE

IEIE

IE

IEIE

IE

AAxyA

AAyxA

AAxyA

AAyxA

=

=

=

=

Note: the x- and y-axis are reversed above to obtain greater approximation of a square and less of a rectangle for the map extent relative to the shape of the installation boundary.

The values above should be rounded down to the nearest 100 meters before applying in the x and y direction.

4. Create your map extent box and develop data to this extent. The thought is to apply the above calculations and create a polygon layer representing the area determined with the above calculations using visual basic, ArcObjects and MapObjects.


Appendix A

These pictorials and screen captures are prototypes from either the AML or the VB application. Throughout developmental stages, any one of these pictorials or functions described within the document may change if dictated or desired. The current icon for the projection definition on the toolbar will all be modified for the release of the final map production tool. Map Production Toolbar

SI Conversion

North Arrow

Slope Guide

Scale Bars

Projection Definition

MG

RS Box

Spell Check

Map Extent

Grid Reference Guide

SAMPLE 1000 METER GRID SQUARE

46

4512 13

Samplepoint

SAMPLE 1000 METER GRID SQUARE

46

4512 13

Samplepoint

100,000 M SQUARE IDENTIFICATION

GRID ZONE DESIGNATION

10S

100 METER REFERENCE

1. Read large numbers labeling the VERTICAL grid line left ofpoint and estimate tenths (100 meters) from grid lineto point. 12 3

2. Read large numbers labeling the HORIZONTAL grid line belowpoint and estimate tenths (100 meters) from grid line topoint. 45 6

Example: 123456

WHEN REPORTING ACROSS A 100,000 METER LINE, PREFIXTHE 100,000 METER SQUARE IDENTIFICATION IN WHICH THEPOINT LIES.

Example: FG123456

WHEN REPORTING ACROSS THE GRID ZONE DESIGNATIONAREA, PREFIX THE GRID ZONE DESIGNATION

Example: 10SFG123456


Magnetic North Arrow

GRID CONVERGENCE

FORCENTER OF SHEET

GN

10/03/2002G-MANGLE

ELEVATION: 459 FEET

TOCONVERT AMAGNETIC AZIMUTHTO AGRIDAZIMUTH

TOCONVERTA GRID AZIMUTH TOAMAGNETIC AZIMUTH

GR

IDN

OR

TH

MA

GN

ET

ICN

OR

TH

TR

UE

NO

RTH


Slope Guide

3% 1.7º

4% 2.3º

5% 2.9º

6% 3.4º

7% 4º

8% 4.6º

9% 5.1º

10% 5.7º

11% 6.3º

12% 6.8º

13% 7.4º

14% 8º

15% 8.5º

PERCENTAGE DEGREE

A B C

AB - HORIZONTAL DISTANCE BETWEEN CONTOURSAC - HORIZONTAL DISTANCE BETWEEN INDEX CONTOURS

SLOPE GUIDE

Slope Guide Applies to Contour Interval of 10Feet Only


Conversion Graph

CONVERSION GRAPH(1 meter = 3.28 feet)Meters Feet

0

100

200

300

400

0

100

200

300

400

500

600

700

800

900

1000

1100

1200

1300


Scale Bar

ELEVATIONS IN METERS

SCALE 1:12,500

0.5 0 0.50.25 Miles

100 0 100 200 300 400 50050 Meters

0.5 0 0.50.25 Nautical Miles

GUI prototype is not yet available.


Projection Definition ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

SPHEROIDGRATICULEGRIDPROJECTIONVERTICAL DATUMHORIZONTAL DATUMCONTROL BYPREPARED BY

PUBLISHED BY! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

WGS84HALF MINUTE LATITUDE-LONGITUDE TICS

1000-METER UTM ZONE 10 (BLACK NUMBERED LINESUNIVERSAL TRANSVERSE MERCATOR

NATIONAL GEODETIC VERTICAL DATUM OF 19291984 WORLD GEODETIC SYSTEM

USGS, NATIONAL GEODETIC SURVEY POINTSCOLORADO STATE UNIVERSITY

CENTER FOR ENVIRONMENTAL MANAGEMENT OF MILITARY LANDSUNPUBLISHED


Appendix B

ConstantsSpheroid (WGS84)a = 6378137.000b = 6356752.314eccentricity or E squared = .006694379991/f or reciprocal flattening = 298.2572235

Coordinate System Origin False Easting False Northing CM Scale factor

UTM 0 North 500,000m

0m in N Hemp; 10,000,000m in S. Hemp. 0.9996 at at CM

UPS

North or South Pole 2,000,000m 2,000,000m 0.994 at pole

Constants Continued

Constants Continued1 nautical mile = 1,852m1 nautical mile = 6076.11548556 International Feet1 nautical mile = 6076.10333333 US Survey Feet1 International Statute mile = 1,609.344 meters1 International Foot = .3048 meters1 meter = 3.28083333 Survey Feet1 meter = 3.28083989501 International feet1 US Survey Foot = .30480060960 meter1 Inch = .0254 meters1 degree = 17.78 mils1 minute = 2.963 mils1 degree = .0175 radians1 second = .000004848 radians6400 mils = 360 degrees1 degree = 1/360th part of a circlePi = 3.141592653589792pi radians = 360 degrees


Appendix C Arrangement A1

Arrangement B1

1These images were scanned from a NIMA document (PS/3AA/101).


References Army Regulations AR350-4; Integrated Training Area Management (ITAM); Department of the Army; Washington

DC; 1998. Field Manuals FM 3-25.26 (21-26); Map Reading and Land Navigation; Headquarters Department of Army; 2001. FM 21-31; Topographic Symbols; Headquarters Department of the Army; Washington DC; 1961. FM 101-5-1/MCRP 5-2-A; Operational Terms and Graphics; Headquarters Department of the Army United States Marine Corps; Washington DC. 1997. Military Handbooks/Standards MIL-HDBK-857; Geospatial Symbology for Digital Display (GeoSym); (The document is subject

to change is not an officially released standard.) MIL-PRF-89045 Draft; Geospatial Symbols for Digital Displays (GeoSym); National Imagery and

Mapping Agency; 1998. MIL-STD-240; Mapping, Charting & Geodesy Reproduction and Printing; Headquarters Department of Army; 1995. Technical Manuals TEC-SR-7; Handbook for Transformation of Datums, Projections, Grids, and Common Coordinate

Systems; U.S. Army Corps of Engineers Topographic Engineering Center; Alexandra, VA; 1996. Technical Reports TR 8350.2; Department of Defense World Geodetic System 1984; National Imagery and Mapping Agency. Bethesda, MD; 2000. Training Manuals TM 8358.1; Datums, Ellipsoids, Grids, and Grid Reference Systems; Defense Mapping Agency; Bethesda, MD; 1990. TM 5-241-1; Grids and Grid References; Headquarters Department of the Army; Washington, DC; 1983. World Manuals WM/00/17R; Macmillan, S. and J. Quinn, 2000; The Derivation of World Magnetic Model 2000;

British Geological Survey Technical Report. Miscellaneous 1992. Muehrcke, Phillip and Muehrcke, Juliana. Map Use: Reading, Analysis, and Interpretation

3rd Ed. JP Publications. Madison, Wisconsin. 1995 August. Headquarters Department of the Army. Integrated Training Area Management

(ITAM) Program Strategy. Washington, DC PS/3AA/101; DMA 1:50,000 scale Prototype Style Sheet Appendix 7; Defense Mapping Agency;

Bethesda, MD; 1983.

army itam gis: developing a standard army training map ... · m. o’donnell, p. dubois / esri 2003...

Documents