Attachment 02 -- Data Layer Specification for Military Operations Feature Classes (15 December 2015).pdf

GEOFidelis

Geospatial Data Layer Specifications For GEOFidelis Data Model Version 3.0.0.1

Feature Type: ExplosiveDangerZone

Prepared for:

Marine Corps Installation Geospatial Information and Services Program (GEOFidelis)

12/15/2015

GEOFidelis Geospatial Data Layer Specification – ExplosiveDangerZone December 2015 i

TABLE OF CONTENTS

TABLE OF CONTENTS ........................................................................................... I DOCUMENT CHANGE HISTORY ............................................................................... II

1.0 FEATURE TYPE DESCRIPTION

2.0 POLICY AND REGULATIONS

2.1 DATA ACCESS AND RELEASE GUIDELINES

3.0 REPRESENTATION

3.1 GEOGRAPHIC REPRESENTATION

3.2 POSITIONAL ACCURACY

3.3 LOGICAL CONSISTENCY

3.4 TEMPORAL REPRESENTATION

4.0 VALID SOURCES AND SOURCE SELECTION CRITERIA

5.0 SPECIFICATIONS FOR ATTRIBUTION

APPENDIX A – FEATURE DATASET NAMING CONVENTION .................................. A-1 ii

DOCUMENT CHANGE HISTORY

Version Description Date Completed

0.1 Discussion Draft 6 Jan 2014

0.2 Revision based on Functional Data Set Lead feedback 10 Feb 2014

0.3 Preliminary Draft Approval 5 Mar 2014

0.4 Community Review 5 Jul 2014

0.5 Revision based on Community Review feedback 8 Aug 2015

0.6 Second Functional Data Set Lead Review 23 Aug 2015

0.7 Final Draft Approval 15 Dec 2015

1.0 Publication 21 Dec 2015

1.0 FEATURE TYPE DESCRIPTION

An explosive danger zone (EDZ) is defined as an area denoting the minimum safe distance from a site where explosive training will be conducted. EDZs are generally transient in nature and are only active while the associated activity is occurring.

The scope of this data layer is limited to EDZs associated with certified military ranges.

Certified ranges are ranges that have been certified using the Range Certification module found on the Marine Corps Range and Training Area Management System (MCRTAMS) website. Each EDZ included in the EDZ map and accompanying certificate package, derived from the Range Manager’s Toolkit (RMTK), should be included in this feature type.

Features without a corresponding record and data in the Range Manager’s Toolkit Explosive Training Range (RMTK ETR) ETRT_info table are invalid.

2.0 POLICY AND REGULATIONS

The following documents identify programs and policies pertinent to the creation and maintenance of the ExplosiveDangerZone feature type. The dates cited reflect the most recent version of the document at the time of this GEOFidelis Geospatial Data Layer Specification (DLS)’s publication.

DODI 4165.3 DoD Facility Classes and Construction Categories (24 Aug 2012) Available from the official Department of Defense (DoD) Issuances website http://www.dtic.mil/whs/directives/corres/ins1.html

MCO 3570.1 Range Safety (16 Apr 2014) Available from the Marine Corps Range and Training Area Management System website https://rtam.tecom.usmc.mil/rm/references.asp?SEID=RR_USMC

SOUM 6-15 The Range Managers Toolkit (RMTK) (14 Apr 2015) Available from the Marine Corps Range and Training Area Management System website https://rtam.tecom.usmc.mil/rm/Safety.asp?SEID=RS_SOUM

DODD 4715.11 Environmental and Explosives Safety Management On Operational Ranges Within the United States (24 Apr 2007)

Available from the official DoD Issuances website http://www.dtic.mil/whs/directives/corres/dir.html

DODD 4715.12 Environmental and Explosives Safety Management On Operational Ranges Outside the United States (24 Apr 2007)

Available from the official DoD Issuances website http://www.dtic.mil/whs/directives/corres/dir.html

DODI 4165.14 Real Property Inventory and Forecasting 17 Jan 2014) http://www.dtic.mil/whs/directives/corres/ins1.html https://rtam.tecom.usmc.mil/rm/references.asp?SEID=RR_USMC https://rtam.tecom.usmc.mil/rm/Safety.asp?SEID=RS_SOUM%20%20 http://www.dtic.mil/whs/directives/corres/dir.html

Available from the official DoD Issuances website http://www.dtic.mil/whs/directives/corres/ins1.html

MCO 3550.10 Ch 1 Policies and Procedures for Range and Training Area (RTA) Management (16 Feb 2008)

Available from the Marine Corps Range and Training Area Management System website https://rtam.tecom.usmc.mil/rm/references.asp?SEID=RR_USMC

MCO 3550.9 Range Certification (28 Jun 2004) Available from the Marine Corps Range and Training Area Management System website https://rtam.tecom.usmc.mil/rm/references.asp?SEID=RR_USMC

DODD 3200.15 Sustainment of Ranges and Operating Areas (21 Nov 2003) Available from the official DoD Issuances website http://www.dtic.mil/whs/directives/corres/dir.html

MCO P8020.11 Department of the Navy Explosives Safety Policy (15 Feb 2000) Available from the United States Marine Corps (USMC) official website.

https://www.marines.mil/News/Publications.aspx

2.1 DATA ACCESS AND RELEASE GUIDELINES

All USMC installations maintain both Unclassified and Controlled Unclassified Information (CUI) geospatial data. CUI is applied by DoD to its unclassified information that may be exempt from mandatory release to the public under Section 552 of Title 5, U.S.C., “Freedom of Information Act (FOIA).” GEOFidelis utilizes the Unclassified and CUI designations to assist IGI&S managers with data access and release. The data associated with the ExplosiveDangerZone feature type, has been designated as CUI. This designation has been set by the Functional Data Set Lead or the Geospatial Information Officer based on Federal policy, sensitivity, or HQMC determination. Implementation of the data access and release procedures that relate to this designation ensure all geospatial data is managed for continued operation of GEOFidelis on the Unclassified but Sensitive Internet Protocol (IP) Router Network (NIPRNet). Users with GEOFidelis accounts have full access to GEOFidelis geospatial data that is unclassified and not determined to be CUI.

3.0 REPRESENTATION

3.1 GEOGRAPHIC REPRESENTATION

The GEOFidelis Data Model (GDM) 3.0.0.1 feature type ExplosiveDangerZone will be used to represent the EDZ geospatial content. The Installation Subject Matter Expert (SME), the Range Control Officer (RCO) are responsible for identifying their respective installation’s current EDZs. EDZs are generated by the RMTK ETR tool, based on a calculation of the net explosive weight (NEW) of the explosive materials to be detonated and will be depicted as polygons (areas). The outermost geographic extent, or area contained within the polygon http://www.dtic.mil/whs/directives/corres/ins1.html https://rtam.tecom.usmc.mil/rm/references.asp?SEID=RR_USMC https://rtam.tecom.usmc.mil/rm/references.asp?SEID=RR_USMC https://www.marines.mil/News/Publications.aspx represents the minimum safe distance non-operational personnel must be from the detonation.

All EDZ features will be captured with horizontal (x, y) coordinates. Vertical (z) and measure

(m) coordinates are not required for EDZ polygons.

3.2 POSITIONAL ACCURACY

Positional accuracy for EDZs is contingent upon the data used by the RMTK ETR tool. To ensure a minimum absolute horizontal accuracy of 2.5 meters for EDZ features, explosive site features must meet the positional accuracy standards in the DLS for the ExplosiveSite feature type. The horizontal accuracy will be compiled, tested, and reported in accordance with Part 3 of the Federal Geographic Data Committee’s Geospatial Positioning Accuracy Standards: the National Standard for Spatial Data Accuracy (NSSDA). Spatial accuracy will be reported at the 95% confidence level. The spatial accuracy standard is available at http://www.fgdc.gov/standards/standards_publications/index_html.

3.3 LOGICAL CONSISTENCY

All data will adhere to GEOFidelis data management guidance regarding topological coherence. In addition:

• Most EDZ features will be inside and covered by the Site feature type, unless a specific business requirement necessitating the inclusion of features adjacent or contiguous to the boundary is noted in the feature type metadata (exceptions will be approved and in accordance with appropriate designated authority);

• EDZ areas may overlap with other EDZ areas provided overlapping areas contain unique attributes and are for discrete EDZs;

• And, EDZ features will not overlap features in the NoFireArea feature type.

3.4 TEMPORAL REPRESENTATION

EDZ features will reflect existing conditions. Updates to the completed ExplosiveDangerZone feature type will occur when an update to policy regarding the use of the applicable EDZ munition has been published, the source feature type (listed in 3.2) is changed, allowable activity parameters for an existing EDZ change, and/or the range certification or recertification parameters for the applicable munitions or weapons is designated. Updates to the completed ExplosiveDangerZone feature type will also occur when an existing EDZ is changed or a new EDZ is designated. At a minimum, the ExplosiveDangerZone feature type will be validated annually for changes to the EDZ creation parameters associated with the weapon system that the danger zone represents. Changes to the creation parameter will require changes to data and maps depicting the danger zone.

http://www.fgdc.gov/standards/standards_publications/index_html

4.0 VALID SOURCES AND SOURCE SELECTION CRITERIA

Information for the ExplosiveDangerZone feature type will be obtained and validated at the installation level from the RCO. The RCO will have overall responsibility for completing and updating the spatial, attribute, and metadata features of the ExplosiveDangerZone feature type, in accordance with this document and with all applicable GEOFidelis data management guidance.

The following source toolset is to be used in creating or maintaining the ExplosiveDangerZone feature type. Spatial data obtained from the following source must meet positional accuracy requirements specified in section 3.2.

• RMTK ETR Tool: This is the only valid method for EDZ spatial data creation. The RMTK ETR Tool includes an export function that exports the SDZ feature class to a GDM compliant database. To ensure positional accuracy the positional input data required to generate an EDZ must conform to the standards set forth in this document. For more information on the RMTK ETR tool visit the MCRTAMS Website at

HTTPS://RTAM.TECOM.USMC.MIL/

5.0 SPECIFICATIONS FOR ATTRIBUTION

Table 1 lists all GDM 3.0.0.1 attributes for the ExplosiveDangerZone feature type. In order to comply with USMC geospatial data standards, all of the following fields will be included in the attribute table, however not all fields are required to be populated. Attributes are categorized as Mandatory, Optional, or Conditional, as defined in the table below. This table does not list the attributes in order of appearance in the attribute table. Users have the ability to determine the order of attributes in their data. Foreign Key Attributes are highlighted in green within their respective categories.

• Mandatory: Attributes are required by the Functional Data Set Lead to be populated.

Null values are not permitted.

• Optional: Attributes are not required by the Functional Data Set Lead to be populated. Null values are permitted.

• Conditional: Attributes contingent upon another attribute being populated with a specific value. Contingency is determined by the Functional Data Set Lead.

https://rtam.tecom.usmc.mil/

Note: Data Source N/A indicates that there is no authoritative database or source from which this attribute will be populated.

Note: Foreign Key Attributes are highlighted in green. Corresponding Business Data Relationships are described in GEOFidelis data management guidance.

Table 1: GEOFidelis Data Model 3.0.0.1 Attributes

Attribute Name Description Assigned Domain

Values Example Values Data Source

MANDATORY

explosiveDangerZoneIDPK A unique, user defined identifier for each record or instance of an explosive danger zone.

Notes: If a naming convention does not exist, use the following naming convention:

EDZ(Feature type abbreviation)_AA(Two letter installation abbreviation)_000(three digit sequential number) See example values and Appendix A.

If a naming convention already exists, the above guidance may be disregarded.

N/A EDZ_BU_024;

EDZ_HI_134

N/A sdsFeatureDescription

A narrative describing the feature.

Notes: The Range Standard Operating Procedure (SOP) will be referenced in the creation of the description. Any other auxiliary information about the explosive danger zone can be listed in this field. Efforts will be made to maintain the field searchable by including keywords and delimiters like commas or underscores.

N/A Directional EDZ for a NEW of 5lbs on Range 101

N/A

Note: Data Source N/A indicates that there is no authoritative database or source from which this attribute will be populated.

Note: Foreign Key Attributes are highlighted in green. Corresponding Business Data Relationships are described in GEOFidelis data management guidance.

Values Example Values Data Source sdsFeatureName

The common name of the feature.

Notes: When applicable, feature name will reflect what is found in the Range SOP. Efforts will be made to ensure this field’s values are suitable for labeling on printed and electronic cartographic products.

N/A Range 101 Directional EDZ;

Rang 104 Bare Charge EDZ sdsID A unique identifier for all features and objects in the SDSFIE.

N/A 18098ff9-e616-49a9-b8b9-d81671e5bc0c

N/A [This attribute is system generated.]

EDZoneIDFK Foreign key linking to Explosive Training Range Tool Parameter Table.

N/A Range101_EDZ The ETRT_info “LocationName” value for the EDZ is the acceptable value for this field. This value can be found in the ETRT_info parameter table generated by the ETR Tool.

OPTIONAL

sdsMetadataID The foreign key to a metadata record.

Notes: Follow the procedures set in place by the GEOFidelis Program to populate this attribute.

N/A 10004567 N/A

A-1

APPENDIX A – FEATURE DATASET NAMING CONVENTION

Abbreviated feature type and installation names may be used in the attribution for this feature dataset. Table A-1 lists the standard abbreviations to be used for all Military_Operations dataset feature types.

Table A-1: MILITARY_OPERATIONS Feature Types

Feature Type Abbreviation AmmunitionStorage STLO ExplosiveDangerZone EDZ ExplosiveSite EXPS FiringSite FP ImpactArea RTIM MilitaryDropZone RTDZ MilitaryLandingZone RTLZ MilitaryLaserSurfaceDangerZone LSDZ MilitaryMoutStructure RTMT MilitaryObservation Position RTOP MilitaryRange RTRG MilitaryRangeEquipment RTEQ MilitaryRangeLighting RTLG MilitarySurfaceDangerZone SDZ MilitaryTarget TP MilitaryTrainingLocation RTTA MilitaryWeaponDangerZone WDZ NoFireArea RTNF RangeControllerPosition RTRC UnexplodedOrdnanceClearance RTUX USMCSpecialUseAirspace SUAR WeaponTargetLine WPLN

Table A-2 lists the standard abbreviations to be used for all installation names.

Table A-2: Installation Names

Installation Abbreviation MCLB Albany AL MCLB Barstow BA MCAS Beaufort BE MCSF Blount Island BI MCMWTC Bridgeport BP MCB Camp Butler BU

A-2

MCB Camp Lejeune LE Camp Mujuk MU MCAS Camp Pendleton PA MCB Camp Pendleton PE MCAS Cherry Point CP MCB Hawaii HI MCAS Iwakuni IW MCAS Miramar MI MCAS New River NR MCRD Parris Island PI MCB Quantico QU MCRD San Diego SD MCAGCC Twentynine Palms TP MARBKS Washington DC EI MCAS Yuma YU

MARFORRES MR

Feature Type: FiringSite

GEOFidelis Geospatial Data Layer Specification – FiringSite December 2015

TABLE OF CONTENTS ........................................................................................... I DOCUMENT CHANGE HISTORY ............................................................................... II

1.0 FEATURE TYPE DESCRIPTION

2.0 POLICY AND REGULATIONS

2.1 DATA ACCESS AND RELEASE GUIDELINES

3.0 REPRESENTATION

3.1 GEOGRAPHIC REPRESENTATION

3.2 POSITIONAL ACCURACY

3.3 LOGICAL CONSISTENCY

3.4 TEMPORAL REPRESENTATION

4.0 VALID SOURCES AND SOURCE SELECTION CRITERIA

5.0 SPECIFICATIONS FOR ATTRIBUTION

0.1 Initial Functional Data Set Lead Review 6 Nov 2013

0.2 Revision based on Functional Data Set Lead

feedback 10 Nov 2013

0.3 Preliminary Draft Approval 5 Dec 2013

0.4 Community Review 10 Dec 2013

0.5 Revision based on Community Review feedback 8 Aug 2015

0.6 Second Functional Data Set Lead Review 23 Aug 2015

1.0 Published 21 Dec 2015

A firing site is defined as a fixed location used for the firing of weapon systems. Fixed locations are geographic locations where a laser, direct fire and/or indirect fire weapon system will be fired. The scope of the FiringSite feature type includes all fixed firing site locations, including fixed linear locations such as start fire and cease fire lines, and convoy courses.

Firing site locations may also serve as observation points, in which case features will be recorded in both the FiringSite feature type and the MilitaryObservationPosition feature type.

Common names for this feature type include, but are not limited to, firing point, firing position, firing area, small arms firing point, mortar firing point, artillery firing point, multiple launch rocket system (MLRS) firing point, artillery firing position, battle position, fighting position, firing line, move-out lane, and firing movement lane.

The following documents inform programs and policies pertinent to the creation and maintenance of the FiringSite feature type. The dates cited reflect the most recent version of the document at the time of this GEOFidelis Geospatial Data Layer Specification (DLS)’s publication.

MCO 3550.9 Range Certification (28 Jun 2004) Available from the Marine Corps Range and Training Area Management System website https://rtam.tecom.usmc.mil/rm/references.asp?SEID=RR_USMC

MCO 3550.10 Ch 1 Policies and Procedures for Range and Training Area (RTA) Management (16 Feb 2008)

Available from the Marine Corps Range and Training Area Management System website https://rtam.tecom.usmc.mil/rm/references.asp?SEID=RR_USMC

MCO 3570.1 Range Safety (16 Apr 2014) Available from the Marine Corps Range and Training Area Management System website https://rtam.tecom.usmc.mil/rm/references.asp?SEID=RR_USMC

DODD 3200.15 Sustainment of Ranges and Operating Areas (21 Nov 2003) Available from the official Department of Defense (DoD) Issuances website http://www.dtic.mil/whs/directives/corres/dir.html

DODD 4715.11 Environmental and Explosives Safety Management On Operational Ranges Within the United States (24 Apr 2007)

Available from the official DoD Issuances website http://www.dtic.mil/whs/directives/corres/dir.html https://rtam.tecom.usmc.mil/rm/references.asp?SEID=RR_USMC https://rtam.tecom.usmc.mil/rm/references.asp?SEID=RR_USMC https://rtam.tecom.usmc.mil/rm/references.asp?SEID=RR_USMC

DODD 4715.12 Environmental and Explosives Safety Management On Operational Ranges Outside the United States (24 Apr 2007)

Available from the official DoD Issuances website http://www.dtic.mil/whs/directives/corres/dir.html

DODI 4165.14 Real Property Inventory and Forecasting (31 Mar 2006) Available from the official DoD Issuances website http://www.dtic.mil/whs/directives/corres/ins1.html

DODI 4165.3 DoD Facility Classes and Construction Categories (24 Aug 2012) Available from the official DoD Issuances website http://www.dtic.mil/whs/directives/corres/ins1.html

2.1 DATA ACCESS AND RELEASE GUIDELINES

All United States Marine Corps (USMC) installations maintain both Unclassified and Controlled Unclassified Information (CUI) geospatial data. CUI is applied by DoD to its unclassified information that may be exempt from mandatory release to the public under Section 552 of Title 5, U.S.C., “Freedom of Information Act (FOIA).” GEOFidelis utilizes the Unclassified and CUI designations to assist IGI&S managers with data access and release.

The data associated with the FiringSite feature type, has been designated as Unclassified.

This designation has been set by the Functional Data Set Lead or the Geospatial Information Officer based on the Federal policy, sensitivity, or HQMC determination. Implementation of the data access and release procedures that relate to this designation ensure all geospatial data is managed for continued operation of GEOFidelis on the Unclassified but Sensitive Internet Protocol (IP) Router Network (NIPRNet). Users with GEOFidelis accounts have full access to GEOFidelis geospatial data that is unclassified and not determined to be CUI.

The GEOFidelis Data Model (GDM) 3.0.0.1 feature type FiringSite will be used to represent the firing site geospatial content. The Installation Subject Matter Expert (SME), the Range Control Officer (RCO), will define an installation’s current firing sites. Firing site features will be depicted as points, lines, or polygons (areas).

http://www.dtic.mil/whs/directives/corres/dir.html http://www.dtic.mil/whs/directives/corres/ins1.html

Firing site points will represent the center of fixed locations utilized for firing weapon systems for sites that have a geographic area smaller than or equal to the sum of the acceptable positional accuracy and the size of the largest weapon system fired. For example, if the acceptable positional accuracy for a firing site is 2.5 meters, and the largest weapon system fired is an M1A1 Abrams, measuring 10 meters by 3.5 meters, the concrete pad that will be the firing site must be smaller than or equal to 15 meters by 8.5 meters to be recorded as a point feature. Figure 1 is an example of a firing site that should be recorded as a point feature.

Figure 1

If the size of the firing site’s geographic location is larger than the sum of the acceptable positional accuracy and the size of the largest weapon system fired, then the feature will be recorded as a polygon. Figure 2 is an example of a firing site that should be recorded as a polygon feature.

Firing site lines will represent the center of fixed linear locations used for the firing of weapon systems. Firing site lines can be a road along which targets will be engaged, a linear representation of static firing points, or the start and cease fire lines from a movement or maneuver box. Firing lines are typically known for their distance from the target.

Firing site polygons will represent the outermost extent of areas used as firing sites when there are no static firing points, or when static firing points have a geographic area larger than the sum of the acceptable positional accuracy and the size of the largest weapon system fired. Firing site polygons can represent a maneuver or movement box.

All firing site features will be captured with horizontal (x, y) coordinates. Vertical (z) coordinates are not required for firing site lines or polygons. However, firing site points will capture z values representing the height, in MSL elevation, at the base of firing site.

Measure (m) coordinates are not required for firing site points, lines, or polygons.

3.2 POSITIONAL ACCURACY

Figure 2

The minimum absolute horizontal accuracy for firing site features is 2.5 meters. Firing site features with a z coordinate must also meet a minimum absolute vertical accuracy of 5 meters. The horizontal accuracy will be compiled, tested, and reported in accordance with Part 3 of the Federal Geographic Data Committee’s Geospatial Positioning Accuracy Standards: the National Standard for Spatial Data Accuracy (NSSDA). Spatial accuracy will be reported at the 95% confidence level. The spatial accuracy standard is available at http://www.fgdc.gov/standards_publications/index.html.

3.3 LOGICAL CONSISTENCY

All data will adhere to GEOFidelis data management guidance regarding topological coherence. In addition:

• All firing sites will be inside and covered by the Site feature type;

• All firing sites will be fully contained within the corresponding MilitaryRange or

MilitaryTrainingLocation features;

• Firing site line features representing start and cease fire lines will be covered by the boundary of firing site areas;

• Firing sites serving as observation points will have the same geographic coordinate as corresponding features in the MilitaryObservationPosition feature type;

• Firing site areas may overlap with other firing site areas, or with firing site points or lines, provided the overlapping features contain unique attributes and are for discrete firing site features;

• And, firing site points may overlap with firing site lines, provided the overlapping features contain unique attributes and are for discrete firing site features.

3.4 TEMPORAL REPRESENTATION

Firing site features will reflect existing conditions. Updates to the completed FiringSite feature type will occur when a firing site’s geography or attribute values are changed, a firing site is removed, or a new firing site is designated. At a minimum, the FiringSite feature type will be validated annually to determine if revision of data or maps is necessary.

Information for the FiringSite feature type will be obtained and/or validated at the installation level from the RCO. The RCO will have overall responsibility for completing and updating the spatial, attribute, and metadata features of the FiringSite feature type, in accordance with this document and with GEOFidelis data management guidance.

The following source materials and toolsets, listed in order of preference, are to be used in creating or maintaining the FiringSite feature type. Spatial data obtained from the following sources must meet positional accuracy requirements specified in section 3.2. Sources that are to be used for attribution only are denoted as such in their description.

http://www.fgdc.gov/standards_publications/index.html

• Installation Policy Documentation – Utilize existing memos, orders or other documentation from, but not limited to, the following offices: Range Control, Natural Resource, Environmental and Archeological, and Installation Development or Planning Department/Division. When available for the firing site, installation policy documentation is the authoritative source for spatial and attribution data for a FiringSite feature.

• Range Standard Operating Procedures (SOP): A range SOP is set of instructions covering those features of operations which lend themselves to a definite or standardized procedure without loss of effectiveness. The procedure is applicable unless ordered otherwise. A range SOP is created and maintained by the installation range management/control office and it defines the processes and procedures associated with training on the installation's ranges and training areas. The range SOP provides data for allowed or available range areas, impact areas, target sites, firing sites, landing zones, drop zones, observation points, special use airspace and training areas. Restrictions associated with training on the installation may also be included in the range SOP – for example, limitations on what munitions can be fired at specific ranges, and restrictions on areas where firing or training is prohibited.

Ranges that have been certified for a specific training event through the range certification/recertification process may have maps depicting danger zones associated with the training events.

The range SOP will include maps depicting the ranges and many other range and training area feature types. If no installation policy documentation exists for a firing site, the range SOP is the authoritative source for attribution data. The range SOP is also a source for spatial data, however accuracy and precision of range SOP location information varies by installation, so range SOP spatial data may only be used if the installation’s range SOP meets the specified positional accuracy requirements.

• Traditional Survey – When utilizing traditional survey as the data collection method, a state licensed surveyor will perform a field survey that notes boundary features such as fences, rivers, lakes, roads, etc., and presence or absence of any monuments that were found or set. Depending on the format of the survey findings, a Geographic Information System (GIS) professional can export/create the layer in accordance with GEOFidelis data management guidance. Traditional survey is the preferred source for spatial data but will not provide much, if any, attribution data.

Discrepancies between traditional survey and any of the authoritative sources above should be brought to the attention of the RCO and reconciled.

• GPS Field Survey – All position fixes will be determined with 4 or more satellites.

Manual 3D or overdetermined 3D (5 satellites minimum) modes are acceptable. 2D fixes (using only three satellites) are not acceptable. 3D positions generated from 2D fixes supplemented with user entered elevations are also not acceptable. When the above settings do not provide the minimum acceptable horizontal positional accuracy, use the manufacturer’s recommended minimum number of satellites that will enable the collector to achieve better than 2.5m positional accuracy at a 95% confidence level. GPS field survey is a valid source of spatial data but will not provide much, if any, attribution data. Discrepancies between GPS field survey and any of the authoritative sources above should be brought to the attention of the RCO and reconciled.

• External Tabular Data – Utilize existing external tabular data from, but not limited to, the following sources: Installation Range Facility Management Support System (RFMSS) database, Range Control, and Installation Development or Planning Department/Division. External tabular data is commonly used to manage firing sites and can contain spatial and attribution data.

• Traditional Survey Documents – Utilize existing survey documents, signed and stamped by a state licensed surveyor, which accurately describe the feature(s) through a field survey. Survey documents will include noted boundary features such as fences, rivers, lakes, roads, etc., and presence or absence of a monument that was either found or set. The result may be an exportable geospatial file (CADD, shapefile, etc.) or recordable legal description, but may also only list the sources used and the findings sited.

• Imagery – Utilize imagery to extract spatial data for visible firing sites. To utilize imagery, a GIS professional can digitize features from a georeferenced raster dataset having spatial resolution of 1m or less and a horizontal accuracy of 2.5m or better.

• Hard-Copy Maps – Utilize existing installation hard-copy maps, blue prints, and Computer Aided Design (CAD) drawings, such as installation master planning maps, from, but not limited to, the following offices: Range Control, and Installation Development or Planning Department/Division. Hard-copy maps can provide attribution data, or spatial data if it appears as coordinates on the map. Location information should not be digitized for firing sites using a scanning and georeferencing process unless specified positional accuracy requirements can be achieved.

• External Geospatial Organization Data Sources – Utilize existing geospatial data from external sources to include, but not limited to, National Geospatial-Intelligence Agency (NGA) Military Installation Maps (MIMs). MIMs can provide attribution data but should not be used to digitize spatial data because MIM accuracy standards do not meet specified positional accuracy requirements.

Table 1 lists all GDM 3.0.0.1 attributes for the FiringSite feature type. In order to comply with USMC geospatial data standards, all of the following fields will be included in the attribute table, however not all fields are required to be populated. Attributes are categorized as Mandatory, Optional, or Conditional, as defined in the table below. This table does not list the attributes in order of appearance in the attribute table. Users have the ability to determine the order of attributes in their data. Foreign Key Attributes are highlighted in green within their respective categories.

• Mandatory: Attributes are required by the Functional Data Set Lead to be populated.

Null values are not permitted.

• Optional: Attributes are not required by the Functional Data Set Lead to be populated. Null values are permitted.

• Conditional: Attributes contingent upon another attribute being populated with a

Note: Data Source N/A indicates that there is no authoritative database or source from which this attribute will be populated.

Note: Foreign Key Attributes are highlighted in green. Corresponding Business Data Relationships are described in GEOFidelis data management guidance.

Values Example Values Data Source

MANDATORY

firingSiteIDPK

Primary key. A unique, user defined identifier for each record or instance of a firing point.

Notes: If a naming convention does not exist, use the following naming convention:

FP(Feature type abbreviation) _AA)Two letter installation abbreviation)_0000(A four digit sequential number See example values and Appendix A.

If a naming convention already exists, the above guidance may be disregarded.

N/A FP_LE_0017;

FP_YU_0021

N/A firingSiteType Discriminator. The type of firing point at the range.

FiringSiteType aerialGunnery;

grenades;

largeCaliber

N/A isStationary Is the firing line stationary or moving. N/A Yes; No N/A operationalStatus Operational status of the firing site. RangeOperationalStatus abandoned; closed;

historic

Note: Data Source N/A indicates that there is no authoritative database or source from which this attribute will be populated.

Note: Foreign Key Attributes are highlighted in green. Corresponding Business Data Relationships are described in GEOFidelis data management guidance.

Values Example Values Data Source sdsFeatureDescription

A narrative describing the feature.

Notes: The Range SOP will be referenced in the creation of the description. Include all information about the site available. For example, a list of allowable DODICs and allowed firing postures are all acceptable information for this field. Any other auxiliary information about firing site can be listed in this field. Efforts will be made to maintain the field searchable by including keywords and delimiters like commas or underscores.

N/A Lane01, 300yards, Prone, A062;

Artillery Firing Position, Gun Position 4, No M825

N/A sdsFeatureName

The common name of the feature.

Notes: If an established naming convention does not exist, use a similar naming convention as firingSiteIDPK.

Efforts will be made to ensure this field’s values are suitable for labeling on printed and electronic cartographic products.

N/A Lane 1 – 300 yds;

GP 4

N/A sdsID A unique identifier for all features and objects in the SDSFIE.

N/A 18098ff9-e616-49a9-b8b9-d81671e5bc0c

N/A [This attribute is system generated.]

Note: Data Source N/A indicates that there is no authoritative database or source from which this attribute will be populated.

Note: Foreign Key Attributes are highlighted in green. Corresponding Business Data Relationships are described in GEOFidelis data management guidance.

OPTIONAL

sdsMetadataID

The foreign key to a metadata record.

Notes: Follow procedures set in place by the GEOFidelis Program to populate this attribute.

N/A 10004567; 99923773 N/A

Abbreviated feature type and installation names may be used in the attribution for this feature dataset. Table A-1 lists the standard abbreviations to be used for all

ExplosiveDangerZone EDZ ExplosiveSite EXPS FiringSite FP ImpactArea RTIM MilitaryDropZone RTDZ MilitaryLandingZone RTLZ MilitaryLaserSurfaceDangerZone LSDZ MilitaryMoutStructure RTMT MilitaryObservation Position RTOP MilitaryRange RTRG MilitaryRangeEquipment RTEQ MilitaryRangeLighting RTLG MilitarySurfaceDangerZone SDZ MilitaryTarget TP MilitaryTrainingLocation RTTA MilitaryWeaponDangerZone WDZ NoFireArea RTNF RangeControllerPosition RTRC UnexplodedOrdnanceClearance RTUX

MCLB Barstow BA MCAS Beaufort BE MCSF Blount Island BI

MCAS Cherry Point CP MARBKS Washington DC EI MCB Hawaii HI MCAS Iwakuni IW MCB Camp Lejeune LE MCAS Miramar MI

MARFORRES MR

Camp Mujuk MU MCAS New River NR MCAS Camp Pendleton PA MCB Camp Pendleton PE MCRD Parris Island PI MCB Quantico QU MCRD San Diego SD MCAGCC Twentynine Palms TP

Feature Type: ImpactArea

GEOFidelis Geospatial Data Layer Specification – ImpactArea December 2015

TABLE OF CONTENTS ........................................................................................... I DOCUMENT CHANGE HISTORY ............................................................................... II

1.0 FEATURE TYPE DESCRIPTION

2.0 POLICY AND REGULATIONS

2.1 DATA ACCESS AND RELEASE GUIDELINES

3.0 REPRESENTATION

3.1 GEOGRAPHIC REPRESENTATION

3.2 POSITIONAL ACCURACY

3.3 LOGICAL CONSISTENCY

3.4 TEMPORAL REPRESENTATION

4.0 VALID SOURCES AND SOURCE SELECTION CRITERIA

5.0 SPECIFICATIONS FOR ATTRIBUTION

0.1 Initial Functional Data Set Lead Review 06 Nov 2013

0.2 Revision based on Functional Data Set Lead

feedback 10 Nov 2013

0.3 Preliminary Draft Approval 5 Dec 2013

0.4 Community Review 10 Dec 2013

0.5 Revision based on Community Review feedback 8 Aug 2015

0.6 Second Functional Data Set Lead Review 23 Aug 2015

An impact area is defined as the ground and associated airspace within the training complex used to contain fired or launched ammunition and explosives and the resulting fragments, debris, and components from various weapon systems.

The scope of the ImpactArea feature type is limited to dedicated and high-hazard impact areas. Dedicated impact areas are impact areas with permanently delineated boundaries normally used to contain non-sensitive ammunition and explosive munitions. High-hazard impact areas are permanently designated impact areas used to contain sensitive, high-explosive military munitions. A high-hazard impact area is normally delineated within a dedicated impact area where access is restricted due to unexploded ordnance (UXO) explosive safety hazards associated with the use of sensitive-fuse munitions. United States Marine Corps (USMC) Real Property assets as well as non-Real Property assets may be included in this feature type at the discretion of the Installation Range Control Officer (RCO). The Internet Navy Facility Assets Data Store (iNFADS) is the authoritative data source for all Navy and USMC facilities, described in greater detail in Section 4.0 of this document. This feature type will include select existing facilities within the basic category Impact, Maneuver, Training Areas (174) with Real Property Unique Identifier (RPUID) codes found in iNFADS, a Facility Type Code equal to ‘3,’ an RPA Type Code equal to ‘S,’ and the category code(s):

• 17430 (Impact Area Dudded) — An area having designated boundaries within which all ordnance will detonate or impact shall be categorized as Impact Area Dudded. This area includes all impact areas that do not contain automated targets or targets classified as real property. Vehicle bodies are sometimes placed in the area to act as targets for artillery direct and indirect fire. The primary function of the impact area is to contain weapons effects as much as possible using earthen berms or natural terrain features. Assume the impact areas contain unexploded ordnance and may not be used for maneuver. This area is typically managed and scheduled by a range name or code through the installation training or range control manager, and is accounted for with a separate facility number and individual real property record. Historic impact areas will also be represented in this feature type. Historic impact areas are areas previously used as dedicated or high-hazard impact areas for which use as an impact area has been suspended. Historic impact areas are no longer used to contain fired or launched ammunition and explosives and the resulting fragments, debris, and components. These areas may or may not have been cleared.

• 17431 (Impact Area Non-Dudded) — An area having designated boundaries within which ordnance that does not produce duds will impact is an Impact Area Non-Dudded. This area is composed mostly of the safety fans for small arms ranges. This area includes all impact areas that do not contain automated targets or targets classified as real property. The primary function of the impact area is to contain weapons effects as much as possible using earthen berms or natural terrain features. A separate facility number and individual real property record shall be issued to account for each area that should be managed and scheduled by a range name or code through the installation training or range control manager. Although these impact areas may be used for maneuver, when the weapons ranges are not in use, they will remain categorized as impact areas.

Temporary impact areas or surface danger zones will not normally be included in this feature type. However, temporary impact areas may be included in this feature type if, for example, the temporary impact area associates with a Land Owner Agreement for NON- DOD land.

Common names for this feature type include, but are not limited to, impact area, dudded impact site, impact restricted area, non-dudded impact site, historic impact area, and research development testing evaluation (RDT&E) range impact area.

maintenance of the ImpactArea feature type. The dates cited reflect the most recent version of the document at the time of this GEOFidelis Geospatial Data Layer Specification (DLS)’s publication.

MCO 3550.9 Range Certification (28 Jun 2004) Available from the Marine Corps Range and Training Area Management System website https://rtam.tecom.usmc.mil/rm/references.asp?SEID=RR_USMC

MCO 3550.10 Ch 1 Policies and Procedures for Range and Training Area (RTA) Management (16 Feb 2008)

Available from the Marine Corps Range and Training Area Management System website https://rtam.tecom.usmc.mil/rm/references.asp?SEID=RR_USMC

MCO 3550.12 Operational Range Clearance Program (21 Aug 2008) Available from the Marine Corps Range and Training Area Management System website https://rtam.tecom.usmc.mil/rm/references.asp?SEID=RR_USMC

MCO 3570.1 Range Safety (16 Apr 2014) Available from the Marine Corps Range and Training Area Management System website https://rtam.tecom.usmc.mil/rm/references.asp?SEID=RR_USMC

MCO 3571.2 Explosive Ordnance Disposal (EOD) Program (30 Aug 2010) Available from the official United States Marine Corps (USMC) website https://www.marines.mil/News/Publications.aspx

MCO 5090.2A Environmental Compliance Protection Manual (Aug 2013) Available from the official USMC website https://www.marines.mil/News/Publications.aspx

MCO 8020.10 Ammunition and Explosives Safety (31 Oct 2007) Available from the official USMC website https://www.marines.mil/News/Publications.aspx https://rtam.tecom.usmc.mil/rm/references.asp?SEID=RR_USMC https://rtam.tecom.usmc.mil/rm/references.asp?SEID=RR_USMC https://rtam.tecom.usmc.mil/rm/references.asp?SEID=RR_USMC https://rtam.tecom.usmc.mil/rm/references.asp?SEID=RR_USMC https://www.marines.mil/News/Publications.aspx

DODD 3200.15 Sustainment of Ranges and Operating Areas (21 Nov 2003) Available from the official Department of Defense (DoD) Issuances website http://www.dtic.mil/whs/directives/corres/dir.html

DODD 4715.11 Environmental and Explosives Safety Management On Operational Ranges Within the United States (24 Apr 2007)

Available from the official DoD Issuances website http://www.dtic.mil/whs/directives/corres/dir.html

DODD 4715.12 Environmental and Explosives Safety Management On Operational Ranges Outside the United States (24 Apr 2007)

Available from the official DoD Issuances website http://www.dtic.mil/whs/directives/corres/dir.html

DODI 4165.14 Real Property Inventory and Forecasting (31 Mar 2006) Available from the official DoD Issuances website http://www.dtic.mil/whs/directives/corres/ins1.html

DODI 4165.3 DoD Facility Classes and Construction Categories (24 Aug 2012) Available from the official DoD Issuances website http://www.dtic.mil/whs/directives/corres/ins1.html

NAVFAC P-78 Real Property Inventory Manual (Jul 2008) Available from the NAVFAC Enterprise Document Library’s Informational Publications website https://portal.navfac.navy.mil/portal/page/portal/navfac/navfac_docs_pp/p-pubs

2.1 DATA ACCESS AND RELEASE GUIDELINES

All USMC installations maintain both Unclassified and Controlled Unclassified Information (CUI) geospatial data. CUI is applied by DoD to its unclassified information that may be exempt from mandatory release to the public under Section 552 of Title 5, U.S.C., “Freedom of Information Act (FOIA).” GEOFidelis utilizes the Unclassified and CUI designations to assist IGI&S managers with data access and release. The data associated with the ImpactArea feature type, has been designated as Unclassified. This designation has been set by the Functional Data Set Lead or the Geospatial Information Officer based on Federal policy, sensitivity, or HQMC determination. Implementation of the data access and release procedures that relate to this designation ensure all geospatial data is managed for continued operation of GEOFidelis on the Unclassified but Sensitive Internet Protocol (IP)

The GEOFidelis Data Model (GDM) 3.0.0.1 feature type ImpactArea will be used to represent the impact area geospatial content. The Installation Subject Matter Expert (SME), the RCO, http://www.dtic.mil/whs/directives/corres/dir.html http://www.dtic.mil/whs/directives/corres/dir.html http://www.dtic.mil/whs/directives/corres/dir.html http://www.dtic.mil/whs/directives/corres/ins1.html https://portal.navfac.navy.mil/portal/page/portal/navfac/navfac_docs_pp/p-pubs will define an installation’s current impact areas. Impact area features will be depicted as polygons (areas).

Impact area polygons will represent the outermost geographic extent of areas used as impact areas. The extent of impact areas may be designated in the installation documentation, range Standard Operating Procedure (SOP) or defined by signs warning of the existence of the impact area along the perimeter. In any cases where these sources conflict, the range SOP will take precedence.

USMC owned impact area polygons that are identified as assets in real property will have a one-to-one relationship with iNFADS through the FacilityIDFK attribute. Impact areas that are not owned by the USMC may be included in this feature type at the discretion of the RCO, however these polygon features will not have an iNFADS correlation.

All impact area features will be captured with horizontal (x, y) coordinates. Vertical (z) and measure (m) coordinates are not required for impact area polygons.

3.2 POSITIONAL ACCURACY

The minimum absolute horizontal accuracy for impact area features is 2.5 meters. The horizontal accuracy will be compiled, tested, and reported in accordance with Part 3 of the Federal Geographic Data Committee’s Geospatial Positioning Accuracy Standards: the National Standard for Spatial Data Accuracy (NSSDA). Spatial accuracy will be reported at the 95% confidence level. The spatial accuracy standard is available at http://www.fgdc.gov/standards_publications/index.html.

3.3 LOGICAL CONSISTENCY

All data will adhere to GEOFidelis data management guidance regarding topological coherence. In addition:

• Impact areas may overlap provided the overlapping features contain unique attributes and are for discrete impact areas;

• Historic impact areas may overlap current operational impact areas.

• Impact areas will not overlap the NoFireArea feature type, with the exception of historic impact areas;

• And, all impact areas will be inside and covered by the Site feature type, unless they are over offshore waters.

3.4 TEMPORAL REPRESENTATION

Impact area features will reflect existing conditions. Updates to the completed ImpactArea feature type will occur when an impact area’s geography or attribute values are changed, an impact area is removed, or a new impact area is designated. Updates to the feature type’s attribution should also occur when related information is added to or modified in iNFADS. At a minimum, the ImpactArea feature type will be validated annually to determine if revision of data or maps is necessary.

Information for the ImpactArea feature type will be obtained and/or validated at the installation level from the RCO. The RCO will have overall responsibility for completing and updating the spatial, attribute, and metadata features of the ImpactArea feature type, in accordance with this document and with GEOFidelis data management guidance.

The following source materials and toolsets, listed in order of preference, are to be used in creating or maintaining the ImpactArea feature type. Spatial data obtained from the following sources must meet positional accuracy requirements specified in section 3.2.

Sources that are to be used for attribution only are denoted as such in their description.

• Internet Naval Facility Assets Data Store (iNFADS): iNFADS is the authoritative data source and system for the collection, processing, storage, and display of USMC real property facilities data. iNFADS maintains records of each facility (building, structure, utility, and land) of legal interest to the Department of Navy, which serve as the official records of the Navy’s real property assets. Records are governed by business rules which identify the specific data needed in order to create and update a facility record. GEOFidelis geospatial data layer features that are captured by the real property inventory are connected to their corresponding iNFADS records using the RPUID code captured in the attribute table. Further details on the realPropertyUniqueIdentifier attribute can be found in Table 1: GEOFidelis Data Model 3.0.0.1 Attributes. This source is to be used for attribution only.

• Installation Policy Documentation – Utilize existing memos, orders or other documentation from, but not limited to, the following offices: Range Control, Natural Resource, Environmental and Archeological, and Installation Development or Planning Department/Division. When available for the impact area, installation policy documentation is the authoritative source for spatial and attribution data for an ImpactArea feature.

• Range Standard Operating Procedures (SOP): A range SOP is set of instructions covering those features of operations which lend themselves to a definite or standardized procedure without loss of effectiveness. The procedure is applicable unless ordered otherwise.