Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:72327 | 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 Description of Original Data:
These lidar data are processed Classified LAS 1.4 files, formatted to 1351 individual 4,500 ft x 4,500 ft tiles; used to create intensity images, 3D breaklines and hydro-flattened DEMs as necessary.
Geographic Extent: The AOI is covering approximately 907 square miles of Dodge County along with a 100-foot buffer zone outside the county for the lidar data.
Dataset Description of Original Data:
The WI Dodge County Lidar 2017 B17 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.70 meter. Project specifications were based on the U.S. Geological Survey National Geospatial Program Lidar Base Specification, Version 1.2. The data was developed based on a horizontal projection/datum of NAD 1983 2011 WISCRS Dodge and Jefferson Survey Feet and vertical datum of NAVD88 (GEOID12B), Survey Feet. Lidar data was delivered as; flightline-extent raw LAS v1.4 swaths, classified point cloud LAS v1.4 files formatted to 1351 individual 4,500 ft x 4,500 ft tiles in NAD 1983 2011 WISCRS Dodge and Jefferson Survey Feet. Derivatives were produced as tiled; Bare Earth Surface DEMs, Intensity Images; all tiled to the same 4,500 ft x 4,500 ft schema.
Ground Conditions: Lidar was collected in April of 2017, while no snow was on the ground and rivers were at or below normal levels. In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Woolpert established a total of 15 ground control points that were used to calibrate the lidar to known ground locations established throughout the project area. Additional independent accuracy checkpoints were collected (58 NVA points and 48 VVA points) and used to assess the vertical accuracy of the data. 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 Tiles (EPT) 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:
- 2017-04-12 00:00:00 - Classified LAS Processing: Classification Filters were applied to aid in the definition of terrain characteristics and to maintain ground. Filtering processes address aspects of the data such as; ground points, noise points, air points, low points, manmade features, vegetation, and overlap points. The Bare Earth surface was manually reviewed to ensure correct classification of Class 2 (Ground). Upon completion of bare earth review hydro-breaklines were generated through heads-up digitization. Ground (Class 2) Lidar points inside Inland Ponds and Lakes, and Inland Streams and Rivers were classified to Water (Class 9). A buffer of 2.3 feet was used around each hydro-flattened feature to classify Ground points (Class 2) to Ignored ground (Class 10). Island features were checked to ensure that Ground point (Class 2) remained classified as Ground. Ground points (Class 2) within 2.3 feet of breaklines, used to reduce triangulation between bridge decks were also classified to Ignored ground (Class 10). All bridge decks were classified to Bridge (Class 17). All remaining Points were filtered , or manually classified to their respective Point Classification; Processed (Class 1), Low Noise (Class 7), High Noise (Class 18) Overlap data was identified using the Overlap Flag, LAS 1.4 specifications. All data was manually reviewed and any remaining artifacts removed. The bare-earth (Class 2 - Ground) lidar points underwent a manual QA/QC step to verify the quality of the DEM as well as a peer-based QC review. This included a review of the DEM surface to remove artifacts and ensure topographic quality. Classification of water (class 9) and ignored ground (class 10) was completed via the use of the hydrologic breaklines collected for the hydro-flattening phase. Buildings (Class 6) was achieved via the used of digitized building footprints. The overlap classes were determined by first identifying the overlapping areas and reclassifying the LAS data by offset from a corridor. This allows the returns located on the edge of the swath to be removed from the bare earth coverage in an effort to produce a more uniform data density. The returns determined to be overlap including overlap default, ground, water, and ignored ground are then applied an overlap flag and reclassified to their respective standard classification value. The surveyed ground control points are used to make vertical adjustments to the data set and to perform the accuracy checks and statistical analysis of the lidar dataset. Supervisory QC monitoring of work in progress and completed editing ensured consistency of classification character and adherence to project requirements across the entire project area. The resulting deliverables for this task order consist of classified LAS file in LAS 1.4 format, DEM files in ERDAS IMG format and ArcGrid format, 8-bit gray scale Intensity files in GeoTIFF format, Hydrologic and Bridge abutment breakline data in ESRI geodatabase format.
- 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 the vertical units were converted to meters (NAVD88 Geoid12B).
- 2024-03-14 00:00:00 - The NOAA Office for Coastal Management (OCM) created references to the Entwine Point Tiles (EPT) 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. This is the AWS URL being accessed: https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_WI_DodgeCo_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_WI_DodgeCo_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 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.