Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:71978 | Published / External
This is an outdated version of the NOAA Data Management Plan template. InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. Please see the Data Management Plan Help Guide to learn more.
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 individual 2500 ft x 2500 ft tiles; used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary.
This large project was divided into 9 USGS work units. They are:
CA_SanJoaquin_1 (USGS Work Unit 300024), 2870 square miles, horizontal projection/datum of NAD83 (2011) CA State Plane Zone 3, US Feet
CA_SanJoaquin_2 (USGS Work Unit 217608), 1889 square miles, horizontal projection/datum of NAD83 (2011) CA State Plane Zone 3, US Feet
CA_SanJoaquin_3 (USGS Work Unit 300025), 1898 square miles, horizontal projection/datum of NAD83 (2011) CA State Plane Zone 4, US Feet
CA_SanJoaquin_4 (USGS Work Unit 300026), 2133 square miles, horizontal projection/datum of NAD83 (2011) CA State Plane Zone 4, US Feet
CA_SanJoaquin_5 (USGS Work Unit 300027), 1570 square miles, horizontal projection/datum of NAD83 (2011) CA State Plane Zone 4, US Feet
CA_SanJoaquin_6 (USGS Work Unit 300028), 1455 square miles, horizontal projection/datum of NAD83 (2011) CA State Plane Zone 5, US Feet
CA_SanJoaquin_7 (USGS Work Unit 300029), 1660 square miles, horizontal projection/datum of NAD83 (2011) CA State Plane Zone 5, US Feet
CA_SanJoaquin_8_Reflight (USGS Work Unit 300177), 0.22 square miles, horizontal projection/datum of NAD83 (2011) CA State Plane Zone 3, US Feet
CA_SanJoaquin_9_Reflight (USGS Work Unit 300242), 0.67 square miles, horizontal projection/datum of NAD83 (2011) CA State Plane Zone 3, US Feet
Dataset Description: The San_Joaquin 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, 2020 rev. A. The data were developed based on a horizontal projection/datum of NAD 1983 2011 State Plane California Zones 3 (FIPS 0403), 4 (FIPS 0404, 5 (FIPS 0405) Ft US, Foot US and vertical datum of NAVD88 Geoid 18, Foot US. LiDAR data were delivered as processed Classified LAS 1.4 files formatted to individual 2500 ft x 2500 ft tiles, as tiled intensity imagery, and as tiled bare earth DEMs; all tiled to the same 2500 ft x 2500 ft schema. Continuous breaklines were produced in Esri file geodatabase format.
Ground Conditions: LiDAR was collected in winter and spring 2021, while no snow was on the ground and rivers were at or below normal levels.
This metadata record supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV is leveraging the Entwine Point Tiles (EPT) hosted by USGS on Amazon Web Services.
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.
CA_SanJoaquin_1
W: -121.18, E: -119.67, N: 37.41, S: 36.76CA_SanJoaquin_2
W: -120.91, E: -119.17, N: 37.04, S: 36.53CA_SanJoaquin_3
W: -120.53, E: -118.92, N: 36.52, S: 36.11CA_SanJoaquin_4
W: -120.36, E: -118.91, N: 36.11, S: 35.78CA_SanJoaquin_5
W: -120.16, E: -118.91, N: 35.79, S: 35.44CA_SanJoaquin_6
W: -119.8, E: -118.57, N: 35.44, S: 34.91CA_SanJoaquin_7
W: -120.77, E: -120.76, N: 37.137, S: 37.13CA_SanJoaquin_8_Reflight (tile s64825w18700)
W: -119.15, E: -119.122, N: 36.46, S: 36.35CA_SanJoaquin_9_Reflight (tiles s65150w20125 and s65225w20500)
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):
Lineage Statement:
The NOAA Office for Coastal Management (OCM) ingested references to the USGS Entwine Point Tiles (EPT) hosted on Amazon Web Services (AWS) into the Digital Coast Data Access Viewer (DAV). The DAV accesses the point cloud as it resides on AWS under the usgs-lidar-public-container.
Process Steps:
- 2022-01-01 00:00:00 - Raw Data and Boresight Processing: The boresight for each lift was done individually as the solution may change slightly from lift to lift. The following steps describe the Raw Data Processing and Boresight process: 1) Technicians processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source data for boresight. 2) Technicians first used NV5 Geospatial proprietary and commercial software to calculate initial boresight adjustment angles based on sample areas selected in the lift. These areas cover calibration flight lines collected in the lift, cross tie, and production flight lines. These areas are well distributed in the lift coverage and cover multiple terrain types that are necessary for boresight angle calculation. The technicians then analyzed the results and made any necessary additional adjustment until it was acceptable for the selected areas. 3) Once the boresight angle calculation was completed for the selected areas, the adjusted settings were applied to all of the flight lines of the lift and checked for consistency. The technicians utilized commercial and proprietary software packages to analyze how well flight line overlaps matched for the entire lift and adjusted as necessary until the results met the project specifications. 4) Once all lifts were completed with individual boresight adjustment, 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 7 cm RMSEz within individual swaths and less than or equal to 10 cm RMSEz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed checkpoints after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met.
- 2022-01-01 00:00:00 - LAS Point Classification: The point classification was performed as described below. The bare earth surface was manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface was finalized, it was then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS Class 2) LiDAR data inside of the Lake Pond and Double Line Drain hydro-flattened breaklines were then classified to Water (ASPRS Class 9) using proprietary tools. A buffer of 0.5 meter was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 20). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (ASPRS Class 2) points were reclassified to the correct classification after the automated classification was completed. Any noise that was identified either through manual review or automated routines was classified to the appropriate class ( ASPRS Class 7 and/or ASPRS Class 18) followed by flagging with the withheld bit. All data were manually reviewed and any remaining artifacts removed using functionality provided by 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 for both the Point Cloud Data and the Bare Earth. NV5 Geospatial 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.
- CA_SanJoaquin_8_Reflight (Work Unit 300177, Tile s64825w18700)) Work unit 300177 was created specifically to deal with a data void that was discovered during data processing. The data void impacted a total of 1 tile. The void was filled using an auto-correlated point cloud. NV5G utilized autocorrelated point cloud data. This point cloud data was generated from the from San Joaquin 2021 Imagery acquired by Towill, Inc. using INPHO Match-T DSM version 13 software. The resulting point cloud measured roughly 26 pts/sqm. NV5G utilized proprietary software to merge the auto-correlated point cloud with the lidar point cloud and create as seamless a dataset as possible. All points used from the auto-correlated point cloud have had the synthetic bit applied for easy identification within the LAS file. CA_SanJoaquin_9_Reflight (Work Unit 300242, Tiles s65150w20125 and s65225w20500) Work unit 300242 was created specifically to deal with 2 data voids that were discovered during data processing. These data voids impacted a total of 2 tiles. The voids were filled using an auto-correlated point cloud. NV5G utilized autocorrelated point cloud data. This point cloud data was generated from the from San Joaquin 2021 Imagery acquired by Towill, Inc. using INPHO Match-T DSM version 13 software. The resulting point cloud measured roughly 26 pts/sqm. NV5G utilized proprietary software to merge the auto-correlated point cloud with the lidar point cloud and create as seamless a dataset as possible. All points used from the auto-correlated point cloud have had the synthetic bit applied for easy identification within the LAS file.
- Original point clouds in LAS/LAZ format were restructured as Entwine Point Tiles and stored on Amazon Web Services. The data were reprojected horizontally to WGS84 web mercator (EPSG 3857) and the vertical units were converted to meters (NAVD88 GEOID18).
- 2024-01-26 00:00:00 - The NOAA Office for Coastal Management (OCM) created references to the Entwine Point Tiles (EPT) that were ingested into the NOAA Digital Coast Data Access Viewer (DAV). No changes were made to the data. The DAV will access the point cloud as it resides on Amazon Web Services (AWS) under the usgs-lidar-public container. These are the AWS URLs being accessed: https://s3-us-west-2.amazonaws.com/usgs-lidar-public/CA_SanJoaquin_1_2021/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/CA_SanJoaquin_2_2021/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/CA_SanJoaquin_3_2021/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/CA_SanJoaquin_4_2021/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/CA_SanJoaquin_5_2021/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/CA_SanJoaquin_6_2021/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/CA_SanJoaquin_7_2021/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/CA_SanJoaquin_8_Reflight_2021/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/CA_SanJoaquin_9_Reflight_2021/ept.json
(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.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://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/CA_SanJoaquin_2021_A21/
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 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.