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.

URL of higher-level DM Plan (if any) as submitted to DM Plan Repository:

Always left blank

1. General Description of Data to be Managed

1.1. Name of the Data, data collection Project, or data-producing Program:

2019-2020 NOAA NGS Topobathy Lidar DEM: Coastal VA, NC, SC

Taken From: Item Identification | Title

1.2. Summary description of the data:

NOAA Florence Topobathymetric Lidar data were collected by NV5 Geospatial (NV5) in 9 blocks from 20191126 - 20200825 using the follow sensors:

Block01 -Riegl VQ880GII system

Block02 - Riegl VQ-880-G and Riegl VQ-880-GII systems

Block03 - Riegl VQ880G, Riegl VQ880GII, and Riegl VQ880GH systems

Block04 - Riegl VQ880GII and Leica Chiroptera 4x systems

Block05 - Riegl VQ880GII, Leica Chiroptera 4x and Hawkeye systems

Block06 - Riegl VQ880GII, Leica Chiroptera 4x and Hawkeye systems

Block07 - Riegl VQ880G, Riegl VQ880GII, and Leica Chiroptera 4x systems

Block08 - Riegl VQ880G and Riegl VQ880GII systems

Block09 - Riegl VQ880G and Riegl VQ880GII systems

This dataset includes topobathymetric data in a LAS format 1.4, point data record format 6, with classifications in accordance with project specifications and the American Society for Photogrammetry and Remote Sensing (ASPRS) classification standards.

This data set also includes LiDAR intensity values, number of returns, return number, time, and scan angle. The 100 meter buffered project area consists of approximately 3,075,010 acres along the Eastern coast of Virginia, North Carolina, and South Carolina.

The delivered classified lidar data were then transformed from ellipsoid to geoidal height (Geoid18) and used to create topobathymetric DEMs in GeoTIFF format with 1m pixel resolution.

Taken From: Item Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.

1.3. Is this a one-time data collection, or an ongoing series of measurements?

One-time data collection

Taken From: Extents / Time Frames | Time Frame Type
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.

1.4. Actual or planned temporal coverage of the data:

2019-11-26 to 2019-12-21, 2019-11-28 to 2020-03-18, 2019-11-26 to 2020-04-02, 2019-12-08 to 2020-08-25, 2019-12-10 to 2020-07-27, 2019-11-26 to 2020-06-22, 2019-12-07 to 2020-04-04, 2019-12-09 to 2020-04-28, 2019-12-04 to 2020-05-30

Taken From: Extents | Time Frame - Start, Time Frame - End
Notes: All time frames from all extent groups are included.

1.5. Actual or planned geographic coverage of the data:

W: -77.904502, E: -77.289632, N: 34.545077, S: 34.12689
W: -77.510503, E: -76.4876, N: 34.877717, S: 34.527625
W: -79.40181, E: -77.800145, N: 34.285932, S: 33.16496
W: -76.592761, E: -75.933037, N: 35.203366, S: 34.646674
W: -75.996936, E: -75.4444, N: 35.8734, S: 35.10379
W: -76.1174, E: -75.55938, N: 36.945709, S: 35.8646
W: -77.16282, E: -76.36149, N: 35.37506, S: 34.81832
W: -77.147204, E: -75.65982, N: 35.82732, S: 35.26935
W: -76.782432, E: -75.661664, N: 36.45838, S: 35.500726

Taken From: Extents | Geographic Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.

1.6. Type(s) of data:
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)

Model (digital)

Taken From: Data Set Information | Data Presentation Form

1.7. Data collection method(s):
(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.)

No information found

Taken From: Acquisition Information | Instruments, Platforms

1.8. If data are from a NOAA Observing System of Record, indicate name of system:

Always left blank due to field exemption

1.8.1. If data are from another observing system, please specify:

Always left blank due to field exemption

2. Point of Contact for this Data Management Plan (author or maintainer)

2.1. Name:

NOAA Office for Coastal Management (NOAA/OCM)

Taken From: Support Roles (Metadata Contact) | Person
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.

2.2. Title:

Metadata Contact

Always listed as "Metadata Contact"

2.3. Affiliation or facility:

NOAA Office for Coastal Management (NOAA/OCM)

Taken From: Support Roles (Metadata Contact) | Organization
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.

2.4. E-mail address:

coastal.info@noaa.gov

Notes: The email address is taken from the address listed for the Person assigned as the Metadata Contact in Support Roles.

2.5. Phone number:

(843) 740-1202

Notes: The phone number is taken from the number listed for the Person assigned as the Metadata Contact in Support Roles. If the phone number is missing or incorrect, please contact your Librarian to update the Person record.

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.

3.1. Name:

No information found

Taken From: Support Roles (Data Steward) | Person
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.

3.2. Position Title:

Data Steward

Always listed as "Data Steward"

4. Resources

Programs must identify resources within their own budget for managing the data they produce.

4.1. Have resources for management of these data been identified?

Yes

Taken From: Data Management | Have resources for management of these data been identified?

4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):

Unknown

Taken From: Data Management | Approximate percentage of budget for these data devoted to data management

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.

5.1. Processing workflow of the data from collection or acquisition to making it publicly accessible
(describe or provide URL of description):

Process Steps:

2020-10-02 00:00:00 - Data for the NOAA Florence Topobathymetric Lidar project area was acquired by NV5 Geospatial (NV5). All derived DEMdata is referenced to: Horizontal Datum-NAD83(2011) epoch: 2010.00 Projection-UTM Zone 18N Horizontal Units-meters Vertical Datum-NAVD88 (Geoid18) Vertical Units-meters The collected lidar data were immediately processed in the field by NV5 to a level that will allow QA\QC measures to determine if the sensor is functioning properly and assess the coverage of submerged topography. An initial SBET was created in POSPAC MMS 8.3 SP3 and loaded into RiProcess which applies pre-calibrated angular misalignment corrections of scanner position to extract the raw point cloud into geo-referenced LAS files. These files were inspected for sensor malfunctions and then passed through automated raster generation using LAStools to develop an initial assessment of bathymetric coverage. NV5 reviewed all acquired flight lines to ensure complete coverage and positional accuracy of the laser points. These rasters were also used to create an initial product in Quick Look Coverage Maps. These Quick Look files are not fully processed data or final products but provide rapid assessment of approximate coverage and depth penetration. NV5 resolved kinematic corrections for aircraft position data using aircraft GNSS and Applanix's proprietary PP-RTX solution. When PP-RTX was not used NV5 conducted static Global Navigation Satellite System (GNSS) ground surveys (1 Hz recording frequency) using base stations over known monument locations during flights. After the airborne survey, static GPS data were triangulated with nearby Continuously Operating Reference Stations (CORS) using the Online Positioning User Service (OPUS) for precise positioning. Multiple independent sessions over the same base station were performed to confirm antenna height measurements and to refine position accuracy. This data was used to correct the continuous on board measurements of the aircraft position recorded throughout the flight. A final smoothed best estimate trajectory (SBET) was developed that blends post-processed aircraft position with attitude data. Using the SBETs, sensor head position and attitude were then calculated throughout the survey. Trimble Business Center v.3.90, Blue Marble Geographic Calculator 2019, and PosPac MMS 8.3 SP3 were used for these processes.
2020-12-17 00:00:00 - Following final SBET creation, NV5 used RiProcess 1.8.5 to calculate laser point positioning by associating SBET positions to each laser point return time, scan angle, and intensity. Terra 19 and LasTools were used to classify water surface and create a water surface model. They are created for single swaths to ensure temporal differences and wave or water surface height variations between flight lines do not impact the refraction of the bathymetric data. These models are used in NV5's LasMonkey refraction tool to determine the accurate positioning of bathymetric points. All lidar data below water surface models were classified as water column to be refracted. 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 tool corrects for this difference by adjusting the depth (distance traveled) and horizontal positioning (change of angle/direction) of the lidar data. Using raster-based QC methods, the output data is verified to ensure the refraction tool functioned properly. In addition, for Blocks 4 - 7, following final SBET creation for the Leica Chiroptera 4X and Hawkeye systems, NV5 used Leica Lidar Survey Studio (LSS) to calculate laser point positioning by associating SBET positions to each laser point return time, scan angle, and intensity. Leica LSS was used to derive a synthetic water surface to create a water surface model. 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 tool corrects for this difference by adjusting the depth (distance traveled) and horizontal positioning (change of angle/direction) of the lidar data. All lidar data below water surface models were classified as water column to correct for refraction. Using raster-based QC methods, the output data is verified to ensure the refraction tool functioned properly.
2022-01-29 00:00:00 - Once all data was refracted by flight line data was exported to LAS 1.4 format and combined into 500 m x 500 m tiles. Data were then further calibrated using TerraMatch. NV5 used custom algorithms in TerraScan to classify the initial ground/submerged topography surface points. Relative accuracy of overlapping swaths was compared and verified through the use Delta-Z (DZ) orthos created using NV5's Las Product Creator. Absolute vertical accuracy of the calibrated data was assessed using ground survey data and complete coverage was again verified. Post automated classification NV5 then performed manual editing to review all classification and improve the final topobathymetric surface. NV5's LasMonkey was used to update LAS header information, including all projection and coordinate reference system information. The final lidar data are in LAS format 1.4 and point data record format 6. The delivered dataset used the following classification scheme for Block01, Block02, Block03, Block08 and Block09: 1 - Unclassified 2 - Ground 7 - Noise 40 - Bathymetric Bottom or Submerged Topography 41 - Water Surface 43 - Submerged feature 45 - Water Column 46 - Temporal Bathymetric Bottom 71 - Overlap Default 72 - Overlap Ground 81 - Overlap Water Surface 85 - Overlap Water Column 1-Overlap - Edge Clip The delivered dataset used the following classification scheme for Block04, Block05, Block06 and Block07: 1 - unclassified 2 - ground 7 - noise 40 - bathymetric bottom or submerged topography 41 - water surface 42 Synthetic- Chiroptera synthetic water surface 43 - submerged feature 45 - water column 46 - overlap bathy bottom - temporally different from a separate lift 71 - unclassified associated with areas of overlap bathy bottom/temporal bathymetric differences 72 - ground associated with areas of overlap bathy bottom/temporal bathymetric differences 81 - water surface associated with areas of overlap bathy bottom/temporal bathymetric differences 81 Synthetic - Chiroptera synthetic water surface associated with areas of overlap bathy bottom/temporal bathymetric differences 85 - water column associated with areas of overlap bathy bottom/temporal bathymetric differences 1 Overlap - edge clip 1 Withheld - unrefracted green data from Chiroptera sensor
2020-10-02 00:00:00 - NV5 transformed the final LiDAR data from ellipsoid heights to orthometric heights referenced to NAVD88, Geoid 18 to create the final topobathymetric void clipped DEMs. The topobathymetric bare earth DEMs were output at 1 meter resolution in GeoTIFF format into 5000 m x 5000 m tiles. The rasters are clipped to the extent of the project boundary and named according to project specifications. A bathymetric void shapefile was created to indicate areas where there was a lack of bathymetric returns. This shape was created by triangulating bathymetric bottom points with an edge length maximum of 4.56m to identify all areas greater then 9 square meters without bathymetric returns. This shapefile was used to clip and exclude interpolated elevation data from these areas in the bathymetric void clipped topobathymetric bare earth model.

Taken From: Lineage | Lineage Statement, Process Steps (Process Date/Time, Source Citation Title, Description)

5.1.1. If data at different stages of the workflow, or products derived from these data, are subject to a separate data management plan, provide reference to other plan:

Always left blank

5.2. Quality control procedures employed
(describe or provide URL of description):

No information found

Taken From: Data Quality | Quality Control Procedures Employed

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.

6.1. Does metadata comply with EDMC Data Documentation directive?

No

Notes: All required DMP fields must be populated and valid to comply with the directive.

6.1.1. If metadata are non-existent or non-compliant, please explain:

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.4. Approximate delay between data collection and dissemination
8.3. Approximate delay between data collection and submission to an archive facility

Notes: Required DMP fields that are not populated or invalid are listed here.

6.2. Name of organization or facility providing metadata hosting:

NMFS Office of Science and Technology

Always listed as "NMFS Office of Science and Technology"

6.2.1. If service is needed for metadata hosting, please indicate:

Always left blank

6.3. URL of metadata folder or data catalog, if known:

https://www.fisheries.noaa.gov/inport/item/66714

Always listed as the URL to the InPort Data Set record

6.4. Process for producing and maintaining metadata
(describe or provide URL of description):

Metadata produced and maintained in accordance with the NOAA Data Documentation Procedural Directive: https://nosc.noaa.gov/EDMC/DAARWG/docs/EDMC_PD-Data_Documentation_v1.pdf

Always listed with the above statement

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.

7.1. Do these data comply with the Data Access directive?

Yes

Taken From: Data Management | Do these data comply with the Data Access directive?

7.1.1. If the data are not to be made available to the public at all, or with limitations, has a Waiver (Appendix A of Data Access directive) been filed?

No information found

Taken From: Data Management | Is access to the data limited based on an approved waiver?

7.1.2. If there are limitations to public data access, describe how data are protected from unauthorized access or disclosure:

None

Taken From: Access Info | Data Access Constraints

7.2. Name of organization of facility providing data access:

NOAA Office for Coastal Management (NOAA/OCM)

Taken From: Support Roles (Distributor) | Organization
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.

7.2.1. If data hosting service is needed, please indicate:

Taken From: Data Management | If data hosting service is needed, please indicate
Notes: This field is required if a Distributor has not been specified.

7.2.2. URL of data access service, if known:

https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9468
https://noaa-nos-coastal-lidar-pds.s3.us-east-1.amazonaws.com/dem/NGS_VAtoSC_Topobathy_DEM_2020_9468/index.html

Taken From: Distribution Info | Download URL
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.

7.3. Data access methods or services offered:

Data is available online for bulk or custom downloads

Taken From: Access Info | Data Access Procedure

7.4. Approximate delay between data collection and dissemination:

No information found

Taken From: Data Management | Approximate delay between data collection and dissemination

7.4.1. If delay is longer than latency of automated processing, indicate under what authority data access is delayed:

Taken From: Data Management | If delay is longer than latency of automated processing, indicate under what authority data access is delayed
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.

8.1. Actual or planned long-term data archive location:
(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)

NCEI_CO

Taken From: Data Management | Actual or planned long-term data archive location

8.1.1. If World Data Center or Other, specify:

Taken From: Data Management | Actual or planned long-term data archive location
Notes: This field is required if archive location is World Data Center or Other.

8.1.2. If To Be Determined, Unable to Archive or No Archiving Intended, explain:

Taken From: Data Management | If To Be Determined, Unable to Archive or No Archiving Intended, explain
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.

8.2. Data storage facility prior to being sent to an archive facility (if any):

Office for Coastal Management - Charleston, SC

Taken From: Physical Location | Organization, City, State, Location Description
Notes: Physical Location Organization, City and State are required, or a Location Description is required.

8.3. Approximate delay between data collection and submission to an archive facility:

No information found

Taken From: Data Management | 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?
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.

Taken From: Data Management | How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?

9. Additional Line Office or Staff Office Questions

Line and Staff Offices may extend this template by inserting additional questions in this section.

Always left blank