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.

URL of higher-level DM Plan (if any) as submitted to DM Plan Repository:
Always left blank

1. General Description of Data to be Managed

1.1. Name of the Data, data collection Project, or data-producing Program:
2010 US B.O.R. Lidar: Klamath River, CA
1.2. Summary description of the data:

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 uses 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 dataset.

OCM received 1,039 LAZ files from the Oregon Lidar Consortium. The files were in California State Plane zone 1 projected coordinate system, NAD83 (HARN) and geoid09. No metadata came with this dataset; information in this record is derived from the accompanying project report, which is linked below. Additionally, bare-earth DEMs produced from this dataset are available for download, and are linked in the Related Items section below.

Taken From: Item Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.
Edit
1.3. Is this a one-time data collection, or an ongoing series of measurements?
One-time data collection
Taken From: Extents / Time Frames | Time Frame Type
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
Edit
1.4. Actual or planned temporal coverage of the data:
2010-02-27 to 2010-03-15
Taken From: Extents | Time Frame - Start, Time Frame - End
Notes: All time frames from all extent groups are included.
Edit
1.5. Actual or planned geographic coverage of the data:
W: -123.488, E: -121.7, N: 42.284, S: 41.813
Taken From: Extents | Geographic Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.
Edit
1.6. Type(s) of data:
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
No information found
1.7. Data collection method(s):
(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.)
No information found
1.8. If data are from a NOAA Observing System of Record, indicate name of system:
Always left blank due to field exemption
1.8.1. If data are from another observing system, please specify:
Always left blank due to field exemption

2. Point of Contact for this Data Management Plan (author or maintainer)

2.1. Name:
NOAA Office for Coastal Management (NOAA/OCM)
Taken From: Support Roles (Metadata Contact) | Person
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.
Edit
2.2. Title:
Metadata Contact
Always listed as "Metadata Contact"
2.3. Affiliation or facility:
NOAA Office for Coastal Management (NOAA/OCM)
Taken From: Support Roles (Metadata Contact) | Organization
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
Edit
2.4. E-mail address:
coastal.info@noaa.gov
Notes: The email address is taken from the address listed for the Person assigned as the Metadata Contact in Support Roles.
2.5. Phone number:
(843) 740-1202
Notes: The phone number is taken from the number listed for the Person assigned as the Metadata Contact in Support Roles. If the phone number is missing or incorrect, please contact your Librarian to update the Person record.

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.

3.1. Name:
No information found
Taken From: Support Roles (Data Steward) | Person
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.
Edit
3.2. Position Title:
Data Steward
Always listed as "Data Steward"

4. Resources

Programs must identify resources within their own budget for managing the data they produce.

4.1. Have resources for management of these data been identified?
Yes
4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):
Unknown

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.

5.1. Processing workflow of the data from collection or acquisition to making it publicly accessible
(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.
5.1.1. If data at different stages of the workflow, or products derived from these data, are subject to a separate data management plan, provide reference to other plan:
Always left blank
5.2. Quality control procedures employed
(describe or provide URL of description):
No information found

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.

6.1. Does metadata comply with EDMC Data Documentation directive?
No
Notes: All required DMP fields must be populated and valid to comply with the directive.
6.1.1. If metadata are non-existent or non-compliant, please explain:

Missing/invalid information:

  • 1.6. Type(s) of data
  • 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
Notes: Required DMP fields that are not populated or invalid are listed here.
6.2. Name of organization or facility providing metadata hosting:
NMFS Office of Science and Technology
Always listed as "NMFS Office of Science and Technology"
6.2.1. If service is needed for metadata hosting, please indicate:
Always left blank
6.3. URL of metadata folder or data catalog, if known:
Always listed as the URL to the InPort Data Set record
6.4. Process for producing and maintaining metadata
(describe or provide URL of description):
Metadata produced and maintained in accordance with the NOAA Data Documentation Procedural Directive: https://nosc.noaa.gov/EDMC/DAARWG/docs/EDMC_PD-Data_Documentation_v1.pdf
Always listed with the above statement

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.

7.1. Do these data comply with the Data Access directive?
Yes
7.1.1. If the data are not to be made available to the public at all, or with limitations, has a Waiver (Appendix A of Data Access directive) been filed?
No information found
7.1.2. If there are limitations to public data access, describe how data are protected from unauthorized access or disclosure:

None

7.2. Name of organization of facility providing data access:
NOAA Office for Coastal Management (NOAA/OCM)
Taken From: Support Roles (Distributor) | Organization
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.
Edit
7.2.1. If data hosting service is needed, please indicate:
Taken From: Data Management | If data hosting service is needed, please indicate
Notes: This field is required if a Distributor has not been specified.
Edit
7.2.2. URL of data access service, if known:
Taken From: Distribution Info | Download URL
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Edit
7.3. Data access methods or services offered:

Data is available online for custom downloads

7.4. Approximate delay between data collection and dissemination:
No information found
7.4.1. If delay is longer than latency of automated processing, indicate under what authority data access is delayed:

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.

8.1. Actual or planned long-term data archive location:
(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)
NCEI-CO
8.1.1. If World Data Center or Other, specify:
Taken From: Data Management | Actual or planned long-term data archive location
Notes: This field is required if archive location is World Data Center or Other.
Edit
8.1.2. If To Be Determined, Unable to Archive or No Archiving Intended, explain:
Taken From: Data Management | If To Be Determined, Unable to Archive or No Archiving Intended, explain
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
Edit
8.2. Data storage facility prior to being sent to an archive facility (if any):
Office for Coastal Management - Charleston, SC
Taken From: Physical Location | Organization, City, State, Location Description
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
Edit
8.3. Approximate delay between data collection and submission to an archive facility:
No information found
8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
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.

Always left blank