Data Management Plan
GUID: gov.noaa.nmfs.inport:65520 | 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
Dataset Description: The CA Central Valley Lidar 2016 D16 Mod 002: CA Sacramento Delta Lidar 2017 D16 lidar project called for the planning, acquisition, processing, and production of derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.35 meters. Project specifications were based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.2
Ground Conditions: Lidar was collected from December 9, 2017 through January 21, 2018 by Woolpert, while no snow was on the ground and rivers were at or below normal levels. Saturated or partially flooded farm fields were identified following data acquisition. Through technical guidance discussions with USGS and the California Department of Water, it was determined such areas shall not be considered hydrologic features. Intermittently, partially flooded, irregular, and apparently non-agricultural fields were treated as hydrologic features. In all cases, best professional judgement was used in determination of treatment. In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Woolpert established 35 ground control points that were used to calibrate the lidar to known ground locations established throughout the project area. An additional 143 independent accuracy checkpoints (75 NVA points and 68 VVA points), were collected and used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data.
In addition to these bare earth Digital Elevation Model (DEM) data, the lidar point data that these DEM data were created from, are also available. These data are available for custom download at the link provided in the URL section of this metadata record.
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):
Lineage Statement:
This data set was downloaded from the CA DWR ftp site and processed to make it available for custom download from the Data Access Viewer (DAV) and for bulk download from https.
Process Steps:
- 2017-12-09 00:00:00 - The data was developed based on a horizontal datum/projection of NAD83 (NSRS2007) UTM Zone 10 (EPSG 3717) meters, and a vertical datum of NAVD88 (GEOID12B), US survey feet. DEM data was delivered as ERDAS IMG files formatted to 1,706 individual 1,500-meter x 1,500-meter tiles. Product: 0.5-meter bare-earth raster digital elevation model (DEM) data tiles in ERDAS IMG format. Geographic Extent: Approximately 1,312 square miles across several counties in central California.
- 2019-06-03 00:00:00 - Hydro-Flattened Digital Elevation Models (DEMs): Class 2 (ground) lidar points in conjunction with the hydro breaklines as well bridge breaklines were used to create a 0.5-meter hydro-flattened bare-earth raster DEM. Using automated scripting routines within ArcMap, an ERDAS IMG file was created for each tile. Each surface is reviewed using Global Mapper to check for any surface anomalies or incorrect elevations found within the surface.
- 2021-09-20 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded 1706 ERDAS .img format files from this CA DWR ftp site: http://gisarchive.cnra.ca.gov/iso/ImageryBaseMapsLandCover/LIDAR/DeltaLIDAR2017/bare_earth/be_rasters/. The files were at a 0.5 m grid spacing. The data were in UTM Zone 10 (NSRS 2007), meters coordinates and in NAVD88 (Geoid12B) elevations in US survey feet. OCM assigned the appropriate EPSG codes (Horiz - 3717, Vert - 6360) and copied the raster files to https for Digital Coast storage and provisioning purposes.
(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
- 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.us-east-1.amazonaws.com/dem/CA_Sacramento_DEM_2017_9368/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 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
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.