Data Management Plan
GUID: gov.noaa.nmfs.inport:56763 | 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 NOAA using a Riegl VQ880G sensor. The data was acquired April 9, 2017. The data includes topobathy data in LAS 1.2 format classified as created, unclassified (1); ground (2); topographic noise (7); bathymetric noise (22); water column (25); bathymetric bottom (26); water surface (27); International Hydrographic Organization S-57 object, not otherwise specified (30) in accordance with project specifications. The project consists of approximately
34 square miles of data along the shores of St. Jeromes Creek. This dataset contains 342 500 m x 500 m lidar tiles.
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:
- 2019-02-01 00:00:00 - Data for the St. Jeromes Creek project was acquired by NOAA using a Riegl VQ880G sensor. All delivered lidar data is referenced to: Horizontal Datum-NAD83 (2011) epoch: 2010 Projection-UTM Zone 18 North Horizontal Units-meters Vertical Datum-NAD83 (2011) epoch: 2010 Vertical Units-meters This dataset encompasses 342 500 m x 500 m lidar tiles. Both green lidar data and NIR lidar data were acquired. NOAA 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. Dewberry received the calibrated green and NIR data and verified complete coverage. Relative accuracy of the green swaths compared to overlapping and adjacent green swaths as well as the relative accuracy of green swaths compared to overlapping and adjacent NIR swaths was verified through the use of Delta-Z (DZ) orthos created in GeoCue software. Intraswath or within a swath relative accuracy was verified using Quick Terrain Modeler. Profiles of elevated planar features, such as roofs, were used to verify horizontal alignment between overlapping swaths. Dewberry used algorithms in TerraScan to create the intial ground/submerged topography surface. Dewberry created 2-D breaklines by digitizing breaklines in a 2-D environment using intensity imagery as a reference. Dewberry used the 2-D breaklines to classify the bathymetric bottom and ground points properly in TerraScan. All lidar data was peer-reviewed. Dewberry's QAQC also included creating void polygons for use during review. All necessary edits were applied to the dataset. GeoCue software was used to update LAS header information, including all projection and coordinate reference system information. The final lidar data is in LAS format 1.2 and point data record format 3. The final classificaton scheme is as follows: 1-Unclassified 2-Ground 7-Topographic Noise 22-Bathymetric Noise 25-Water Column 26-Bathymetric Bottom 27-Water Surface 30-International Hydrograpic Organization (IHO) S-57 Object All data was then verified by an Independent QC department within Dewberry. The independent QC was performed by separate analysts who did not perform manual classification or editing. The independent QC involved quantitative and qualitative reviews.
- The NOAA Office for Coastal Management (OCM) received 616 files in las 1.2 format. The files contained lidar intensity and elevation measurements for the project area. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. Converted from UTM Zone 18 coordinates to geographic coordinates 3. Sorted by gpstime 4. Compressed the data using laszip
(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)
- 2.4. Point of Contact Email
- 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/geoid18/8777/index.html
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Data is available online for custom downloads
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.