Data Management Plan
GUID: gov.noaa.nmfs.inport:53073 | 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
These files contain topographic lidar data collected by the CHARTS system in CNMI. Data were converted from xyz values without return numbers or time stamps. Point classifications have not been done.
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.
Saipan
W: 145.5825, E: 145.6774, N: 15.1001, S: 14.9287Tinian
W: 145.1852, E: 145.2865, N: 14.178, S: 14.1639Rota (airport)
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:
- These data were collected using the CHARTS System 2, including the SHOALS 1000T SN:002 system. It is owned by the Naval Oceanographic Office (NAVO) and operated through contract. The system collects topographic lidar data at 10kHz and hydrographic data at 1kHz. An airborne hydrographic and topographic survey was conducted in the Commonwealth of the Northern Mariana Islands (CNMI) 20-24 March, 2006. This survey was conducted using Kinematic GPS positioning and all hydrographic and topographic data was collected with respect to the NAD83 ellipsoid. No new geodetic work was done in CNMI. The kinematic GPS base stations were established over NGS benchmarks. The aircraft was initially positioned using the published NGS DG3988 NAD83 position. In order to precisely position the base station in WGS84 the GPS datasets were submitted to NOAA’s Online Positioning User Service (OPUS). The positions provided by OPUS were then averaged. The final Saipan base station position used for final data processing is: N 15 degrees 13' 34.66282" E 145 degrees 44' 14.50749" WGS84 ellipsoid height: 58.041 meters
- 2018-07-16 00:00:00 - The NOAA Office for Coastal Management (OCM) received files in txt format with longitute, latitude, and elevation in NAD83 ellipsoid heights. Saipan data were received in mean sea level (56.06 meters above the NAD83 ellipsoid). OCM performed the following processing on the data for storage and provisioning purposes within Digital Coast: 1. Saipan data were transformed to ellipsoid heights 2. Data were imported into LAZ format using txt2las.
- 2018-07-16 00:00:00 - The LAStools lasground tool was used for automated point classification. Data were first tiled into 1 km squares in UTM projection with 20 meter buffers using lastile. Lasground was run on the tiles with the default settings and the buffers were removed. The data was reprojected to geographic coordinates for ingest.
(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.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.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.
None
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://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/8569/index.html
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer;
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.