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
Because no metadata record was provided with the Bradfield to Behms Corridor data, this record was created by the NOAA Office for Coastal Management (OCM) based on information supplied in the Bradfield to Behms Corridor Quality Assurance Report of DOT Roads to Resources Project, the Tetra Tech UAF Light Detection and Ranging (LiDAR) and Ortho-Imagery Data Project Report Bradfield to Behms Corridor, and the Hoonah Corridor metadata. Links to both reports are provided in the URL section of this record.
Tetra Tech was contracted by the University of Alaska Fairbanks (UAF) to provide LiDAR and ortho-imagery data for the Road to Resources in Alaska Program. Tetra Tech collected LIDAR data and aerial imagery during the fall of 2013 and the spring/summer of 2014.
This classified point cloud data is part of a data set of LiDAR point cloud data, derived elevation products and orthoimagery. The data were acquired along 5 corridors in South Eastern Alaska near Ketchikan and Juneau. The data were procured by GINA (Geographic Information Network of Alaska) at the University of Fairbanks (UAF) on behalf of the Alaska DoT (Department of Transportation). The 5 corridors are identified as Anita Bay, Bradfield to Behms, Hoonah, Revilla and Wrangell. The classified data has been classified as follows: Class 1: Unclassified, Class 2: Bare-earth ground, Class 3: Low vegetation, Class 4: Medium Vegetation, Class 5: High Vegetation, Class 7: Noise, Class 8: Ground Model Keypoints, Class 9: Water. Low vegetation (0 - 6 ft), medium vegetation (6 -15 ft), high vegetation ( > 15 ft).
The NOAA Office for Coastal Management (OCM) downloaded this lidar data from the AK DGGS site (https://elevation.alaska.gov/) and processed the data to be available on the Digital Coast Data Access Viewer (DAV). OCM processed all points to the Digital Coast Data Access Viewer (DAV).
In addition to these lidar point data, the bare earth Digital Elevation Models (DEM) created from the lidar point data are also available. These data are available for custom download at the link provided in the URL section of this metadata record.
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.
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):
- The LiDAR data for the Bradfield to Behms corridor was acquired on June 26 and 27 and July 11 of 2014. SBET and shapefile of the trajectory are located with the point cloud data. The data was post processed through PosPac, Waypoint’s GPS and IMU (inertial measurement unit) post processing software, and LMS, Optech’s LiDAR post processing software. PosPac is used to generate the trajectory file which contains the position (X, Y, Z) from differential GPS observations and the plane’s attitude (roll, pitch, heading) from the IMU. LMS is used to join the discreet point range information to the trajectory information through a common time stamp and to calibrate the data. The calibration is achieved by first identifying common features in the overlap of adjacent flight lines, and then adjustments are applied to the IMU’s angular offsets to align the data. Once finished, LMS refines the calibration further through a bundle adjustment to create the final calibrated data set. Classification of the calibrated LiDAR data set is achieved through the use of TerraScan, the industry standard software from TerraSolid for classifying LiDAR. Individual macros were defined that derive and refine a ground surface, vegetation, and buildings. These macros are also used to eliminate spurious points below the surface and high point artifacts. The Bradfield to Behms area was then manually checked and edited to eliminate low and high points as well as to ensure that points are classified appropriately. Breaklines were derived from LiDAR and imagery and help define water classes in the LiDAR data.
- 2018-09-05 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded 110 laz files from the Alaska Division of Geological and Geophysical Surveys data Portal (https://elevation.alaska.gov/). The files contained classified elevation and intensity measurements for the 2014 Bradfield to Behms data set. The data were in Alaska State Plane, Zone 5001 coordinates (NAD83, US survey feet) and NAVD88 elevations (GEOID12A) in feet. The data were classified: Class 1: Unclassified, Class 2: Bare-earth ground, Class 3: Low vegetation, Class 4: Medium Vegetation, Class 5: High Vegetation, Class 7: Noise, Class 8: Ground Model Keypoints, Class 9: Water. OCM processed all points to the Digital Coast Data Access Viewer (DAV). OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. The LAStools software scripts lasinfo and lasvalidate were run on the laz files to check for errors. 2. An internal OCM script was run to check the number of points by classification and by flight ID and the gps times and intensity ranges. 3. Internal OCM scripts were run on the laz files to convert from Alaska State Plane, Zone 5001 coordinates to geographic coordinates, to convert from NAVD88 elevations to ellipsoid elevations using the GEOID12A model, to convert from feet to meters, to assign the geokeys, to assign a lidar domain profile, to sort the data by gps time and zip the data to database and to http.
(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.
- 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.
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.
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Data is available online for custom and bulk 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
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.