Data Management Plan
GUID: gov.noaa.nmfs.inport:58304 | 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
Continental Mapping Consultants, Inc. (CMC) acquired LiDAR data and imagery for the Tualatin National Wildlife Refuge on May 15, 2012. The project area was expanded to include a 100m buffer around the area of interest to ensure complete coverage. The dataset encompasses 19.24 square miles in the Tualatin National Wildlife Refuge, Wapato, Oregon. The lidar was collected with a pulse density of 30-60 points per square meter. Continental Mapping used co-mounted imagery and lidar sensors and a helicopter to acquire the data.
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:
- LiDAR Data Acquisition: The LiDAR acquisition mission was flown on May 15, 2012. LiDAR acquisition of the project area consisted of 21 low level flight lines with an average altitude of 375 meters. The imagery acquisition consisted of 9 high level flight lines flown at an average altitude of 860 meters.
- A network of control points was established within the project boundary to validate the accuracy of the LiDAR data. The network consisted of Real Time Kinetic (RTK) points collected by Terra Remote Sensing, and existing US Fish and Wildlife Service monuments. The following points, WP02, WP03, WP06, and WP08 were verified by Terra Remote Sensing against the active CORS control stations, JIME (Portland, OR) and NWBG (Newberg, OR). An additional network check was completed between CORS stations FTS5, GOBS, and P367. Points WP02 and WP08 were also used as an RTK/PPK (Post Processed Kinematic) base station for the collection of lidar and orthophoto checkpoints.
- The raw project LiDAR data was imported, processed, and outputs were created using the TerraScan software suite. Automated ground filters were run on the raw las data. These filters include factors and settings such as max building size, terrain angle, iteration angle degrees to plane, iteration distance to plane, reduce iteration angle when edge length is less than, and stop triangulation when edge length is less than. After the automated ground filter is run each tile is than checked for spikes and anomalies. Manual edits are applied to any areas that the analysts interpreted the ground doing something other than what the automatic ground filter interpreted. An analyst also classifies and edits any other las point to needed feature classes at this time. Only the LAS inside the provided map limit was classified and checked by analysts. Any points that were relevant to the classification were classified to the SOW requirements and placed using the classes provided in the SOW. Class 1 Processed, but unclassified, Class 2 Bare-Earth Ground, Class 3 Vegetation, Class 4 Roads, Class 7 Noise, Class 9 Water, Class 10 Ignored Ground, Class 11 Withheld. Classified tiles were saved as las (Version 1.2). After classification and edits were complete the projection information was Geo-Coded back into the LAS files.
- 2019-12-11 00:00:00 - NOAA/OCM received the data from DOGAMI in LAZ format . Data were in NAD83(CORS 96) Oregon Lambert horizontally and NAVD88 (Geoid09) vertically. For ingest into the Digital Coast Data Access Viewer data were converted to geographic coordinates on the GRS80 ellipsoid in meters.
(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://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/8963/index.html
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.