Data Management Plan
GUID: gov.noaa.nmfs.inport:58102 | 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
Watershed Sciences, Inc. (WS) collected Light Detection and Ranging (LiDAR) data of the Klamath River and associated riparian zones from Klamath Falls, Oregon to Happy Camp, California for Woolpert, Inc. Acquisition of the data occurred between February 27th and March 15th, 2010. The total deliverable area, including a 100 m buffer, is 107,547 acres.
The LiDAR survey used a Leica ALS60 laser system. For the Klamath River survey area, the sensor was set to yield an average native pulse density of > 8 points per square meter over terrestrial surfaces. Up to 4 range measurements are possible per pulse, and all discernible laser returns were processed for the output data set. This lidar data was used to create bare-earth DEMs.
OCM received bare-earth hydroflattened DEM files in ESRI GRID format from the Oregon Lidar Consortium. The files were in California State Plane zone 1 projected coordinate system, NAD83 (HARN) and geoid09, with 3-foot horizontal resolution. No metadata came with this data set; information in this record is derived from the accompanying project report, which is linked below. Additionally, the points from which this DEM was derived are available for download, and are linked in the Related Items section below.
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:
Data was collected and processed by Watershed Sciences Inc. and Woolpert and delivered to the Oregon Department of Geology and Mineral Industries (DOGAMI). The data was obtained by NOAA from DOGAMI and ingested into the Digital Coast Data Access Viewer.
Process Steps:
- Acquisition. The LiDAR survey uses a Leica ALS60 laser system mounted on a Cessna Caravan. For the Klamath River survey area, the sensor scan angle was ±13 degrees from nadir1 with a pulse rate designed to yield an average native density (number of pulses emitted by the laser system) of > 8 points per square meter over terrestrial surfaces. All survey areas were surveyed with an opposing flight line side-lap of >50% (>100% overlap). The Leica ALS60 system allows up to four range measurements (returns) per pulse, and all discernible laser returns were processed for the output dataset. It is not uncommon for some types of surfaces (e.g. dense vegetation or water) to return fewer pulses than the laser originally emitted. These discrepancies between 'native' and 'delivered' density will vary depending on terrain, land cover and the prevalence of water bodies. (Citation: raw lidar)
- LiDAR survey datasets were referenced to the 1 Hz static ground GPS data collected over pre- surveyed monuments with known coordinates. While surveying, the aircraft collected 2 Hz kinematic GPS data, and the onboard inertial measurement unit (IMU) collected 200 Hz aircraft attitude data. Waypoint GPS v.8.10 was used to process the kinematic corrections for the aircraft. The static and kinematic GPS data were then post-processed after the survey to obtain an accurate GPS solution and aircraft positions. IPAS v.1.35 was used to develop a trajectory file that includes corrected aircraft position and attitude information. The trajectory data for the entire flight survey session were incorporated into a final smoothed best estimated trajectory (SBET) file that contains accurate and continuous aircraft positions and attitudes. Laser point coordinates were computed using the IPAS and ALS Post Processor software suites based on independent data from the LiDAR system (pulse time, scan angle), and aircraft trajectory data (SBET). Laser point returns (first through fourth) were assigned an associated (x, y, z) coordinate along with unique intensity values (0-255). The data were output into large LAS v. 1.2 files; each point maintains the corresponding scan angle, return number (echo), intensity, and x, y, z (easting, northing, and elevation) information. The following processing steps were performed on the data: • LiDAR points were then filtered for noise, pits (artificial low points) and birds (true birds as well as erroneously high points) by screening for absolute elevation limits, isolated points and height above ground. • Points from overlapping lines were tested for internal consistency and final adjustments were made for system misalignments (i.e., pitch, roll, heading offsets and scale). • The TerraScan software suite was used for classifying near-ground points (Soininen, 2004). The resulting ground classified points were visually inspected and additional ground point modeling was performed in site-specific areas to improve ground detail.
- Data was obtained by NOAA Office for Coastal Management from DOGAMI. Data were in California State Plane Zone 1 NAD83(HARN) US survey feet with NAVD88 (Geoid09) US Survey feet vertically. Data were converted to geographic coordinates in ellipsoid heights (meters) using the general cartographic transform package subroutines and reversing the application of GEOID09.
(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://coast.noaa.gov/htdata/lidar3_z/geoid12b/data/8907/
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Data is available online for 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.