Data Management Plan
GUID: gov.noaa.nmfs.inport:54204 | Published / External
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
Vessels traveling in U.S. coastal and inland waters frequently use Automatic Identification Systems (AIS) for navigation safety. The U.S. Coast Guard collects AIS records using shore-side antennas. These records have been filtered and converted from a series of points to a set of track lines for each vessel. Vessels can have one or more tracks of any length, and can be separated by gaps due to intermittent loss of the AIS signal. Tracks will not necessarily start or stop at a well defined port, or when a vessel is not in motion. Vessel tracks are an efficient and spatially unbiased indicator of vessel traffic.
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.
4. Resources
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):
Process Steps:
- 2018-01-15 00:00:00 - 1. Filter the raw NMEA data to a one-minute sample rate and select a subset of fields using MarineCadastre.gov NMEA to SQL Server processing tools 2. Load filtered records to an SQL Server 2017 database using MarineCadastre.gov NMEA to SQL Server processing tools 3. Conduct quality and completeness check using logging results from the filter and loading process 4. Update the IMO, CallSign, VesselName, Length, Width, VesselType, and Draft from United States Coast Guard AVIS where original AIS values are missing 5. Add a new vessel type code to each record fragment that originated from the United States Coast Guard AVIS 6. Develop track line features directly from the SQL Server database using a customize version of the MarineCadastre.gov Track Builder 3.1 (64-bit version) for each month of broadcast records and for each ocean basin, using a filter setting of 30 minutes and 1 mile 7. Added field for vessel type group and populated based on the vessel type code to vessel group mapping described in attribute metadata 8. Added field for track line duration, and calculated the time in minutes between the start and end time for each track feature 9. Performed visual quality and consistency checks, and removed vessel tracks that were clearly invalid (on land) or beyond the ocean basin 10. REPAIR GEOMETRY to remove features with null geometry
(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.
Missing/invalid information:
- 1.3. Is this a one-time data collection, or an ongoing series of measurements?
- 1.4. Actual or planned temporal coverage of the 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.2. Name of organization of facility providing data access
- 7.2.1. If data hosting service is needed, please indicate
- 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.2. Data storage facility prior to being sent to an archive facility
- 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.
https://marinecadastre.gov/downloads/data/ais/ais2016/AtlanticTracks_2016AIS.zip
https://marinecadastre.gov/downloads/data/ais/ais2016/GreatLakesTracks_2016AIS.zip
https://marinecadastre.gov/downloads/data/ais/ais2016/GulfOfMexicoTracks_2016AIS.zip
https://marinecadastre.gov/downloads/data/ais/ais2016/WestCoastTracks_2016AIS.zip
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.
Charleston, SC
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.