Data Management Plan
GUID: gov.noaa.nmfs.inport:59003 | 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
Geographic Extent: OLC Baker County 3DEP 2017 defined project area (DPA) extends approximately 224,286 acres; the buffered project area (BPA) covers approximately 229,671 acres.
This bare earth hydro flattened digital elevation model (DEM) represents the earth's surface with all vegetation and human-made structures removed and hydro flattening performed within the OLC Baker County 3DEP 2017 defined project area. Bare Earth Hydro Flattened DEMs were derived from LiDAR data using TIN processing of the ground point returns. The DEM grid cell size is 1 meter. The data were developed based on the UTM 11N projection; horizontal datum of NAD83 (2011), meters and vertical datum of NAVD88 Geoid 12B, meters. See Process Steps for derivation of raster datasets.
Dataset Description: The OLC Baker County 3DEP 2017 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 LIDAR Base Specification, Version 1.2. The data were developed based on a horizontal projection/datum of NAD83 (2011), meters and vertical datum of NAVD88 Geoid 12B, meters. LiDAR data was delivered in RAW flight line swath format, processed to create Classified LAS 1.4 Files formatted to individual 0.075 USGS quadrangle tiles, and corresponding hydroconditioned Bare Earth DEMs tiled to 7.5 USGS quadrangle schema, and Breaklines in ESRI File-Geodatabase format.
Ground Conditions: LiDAR was collected 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, QSI established a total of 34 QA control points and 637 control points that were used to calibrate the LIDAR to known ground locations established throughout the OLC Baker County 3DEP 2017 project area.
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):
- 2017-10-01 00:00:00 - Lidar Pre-Processing: Airborne GPS and IMU data were merged to develop a Single Best Estimate (SBET) of the lidar system trajectory for each lift. Lidar ranging data were initially calibrated using previous best parameters for this instrument and aircraft. Relative calibration was evaluated using advanced plane-matching analysis and parameter corrections derived. This was repeated iteratively until residual errors between overlapping swaths, across all project lifts, was reduced to acceptable levels. Data were then block adjusted to match surveyed calibration control. Raw data NVA were checked using independently surveyed checkpoints. Swath overage points were identified and tagged within each swath file.
- 2017-10-01 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. 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 area. All classification tags are stored in the original swath files. After completion of classification and final QC approval, the NVA for the project is calculated. Sample areas for each land cover type present in the project area were extracted and forwarded to the U.S. Geological Survey, for Vegetated Vertical Accuracy (VVA) accuracy tests. Upon acceptance, the complete classified lidar swath files were delivered to the U.S. Geological Survey.
- 2017-10-01 00:00:00 - Classified LAS Processing: 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 ground (ASPRS Class 2) LiDAR data inside of the Lake Pond and Double Line Drain hydro flattening breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 0.35 meters was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 10). 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. 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 to Class 18 (High Noise) and Class 129 (Overlap Ground). 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. All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. ArcMap us used as a final check of the bare earth dataset. QSI proprietary software was then used to create the deliverable industry-standard LAS files. QSI 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.
- 2017-10-01 00:00:00 - Hydro Flattening Breakline Processing: Class 2 LiDAR was used to create a bare earth surface model. Proprietary software utilized rasters created within Bentley Microstation to auto-generate breaklines of inland streams and rivers with a 30 meter nominal width which were then manually inspected and digitized. Breaklines for Lakes with surface area greater than 2 acres were generated using heads-up digitization. Elevation values were assigned to all Inland Ponds and Lakes within ESRI ArcMap; Inland Pond and Lake Islands, Inland Stream and River Islands were assigned elevation values from within ESRI ArcMap. All ground (ASPRS Class 2) LiDAR data inside of the collected inland breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 0.35 meters was also used around each hydro-flattened stream. These points were moved from ground (ASPRS Class 2) to Ignored Ground (ASPRS Class 10). The breakline files were then translated to ESRI File-Geodatabase format using ESRI conversion tools.
- 2017-10-01 00:00:00 - Hydro Flattened Raster DEM Process: Class 2 LiDAR in conjunction with the hydro breaklines were used to create a hydro-flattened DEM. Using automated scripting routines within Bentley Microstation, ascii files were created for each tile. The ascii files are then mosaicked together in ArcMap and reviewed for surface anomalies.
- The NOAA Office for Coastal Management (OCM) received 1,838 IMG files from the Oregon Lidar Consortium/ DOGAMI. The data were in UTM Zone 11N (NAD83 2011) coordinates in meters and NAVD88 (Geoid12b) elevations in meters, at 1-m spatial resolution. OCM converted the files from .IMG format to Geotiff format using gdal_warp. The files were then assigned the EPSG codes of 6340 (horizontal) and 5703 (vertical) and then copied 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.
- 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.