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
These data were generated to provide insight into marine traffic patterns on a macro scale so they could be analyzed across the coastal waters of the Continental United States, this data set is for the UTM Zone 15N. For this dataset a transit is counted for every unique vessel intersecting a 1 kilometer square grid cell each day. This data represents the total number of vessel transits from October 2009 - October 2010. Some grid cells were unable to be processed, but this does not interfere with the integrity of this dataset.
Please note multiple connection errors occurred during the time frame of this study. In most cases data gaps were filled by making subsequent request to the coastguard or other groups receiving the same data feed. However, due to resource constraints uninterrupted coverage was not obtained. Overall data outages were minimal on the order less than a day per month and because random and affect all areas uniformly do not has a significant effect on the integrity of the data. Also as stated on the USCG NAIS website AIS data is not representative of all vessel traffic and USCG NAIS receivers do not fully cover the entire extent of this study area. Please take time to understand both of these limitations.
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):
- 2012-07-01 00:00:00 - Source data derived from the raw AIS data processing is as follows: The USCG maintains a network of AIS receivers that collects AIS messages from passing ships. These data are transmitted to USCG data center that compiles the data and provides data feeds to other government agencies. In accordance with the USCG COMDTINST 5230.80, the USCG provided OCS with a "Level A" data feed. Level A is unfiltered real-time data that is less than 96 hours from initial time of transmission. OCS has subscribed to this data since 2008. To limit data storage requirements the data feed was filtered by the USCG to only send one position message per ship per minute and all duplicate messages (i.e. ship broadcasts received by more than one NAIS station) were removed. This real time feed was archived at OCS. A specialized software NOAADATA.py (K. Schwehr. The noaadata-py Software Tool-set, v0.42, 2009. http://vislab-ccom.-unh.edu/schwehr/software/noaadata) is used to create daily files and and load the data into an Oracle Spatial database. Despite receiving this filtered feed, a great deal of conditioning needs to take place to prepare this data to be analyzed. The AIS system was not intended or designed for subsequent analysis; however Calder and Schwehr ably proved, given the proper conditioning, AIS data can be used for traffic analysis. ( B. R. Calder., K. Schwehr. Traffic Analysis for the Calibration of Risk Assessment Methods. Proceedings: US Hydrographic Conference 2009, Norfolk, VA, 11-14 May 2009, http://www.thsoa.org/us09papers.htm) Based on their research, we filtered out AIS messages with non-unique user IDs and vessels with erroneous dimensions. We also separated messages by speed, separating those reporting a speed of less than 0.4 knots into a separate anchored table. The accuracy and abundance of the AIS data support high resolution analysis specifically within port areas. This study however was interested in traffic patterns on a macro scale so patterns could be analyzed across the coastal waters of the Continental United States. To limit the processing time and the overall file size for each region a grid cell size of 1 kilometer was chosen. For this dataset a transits is counted for every unique vessel intersecting a grid cell each day. Multiple trips into a grid cell on a given day by the same vessel are only counted as one transit. Instead of calculating transits based on the coordinates within the AIS message transit lines were created by connecting all the vessels reports each day. Traffic counts were then calculated by summing the number of lines within each cell. Although this dataset only contains the total traffic count "TRNSTS_TTL" the original dataset has transits by AIS vessel type and many other attributes as well. Processed from May - July 2012.
- 2012-10-16 00:00:00 - Further data development processing followed to obtain this feature class: Acquire original source data and maintain a copy on the development tier, create geodatabase import the original shapefiles. Delete all feature will zero values and validate the feature classes' geometry (Data Management > Features > Repair Geometry). Acquire, create and update metadata from providers (as needed). Compressed data set into a zip file for ease of download. (Citation: AIS Vessel Count - 2010)
(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.6. Type(s) of data
- 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.