Data Management Plan
2018 USFS Lidar DEM: National Forest Locations (WA, OR)
|
Data Set
(DS)
| OCM Partners
GUID: gov.noaa.nmfs.inport:69456 | Published / External
GUID: gov.noaa.nmfs.inport:69456 | 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.
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:
2018 USFS Lidar DEM: National Forest Locations (WA, OR)
Taken From: Item
Identification | Title
1.2. Summary description of the data:
Digital Elevation Model created from leaf-on airborne LiDAR collected over approximately 4,141 square miles of national forestry in Oregon and Washington State.
Taken From: Item
Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.
Notes: Only a maximum of 4000 characters will be included.
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.
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
1.4. Actual or planned temporal coverage of the data:
2018-06-29 to 2019-01-24
Taken From: Extents | Time Frame
- Start, Time Frame - End
Notes: All time frames from all extent groups are included.
Notes: All time frames from all extent groups are included.
1.5. Actual or planned geographic coverage of the data:
W: -121.19468639, E: -121.11624439, N: 42.89437835, S: 42.76640243
Sycan Marsh
W: -121.5859, E: -121.2956, N: 45.51534, S: 45.2585East Zone
W: -120.59047, E: -119.8764, N: 48.80922, S: 48.23965Methow Twisp
W: -119.49611, E: -119.025902, N: 44.40912, S: 44.28255North Aldrich
W: -119.04997, E: -118.7215075, N: 43.86232, S: 43.72728Rattlesnake
W: -120.96962, E: -120.08232, N: 43.00656, S: 41.991773Thomas Creek
W: -118.79006, E: -118.677443, N: 44.2937, S: 44.12172Upper Bear Lake
Taken From: Extents | Geographic
Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.
Notes: All geographic areas from all extent groups are included.
1.6. Type(s) of data:
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
Model (digital)
Taken From: Data Set
Information | Data Presentation Form
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.)
(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
Taken From: Acquisition
Information | Instruments, Platforms
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.
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.
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.
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
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.
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.
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):
(describe or provide URL of description):
Lineage Statement:
Data were collected and processed by Atlantic, Inc, for the U.S. Forest Service. The U.S. Forest Service transferred the data to NOAA for distribution on the Digital Coast.
Process Steps:
- Atlantic operated a PACDV (N750DV) outfitted with an Optech Galaxy Prime LiDAR system during the collection of the project area. The data was collected with a nominal pulse spacing of 8 pls/m^2 at a nominal flight height of 1500-1800 meters and a nominal flight speed of 130 kts. Scanner pulse rate was 500 kHz. Atlantic acquired 1588 passes of the AOI as a series of perpendicular and/or adjacent flight-lines executed in 44 flight missions conducted between June 29, 2018 and January 24, 2019. Onboard differential Global Navigation Satellite System (GNSS) unit(s) recorded sample aircraft positions at 2 hertz (Hz) or more frequency. LiDAR data was only acquired when a minimum of six (6) satellites were in view.
- Ground Control: A total of 545 ground survey points were collected in support of this project. Point cloud data accuracy was tested against a Triangulated Irregular Network (TIN) constructed from LiDAR points in clear and open areas. A clear and open area can be characterized with respect to topographic and ground cover variation such that a minimum of five (5) times the Nominal Pulse Spacing (NPS) exists with less than 1/3 of the RMSEZ deviation from a low-slope plane. Slopes that exceed ten (10) percent were avoided. Each land cover type representing ten (10) percent or more of the total project area were tested and reported with a GCP. In land cover categories other than dense urban areas, the tested points did not have obstructions forty-five (45) degrees above the horizon to ensure a satisfactory TIN surface. The GCP value is provided as a target. It is understood that in areas of dense vegetation, swamps, or extremely difficult terrain, this value may be exceeded.
- Atlantic used Leica software products to download the IPAS ABGNSS/IMU data and raw laser scan files from the airborne system. Waypoint Inertial Explorer is used to extract the raw IPAS ABGNSS/IMU data, which is further processed in combination with controlled base stations to provide the final Smoothed Best Estimate Trajectory (SBET) for each mission. The SBETs are combined with the raw laser scan files to export the LiDAR ASCII Standard (*.las) formatted swath point clouds. Using a combination of GeoCue, TerraScan and TerraMatch; overlapping swath point clouds are corrected for any orientation or linear deviations to obtain the best fit swath-to-swath calibration. Relative calibration was evaluated using advanced plane-matching analysis and parameter corrections derived. This process was repeated interactively until residual errors between overlapping swaths, across all project missions, was reduced to ≤2cm. A final analysis of the calibrated lidar is preformed using a TerraMatch tie line report for an overall statistical model of the project area.
- Multiple automated filtering routines are applied to the calibrated LiDAR point cloud identifying and extracting bare-earth and above ground features. GeoCue, TerraScan, and TerraModeler software was used for the initial batch processing, visual inspection and any manual editing of the LiDAR point clouds. Classified point clouds were cut to match the tile index and its corresponding tile names and delivered in .laz format. The classification scheme was 1=unclassified; 2=ground; 7=low point (noise), 18=high noise.
- U.S. Forest services remove high and low noise from 2 LAZ files the vendor missed. Points with Source ID's less than 200 (189, 193, 194) were removed from - FRESY4_503588_978808_20181105.laz FRESY4_505088_978808_20181105.laz
- 2023-03-13 00:00:00 - Data were received by NOAA Office for Coastal Management from the U.S. Forest Service with USFS region 6 Albers coordinates in ERDAS Imagine format. Data were converted to cloud optimized GeoTiff format. (Citation: DEM from classified lidar data)
Taken From: Lineage | Lineage
Statement, Process Steps (Process Date/Time, Source Citation Title, Description)
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):
(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.7. Data collection method(s)
- 3.1. Responsible Party for Data Management
- 5.2. Quality control procedures employed
- 7.3. Data access methods or services offered
- 7.4. Approximate delay between data collection and dissemination
- 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?
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):
(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
7.1.2. If there are limitations to public data access, describe
how data are protected from unauthorized access or disclosure:
None
Taken From: Access Info |
Data Access Constraints
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.
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.
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.
Notes: This field is required if a Distributor has not been specified.
7.2.2. URL of data access service, if known:
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9804/details/9804
https://noaa-nos-coastal-lidar-pds.s3.us-east-1.amazonaws.com/dem/USFS_Forests_2018_9804/index.html
https://noaa-nos-coastal-lidar-pds.s3.us-east-1.amazonaws.com/dem/USFS_Forests_2018_9804/index.html
Taken From: Distribution
Info | Download URL
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
7.3. Data access methods or services offered:
No information found
Taken From: Access Info |
Data Access Procedure
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:
Taken From: Data
Management | If delay is longer than latency of automated processing, indicate under
what authority data access is delayed
Notes: This field is required if applicable.
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.
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)
(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_NC
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.
Notes: This field is required if archive location is World Data Center or Other.
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.
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
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.
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
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
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
No information found
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