Data Management Plan
GUID: gov.noaa.nmfs.inport:64802 | 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
Product: These lidar data are processed Classified LAS 1.4 files, formatted to 8183 individual 2500 ft x 2500 ft tiles; used to create intensity rasters, 3D breaklines and hydro-flattened DEMs as necessary.
Geographic Extent: Santa Clara county, California, covering approximately 1771 square miles.
Dataset Description: The lidar project called for the Planning, Acquisition, processing and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.35 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 2.1. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to 8185 individual 2500 ft x 2500 ft tiles, as tiled intensity rasters, and as tiled bare-earth DEMs; all tiled to the same 2500 ft x 2500 ft schema.
Ground Conditions: Lidar was collected in early 2020, while no snow was on the ground and rivers were at or below normal levels. In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Sanborn Map Company, Inc., utilized a total of 25 ground control points that were used to calibrate the lidar to known ground locations established throughout the project area. An additional 125 independent accuracy checkpoints, 70 in Bare Earth and Urban landcovers (70 NVA points), 55 in Tall Grass and Brushland/Low Trees categories (55 VVA points), were used to assess the vertical accuracy of the data. These check points were not used to calibrate or post process the data.
The NOAA Office for Coastal Management (OCM) downloaded 8183 laz point data files from this USGS site:
The data were processed to the Data Access Viewer (DAV) and http. In addition to these lidar point data, the bare earth Digital Elevation Models (DEM) created from the lidar point data and the hydro breaklines are also available for download. These data are available for download at the links provided in the URL section of this metadata record. Please note that these products have not been reviewed by the NOAA Office for Coastal Management (OCM) and any conclusions drawn from the analysis of this information are not the responsibility of NOAA or OCM.
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):
Data were collected and processed by Sanborn Map Company, Inc. and made available on the USGS ftp site. The data were downloaded from the USGS ftp site by the NOAA Office for Coastal Management (OCM) where the data were processed to make it available for custom download from the Data Access Viewer (DAV) and bulk download from https.
- 2020-01-01 00:00:00 - The boresight was completed prior to project execution. The following steps describe the Raw Data Processing process: 1) Technicians processed the raw data to LAS format flight lines using the final GNSS/IMU solution. This LAS data set was used as source data for lidar matching. 2) Technicians utilized commercial and proprietary software packages to analyze how well flight line overlaps match for the entire lift and adjusted as necessary until the results met the project specifications. 3) Once all lifts were completed with lidar matching, the technicians checked and corrected the vertical misalignment of all flight lines and also the matching between data and ground truth. The relative accuracy was less than or equal to 6 cm RMSEz within individual swaths and less than or equal to 8 cm RMSEz or within swath overlap (between adjacent swaths). 4) The technicians ran a final vertical accuracy check of the flight lines against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification v2.1, and breaklines were collected for water features. Bare-earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening.
- 2020-10-18 00:00:00 - LAS Point Classification: The point classification is performed as described below. The bare-earth surface is then manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface is finalized, it is then used to generate all hydro-breaklines through heads-up digitization. All Class 2 (Ground) lidar data inside of the Lake Pond and Double Line Drain hydro-flattened breaklines were then classified to Class 9 (Water) using LP360 functionality. A buffer of 1 foot was also used around each hydro-flattened feature to classify these Class 2 (Ground) points to Class 20 (Ignored Ground). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the Class 2 (Ground) points were reclassified to the correct classification after the automated classification was completed. All overlap data was processed through automated functionality provided by TerraScan to classify the overlapping flight line data to approved classes by USGS. The overlap data was classified using standard LAS overlap bit. These classes were created through automated processes only and were not verified for classification accuracy. Due to software limitations within TerraScan, these classes were used to trip the withheld bit within various software packages. These processes were reviewed and accepted by USGS through numerous conference calls and pilot study areas. All data was manually reviewed and any remaining artifacts removed using functionality provided by LP360, TerraScan and TerraModeler. Global Mapper was used as a final check of the bare-earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files. Sanborn Map Company, Inc. proprietary software was used to perform final statistical analysis of the classes in the LAS files, on a per tile level to verify final classification metrics and full LAS header information.
- 2020-10-16 00:00:00 - Data was tested at 0.21 meter aggregate nominal pulse spacing and at 22.5 aggregate points per meter. The aggregate nominal pulse spacing was tested on classified tiled LAS using geometrically reliable first-return points without overlap. ANPS was tested using Delaunay Triangulation that produced average point spacing between all nearest neighbors.
- The NOAA Office for Coastal Management (OCM) downloaded 8183 laz point data files from this USGS site: ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/CA_SantaClaraCounty_2020_A20/CA_SantaClaraCounty_2020/LAZ/. The data were in CA State Plane Region 3 FIPS 0403 (NAD83 2011), US survey feet coordinates and NAVD88 (Geoid18) elevations in feet. The data were classified as: 1 - Unclassified, 2 - Ground, 3 - Low Vegetation, 4 - Medium Vegetation, 5 - High Vegetation, 6 - Buildings, 7 - Low Noise, 9 - Water, 17 - Bridge Decks, 18 - High Noise, 20 - Ignored Ground. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 3, 4, 5, 6, 7, 9,17, 18, 20. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Internal OCM scripts were run to check the number of points by classification and by flight ID and the gps, elevation, and intensity ranges. 2. Internal OCM scripts were run on the laz files to: a. Convert from orthometric (NAVD88) elevations to NAD83 (2011) ellipsoid elevations using the Geoid18 model b. Convert the laz files from CA State Plane Region 3 (NAD83 2011), US survey feet coordinates to geographic coordinates c. Convert from vertical units of feet to vertical units of meters. d. Filter points with elevation values less than -25 ft and greater than 5000 ft. e. Filter points outside the geographic range of the bounding coordinates of -36.5, -122.5, 38, -121 degrees f. Assign the geokeys, 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 and 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.