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 dataset is a LiDAR (Light Detection and Ranging) point cloud of the coastal tidal parts of Skagit and Snohomish Counties in WA State. The National Oceanic and Atmospheric Administration’s Office for Coastal Management contracted with Tetra Tech to acquire and process airborne LiDAR over an area of about 186 square miles. Data was to be acquired within a 2 hour window of low tide. Deliverables included classified LiDAR point clouds, breaklines and digital elevation models (DEM). LiDAR data was acquired on 13 and 14 of August 2019. The coastal area was covered in one flight on 8/14 while the inland area was covered on 8/13. The coastal flight took place on 8/14 with a tide window between -0.7 and +0.5 foot. For the airborne LiDAR flight Tetra Tech subcontracted with Eagle Mapping. The data was acquired with a Riegl LMS VQ780i sensor. A ground control survey was conducted to collect calibration points and check points. For the ground survey, Tetra Tech contracted with Compass Data. The LiDAR data and derivative products were to be based on the USGS LiDAR Base Specifications. The coordinate reference system is UTM Zone 10N meters, NAD83(2011). The vertical datum is NAVD88 with Geoid12B.
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.
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):
- 2019-08-14 00:00:00 - Flight Acquisition: LiDAR data was acquired on 13 and 14 of August 2019. The coastal area was covered in one flight on August 14 while the inland area was covered on August 13. The coastal flight took place on August 14 with a tide window between -0.7 and +0.5 foot. For the airborne LiDAR flight Tetra Tech subcontracted with Eagle Mapping. The data was acquired with a Riegl LMS VQ780i sensor.
- 2020-01-16 00:00:00 - Point Cloud Processing: The point cloud data was classified using the software tools Microstation, TerraScan and TerraModeler. Ground points were classified using a macro developed in-house. These points were then edited further manually to obtain the best bare earth representation. Water points were classified and edited using the hydro breaklines. Low, medium and high vegetation points were classified as per the following heights from the ground: low vegetation (0 to 0.6m), medium vegetation (0.6 to 1.5m), high vegetation (above 1.5m). Ignored ground points (class 20) were classified using 0.5m buffer distance from the hydro-breaklines. Bridge decks were identified using the surface file and classified accordingly. High and Low points were identified and classified into their respective classes. The point cloud data was finally tiled out in LP360 with the correct definition of the projected coordinate system. The point cloud has been classified using the following classes: Class Description Point Count Min Average Max Class 1 Default (11,419,873 points) Class 2 Ground (2,607,438,873 points) Class 3 Low_vegetation (1,631,352,621 points) Class 4 Medium_vegetation (151,567,537 points) Class 5 High_vegetation (1,039,793,650 points) Class 7 Low_point (840,222 points) Class 9 Water (145,165,821 points) Class 17 Bridge decks (870,198points) Class 18 High_noise (13,400 points) Class 20 Ignored Ground (867,734 points)
- OCM received 82 laz files from TetraTech. Data was received in UTM 10N NAD 83 (2011) meters horizontally and NAVD88 meters vertically. The data were classified as: 1 Default, 2 Ground, 3 Low_vegetation, 4 Medium_vegetation, 5 High_vegetation, 7 Low_point, 9 Water, 17 Bridge decks, 18 High_noise, Class 20 Ignored Ground. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 2. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid12B model, to convert from UTM 10N NAD83 (2011) coordinates in meters to geographic coordinates, to assign the geokeys, to sort the data by gps time and zip the data to database and to http.
(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.
- 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
(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.
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Data is available online for bulk or 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
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.