Data Management Plan
GUID: gov.noaa.nmfs.inport:71982 | 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
Lidar-derived elevation data for the 2019 Oregon Lidar Consortium (OLC) West Metro 3DEP project area. The project area (PA) encompasses 486,551 acres. Data are within Multnomah County, Oregon. The nominal pulse density is eight pulses per square meter. Points that were determined to be geometrically invalid, or invalid surface returns, were removed from the data set. The hydro-flattened bare earth (BE) digital elevation model (DEM) raster grid cell size is 1 meter. The native projection is Albers Equal Area Conic, units are in meters. The native horizontal datum is North American Datum of 1983 (NAD83(2011)); the native vertical datum is North American Vertical Datum of 1988 (NAVD88); (Geoid 12B). Quantum Spatial Inc. collected the lidar and created this dataset in partnership with the Oregon Department of Geology and Mineral Industries (DOGAMI).
Data were subsequently reprocessed to Entwine Point Tile (EPT) format in web mercator projection with vertical meters. The EPT form of the data is used by the NOAA Digital Coast Data Access Viewer, which this metadata record is supporting. Additional processing steps may have been done by the Data Access Viewer and will be recorded in the lineage section.
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):
Process Steps:
- 2019-12-10 00:00:00 - Lidar data acquisition occurred between May 8, 2019 and August 31, 2019. The survey utilized the Riegl 1560i laser systems mounted in a Cessna Caravan. Near nadir scan angles were used to increase penetration of vegetation to ground surfaces. Ground level GPS and aircraft IMU were collected during the flight. Processing.1. Airborne GPS and IMU data were merged to develop a Single Best Estimate (SBET) of the lidar system trajectory for each flight line. Flight lines and data were reviewed to ensure complete coverage of the study area and positional accuracy of the laser points. 2. Laser point return coordinates were computed using ALS Post Processor software and IPAS Pro GPS/INS software, based on independent data from the LiDAR system, IMU, and aircraft. 3. The raw LiDAR file was assembled into flight lines per return with each point having an associated x, y, and z coordinate. 4. Visual inspection of swath to swath laser point consistencies within the study area were used to perform manual refinements of system alignment. 5. Custom algorithms were designed to evaluate points between adjacent flight lines. Automated system alignment was computed based upon randomly selected swath to swath accuracy measurements that consider elevation, slope, and intensities. Specifically, refinement in the combination of system pitch, roll and yaw offset parameters optimize internal consistency. 6. Noise (e.g., pits and birds) was filtered using ALS postprocessing software, based on known elevation ranges and included the removal of any cycle slips. 7. Using TerraScan and Microstation, ground classifications utilized custom settings appropriate to the study area. 8. The corrected and filtered return points were compared to the RTK ground survey points collected to verify the vertical and horizontal accuracies. 9. Points were output as laser points, TINed and GRIDed surfaces.
- 2019-12-10 00:00:00 - Lidar Post-Processing: The calibrated and controlled lidar swaths were processed using automatic point classification routines in proprietary software. These routines operate against the entire collection (all swaths, all lifts), eliminating character differences between files. Proprietary software was used to thin this dataset from a pulse density of approximately 60 ppsm to the target 8 ppsm. The software randomly selects pulses to remove, including all returns associated, and keeps a user specified percentage of pulses to obtain desired point density. Data were then distributed as virtual tiles to experienced lidar analysts for localized automatic classification, manual editing, and peer-based QC checks. Supervisory QC monitoring of work in progress and completed editing ensured consistency of classification character and adherence to project requirements across the entire project. All classification tags were stored in the original swath files. After completion of classification and final QC approval, the NVA and VVA for the project were calculated. Sample areas for each land cover type present in the project were extracted and forwarded to the client, along with the results of the accuracy tests. Upon acceptance, the complete classified lidar swath files were delivered to the client. Points that were determined to be geometrically invalid, or invalid surface returns, were removed from the data set.
- 2019-12-10 00:00:00 - Hydro-Flattened Raster DEM Processing: Class 2 (Ground) LiDAR points in conjunction with the hydro-breaklines were used to create a 1-meter hydro-flattened raster DEM. Using automated scripting routines within LasTools, an GeoTIFF file was created for each tile. Each surface is reviewed using ArcMap to check for any surface anomalies or incorrect elevations found within the surface.
- 2024-01-31 00:00:00 - Data were converted to Entwine Point Tiles (EPT) in Web Mercator projection and units of meters by USGS. NOAA is leveraging the EPT files for use in the Digital Coast Data Access Viewer and created this metadata to support that usage. (Citation: Entwine Point Tiles)
(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://s3-us-west-2.amazonaws.com/usgs-lidar-public/OR_OLCMetro_2019/ept.json
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 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.