Data Management Plan
GUID: gov.noaa.nmfs.inport:50147 | 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
Terrapoint, on behalf of multiple agencies, collected topographic lidar of the Lower Columbia River area. Field data collection took place between the dates of January 10th and February 20th, 2005. The control network
and checkpoint surveys were performed from January 4th to February 12th, 2005. The project area covers approximately 890 square miles along the Columbia River, from the Bonneville Dam to the Pacific Ocean.
A total of 431 flightlines were required to cover the project area flightlines.
Terrapoint used a 40 kHz Airborne Laser Terrain Mapping System ALTMS sensor attached to a Navajo Twin-engin aircraft (C-FVZM). The mission was flown at 3500 feet above ground level at an average speed of 140 knots. The system
consists of a 36 degree full scan angle laser, a Trimble 4700 GPS receiver and a Honeywell H764 IMU unit. The nominal flightline spacing was 1070 feet with 30 to 50% sidelap.
The surveyed and processed data was received divided by funding agency. The agency responsible for funding each tile is represented as a number (0:COE, 1:DNR, 2:DOGAMI, 3:DOI) in the "User Data" field of each LAS file.
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:
- 2005-01-01 00:00:00 - The following software was used to reduce the GPS kinematic data, compute the 3-D laser points, classify and edit laser points, produce shaded relief images and transform the ellipsoidal heights to Orthometric: ArcView, Flykin, Microstation, TerraScan, TerraModeler, TerraModel, and Terrapoint Proprietary LiDAR processing software
- 2013-08-01 00:00:00 - The NOAA Office for Coastal Management (OCM) received topographic files in ASCII .TXT format. The files contained lidar elevation measurements, GPS time measurements (week/second), number of returns, return number, scan angle, intensity, and classification. The data were received in Washington State Plane South Zone 4602, NAD83 coordinates and were vertically referenced to NAVD88 using the Geoid03 model. The vertical units of the data were feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The ASCII .TXT files were run through a parser to convert GPS Week/Second Time to Adjusted Standard GPS Time and change the format of the Classification field. 2. The parsed ASCII .TXT files were converted to LAS version 1.2 using LAStools' txt2las tool. 3. The User Data field was set depending on agency which funded the tile. The User Data values are: 0 (COE), 1 (DNR), 2 (DOGAMI), 3 (DOI). 4. The topographic las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid03. 5. The topographic las files were converted from a Projected Coordinate System (WA SP South) to a Geographic Coordinate system (NAD 83). 6. The topographic las files' vertical units were converted from feet to meters. 7. The topographic las files' horizontal units were converted from feet to decimal degrees.
(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.amazonaws.com/laz/geoid18/2535/index.html
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
This data can be obtained on-line at the following URL:
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2535
;
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.