Data Management Plan
DMP Template v2.0.1 (2015-01-01)Please provide the following information, and submit to the NOAA DM Plan Repository.
Reference to Master DM Plan (if applicable)
As stated in Section IV, Requirement 1.3, DM Plans may be hierarchical. If this DM Plan inherits provisions from a higher-level DM Plan already submitted to the Repository, then this more-specific Plan only needs to provide information that differs from what was provided in the Master DM Plan.
1. General Description of Data to be Managed
Automatic Identification Systems (AIS) are a navigation safety device that transmits and monitors the location and characteristics of many vessels in U.S. and international waters in real-time. In the U.S. the Coast Guard and industry collect AIS data, which can also be used for a variety of coastal planning purposes. NOAA and BOEM have worked jointly to re-task and make available some of the most important records from the U.S. Coast Guard's national network of AIS receivers. Information such as location, time, ship type, length, width, and draft have been extracted from the raw data and prepared as track lines for analyses in desktop GIS software.
Notes: Only a maximum of 4000 characters will be included.
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
Notes: All time frames from all extent groups are included.
Notes: All geographic areas from all extent groups are included.
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
(e.g., satellite, airplane, unmanned aerial system, radar, weather station, moored buoy, research vessel, autonomous underwater vehicle, animal tagging, manual surveys, enforcement activities, numerical model, etc.)
2. Point of Contact for this Data Management Plan (author or maintainer)
Notes: The name of the Person of the most recent Support Role of type "Metadata Contact" is used. The support role must be in effect.
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
3. Responsible Party for Data Management
Program Managers, or their designee, shall be responsible for assuring the proper management of the data produced by their Program. Please indicate the responsible party below.
Notes: The name of the Person of the most recent Support Role of type "Data Steward" is used. The support role must be in effect.
Programs must identify resources within their own budget for managing the data they produce.
5. Data Lineage and Quality
NOAA has issued Information Quality Guidelines for ensuring and maximizing the quality, objectivity, utility, and integrity of information which it disseminates.
(describe or provide URL of description):
- 2014-02-01 00:00:00 - 1 Download all 2011 geodatabases for UTM zones 14, 15, and 16 from https://marinecadastre.gov/AIS/default.aspx as well as the AIS Track Builder tool. 2 For all months in Zone 14, 15, and 16 deleted data points from the Broadcast feature class falling outside the United States, Gulf of Mexico region UTM zones 14, 15 and 16. Used Esri's World UTM Grid from ArcGIS online for reference. 3 Create model for each of the UTM zones to run the track builder tool on each of the monthly Broadcast feature classes. Settings used for the tool was to break track lines using "Maximum Time and Distance", maximum time value = 30 and maximum distance value = 1. Also included both the Voyage and Vessel attributes. Ran Model for each UTM zone. 4 CLIP Broadcast points for all months in zone 15 and the months of March and April to smaller quadrants of their respective UTM zone grids. This was to get the tracklines tool to run successfully for the region around New Orleans. 5 Create model to run the track builder tool on each for each of these newly clipped areas. Settings used for the tool was to break track lines using "Maximum Time and Distance", maximum time value = 30 and maximum distance value = 1. Also included both the Voyage and Vessel attributes. 6 MERGE all outputs stemming from step 5 together per month. 7 MERGE of all monthly track line feature classes for each of the UTM zones. Now have 3 feature classes representing total 2011 annual vessel traffic for each UTM Zone 14, 15, and 16. 8 Removal of superfluous fields. 9 Create model to create max draught in meters field for annual feature class, calculate statistics to find the maximum draft value, create new field "maxDraught" in this statistics result intermediate feature class, add values to this new field using field calculator in expression: [max draught statistic] *0.1. This calculation converts the draught values form 1/10th meter units to meter units. Join this field to the annual feature class based on the MMSI field. 10 Repair geometry for each of the annual track line feature classes for each UTM Zone. 11 REPROJECT all three UTM zone's annual tracklines into web mercator. 12 MERGE all three UTM zone's annual track lines into one feature class to create 2011 annual Gulf of Mexico track lines feature class. 13 Repair geometry for the merged regional file. 14 Add spatial index. (Citation: 2011 United States Automatic Identification System Database)
(describe or provide URL of description):
6. Data Documentation
The EDMC Data Documentation Procedural Directive requires that NOAA data be well documented, specifies the use of ISO 19115 and related standards for documentation of new data, and provides links to resources and tools for metadata creation and validation.
- 1.7. Data collection method(s)
- 3.1. Responsible Party for Data Management
- 4.1. Have resources for management of these data been identified?
- 4.2. Approximate percentage of the budget for these data devoted to data management
- 5.2. Quality control procedures employed
- 7.1. Do these data comply with the Data Access directive?
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.1.2. If there are limitations to data access, describe how data are protected
- 7.3. Data access methods or services offered
- 7.4. Approximate delay between data collection and dissemination
- 8.1. Actual or planned long-term data archive location
- 8.3. Approximate delay between data collection and submission to an archive facility
- 8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
(describe or provide URL of description):
7. Data Access
NAO 212-15 states that access to environmental data may only be restricted when distribution is explicitly limited by law, regulation, policy (such as those applicable to personally identifiable information or protected critical infrastructure information or proprietary trade information) or by security requirements. The EDMC Data Access Procedural Directive contains specific guidance, recommends the use of open-standard, interoperable, non-proprietary web services, provides information about resources and tools to enable data access, and includes a Waiver to be submitted to justify any approach other than full, unrestricted public access.
Notes: The name of the Organization of the most recent Support Role of type "Distributor" is used. The support role must be in effect. This information is not required if an approved access waiver exists for this data.
Notes: This field is required if a Distributor has not been specified.
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Notes: This field is required if applicable.
8. Data Preservation and Protection
The NOAA Procedure for Scientific Records Appraisal and Archive Approval describes how to identify, appraise and decide what scientific records are to be preserved in a NOAA archive.
(Specify NCEI-MD, NCEI-CO, NCEI-NC, NCEI-MS, World Data Center (WDC) facility, Other, To Be Determined, Unable to Archive, or No Archiving Intended)
Notes: This field is required if archive location is World Data Center or Other.
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.