|Title:||Military Operating Area Boundaries|
An Operating Area (OPAREA) Complex boundary is the bounded area in which national defense training exercises and system qualification tests are routinely conducted. OPAREA boundaries are formally established by national designation and by international treaty for national defense training purposes, and allow for specific exercises and training events to be coordinated with other federal, state, and local agencies, and also the general public, as in Notices to Mariners (NOTMARS). Includes the OPAREA, range complex boundaries and study areas.
The MarineCadastre.gov team worked with the Navy to provide this data, which is a subset of the Navy's Common Operating Picture, for ocean planning purposes. This data was derived from the Navy Common Operating Picture data which was received via email on December 6, 2018. Any questions about access to or the content of the data should be directed to the Navy at email@example.com.
This data is compliant with Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE) Version 2.6.
To support ocean planning activities pursuant to the Executive Order Regarding the Ocean Policy to Advance the Economic, Security, and Environmental Interests of the United States, the Energy Policy Act, the National Environmental Policy Act, the Rivers and Harbors Act, and the Coastal Zone Management Act.
This data was created by migrating COP Atlantic Gomex and PACFLT Operating Areas (OPAREA) features and attributes into SDSFIE 2.6 Military OPAREA Bnd Area feature class.
Installation_ID's were attributed with prefix value for operating area. E.g. JAX represents Jacksonville OPAREA. BOS represents Boston OPAREA.
All Primary Keys contain unique values. Primary Key was attributed by concatenating the Installation_ID prefix value with the Feat_Name or Feat_Description value.
Feature name and feature description, and data source values were attributed when possible. The data source field contains the name of the data source used in creating the feature class.
Original contact information:
Contact Name: EIMS Data WIPT Team
Contact Org: U.S. Fleet Forces
|Global Change Master Directory (GCMD) Science Keywords||
EARTH SCIENCE > HUMAN DIMENSIONS > ENVIRONMENTAL GOVERNANCE/MANAGEMENT
|ISO 19115 Topic Category||boundaries|
|ISO 19115 Topic Category||intelligenceMilitary|
|ISO 19115 Topic Category||oceans|
|None||Common Operating Picture (COP) Atlantic Gomex|
|None||U.S. Fleet Forces - U.S. Navy|
|Global Change Master Directory (GCMD) Location Keywords||
CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA
|None||Gulf of Mexico|
|Organization:||Office for Coastal Management|
Data Set Information
|Data Set Scope Code:||Data Set|
|Maintenance Frequency:||As Needed|
|Data Set Credit:||Department of Defense, NGA, NUWC|
Point of Contact
|Date Effective From:||2017-09-20|
|Date Effective To:|
|Contact (Organization):||NOAA Office for Coastal Management (NOAA/OCM)|
2234 South Hobson Ave
Charleston, SC 29405-2413
|Currentness Reference:||Ground Condition|
Extent Group 1
Extent Group 1 / Geographic Area 1
Extent Group 1 / Time Frame 1
|Time Frame Type:||Discrete|
Vector Representation 1
|Complex Object Present?:||Yes|
|Complex Object Count:||66|
|Data Access Constraints:||
|Data Use Constraints:||
MarineCadastre.gov Data Registry
Activity Log 1
Date that the source FGDC record was last modified.
Activity Log 2
Converted from FGDC Content Standard for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details.
Activity Log 3
Partial upload of Positional Accuracy fields only.
Version 6.2 (Build 9200) ; Esri ArcGIS 10.4.1.5686
The attributes in this dataset are believed to be accurate.
|Horizontal Positional Accuracy:||
Maximum scale of intended use is 1:80,000.
Spatial and attribute properties are believed to be complete. Geometric thresholds from original data are preserved. No tests have been completed for exhaustiveness.
These data are believed to be logically consistent. Geometry is topologically clean.
Military Operations Area OPAREA - Commander, U.S. Fleet Forces - U.S. Navy, Common Operating Picture (COP) Atlantic Gomex
|Contact Name:||U.S. Fleet Forces, EIMS Data WIPT Team|
|Extent Start Date/Time:||2017-08-11|
Common Operating Picture (COP) Atlantic Gomex, COP_Atlantic_GOMEX.zip | Source Geospatial Form: vector digital data | Type of Source Media: online
|Contact Role Type:||Originator|
|Contact Name:||U.S. Navy|
Process Step 1
1. Go to Navy EIMS and login, download latest COP_Atlantic_GOMEX.zip
2. Unzip files, find and copy the feature class within the "military_operations" feature dataset named "military_oparea_bnd_area" into a new file geodatabase.
3. Rename file to "MilitaryOperatingAreaBoundaries".
4. Delete submarine areas.
4. Check geometry and project data into WGS 1984 Auxiliary Sphere.
5. Export metadata XML and tailor to include minor edits and distribution information for NOAA Office for Coastal Management. Included having to add in attribute definitions as these were missing.
|Process Date/Time:||2017-08-01 00:00:00|
Process Step 2
1. Received email containing PACFLT_OPAREA_Boundaries.shp on 12-06-2018
2. Download zip
3. Project Pacific data into NAD83
4. Merge data with Atlantic/ GOMEX
|Process Date/Time:||2018-12-01 00:00:00|
|Process Contact:||Office for Coastal Management (OCM)|
Process Step 3
Received email from source containing updates to the Eglin Gulf Test and Training Range area.
Copied in updated feature.
|Process Date/Time:||2020-02-01 00:00:00|
Rubric scores updated every 15m
|Entity||Military Operating Area Boundaries|
|Catalog Item ID:||55364|
|Metadata Record Created By:||Anna Verrill|
|Metadata Record Created:||2019-01-22 17:33+0000|
|Metadata Record Last Modified By:||Jesse Brass|
|Metadata Record Last Modified:||2022-01-11 18:58+0000|
|Metadata Record Published:||2019-01-22|
|Metadata Publication Status:||Published Externally|
|Do Not Publish?:||N|
|Metadata Review Frequency:||1 Year|