Data Management Plan
GUID: gov.noaa.nmfs.inport:72134 | 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
This data was collected by Woolpert using a Leica HawkEye 4X sensor. The data was acquired on 20221021. The data includes topobathy data in an LAS 1.4 format file classified as unclassified (1), ground (2), low noise (7), topo water surface (9), high noise (18), bathymetric point (40), bathymetric water surface (41), synthetic derived water surface (42), submerged object (43), International Hydrographic Organization (IHO) S-57 object (44), submerged aquatic vegetation (64), and bathymetric bottom temporal changes (65) in accordance with Project specifications. This data set also includes lidar intensity values.
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:
- 2023-07-31 00:00:00 - The files contained lidar elevation and intensity measurements of the area surrounding Faleasao, American Samoa. This dataset encompasses 58 500m x 500m tiles. Both green and NIR lidar data were acquired. Woolpert acquired, calibrated, and performed the refraction correction of the lidar data. Light travels at different speeds in air versus water and its direction of travel or angle is changed or refracted when entering the water column. The refraction correction process corrects for this difference by adjusting the depth (distance traveled) and horizontal position (change of angle/direction) of the lidar data acquired within water. Relative accuracy of the swaths compared to overlapping and adjacent swaths was verified through the use of Delta-Z (DZ) orthos created in LASTools software. Profiles of elevated planar features, such as roofs, were used to verify horizontal alignment between overlapping swaths. The NovAtel software was utilized for GPS and inertial processing, Data were processed to an initial LAS format using the Leica Lidar Survey Studio software. Algorithms in TerraScan was used to create the initial ground surface. All lidar data was peer-reviewed. QAQC also included creating void polygons for use during review. All necessary edits were applied to the dataset. LASTools was used to update LAS header information, including all projection and coordinate reference system information. The final lidar data is in LAS format 1.4 and point data record format 6.
- 2023-06-08 00:00:00 - Data were processed in NAD83 (PA11) horizontal and vertical datum. The data is in UTM Zone 2S coordinates and ellipsoid elevations in meters. Horizontal Datum-NAD83 (PA11) epoch: 2010.0 Projection-UTM Zone 2 South Horizontal Units-meters Vertical Datum-NAD83 (PA11) Ellipsoid height Vertical Units-meters The final classification scheme is as follows: 1-Unclassified 2-Ground 7-Low Noise 9-Topo Water Surface 18-High Noise 40-Bathymetric Point 41-Bathymetric Water Surface 42-Synthetic Derived Water Surface 43-Submerged Object 44-International Hydrographic Organization (IHO) S-57 Object 64-Submerged Aquatic Vegetation 65-Bathymetric Bottom Temporal Changes
- 2022-04-11 00:00:00 - The NOAA Office for Coastal Management (OCM) received files in laz format. The files contained lidar elevation and intensity measurements of that area surrounding Faleasao, American Samoa. The data were in UTM Zone 2 coordinates and ellipsoid elevations in meters. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Converted from UTM Zone 2 to geographic coordinates 2. Sorted by gps time
(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
- 5.2. Quality control procedures employed
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.3. Data access methods or services offered
- 7.4. Approximate delay between data collection and dissemination
- 8.3. Approximate delay between data collection and submission to an archive facility
(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/10080/index.html
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
Data is backed up to tape and to cloud storage.
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.