2019 WROC Lidar: WI Counties (Adams, Jefferson, Lafayette, Monroe, Pepin)
Data Set (DS) | OCM Partners (OCMP)GUID: gov.noaa.nmfs.inport:70629 | Updated: July 31, 2024 | Published / External
Summary
Short Citation
OCM Partners, 2024: 2019 WROC Lidar: WI Counties (Adams, Jefferson, Lafayette, Monroe, Pepin), https://www.fisheries.noaa.gov/inport/item/70629.
Full Citation Examples
WI_Adams_2019 (Work Unit 177786)
The Adams County lidar project area covers approximately 696 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 Adams County requirements and on the U.S. Geological Survey National Geospatial Program LiDAR Base Specification, Version 1.3. The data was developed based on a horizontal projection/datum of NAD83(2011) / Adams County (ftUS) (EPSG Code: 7587), and vertical datum of NAVD88 - Geoid12B (Feet). LiDAR data was acquired using the Leica ALS 80 LiDAR sensor serial number SN 8146 from April 21, 2019 to April 23, 2019 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_Jefferson_2019 (Work Unit 173957)
The Jefferson County lidar project area covers approximately 589 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 Jefferson County requirements and on the U.S. Geological Survey National Geospatial Program LiDAR Base Specification, Version 1.3. The data was developed based on a horizontal projection/datum of NAD83(2011) / Wisconsin State Plane, South Zone (ftUS) (EPSG Code: 6609), and vertical datum of NAVD88 - Geoid12B (Feet). LiDAR data was acquired using two Riegl VQ 1560i sensors with serial numbers SN546 and SN061 from April 20, 2019 to April 21, 2019 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_Lafayette_2019 (Work Unit 177783)
The Lafayette County lidar project area covers approximately 641 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 Lafayette County requirements and on the U.S. Geological Survey National Geospatial Program LiDAR Base Specification, Version 1.3. The data was developed based on a horizontal projection/datum of NAD83(2011) / Lafayette County (ftUS) (EPSG Code: 7608), and vertical datum of NAVD88 - Geoid12B (Feet). LiDAR data was acquired using the Riegl VQ 1560i SN061 Sensor on April 8, 2019 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_Monroe_2019 (Work Unit 177789)
The Monroe County lidar project area covers approximately 916 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 Monroe County requirements and on the U.S. Geological Survey National Geospatial Program LiDAR Base Specification, Version 1.3. The data was developed based on a horizontal projection/datum of NAD83(2011) / Monroe County (ftUS) (EPSG Code: 7621), and vertical datum of NAVD88 - Geoid12B (Feet). LiDAR data was acquired using the Riegl VQ 1560i SN061 Sensor from April 9, 2019 through April 28, 2019 in three 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_Pepin_2019 (Work Unit 177780)
The Pepin County lidar project area covers approximately 255 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 Pepin County requirements and on the U.S. Geological Survey National Geospatial Program LiDAR Base Specification, Version 1.3. The data was developed based on a horizontal projection/datum of NAD83(2011) / Pepin County (ftUS) (EPSG Code: 7624), and vertical datum of NAVD88 - Geoid12B (Feet). LiDAR data was acquired using the Riegl VQ 1560i SN061 Sensor on May 4, 2019 in 1 total lift. 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.
Distribution Information
-
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options.
-
LAS/LAZ - LASer
Bulk download of data files in LAZ format, WISCRS NAD83(2011), US survey feet coordinates and NAVD88 (Geoid12B) elevations in feet.
None
Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations. Acknowledgement of the U.S. Geological Survey would be appreciated for products derived from these data.
Controlled Theme Keywords
elevation, TERRAIN ELEVATION
Child Items
No Child Items for this record.
Contact Information
Point of Contact
NOAA Office for Coastal Management (NOAA/OCM)
coastal.info@noaa.gov
(843) 740-1202
https://coast.noaa.gov
Metadata Contact
NOAA Office for Coastal Management (NOAA/OCM)
coastal.info@noaa.gov
(843) 740-1202
https://coast.noaa.gov
Extents
-90.030164° W,
-89.593469° E,
44.250431° N,
43.639605° S
WI_Adams_2019 (Work Unit 177786)
2019-04-21
Date of collection for WI_Adams_2019 (Work Unit 177786)
2019-04-23
Date of collection for WI_Adams_2019 (Work Unit 177786)
Item Identification
Title: | 2019 WROC Lidar: WI Counties (Adams, Jefferson, Lafayette, Monroe, Pepin) |
---|---|
Short Name: | wi2019_counties_m9885_metadata |
Status: | Completed |
Creation Date: | 2019 |
Publication Date: | 2020-04-21 |
Abstract: |
WI_Adams_2019 (Work Unit 177786) The Adams County lidar project area covers approximately 696 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 Adams County requirements and on the U.S. Geological Survey National Geospatial Program LiDAR Base Specification, Version 1.3. The data was developed based on a horizontal projection/datum of NAD83(2011) / Adams County (ftUS) (EPSG Code: 7587), and vertical datum of NAVD88 - Geoid12B (Feet). LiDAR data was acquired using the Leica ALS 80 LiDAR sensor serial number SN 8146 from April 21, 2019 to April 23, 2019 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_Jefferson_2019 (Work Unit 173957) The Jefferson County lidar project area covers approximately 589 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 Jefferson County requirements and on the U.S. Geological Survey National Geospatial Program LiDAR Base Specification, Version 1.3. The data was developed based on a horizontal projection/datum of NAD83(2011) / Wisconsin State Plane, South Zone (ftUS) (EPSG Code: 6609), and vertical datum of NAVD88 - Geoid12B (Feet). LiDAR data was acquired using two Riegl VQ 1560i sensors with serial numbers SN546 and SN061 from April 20, 2019 to April 21, 2019 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_Lafayette_2019 (Work Unit 177783) The Lafayette County lidar project area covers approximately 641 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 Lafayette County requirements and on the U.S. Geological Survey National Geospatial Program LiDAR Base Specification, Version 1.3. The data was developed based on a horizontal projection/datum of NAD83(2011) / Lafayette County (ftUS) (EPSG Code: 7608), and vertical datum of NAVD88 - Geoid12B (Feet). LiDAR data was acquired using the Riegl VQ 1560i SN061 Sensor on April 8, 2019 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_Monroe_2019 (Work Unit 177789) The Monroe County lidar project area covers approximately 916 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 Monroe County requirements and on the U.S. Geological Survey National Geospatial Program LiDAR Base Specification, Version 1.3. The data was developed based on a horizontal projection/datum of NAD83(2011) / Monroe County (ftUS) (EPSG Code: 7621), and vertical datum of NAVD88 - Geoid12B (Feet). LiDAR data was acquired using the Riegl VQ 1560i SN061 Sensor from April 9, 2019 through April 28, 2019 in three 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_Pepin_2019 (Work Unit 177780) The Pepin County lidar project area covers approximately 255 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 Pepin County requirements and on the U.S. Geological Survey National Geospatial Program LiDAR Base Specification, Version 1.3. The data was developed based on a horizontal projection/datum of NAD83(2011) / Pepin County (ftUS) (EPSG Code: 7624), and vertical datum of NAVD88 - Geoid12B (Feet). LiDAR data was acquired using the Riegl VQ 1560i SN061 Sensor on May 4, 2019 in 1 total lift. 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. |
Purpose: |
This data, along with its derivatives, is the result of a countywide elevation mapping with cooperative partnerships from Adams, Jefferson, Lafayette, Monroe, and Pepin counties, Wisconsin DOA, and the USGS 3DEP program. This data was produced from lidar data collected in April and May 2019, which was processed and delivered in 2020. |
Supplemental Information: |
The following are the USGS lidar fields in JSON: {
"ldrinfo" : {
"ldrspec" : "National Geospatial Program (NGP) Lidar Base Specification v1.3", "ldrsens" : "Leica ALS 80_SN 8146", "ldrmaxnr" : "4", "ldrnps" : "0.71", "ldrdens" : "2.0", "ldranps" : "0.71", "ldradens" : "2.0", "ldrfltht" : "2346", "ldrfltsp" : "160", "ldrscana" : "40", "ldrscanr" : "49", "ldrpulsr" : "381", "ldrpulsd" : "4", "ldrpulsw" : "0.48", "ldrwavel" : "1020", "ldrmpia" : "1", "ldrbmdiv" : "0.22", "ldrswatw" : "1560", "ldrswato" : "30", "ldrgeoid" : "National Geodetic Survey (NGS) Geoid12B" }, "ldrinfo" : {
"ldrspec" : "USGS-NGP Base Lidar Specification v1.3", "ldrsens" : "Leica ALS 80_SN 8146", "ldrmaxnr" : "UNKNOWN", "ldrnps" : "0.71", "ldrdens" : "2.0", "ldranps" : "0.71", "ldradens" : "2.0", "ldrfltht" : "2346", "ldrfltsp" : "160", "ldrscana" : "40", "ldrscanr" : "49", "ldrpulsr" : "381", "ldrpulsd" : "4", "ldrpulsw" : "0.48", "ldrwavel" : "1020", "ldrmpia" : "1", "ldrbmdiv" : "0.22", "ldrswatw" : "1560", "ldrswato" : "30", "ldrgeoid" : "National Geodetic Survey (NGS) Geoid12B" }, "ldraccur" : {
"ldrchacc" : "Not Calculated", "rawnva" : "0", "rawnvan" : "0", "clsnva" : "0", "clsnvan" : "0" }, "lasinfo" : {
"lasver" : "1.4", "lasprf" : "6", "laswheld" : "Withheld (ignore) points were identified in these files using the standard LAS Withheld bit.", "lasolap" : "Swath "overage" points were identified in these files using the standard LAS overlap bit.", "lasintr" : "11", "lasclass" : {
"clascode" : "1", "clasitem" : "Processed, but Unclassified" }, "lasclass" : {
"clascode" : "2", "clasitem" : "Bare Earth Ground" }, "lasclass" : {
"clascode" : "5", "clasitem" : "High Vegetation" }, "lasclass" : {
"clascode" : "6", "clasitem" : "Buildings" }, "lasclass" : {
"clascode" : "7", "clasitem" : "Low Noise" }, "lasclass" : {
"clascode" : "9", "clasitem" : "Water" }, "lasclass" : {
"clascode" : "17", "clasitem" : "Bridge Deck" }, "lasclass" : {
"clascode" : "18", "clasitem" : "High Noise" }, "lasclass" : {
"clascode" : "20", "clasitem" : "Ignored Ground" } }} |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Science Keywords |
EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION
|
ISO 19115 Topic Category |
elevation
|
Spatial Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Location Keywords |
CONTINENT
|
Global Change Master Directory (GCMD) Location Keywords |
CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA
|
Global Change Master Directory (GCMD) Location Keywords |
CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > WISCONSIN
|
Global Change Master Directory (GCMD) Location Keywords |
VERTICAL LOCATION > LAND SURFACE
|
Instrument Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Instrument Keywords |
LIDAR > Light Detection and Ranging
|
Platform Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Platform Keywords |
Airplane > Airplane
|
Physical Location
Organization: | Office for Coastal Management |
---|---|
City: | Charleston |
State/Province: | SC |
Data Set Information
Data Set Scope Code: | Data Set |
---|---|
Data Set Type: | Elevation |
Maintenance Frequency: | None Planned |
Data Presentation Form: | Model (digital) |
Distribution Liability: |
Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners, |
Data Set Credit: | Ayres Associates, WROC (Wisconsin Regional Orthoimagery Consortium), USGS |
Support Roles
Data Steward
Date Effective From: | 2023 |
---|---|
Date Effective To: | |
Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address: | coastal.info@noaa.gov |
Phone: | (843) 740-1202 |
URL: | https://coast.noaa.gov |
Distributor
Date Effective From: | 2023 |
---|---|
Date Effective To: | |
Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address: | coastal.info@noaa.gov |
Phone: | (843) 740-1202 |
URL: | https://coast.noaa.gov |
Distributor
Date Effective From: | 2020 |
---|---|
Date Effective To: | |
Contact (Organization): | U.S. Geological Survey |
Address: |
12201 Sunrise Valley Drive Reston, VA 20191 USA |
URL: | USGS Home |
Metadata Contact
Date Effective From: | 2023 |
---|---|
Date Effective To: | |
Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address: | coastal.info@noaa.gov |
Phone: | (843) 740-1202 |
URL: | https://coast.noaa.gov |
Point of Contact
Date Effective From: | 2023 |
---|---|
Date Effective To: | |
Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address: | coastal.info@noaa.gov |
Phone: | (843) 740-1202 |
URL: | https://coast.noaa.gov |
Extents
Currentness Reference: | Ground Condition |
---|
Extent Group 1
Extent Group 1 / Geographic Area 1
W° Bound: | -90.030164 | |
---|---|---|
E° Bound: | -89.593469 | |
N° Bound: | 44.250431 | |
S° Bound: | 43.639605 | |
Description |
WI_Adams_2019 (Work Unit 177786) |
Extent Group 1 / Time Frame 1
Time Frame Type: | Discrete |
---|---|
Start: | 2019-04-21 |
Description: |
Date of collection for WI_Adams_2019 (Work Unit 177786) |
Extent Group 1 / Time Frame 2
Time Frame Type: | Discrete |
---|---|
Start: | 2019-04-23 |
Description: |
Date of collection for WI_Adams_2019 (Work Unit 177786) |
Extent Group 2
Extent Group 2 / Geographic Area 1
W° Bound: | -90.98 | |
---|---|---|
E° Bound: | -90.3 | |
N° Bound: | 44.16 | |
S° Bound: | 43.72 | |
Description |
WI_Monroe_2019 (Work Unit 177789) |
Extent Group 2 / Time Frame 1
Time Frame Type: | Discrete |
---|---|
Start: | 2019-04-09 |
Description: |
Date of collection for WI_Monroe_2019 (Work Unit 177789) |
Extent Group 2 / Time Frame 2
Time Frame Type: | Discrete |
---|---|
Start: | 2019-04-19 |
Description: |
Date of collection for WI_Monroe_2019 (Work Unit 177789) |
Extent Group 2 / Time Frame 3
Time Frame Type: | Discrete |
---|---|
Start: | 2019-04-28 |
Description: |
Date of collection for WI_Monroe_2019 (Work Unit 177789) |
Extent Group 3
Extent Group 3 / Geographic Area 1
W° Bound: | -92.32 | |
---|---|---|
E° Bound: | -91.65 | |
N° Bound: | 44.69 | |
S° Bound: | 44.4 | |
Description |
WI_Pepin_2019 (Work Unit 177780) |
Extent Group 3 / Time Frame 1
Time Frame Type: | Discrete |
---|---|
Start: | 2019-05-04 |
Description: |
Date of collection for WI_Pepin_2019 (Work Unit 177780) |
Extent Group 4
Extent Group 4 / Geographic Area 1
W° Bound: | -90.43 | |
---|---|---|
E° Bound: | -89.84 | |
N° Bound: | 42.82 | |
S° Bound: | 42.5 | |
Description |
WI_Lafayette_2019 (Work Unit 177783) |
Extent Group 4 / Time Frame 1
Time Frame Type: | Discrete |
---|---|
Start: | 2019-04-08 |
Description: |
Date of collection for WI_Lafayette_2019 (Work Unit 177783) |
Extent Group 5
Extent Group 5 / Geographic Area 1
W° Bound: | -89.02 | |
---|---|---|
E° Bound: | -88.53 | |
N° Bound: | 43.2 | |
S° Bound: | 42.84 | |
Description |
WI_Jefferson_2019 (Work Unit 173957) |
Extent Group 5 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2019-04-20 |
End: | 2019-04-21 |
Description: |
Dates of collection for WI_Jefferson_2019 (Work Unit 173957) |
Spatial Information
Spatial Representation
Representations Used
Grid: | No |
---|---|
Vector: | Yes |
Text / Table: | No |
TIN: | No |
Stereo Model: | No |
Video: | No |
Reference Systems
Reference System 1
Coordinate Reference System |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Reference System 2
Coordinate Reference System |
|||||||||||||||||||||||
|
Access Information
Security Class: | Unclassified |
---|---|
Data Access Procedure: |
Data is available online for bulk and custom downloads. |
Data Access Constraints: |
None |
Data Use Constraints: |
Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations. Acknowledgement of the U.S. Geological Survey would be appreciated for products derived from these data. |
Distribution Information
Distribution 1
Start Date: | 2023-08-24 |
---|---|
End Date: | Present |
Download URL: | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9885/details/9885 |
Distributor: | NOAA Office for Coastal Management (NOAA/OCM) (2023 - Present) |
File Name: | Customized Download |
Description: |
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options. |
File Type (Deprecated): | Zip |
Compression: | Zip |
Distribution 2
Start Date: | 2020 |
---|---|
End Date: | Present |
Download URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/WI_Statewide_2019_A19/ |
Distributor: | U.S. Geological Survey (2020 - Present) |
File Name: | Bulk Download |
Description: |
Bulk download of data files in LAZ format, WISCRS NAD83(2011), US survey feet coordinates and NAVD88 (Geoid12B) elevations in feet. |
File Type (Deprecated): | LAZ |
Distribution Format: | LAS/LAZ - LASer |
URLs
URL 1
URL: | https://coast.noaa.gov/dataviewer/ |
---|---|
Name: | NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) |
URL Type: |
Online Resource
|
File Resource Format: | HTML |
Description: |
The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer. |
URL 2
URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/WI_Statewide_2019_A19/WI_Statewide_2019_A19_WP_Report.pdf |
---|---|
Name: | USGS Project Report |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the USGS Project Report that provides information about the project, vertical accuracy results, the point classes and sensors used. |
URL 3
URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/WI_Statewide_2019_A19/ |
---|---|
Name: | USGS Additional Info |
URL Type: |
Online Resource
|
Description: |
Link to the reports, breaklines, metadata, and spatial metadata. |
URL 4
URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/WI_Statewide_2019_A19/WI_Adams_2019/reports/Adams%20County%20Collection%20Report.pdf |
---|---|
Name: | Lidar Report - WI_Adams_2019 |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the Ayres lidar report for WI_Adams_2019 |
URL 5
URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/WI_Statewide_2019_A19/WI_Jefferson_2019/reports/Jefferson%20County%20Collection%20Report.pdf |
---|---|
Name: | Lidar Report - WI_Jefferson_2019 |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the Ayres lidar report for WI_Jefferson_2019 |
URL 6
URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/WI_Statewide_2019_A19/WI_Lafayette_2019/reports/Lafayette%20County%20Collection%20Report.pdf |
---|---|
Name: | Lidar Report - WI_Lafayette_2019 |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the Ayres lidar report for WI_Lafayette_2019 |
URL 7
URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/WI_Statewide_2019_A19/WI_Monroe_2019/reports/Monroe%20County%20Collection%20Report.pdf |
---|---|
Name: | Lidar Report - WI_Monroe_2019 |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the Ayres lidar report for WI_Monroe_2019 |
URL 8
URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/WI_Statewide_2019_A19/WI_Pepin_2019/reports/Pepin%20County%20Collection%20Report.pdf |
---|---|
Name: | Lidar Report - WI_Pepin_2019 |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the Ayres lidar report for WI_Pepin_2019 |
URL 9
URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_Adams_2019/ept.json |
---|---|
Name: | USGS Entwine Point Tile (EPT) - WI_Adams_2019 |
URL Type: |
Online Resource
|
File Resource Format: | json |
Description: |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
URL 10
URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_Jefferson_2019/ept.json |
---|---|
Name: | USGS Entwine Point Tile (EPT) - WI_Jefferson_2019 |
URL Type: |
Online Resource
|
File Resource Format: | json |
Description: |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
URL 11
URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_Lafayette_2019/ept.json |
---|---|
Name: | USGS Entwine Point Tile (EPT) - WI_Lafayette_2019 |
URL Type: |
Online Resource
|
File Resource Format: | json |
Description: |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
URL 12
URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_Monroe_2019/ept.json |
---|---|
Name: | USGS Entwine Point Tile (EPT) - WI_Monroe_2019 |
URL Type: |
Online Resource
|
File Resource Format: | json |
Description: |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
URL 13
URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_Pepin_2019/ept.json |
---|---|
Name: | USGS Entwine Point Tile (EPT) - WI_Pepin_2019 |
URL Type: |
Online Resource
|
File Resource Format: | json |
Description: |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
URL 14
URL: | https://usgs.entwine.io/data/view.html?r=[%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_Adams_2019/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_Lafayette_2019/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_Jefferson_2019/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_Monroe_2019/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_Pepin_2019/ept.json%22] |
---|---|
Name: | USGS 3D View |
URL Type: |
Online Resource
|
Description: |
Link to view the point cloud, using the Entwine Point Tile (EPT) format, in the 3D Potree viewer. |
Technical Environment
Description: |
Terrasolid |
---|
Data Quality
Vertical Positional Accuracy: |
This data set was produced to meet ASPRS Positional Accuracy Standard for Digital Geospatial Data (2014) for a 10-cm RMSEz Vertical Accuracy Class. USGS Determined Vertical Accuracy: Non-Vegetated Vertical Accuracy (NVA) = 3.6 cm RMSE Vegetated Vertical Accuracy (VVA) = 14.55 cm at 95th Percentile |
---|---|
Completeness Report: |
These LAS data files include all data points collected. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The raw point cloud is complete and data passes Vertical Accuracy specifications. |
Conceptual Consistency: |
Data covers the entire area specified for this project. |
Data Management
Have Resources for Management of these Data Been Identified?: | Yes |
---|---|
Approximate Percentage of Budget for these Data Devoted to Data Management: | Unknown |
Do these Data Comply with the Data Access Directive?: | Yes |
Actual or Planned Long-Term Data Archive Location: | NCEI-CO |
How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive?: |
Data is backed up to tape and to cloud storage. |
Lineage
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. |
---|
Sources
USGS AWS Entwine Point Tile (EPT) - WI_Adams_2019
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_Adams_2019/ept.json |
Citation URL Name: | Entwine Point Tile for WI_Adams_2019 |
USGS AWS Entwine Point Tile (EPT) - WI_Jefferson_2019
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_Jefferson_2019/ept.json |
Citation URL Name: | Entwine Point Tile for WI_Jefferson_2019 |
USGS AWS Entwine Point Tile (EPT) - WI_Lafayette_2019
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_Lafayette_2019/ept.json |
Citation URL Name: | Entwine Point Tile for WI_Lafayette_2019 |
USGS AWS Entwine Point Tile (EPT) - WI_Monroe_2019
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_Monroe_2019/ept.json |
Citation URL Name: | Entwine Point Tile for WI_Monroe_2019 |
USGS AWS Entwine Point Tile (EPT) - WI_Pepin_2019
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_Pepin_2019/ept.json |
Citation URL Name: | Entwine Point Tile for WI_Pepin_2019 |
Process Steps
Process Step 1
Description: |
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 Leica LMS 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 1.3, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening. |
---|---|
Process Date/Time: | 2019-05-28 00:00:00 |
Process Step 2
Description: |
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 |
---|---|
Process Date/Time: | 2019-05-28 00:00:00 |
Process Step 3
Description: |
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). |
---|---|
Process Contact: | U.S. Geological Survey |
Process Step 4
Description: |
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 URLs being accessed: https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_Adams_2019/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_Jefferson_2019/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_Lafayette_2019/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_Monroe_2019/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_Pepin_2019/ept.json |
---|---|
Process Date/Time: | 2023-08-24 00:00:00 |
Process Contact: | Office for Coastal Management (OCM) |
Catalog Details
Catalog Item ID: | 70629 |
---|---|
GUID: | gov.noaa.nmfs.inport:70629 |
Metadata Record Created By: | Rebecca Mataosky |
Metadata Record Created: | 2023-08-24 19:24+0000 |
Metadata Record Last Modified By: | Rebecca Mataosky |
Metadata Record Last Modified: | 2024-07-31 18:47+0000 |
Metadata Record Published: | 2023-08-25 |
Owner Org: | OCMP |
Metadata Publication Status: | Published Externally |
Do Not Publish?: | N |
Metadata Last Review Date: | 2023-08-25 |
Metadata Review Frequency: | 1 Year |
Metadata Next Review Date: | 2024-08-25 |