2014 USGS Lidar: Schoharie County, NY
OCM Partners
Data Set
(DS)
| ID: 70223
| Published / External
Created: 2023-06-30
|
Last Modified: 2023-10-17
Project (PRJ) | ID: 49401
ID: 70223
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2014 USGS Lidar: Schoharie County, NY |
---|---|
Short Name | ny2014_schoharie_m9855_metadata |
* Status | Completed |
Creation Date | 2014 |
Revision Date | |
• Publication Date | 2015-05 |
* » Abstract |
The Atlantic Group collected aproximately 965 square miles in the New York. The data includes full coverage of Schoharie County, with partial coverage in the counties of Montgomery and Schenectady. The nominal pulse spacing for this project was no greater than 0.7 meters. Dewberry used proprietary procedures to classify the LAS and then performed manual classifications according to project specifications: 1-Unclassified, 2-Ground, 7-Noise, 9-Water, and 10-Ignored Ground due to breakline proximity. The LiDAR data were processed to a bare-earth digital terrain model (DTM). Detailed breaklines and bare-earth Digital Elevation Models (DEMs) were produced for the project area. Deliverables were produced in UTM coordinates. The data was formatted according to tiles with each UTM tile covering an area of 1,500 meters by 1,500 meters. A total of 1222 UTM tiles were produced for the project encompassing an area of approximately 965 sq. miles. This project includes the Watershed expansion area that encompasses approximately 328 square miles (528 tiles) of the project area. 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 |
The purpose of this LiDAR data was to produce high accuracy 3D elevation products, including tiled LiDAR in LAS 1.2 format, 3D breaklines, 1 meter cell size hydro flattened Digital Elevation Models (DEMs) for UTM. All products follow and comply with USGS Program Lidar Base Specification Version 1.0. |
Notes | |
Other Citation Details | |
• Supplemental Information |
A complete description of this dataset is available in the Final Project Report submitted to the U.S. Geological Survey. |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION |
ISO 19115 Topic Category | elevation |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* 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 > NEW YORK |
Global Change Master Directory (GCMD) Location Keywords | VERTICAL LOCATION > LAND SURFACE |
None | Montgomery County |
None | Schnectady County |
None | Schoharie County |
Stratum Keywords
Thesaurus | Keyword |
---|---|
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 |
• Country | |
• » Location Description |
Data Set Information
* Data Set Scope Code | Data Set |
---|---|
• Data Set Type | Elevation |
• Maintenance Frequency | As Needed |
Maintenance Note | |
» Data Presentation Form | Model (digital) |
• Entity Attribute Overview | |
Entity Attribute Detail Citation |
none |
Entity Attribute Detail URL | |
Distribution Liability |
This data was produced for the U.S. Geological Survey according to specific project requirements. This information is provided "as is". Further documentation of this data can be obtained by contacting: USGS, 1400 Independence Road, Rolla, MO 65401. Telephone (573) 308-3756. 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 | U.S. Geological Survey |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2023 |
Date Effective To | |
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 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Distributor |
---|---|
* » Date Effective From | 2023 |
Date Effective To | |
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 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Distributor |
---|---|
* » Date Effective From | 2014 |
Date Effective To | |
Organization | U.S. Geological Survey |
Address |
12201 Sunrise Valley Drive Reston, VA 20191 USA |
Email Address | |
Phone | |
Fax | |
Mobile | |
URL | https://usgs.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Metadata Contact |
---|---|
* » Date Effective From | 2023 |
Date Effective To | |
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 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Point of Contact |
---|---|
* » Date Effective From | 2023 |
Date Effective To | |
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 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
Extents
Currentness Reference | Ground Condition |
---|
Extent Group 1
Extent Description |
---|
Extent Group 1 / Geographic Area 1
* » W° Bound | -74.77 |
---|---|
* » E° Bound | -74.06 |
* » N° Bound | 43 |
* » S° Bound | 42.35 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2014-05-26 |
End | 2014-06-01 |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Spatial Information
Spatial Resolution
Angular Distance | |
---|---|
Angular Distance Units | |
Horizontal Distance | |
Horizontal Distance Units | |
Vertical Distance | |
Vertical Distance Units | |
Equivalent Scale Denominator | |
Level of Detail Description |
Spatial Representation
Grid Representation Used? | No |
---|---|
Vector Representation Used? | Yes |
Text / Table Representation Used? | No |
TIN Representation Used? | No |
Stereo Model Representation Used? | No |
Video Representation Used? | No |
Grid Representation
Dimension Count | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Cell Geometry | |||||||||||||
Transformation Parameter Available? | |||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
Vector Representation
Topology Level | |
---|---|
Complex Object Present? | |
Complex Object Count | |
Composite Object Present? | |
Composite Object Count | |
Curve Object Present? | |
Curve Object Count | |
Point Object Present? | |
Point Object Count | |
Solid Object Present? | |
Solid Object Count | |
Surface Object Present? | |
Surface Object Count |
Reference Systems
Reference System
EPSG Code | EPSG:3857 | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Reference System
EPSG Code | EPSG:5703 | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Reference System
EPSG Code | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Access Information
Data License | |
---|---|
Data License URL | |
Data License Statement | |
* » Security Class | Unclassified |
* Security Classification System | |
Security Handling Description | |
• Data Access Policy | |
» 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. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | 2023-06-30 |
---|---|
End Date | Present |
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9855/details/9855 |
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 Date/Time | |
File Type (Deprecated) | Zip |
Distribution Format | |
File Size | |
Application Version | |
Compression | Zip |
Review Status |
Start Date | 2023-06-30 |
---|---|
End Date | Present |
» Download URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/Schoharie_Creek_Watershed_Expansion_QL2_LiDAR/NY_Schoharie_2014/LAZ/ |
Distributor | U.S. Geological Survey (2014 - Present) |
File Name | Bulk Download |
Description |
Bulk download of data files in LAZ format, UTM Zone 18N NAD83(2011), meters coordinates and NAVD88 (Geoid12A) elevations in meters . |
File Date/Time | |
File Type (Deprecated) | LAZ |
Distribution Format | LAS/LAZ - LASer |
File Size | |
Application Version | |
Compression | Zip |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
URLs
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 | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/Schoharie_Creek_Watershed_Expansion_QL2_LiDAR/NY_Schoharie_2014/reports/Schoharie_LiDAR_Project_Report_USGS_20150707_FINAL.pdf |
---|---|
Name | Dewberry Lidar Report |
URL Type | Online Resource |
File Resource Format | |
Description |
Link to the Dewberry lidar report. |
URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/Schoharie_Creek_Watershed_Expansion_QL2_LiDAR/NY_Schoharie_2014/ |
---|---|
Name | USGS Additional Info |
URL Type | Online Resource |
File Resource Format | |
Description |
Link to the reports, breaklines, metadata, and spatial metadata. |
URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_NY_Schoharie_2014_LAS_2016/ept.json |
---|---|
Name | USGS Entwine Point Tile (EPT) |
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 | https://usgs.entwine.io/data/view.html?r=https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_NY_Schoharie_2014_LAS_2016/ept.json |
---|---|
Name | USGS 3D View |
URL Type | Online Resource |
File Resource Format | |
Description |
Link to view the point cloud, using the Entwine Point Tile (EPT) format, in the 3D Potree viewer. |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
Activity Log
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Issues
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Technical Environment
Description |
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 10.0 |
---|
Data Quality
Representativeness | |
---|---|
Accuracy | |
Analytical Accuracy | |
Horizontal Positional Accuracy |
Lidar source compiled to meet 1 meter horizontal accuracy. Project specifications required a horizontal accuracy of 1 m based on a RMSEr (0.578m) x 1.7308. Only checkpoints photo-identifiable in the intensity imagery can be used to test the horizontal accuracy of the LiDAR. Photo-identifiable checkpoints in intensity imagery typically include checkpoints located at the ends of paint stripes on concrete or asphalt surfaces or checkpoints located at 90 degree corners of different reflectivity, e.g. a sidewalk corner adjoining a grass surface. The xy coordinates of checkpoints, as defined in the intensity imagery, are compared to surveyed xy coordinates for each photo-identifiable checkpoint. These differences are used to compute the tested horizontal accuracy of the LiDAR. As not all projects contain photo-identifiable checkpoints, the horizontal accuracy of the LiDAR cannot always be tested. LiDAR vendors perform calibrations on the LiDAR sensor and compare data to adjoining flight lines to ensure LiDAR meets the 1 meter horizontal accuracy standard at the 95% confidence level. However, Dewberry tested the horizontal accuracy of the LiDAR by comparing photo-identifiable survey checkpoints to the LiDAR Intensity Imagery. As only seventeen (17) checkpoints were photo-identifiable, the results are not statistically significant enough to report as a final tested value. However, the results are reported below. Using NSSDA methodology, horizontal accuracy at the 95% confidence level (called Accuracyr) is computed by the formula RMSEr x 1.7308. The project dataset for the Schoharie County and Schoharie Creek Watershed Expansion LiDAR Project satisfies the criteria: Lidar dataset tested 0.553 m horizontal accuracy at 95% confidence level, based on RMSEr (0.320 m) x 1.7308. Please see the final project report delivered to the U.S. Geological Survey for more details. |
Vertical Positional Accuracy |
The vertical accuracy of the LiDAR was tested by Dewberry with 108 independent survey checkpoints. The survey checkpoints were evenly distributed throughout the project area and were located in areas of bare earth and open terrain (22), tall weeds and crops (21), forested and fully grown (21), brush and small trees (22), and urban (22). The vertical accuracy is tested by comparing survey checkpoints to a triangulated irregular network (TIN) that is created from the LiDAR points. Checkpoints are always compared to interpolated surfaces created from the LiDAR point cloud because it is unlikely that a survey checkpoint will be located at the location of a discrete LiDAR point. Checkpoints in open terrain were used to compute the Fundamental Vertical Accuracy (FVA). Project specifications required a FVA of 0.181 m based on a RMSEz (0.0925m) x 1.9600. All checkpoints will be used to compute the Consolidated Vertical Accuracy (CVA). Project specifications require a CVA of 0.269 m based on the 95th percentile. Supplemental Vertical Accuracy (SVA) will be computed on each individual land cover category other than open terrain. Target specifications for SVA are 0.269 m based on the 95th percentile. NDEP and ASPRS testing methodologies allow individual SVA's to fail as long as the mandatory CVA passes project specifications. Based on the vertical accuracy testing, using NSSDA and FEMA methodology, vertical accuracy at the 95% confidence level (called Accuracyz) is computed by the formula RMSEz x 1.9600. The dataset for the Schoharie County and Schoharie Watershed Expansion LiDAR project tested 0.156 m vertical accuracy at 95% confidence level in open terrain, based on RMSEz (0.080 m) x 1.9600. Based on the vertical accuracy testing, using NDEP and ASPRS methodology, consolidated vertical accuracy (CVA) is computed using the 95th percentile method. The dataset for the Schoharie County and Schoharie Watershed Expansion LiDAR project tested 0.249 m consolidated vertical accuracy at 95th percentile in all land cover categories combined. The 5% outliers consist of 6 checkpoint that is larger than the 95th percentile. The checkpoints have a DZ value range of -0.487 m to 0.415 m. Based on the vertical accuracy testing, using NDEP and ASPRS methodology, supplemental vertical accuracy (SVA) is computed using the 95th percentile method. The dataset for the Schoharie County and Schoharie Watershed Expansion LiDAR project tested 0.302 m supplemental vertical accuracy at 95th percentile in the forested and fully grown land cover category. The dataset for the Schoharie County and Schoharie Watershed Expansion LiDAR project tested 0.145 m supplemental vertical accuracy at 95th percentile in the urban land cover category. The dataset for the Schoharie County and Schoharie Watershed Expansion LiDAR project tested 0.238 m supplemental vertical accuracy at 95th percentile in the grass, weeds, and crops land cover category. The dataset for the Schoharie County and Schoharie Watershed Expansion LiDAR project tested 0.312 m supplemental vertical accuracy at 95th percentile in the brush land and trees land cover category. |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
A visual qualitative assessment was performed to ensure data completeness and bare earth data cleanliness. Data passes vertical accuracy specifications. Two small voids impacting two tiles were identified and have been corrected. |
Conceptual Consistency |
Data covers the tile scheme provided for the project area. |
» Quality Control Procedures Employed |
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 |
» Is Access to the Data Limited Based on an Approved Waiver? | |
» If Distributor (Data Hosting Service) is Needed, Please Indicate | |
» Approximate Delay Between Data Collection and Dissemination | |
» If Delay is Longer than Latency of Automated Processing, Indicate Under What Authority Data Access is Delayed | |
» Actual or Planned Long-Term Data Archive Location | NCEI-CO |
» Approximate Delay Between Data Collection and Archiving | |
» 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) file 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
Citation Title | USGS AWS Entwine Point Tile (EPT) |
---|---|
Contact Role Type | Publisher |
Contact Type | Organization |
Contact Name | USGS |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Scale Denominator | |
Citation URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_NY_Schoharie_2014_LAS_2016/ept.json |
Citation URL Name | Entwine Point Tile for USGS_LPC_NY_Schoharie_2014_LAS_2016 |
Citation URL Description | |
Source Contribution |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Process Steps
Process Step Number | 1 |
---|---|
» Description |
Data for the Schoharie County and Schoharie Watershed Expansion LiDAR project was acquired by The Atlantic Group (TAG) using a CESSNA TU206G aircraft. The project area included approximately 965 contiguous square miles for Schoharie County, New York. LiDAR sensor data was collected with the Leica ALS70-HP LiDAR system. No imagery was requested or delivered. The calibrated data was processed to NAD83(2011) UTM 18, meters, NAVD88 (Geoid12A), meters. Deliverables for the project included a raw (unclassified) calibrated LiDAR point cloud, survey control, and a final control report. A preliminary RMSEz error check is performed at this stage of the project life cycle in the raw LiDAR dataset against GPS static and kinematic data and compared to RMSEz project specifications. The LiDAR data is examined in open, flat areas away from breaks. Lidar ground points for each flightline generated by an automatic classification routine are used. Overall the LiDAR data products collected by Atlantic meet or exceed the requirements set out in the Statement of Work. The quality control requirements of Atlantic's quality management program were adhered to throughout the acquisition stage fo this project to ensure product quality. LIDAR acquisition began on May 26, 2014 (julian day 146) and was completed on June 2, 2014 (julian day 153). A total of 9 survey missions were flown to complete the project. The flight plan was flown as planned with no modifications. There were no unusual occurrences during the acquisition and the sensor performed within specifications. There were 131 flight lines required to complete the project. The initial step of calibration is to verify availability and status of all needed GPS and Laser data against field notes and compile any data if not complete. Subsequently the mission points are output using Leica's ALS Post Processor, initially with the most recent boresight values. The initial point generation for each mission calibration is verified within Microstation/Terrascan for calibration errors. If a calibration error greater than specification is observed within the mission, the roll pitch and scanner scale corrections that need to be applied are calculated. The missions with the new calibration values are regenerated and validated internally once again to ensure quality. All missions are validated against the adjoining missions for relative vertical biases and collected GPS validation points for absolute vertical accuracy purposes. On a project level, a supplementary coverage check is carried out to ensure no data voids unreported by Field Operations are present. The initial points for each mission calibration are inspected for flight line errors, flight line overlap, slivers or gaps in the data, point data minimums, or issues with the LiDAR unit or GPS. Roll, pitch and scanner scale are optimized during the calibration process until the relative accuracy is met. Relative accuracy and internal quality are checked using at least 3 regularly spaced QC blocks in which points from all lines are loaded and inspected. Vertical differences between ground surfaces of each line are displayed. Color scale is adjusted so that errors greater than the specifications are flagged. Cross sections are visually inspected across each block to validate point to point, flightline to flightline and mission to mission agreement. For this project the specifications used are as follow: Relative accuracy <= 7cm RMSEZ within individual swaths and <=10 cm RMSEZ or within swath overlap (between adjacent swaths). UTM coordinate system, meters, zone 18, horizontal datum NAD83 (2011), vertical datum NAVD88, Geoid 12A |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
Dewberry utilizes a variety of software suites for inventory management, classification, and data processing. All LiDAR related processes begin by importing the data into the GeoCue task management software. The swath data is tiled according to project specifications (1,500 m x 1,500 m). The tiled data is then opened in Terrascan where Dewberry uses proprietary ground classification routines to remove any non-ground points and generate an accurate ground surface. The ground routine consists of three main parameters (building size, iteration angle, and iteration distance); by adjusting these parameters and running several iterations of this routine an initial ground surface is developed. The building size parameter sets a roaming window size. Each tile is loaded with neighboring points from adjacent tiles and the routine classifies the data section by section based on this roaming window size. The second most important parameter is the maximum terrain angle, which sets the highest allowed terrain angle within the model. Once the ground routine has been completed a manual quality control routine is done using hillshades, cross-sections, and profiles within the Terrasolid software suite. After this QC step, a peer review and supervisor manual inspection is completed on a percentage of the classified tiles based on the project size and variability of the terrain. After the ground classification corrections were completed, the dataset was processed through a water classification routine that utilizes breaklines compiled by Atlantic to automatically classify hydrographic features. The water classification routine selects ground points within the breakline polygons and automatically classifies them as class 9, water. During this water classification routine, points that are within 0.3 meter of the hydrographic features are moved to class 10, an ignored ground due to breakline proximity. In addition to classes 1, 2, 9, and 10, there is a Class 7, noise points . Class 7 was only used if needed when points could manually be identified as low/high points.
The fully classified dataset is then processed through Dewberry's comprehensive quality control program. The data was classified as follows: Class 1 = Unclassified. This class includes vegetation, buildings, noise etc. Class 2 = Ground Class 7= Noise Class 9 = Water Class 10=Ignored The LAS header information was verified to contain the following: Class (Integer) GPS Week Time (0.0001 seconds) Easting (0.003 m) Northing (0.003 m) Elevation (0.003 m) Echo Number (Integer 1 to 4) Echo (Integer 1 to 4) Intensity (8 bit integer) Flight Line (Integer) Scan Angle (Integer degree) |
Process Date/Time | 2014-10-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
Original point clouds in LAS/LAZ format were restructured as an Entwine Point Tile 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 (GEOID12A). |
Process Date/Time | |
Process Contact | U.S. Geological Survey |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 4 |
---|---|
» Description |
The NOAA Office for Coastal Management (OCM) created references to the Entwine Point Tile (EPT) file that was 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_NY_Schoharie_2014_LAS_2016/ept.json |
Process Date/Time | 2023-07-05 00:00:00 |
Process Contact | Office for Coastal Management (OCM) |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Acquisition Information
Instruments
Instrument Unavailable Reason |
---|
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Platforms
Platform Unavailable Reason |
---|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
FAQs
Date | |
---|---|
Author | |
Question | |
Answer |
Child Items
Rubric scores updated every 15m
Score | Type | Title |
---|---|---|
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Catalog Details
Catalog Item ID | 70223 |
---|---|
Metadata Record Created By | Rebecca Mataosky |
Metadata Record Created | 2023-06-30 16:06+0000 |
Metadata Record Last Modified By | SysAdmin InPortAdmin |
» Metadata Record Last Modified | 2023-10-17 16:12+0000 |
Metadata Record Published | 2023-07-05 |
Owner Org | OCMP |
Metadata Publication Status | Published Externally |
Do Not Publish? | N |
Metadata Workflow State | Published / External |
Metadata Last Review Date | 2023-07-05 |
Metadata Review Frequency | 1 Year |
Metadata Next Review Date | 2024-07-05 |
Tags |
---|