Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:63140 | Published / External
This is an outdated version of the NOAA Data Management Plan template. InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. Please see the Data Management Plan Help Guide to learn more.
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
Product: Classified light detection and ranging (lidar) LAS 1.4 files formatted to 4,474 1500 ft x 1500 ft tiles.
In July 2018, Quantum Spatial (QSI) was contracted by the United States Geological Survey (USGS) to collect Light Detection and Ranging (LiDAR) data in the summer of 2018 for several areas of interest (AOIs), comprising the North Slope Borough Communities 3DEP LiDAR project in Alaska. Data were collected to aid USGS in assessing the topographic and geophysical properties of the study area, to support its mission to gather high quality 3D elevation data over the state of Alaska.
Due to inclement weather and the short acquisition timeframe in Alaska, QSI was able to collect LiDAR data in eight out of the eleven contracted AOIs in the 2018 acquisition season: Atqasuk, Barrow North, Barrow South, Barrow Village, Deadhorse, Kaktovic, Nuiqsut and Wainwright. Data collection for the remaining AOIs: Anaktuvuk Pass, Point Lay, and Point Hope was then completed in the summer of 2019.
Dataset Description: The North Slope Borough 3DEP LiDAR project called for the planning, acquisition, and processing of LiDAR data collected at an aggregate nominal pulse spacing (ANPS) of either 0.35 meters or 0.70 meters depending on area. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification, Version 1.3. The data was developed based on the NAD83(2011) horizontal datum and NAVD88 (GEOID12B) vertical datum. Data was projected in the appropriate Alaska State Plane Zone for its location.
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:
- 2019-04-30 00:00:00 - LiDAR Pre-Processing: 1. Review flight lines and data to ensure complete coverage of the study area and positional accuracy of the laser points. 2. Resolve kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. 3. Develop a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with sensor head position and attitude recorded throughout the survey. 4. Calculate laser point position by associating SBET position to each laser point return time, scan angle, intensity, etc. Create raw laser point cloud data for the entire survey in *.las format. Convert data to orthometric elevations by applying a geoid correction. 5. Import raw laser points into manageable blocks (less than 500 MB) to perform manual relative accuracy calibration and filter erroneous points. Classify ground points for individual flight lines. 6. Using ground classified points per each flight line, test the relative accuracy. Perform automated line-to-line calibrations for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Calculate calibrations on ground classified points from paired flight lines and apply results to all points in a flight line. Use every flight line for relative accuracy calibration. 7. Adjust the point cloud by comparing ground classified points to supplemental ground control points.
- 2019-04-30 00:00:00 - LiDAR Post-Processing: 1. Classify data to ground and other client designated classifications using proprietary classification algorithms. 2. Manually QC data classification 3. After completion of classification and final QC approval, calculate final NVA for the project using ground control quality check points.
- The NOAA Office for Coastal Management (OCM) downloaded this data set from this USGS site: ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/AK_NorthSlopeBorough_2018_B18/ All 14 subfolders, or blocks, were downloaded. The total number of files downloaded and processed was 5,467. OCM determined the following information regarding the USGS Quality Level (QL) and Alaska State Plane Zone projection for each block: ------------------------------------------------------------------------------------------------------ "NAD83(2011) / Alaska zone 4 (ftUS)" B9 = QL1 B12 = QL2 B2 = QL1 B6 (2 AOIs) = QL2 ------------------------------------------------------------------------------------------------------ "NAD83(2011) / Alaska zone 2 (ftUS)" B1 = QL1 B5 = QL2 -------------------------------------------------------------------------------------------------------- "NAD83(2011) / Alaska zone 6 (ftUS)" B3 = QL1 (2 AOIs) B7 (3 AOIs) = QL2 ----------------------------------------------------------------------------------------------------- "NAD83(2011) / Alaska zone 7 (ftUS)" B4 = QL1 B8 = QL2 B10 = QL1 B13 = QL2 ---------------------------------------------------------------------------------------------------- "NAD83(2011) / Alaska zone 8 (ftUS)" B11 = Ql1 B14 = QL2 The data were in the above Alaska State Plane zones, (NAD83 2011), U.S. Feet coordinates and NAVD88 (Geoid12B) elevations in U.S Feet. The data were classified as: 1 - Unclassified, 2 - Ground, 3- Low Vegetation (0.5 - 2 meters), 4 - Medium Vegetation (2 - 6 meters), 5 - High Vegetation (6+ meters), 6 - Buildings, 7 - Noise, 9 - Water, 17 - Bridge Decks, 20 - Ignored Ground, 21 - Snow. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). For this mission, only folders Blocks 1, 2, 3, 4, 9, 10 and 11 were processed, as these were the QL1 files. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 2. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid12B model, to convert from Alaska State Plane (NAD83 2011), U.S. Feet coordinates to geographic coordinates, to assign the geokeys, 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.
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/geoid12b/9197/
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.