Data Management Plan
GUID: gov.noaa.nmfs.inport:70466 | 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
Product: These lidar data are processed Classified LAS 1.4 files, formatted to individual 2000 foot x 2000 foot tiles; used to create intensity images, 3D breaklines and hydro-flattened DEMs as necessary.
Geographic Extent:
USGS_LPC_IL_LaSalle_B1 -
LaSalle County, Illinois, covering approximately 1,148 square miles. LaSalle County is one area of interest (AOI) from a lidar survey that was collected over two (2) areas of interest in Illinois identified as LaSalle and Expansion Counties.
USGS_LPC_IL_LaSalle_B2 -
Grundy, Kendall, and DeKalb County, Illinois (Expansion Counties), covering approximately 1,388 square miles. Grundy, Kendall, and DeKalb Counties are one area of interest (AOI) from a lidar survey that was collected over two (2) areas of interest in Illinois identified as LaSalle and Expansion Counties.
LaSalle County and the Expansion Counties cover a total of approximately 2,563 square miles.
Dataset Description:
LaSalle county, Illinois 2017 Lidar project called for the Planning, Acquisition, processing and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.5 meter. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.2; Quality Level 2+. The data was developed based on a horizontal projection/datum of NAD83 (2011), State Plane Coordinate System Illinois East (FIPS 1201), US Survey Feet and vertical datum of NAVD88 (GEOID12B), US Survey Feet. Lidar data was delivered as flightline-extent unclassified LAS swaths, as processed Classified LAS 1.4 files, formatted to 8241 individual 2000 foot x 2000 foot tiles, as tiled Intensity Imagery, and as tiled bare earth DEMs; all tiled to the same 2000 foot x 2000 foot schema.
Grundy, Kendall, and DeKalb Counties, Illinois 2017 Lidar project called for the Planning, Acquisition, processing and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.7 meter. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.2; Quality Level 2. The data was developed based on a horizontal projection/datum of NAD83 (2011), State Plane Coordinate System Illinois East (FIPS 1201), US Survey Feet and vertical datum of NAVD88 (GEOID12B), US Survey Feet. Lidar data was delivered as flightline-extent unclassified LAS swaths, as processed Classified LAS 1.4 files, formatted to 10097 individual 2000 foot x 2000 foot tiles, as tiled Intensity Imagery, and as tiled bare earth DEMs; all tiled to the same 2000 foot x 2000 foot schema.
Ground Conditions:
Lidar was collected in November 2017. Due to an isolated anomaly found in the the lidar data in LaSalle County one re-flight was flown in April 2018, while no snow was on the ground and rivers were at or below normal levels. A Low Confidence polygon was use to circumscribe an area where lidar was reflected by particulates in smoke stack emission. Photons were unable to penetrate through the emissions for collection of ground surface within the polygon. The emission cloud obscures approximately 3.72 acres of ground surface. Tiles in which the emission cloud occurred are 99101727 and 99301727. In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, GRW Aerial Surveys, Inc. established a total of 53 ground control points of which 50 were used to calibrate the lidar to known ground locations established throughout the LaSalle and Expansion Counties project areas. An additional 157 independent accuracy checkpoints, 89 in Bare Earth and Urban landcovers (89 NVA points), 68 in tall Grass/tall weeds/crops, Brush lands/short trees, Forested categories (68 VVA points), were used to assess the vertical accuracy of the data of the entire project area. These checkpoints were not used to calibrate or post process the data.
This metadata record supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV is leveraging the Entwine Point Tiles (EPT) hosted by USGS on Amazon Web Services.
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):
Lineage Statement:
The NOAA Office for Coastal Management (OCM) ingested references to the USGS Entwine Point Tile (EPT) files hosted on Amazon Web Services (AWS) into the Digital Coast Data Access Viewer (DAV). The DAV accesses the point cloud as it resides on AWS under the usgs-lidar-public-container.
Process Steps:
- 2018-06-04 00:00:00 - LAS Point Classification QL2+: The point classification was performed as described below. Classification Filters were applied to aid in the definition of; terrain characteristics, vegetation attribution of low, medium or high and building rooftops. Filtering processes address aspects of the data such as: ground points, noise points, air points, low points, Low vegetation 0.5-5’, medium vegetation 5-20’, high vegetation >20’, building roof tops, withheld and overlap points. The Classified point cloud data was manually reviewed to ensure correct classification of; ground (ASPRS class 2), building rooftops (ASPRS class 6). After the bare earth surface was finalized, it is then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS class 2) lidar data inside of the Inland Ponds and Lakes, and Inland Streams and Rivers classified to water (ASPRS class 9). A buffer of 2.5 was used around each hydro-flattened feature to classify ground (ASPRS class 2) to ignored ground (ASPRS class 10). Island features were checked to ensure that Ground point (ASPRS class 2) remained classified as Ground. Ground points (ASPRS class 2) within 2.5 feet of bridge breaklines, used to reduce triangulation between bridge decks were also classified to Ignored ground (ASPRS class 10). All bridge decks were classified to Bridge deck (ASPRS class 17). All remaining points were filtered, or manually classified to their respective point classification; processed (ASPRS class 1), low vegetation (ASPRS class 3), medium vegetation (ASPRS class 4), high vegetation (ASPRS class 5), buildings (ASPRS class 6), low noise (ASPRS class 7), high noise (ASPRS class 18). TerraScan version 28.06.2017 was used to verify point density, identify withheld and overlap flag bit set flags for the LAS data. LAStools by rapidlasso GmbH, open source las2las version 160119 was used for writing the well known text into the LAS header. Lasinfo was used to verify format and header information.
- Original point clouds in LAS/LAZ format were restructured as Entwine Point Tiles and stored on Amazon Web Services. The data were re-projected horizontally to WGS84 web mercator (EPSG 3857) and no changes were made to the vertical elevations in NAVD88 (GEOID12B).
- 2023-08-14 00:00:00 - The NOAA Office for Coastal Management (OCM) created references to the Entwine Point Tile (EPT) files that were ingested into the NOAA Digital Coast Data Access Viewer (DAV). No changes were made to the data. The DAV will access the point cloud as it resides on Amazon Web Services (AWS) under the usgs-lidar-public container. These are the AWS URLs being accessed: https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_IL_LaSalle_B1_2017_LAS_2019/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_IL_LaSalle_B2_2017_LAS_2019/ept.json
(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://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_IL_LaSalle_B1_2017_LAS_2019/laz/
https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_IL_LaSalle_B2_2017_LAS_2019/laz/
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Data is available online for bulk and 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.