Data Management Plan
GUID: gov.noaa.nmfs.inport:70437 | 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
WI_8County_Chippewa (Work Unit 191373)
The Chippewa County lidar project area covers approximately 1084 square miles which includes a 100 meter buffer around the county boundary. The lidar data was acquired at a nominal point spacing (NPS) of 0.7 meters and a single swath nominal point density (NPD) of 2.0. Project specifications are based on Chippewa County requirements and on the U.S. Geological Survey National Geospatial Program LiDAR Base Specification, Version 2.1. The data was developed based on a horizontal projection/datum of NAD83(2011) / WISCRS Chippewa (ftUS) (EPSG Code: 7595), and vertical datum of NAVD88 - Geoid12B (Feet). LiDAR data was acquired using two Riegl LMS 1560 sensors with serial numbers SN754 and SN1264 from April 30, 2020 to May 7, 2020 in 4 total lifts. Acquisition occurred with leaves absent from deciduous trees, when no snow was present on the ground, and with rivers at or below normal levels.
WI_8County_Columbia (Work Unit 219073)
The Columbia County lidar project area covers approximately 836 square miles which includes a 100 meter buffer around the county boundary. The lidar data was acquired at a nominal point spacing (NPS) of 0.907 meters and an aggregate nominal point density (ANPD) of 2.0. Project specifications are based on Columbia County requirements and on the U.S. Geological Survey National Geospatial Program LiDAR Base Specification, Version 2.1. The data was developed based on a horizontal projection/datum of NAD83(2011) / WISCRS Columbia (ftUS) (EPSG Code: 7597), and vertical datum of NAVD88 - Geoid12B (Feet). LiDAR data was acquired using a Riegl LMS-Q1560 sensor with serial number SN1264 from April 11, 2020 to April 18, 2020 in 2 total lifts. Acquisition occurred with leaves absent from deciduous trees, when no snow was present on the ground, and with rivers at or below normal levels.
WI_8County_EauClaire (Work Unit 219076)
The Eau Claire County lidar project area covers approximately 674 square miles which includes a 100 meter buffer around the county boundary. The lidar data was acquired at a nominal point spacing (NPS) of 0.7 meters and an aggregate nominal point density (ANPD) of 2.0. Project specifications are based on Eau Claire County requirements and on the U.S. Geological Survey National Geospatial Program LiDAR Base Specification, Version 2.1. The data was developed based on a horizontal projection/datum of NAD83(2011) / WISCRS Eau Claire (ftUS) (EPSG Code: 7604), and vertical datum of NAVD88 - Geoid12B (Feet). LiDAR data was acquired using two Riegl LMS-Q1560 LiDAR sensors with serial numbers SN754 and SN1264 from April 30, 2020 to May 7, 2020 in 4 total lifts. Acquisition occurred with leaves absent from deciduous trees, when no snow was present on the ground, and with rivers at or below normal levels.
WI_8County_Grant (Work Unit 219079)
The Grant County lidar project area covers approximately 1250 square miles which includes a 100 meter buffer around the county boundary. The lidar data was acquired at a nominal point spacing (NPS) of 0.7 meters and a aggregate nominal point density (ANPD) of 2.0. Project specifications are based on Grant County requirements and on the U.S. Geological Survey National Geospatial Program LiDAR Base Specification, Version 2.1. The data was developed based on a horizontal projection/datum of NAD83(2011) / WISCRS Grant (ftUS) (EPSG Code: 7607), and vertical datum of NAVD88 - Geoid12B (Feet). LiDAR data was acquired using two Riegl VQ 1560 sensors with serial numbers SN754 and SN1264 from April 19, 2020 to April 30, 2020 in 5 total lifts. Acquisition occurred with leaves absent from deciduous trees, when no snow was present on the ground, and with rivers at or below normal levels.
WI_8County_Menominee (Work Unit 219082)
The Menominee County lidar project area covers approximately 399 square miles which includes a 100 meter buffer around the county boundary. The lidar data was acquired at a nominal point spacing (NPS) of 0.6 meters and a nominal point density (ANPD) of 2.0. Project specifications are based on Menominee County requirements and on the U.S. Geological Survey National Geospatial Program LiDAR Base Specification, Version 2.1. The data was developed based on a horizontal projection/datum of NAD83(2011) / WISCRS Menominee (ftUS) (EPSG Code: 7620), and vertical datum of NAVD88 - Geoid12B (Feet). LiDAR data was acquired using a Leica ALS80 with serial number SN8239 from April 25, 2020 to April 30, 2020 in 2 total lifts. Acquisition occurred with leaves absent from deciduous trees, when no snow was present on the ground, and with rivers at or below normal levels.
WI_8County_Rock (Work Unit 219085)
The Rock County lidar project area covers approximately 771 square miles which includes a 100 meter buffer around the county boundary. The lidar data was acquired at a nominal point spacing (NPS) of 0.7 meters and a aggregate nominal point density (ANPD) of 2.0. Project specifications are based on Rock County requirements and on the U.S. Geological Survey National Geospatial Program LiDAR Base Specification, Version 2.1. The data was developed based on a horizontal projection/datum of NAD83(2011) / WISCRS Rock (ftUS) (EPSG Code: 7629), and vertical datum of NAVD88 - Geoid12B (Feet). LiDAR data was acquired using a Riegl VQ 1560i sensor with serial number 4040 from April 16, 2020 to April 26, 2020 in 5 total lifts. Acquisition occurred with leaves absent from deciduous trees, when no snow was present on the ground, and with rivers at or below normal levels.
WI_8County_Sauk (Work Unit 219088)
The Sauk County lidar project area covers approximately 906 square miles which includes a 100 meter buffer around the county boundary. The lidar data was acquired at a nominal point spacing (NPS) of 0.907 meters and an aggregate nominal point density (ANPD) of 2.0. Project specifications are based on Sauk County requirements and on the U.S. Geological Survey National Geospatial Program LiDAR Base Specification, Version 2.1. The data was developed based on a horizontal projection/datum of NAD83(2011) / WISCRS Sauk (ftUS) (EPSG Code: 7631), and vertical datum of NAVD88 - Geoid12B (Feet). LiDAR data was acquired using a Riegl LMS-Q1560 sensor with serial number SN1264 from April 11, 2020 to April 21, 2020 in 3 total lifts. Acquisition occurred with leaves absent from deciduous trees, when no snow was present on the ground, and with rivers at or below normal levels.
WI_8County_Vernon (Work Unit 219091)
The Vernon County lidar project area covers approximately 874 square miles which includes a 100 meter buffer around the county boundary. The lidar data was acquired at a nominal point spacing (NPS) of 0.7 meters and a single swath nominal point density (NPD) of 2.0. Project specifications are based on Vernon County requirements and on the U.S. Geological Survey National Geospatial Program LiDAR Base Specification, Version 2.1. The data was developed based on a horizontal projection/datum of NAD83(2011) / WISCRS Vernon (ftUS) (EPSG Code: 7637), and vertical datum of NAVD88 - Geoid12B (Feet). LiDAR data was acquired using a Riegl VQ 1560i sensor serial number SN4040 from April 18, 2020 to April 21, 2020 in 3 total lifts. Acquisition occurred with leaves absent from deciduous trees, when no snow was present on the ground, and with rivers at or below normal levels.
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.
WI_8County_Chippewa (Work Unit 191373)
W: -89.8, E: -88.99, N: 43.66, S: 43.27WI_8County_Columbia (Work Unit 219073)
W: -91.67, E: -90.9, N: 44.87, S: 44.58WI_8County_EauClaire (Work Unit 219076)
W: -91.17, E: -90.41, N: 43.22, S: 42.5WI_8County_Grant (Work Unit 219079)
W: -89, E: -88.47, N: 45.13, S: 44.84WI_8County_Menominee (Work Unit 219082)
W: -89.39, E: -88.76, N: 42.86, S: 42.48Wi_8County_Rock (Work Unit 219085)
W: -90.33, E: -89.58, N: 43.65, S: 43.13WI_8County_Sauk (Work Unit 219088)
W: -91.28, E: -90.29, N: 43.74, S: 43.41WI_8County_Vernon (Work Unit 219091)
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:
- 2020-06-24 00:00:00 - The boresight for each lift was done individually as the solution may change slightly from lift to lift. The following steps describe the Raw Data Processing and Boresight process: 1) Technicians processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source data for boresight. 2) Technicians first used RIEGL RiPROCESS software to calculate initial boresight adjustment angles based on sample areas selected in the lift. These areas cover calibration flight lines collected in the lift, cross tie and production flight lines. These areas are well distributed in the lift coverage and cover multiple terrain types that are necessary for boresight angle calculation. The technician then analyzed the results and made any necessary additional adjustment until it is acceptable for the selected areas. 3) Once the boresight angle calculation was completed for the selected areas, the adjusted settings were applied to all of the flight lines of the lift and checked for consistency. The technicians utilized commercial and proprietary software packages to analyze how well flight line overlaps match for the entire lift and adjusted as necessary until the results met the project specifications. 4) Once all lifts were completed with individual boresight adjustment, the technicians checked and corrected the vertical misalignment of all flight lines and also the matching between data and ground truth. The relative accuracy was less than or equal to 7 cm RMSEz within individual swaths and less than or equal to 10 cm RMSEz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification 2.1, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening.
- 2020-06-24 00:00:00 - LAS Point Cloud Classification: LiDAR data processing for the point cloud deliverable consists of classifying the LiDAR using a combination of automated classification and manual edit/reclassification processes. On most projects the automated classification routines will correctly classify 90-95 percent of the LiDAR points. The remaining 5-10 percent of the bare earth ground class must undergo manual edit and reclassification. Because the classified points serve as the foundation for the Terrain, DEM and breakline products, it is necessary for the QA/QC supervisor to review the completed point cloud deliverables prior to the production of any additional products. The following workflow steps are followed for automated LiDAR classification: 1. Lead technicians review the group of LiDAR tiles to determine which automated classification routines will achieve the best results. Factors such as vegetation density, cultural features, and terrain can affect the accuracy of the automated classification. The lead technicians have the ability to edit or tailor specific routines in order to accommodate the factors mentioned above, and achieve the best results and address errors. 2. Distributive processing is used to maximize the available hardware resources and speed up the automated processing as this is a resource-intensive process. 3. Once the results of the automated classification have been reviewed and passed consistent checks, the supervisor then approves the data tiles for manual classification. The following workflow steps are followed for manual edits of the LiDAR bare earth ground classification: 1. LiDAR technicians review each tile for errors made by the automated routines and correctly address errors any points that are in the wrong classification. By methodically panning through each tile, the technicians view the LiDAR points in profile, with a TIN surface, and as a point cloud. 2. Any ancillary data available, such as Google Earth, is used to identify any features that may not be identifiable as points so that the technician can make the determination to which classification the feature belongs. The QA/QC processes for the LiDAR processing phase consist of: 1. The lead technician reviews all automated classification results and adjust the macros as necessary to achieve the optimal efficiency. This is an iterative process, and the technician may need to make several adjustments to the macros, depending upon the complexity of the features in the area being processed. During the manual editing process, the LiDAR technicians use a system of QA, whereby they check each other’s edits. This results in several benefits to the process: There is a greater chance of catching minor blunders It increases communication between technicians on technique and appearance Solutions to problems are communicated efficiently To ensure consistency across the project area, the supervisor reviews the data once the manual editing is complete. For this phase of a project, the following specifications are checked against: • Point cloud – all points must be classified according to the USGS classification standard for LAS. The all-return point cloud must be delivered in fully-compliant LAS version 1.4. • LAS files will use the Spatial Reference Framework according to project specification and all files shall be projected and defined. • General Point classifications: Class 1. Processed, but unclassified Class 2. Bare Earth Class 5. High Vegetation Class 6. Building Class 7. Noise Class 9. Water Class 17. Bridge Decks Class 18. High Noise Class 20. Ignored ground (Breakline proximity) • Outliers, noise, blunders, duplicates, geometrically unreliable points near the extreme edge of the swath, and other points deemed unusable are to be identified using the "Withheld" flag. This applies primarily to points which are identified during pre-processing or through automated post-processing r
- 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-09 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/WI_8County_Chippewa_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_8County_Columbia_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_8County_EauClaire_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_8County_Grant_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_8County_Menominee_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_8County_Rock_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_8County_Sauk_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_8County_Vernon_2020/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/WI_8County_2020_A20/
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.