2015 NYSGPO Lidar: Warren, Washington, and Essex Counties, NY
Data Set (DS) | OCM Partners (OCMP)GUID: gov.noaa.nmfs.inport:65055 | Updated: October 17, 2023 | Published / External
Summary
Short Citation
OCM Partners, 2024: 2015 NYSGPO Lidar: Warren, Washington, and Essex Counties, NY, https://www.fisheries.noaa.gov/inport/item/65055.
Full Citation Examples
Axis Geospatial has contracted Atlantic to obtain professional services related to the development of Light Detection and Ranging (LiDAR) data between April 2015 and June 2015. This data set is consisting of LiDAR Point Cloud, Classified LiDAR, Digital Elevation Model, and LiDAR Intensity Images which all pieces encompasses the entire 2,424 Square miles (6,278 km) of the NY_WarrenWashingtonEssex_Spring2015 project area. The project area spans 5 counties including Warren, Washington, Essex, Hamilton, and Franklin. This data set consists of LiDAR point cloud with nominal pulse spacing of 0.5557 m, and tiled Las files. Each LAS file contains LiDAR point information, which has been calibrated, controlled, and classified.
Ground Conditions: water at normal levels; no unusual inundation; no snow; leaf off
The calibrated point cloud data from the laser sensor was merged to produce processed (*.las) files including but not limited to 3D position, intensity, and time-stamp. A filtering methodology was utilized to produce a multi-return surface elevation model dataset with bare-earth conditions. GeoCue, TerraScan, and TerraModel software was used for the initial batch processing and manual editing of the (*.las) point clouds. The errors (noise columns) in classification were corrected by identifying the areas of dense noise in the point cloud and manually removing the incorrectly classified ground surfaces and above ground features.The Withheld and Overlap flags were utilized for the final LAS v1.4 file production. These classified LiDAR points were then used in the creation of other deliverables such as Bare-Earth Digital Elevation Models (DEMs) and LiDAR Intensity images. The final deliverables include 2783 tiles.
How the Withheld Points are Identified: Withheld (ignore) points were identified in the files using the standard LAS Withheld bit.
Class Code:0
Class Item: Never Classified
Class Code:1
Class Item: Undetermined/Unclassified
Class Code:2
Class Item: Ground
Class Code:7
Class Item:Low Point (Noise)
Class Code:17
Class Item:Bridge Deck
Class Code:18
Class Item:High Noise
In addition to these lidar point data, the bare earth Digital Elevation Models (DEM) created from the lidar point data are also available. These data are available for custom download at the link provided in the URL section of this metadata record.
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, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document. They will be in an orthometric datum.
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.
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
-74.556405° W,
-73.223816° E,
44.297386° N,
43.339153° S
2015-04-29 - 2015-05-23
Item Identification
Title: | 2015 NYSGPO Lidar: Warren, Washington, and Essex Counties, NY |
---|---|
Short Name: | ny2015_warr_wash_essex_m9345_metadata |
Status: | Completed |
Creation Date: | 2015 |
Abstract: |
Axis Geospatial has contracted Atlantic to obtain professional services related to the development of Light Detection and Ranging (LiDAR) data between April 2015 and June 2015. This data set is consisting of LiDAR Point Cloud, Classified LiDAR, Digital Elevation Model, and LiDAR Intensity Images which all pieces encompasses the entire 2,424 Square miles (6,278 km) of the NY_WarrenWashingtonEssex_Spring2015 project area. The project area spans 5 counties including Warren, Washington, Essex, Hamilton, and Franklin. This data set consists of LiDAR point cloud with nominal pulse spacing of 0.5557 m, and tiled Las files. Each LAS file contains LiDAR point information, which has been calibrated, controlled, and classified. Ground Conditions: water at normal levels; no unusual inundation; no snow; leaf off The calibrated point cloud data from the laser sensor was merged to produce processed (*.las) files including but not limited to 3D position, intensity, and time-stamp. A filtering methodology was utilized to produce a multi-return surface elevation model dataset with bare-earth conditions. GeoCue, TerraScan, and TerraModel software was used for the initial batch processing and manual editing of the (*.las) point clouds. The errors (noise columns) in classification were corrected by identifying the areas of dense noise in the point cloud and manually removing the incorrectly classified ground surfaces and above ground features.The Withheld and Overlap flags were utilized for the final LAS v1.4 file production. These classified LiDAR points were then used in the creation of other deliverables such as Bare-Earth Digital Elevation Models (DEMs) and LiDAR Intensity images. The final deliverables include 2783 tiles. How the Withheld Points are Identified: Withheld (ignore) points were identified in the files using the standard LAS Withheld bit. Class Code:0 Class Item: Never Classified Class Code:1 Class Item: Undetermined/Unclassified Class Code:2 Class Item: Ground Class Code:7 Class Item:Low Point (Noise) Class Code:17 Class Item:Bridge Deck Class Code:18 Class Item:High Noise In addition to these lidar point data, the bare earth Digital Elevation Models (DEM) created from the lidar point data are also available. These data are available for custom download at the link provided in the URL section of this metadata record. |
Purpose: |
This LiDAR elevation data and its derivatives including high resolution Bare Earth DEMs and LiDAR Intensity imagery will be used for conservation planning, design, research, floodplain mapping, wetlands identification, dam safety assessments, hydrologic modelling, subsidence monitoring, and general spatial analyst. |
Supplemental Information: |
All Lidar data was acquired, calibrated, and used in the creation of Lidar derived products by Atlantic. The following are the USGS lidar fields in JSON: {
"ldrinfo" : {
"ldrspec" : " USGS-NGP Base Lidar Specification v1.2
", "ldrsens" : " Leica ALS70-HP
", "ldrmaxnr" : " Unlimited
", "ldrnps" : " 0.6
", "ldrdens" : " 2.5
", "ldranps" : " 0.5557
", "ldradens" : " 3.24
", "ldrfltht" : " 2260
", "ldrfltsp" : " 125
", "ldrscana" : " 40
", "ldrscanr" : " 34.4
", "ldrpulsr" : " 252.0
", "ldrpulsd" : " 4
", "ldrpulsw" : " 0.46
", "ldrwavel" : " 1064
", "ldrmpia" : " 1
", "ldrbmdiv" : " 0.15
", "ldrswatw" : " 1565
", "ldrswato" : " 20
", "ldrgeoid" : " National Geodetic Survey (NGS) Geoid12A
" }, "ldraccur" : {
"ldrchacc" : " 0.196
", "rawnva" : " 0.074
", "rawnvan" : " 290
", "clsnva" : " 0.077
", "clsnvan" : " 294
", "clsvva" : " 0.099
", "clsvvan" : " 379
" }, "lasinfo" : {
"lasver" : " 1.4
", "lasprf" : " 6
", "laswheld" : " Withheld (ignore) points were identified in the files using the standard LAS Withheld bit.
", "lasolap" : " Swath overage points were identified in these files using the standard LAS overlap bit.
", "lasintr" : " 32
", "lasclass" : {
"clascode" : "0", "clasitem" : "Never Classified" }, "lasclass" : {
"clascode" : "1", "clasitem" : "Undetermined/Unclassified" }, "lasclass" : {
"clascode" : "2", "clasitem" : "Ground" }, "lasclass" : {
"clascode" : "7", "clasitem" : "Low Noise" }, "lasclass" : {
"clascode" : "17", "clasitem" : "Bridge Deck" }, "lasclass" : {
"clascode" : "18", "clasitem" : "High Noise" } }} |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Science Keywords |
EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION
|
ISO 19115 Topic Category |
elevation
|
UNCONTROLLED | |
None | erosion |
None | Intensity Image |
Spatial Keywords
Thesaurus | Keyword |
---|---|
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
|
UNCONTROLLED | |
None | Continent > North America > United States Of America > New York > Essex County |
None | Continent > North America > United States Of America > New York > Franklin County |
None | Continent > North America > United States Of America > New York > Hamilton County |
None | Continent > North America > United States Of America > New York > Warren County |
None | Continent > North America > United States Of America > New York > Washington County |
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: | As Needed |
Data Presentation Form: | Model (digital) |
Entity Attribute Detail Citation: |
LiDAR Tiles and associated derived products for Axis Geospatial New York AOI |
Distribution Liability: |
The data represented is the result of data collection and processing per contract specifications and indicates the general existing conditions at the time of data collection. As such, it is only valid for its intended use, content, time, and accuracy specifications. The user is responsible for the results of any application of the data for other than its intended purpose. 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: | Axis Geospatial LLC, Atlantic |
Support Roles
Data Steward
Date Effective From: | 2021 |
---|---|
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: | 2021 |
---|---|
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 |
Metadata Contact
Date Effective From: | 2021 |
---|---|
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: | 2021 |
---|---|
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: | -74.556405 | |
---|---|---|
E° Bound: | -73.223816 | |
N° Bound: | 44.297386 | |
S° Bound: | 43.339153 |
Extent Group 1 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2015-04-29 |
End: | 2015-05-23 |
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 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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. |
Distribution Information
Distribution 1
Start Date: | 2021-07-23 |
---|---|
End Date: | Present |
Download URL: | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9345/details/9345 |
Distributor: | NOAA Office for Coastal Management (NOAA/OCM) (2021 - 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: | 2021-07-23 |
---|---|
End Date: | Present |
Download URL: | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9345/index.html |
Distributor: | NOAA Office for Coastal Management (NOAA/OCM) (2021 - Present) |
File Name: | Bulk Download |
Description: |
Bulk download of data files in LAZ format, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document. They will be in an orthometric datum. |
File Type (Deprecated): | LAZ |
Distribution Format: | LAS/LAZ - LASer |
Compression: | Zip |
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://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9345/supplemental/ny2015_warr_wash_ess.kmz |
---|---|
Name: | Browse graphic |
URL Type: |
Browse Graphic
|
File Resource Format: | KML |
Description: |
This graphic displays the footprint for this lidar data set. |
URL 3
URL: | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9352/details/9352 |
---|---|
Name: | Custom DEM Download |
URL Type: |
Online Resource
|
File Resource Format: | Zip |
Description: |
Link to custom download, from the Data Access Viewer (DAV), the raster Digital Elevation Model (DEM) data that were created from this lidar data set. |
Technical Environment
Description: |
CloudPro 1.2.0 Build 85620; GeoCue Version 2014.1.21.2; Windows 7 Operating System |
---|
Data Quality
Horizontal Positional Accuracy: |
Horizontal error in lidar derived elevation data is largely a function of positional error as derived from the Global Navigation Satellite System (GNSS), attitude (angular orientation) error (as derived from the INS) and flying altitude; and can be estimated based on these parameters. As described in Section 7.5 of the ASPRS Positional Accuracy Standards for Digital Geospatial Data the horizontal errors in lidar data are largely a function of GNSS positional error, INS angular error, and flying altitude. Therefore lidar data collected with GNSS error of 0.05m and the IMU error of 0.03492 degrees at an altitude of 2300m; the expected radial horizontal positional error will be RMSEr = 0.130 m. |
---|---|
Vertical Positional Accuracy: |
Vertical Accuracy of the point cloud and bare-earth lidar data was assessed and reported in accordance with the ASPRS Positional Accuracy Standards for Digital Geospatial Data; Six-Hundred and Seventy-Three (673) surveyed points were measured for the purpose of assessing the accuracy of the NY_WarrenWashingtonEssex_Spring2015 project data. (294 NVA + 379 VVA). Both data sets, Lidar and Digital Elevation Models (DEMs) have been tested for individual vertical accuracy levels. The Lidar was tested by using interpolation while the DEMs where tested by extracting the elevation of a pixel containing the checkpoint. All DEM Vertical accuracy results are reported in the DEM metadata reports while this project wide metadata file is reporting the vertical accuracy results from the the source Lidar. This data set was tested to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 10.0 (cm) RMSEz Vertical Accuracy Class. Actual NVA accuracy of the classified point cloud was found to be RMSEz = 0.077 m, equating to +/- 0.152 m at 95% confidence level. Actual VVA accuracy was found to be RMSEz = 0.099 m, equating to +/- 0.178 m at 95% confidence level. |
Completeness Report: |
The raw LAS data files included 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 of good quality and data passes Fundamental Vertical Accuracy specifications.Void areas (i.e., areas outside the project boundary but within the tiling scheme) are coded using a unique NODATA value. This value is identified in the appropriate location within the file header. |
Conceptual Consistency: |
Aerial LiDAR data covers the entire 2,424 square mile area for the NY_WarrenWashingtonEssex_Spring2015 project task. All LiDAR Point Cloud tiles show no edge artifacts or mismatches from tile to tile. Void areas (i.e. areas outside the project boundary but within the tiling scheme) are coded using a unique NODATA value. This value is identified in the appropriate location within the file header. Data cover 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: |
Data were collected and processed by Atlantic for the New York State GIS Program Office (NYSGPO) and posted to their ftp site. The NOAA Office for Coastal Management (OCM) downloaded the data from the ftp site and processed it to make it available for custom download from the Data Access Viewer (DAV) and bulk download from https. |
---|
Sources
NY_WarrenWashingtonEssex_Spring2015
Contact Role Type: | Originator |
---|---|
Contact Type: | Organization |
Contact Name: | Atlantic |
Extent Type: | Range |
Extent Start Date/Time: | 2015-04-29 |
Extent End Date/Time: | 2015-05-23 |
Scale Denominator: | 1200 |
Source Contribution: |
This data source was used (along with the airborne GPS/IMU Data) for georeferencing of the lidar point cloud data used to create all contracted Lidar derived products. Version of the LAS Standard 1.4 / point data record format 6. |
Process Steps
Process Step 1
Description: |
Aerial LiDAR Acquisition: Aerial data collection was acquired in sixteen (16) missions, using the ALS70 SN#7123 at a max flying height of 3500 AGL. This was to support a 2.5 ppm^2 LiDAR point cloud. Airborne GPS and IMU data was collected during the acquisition and supported by Topcon Viper GPS, Data acquisition was completed on May 23rd 2015. Ground Control Survey: A survey was performed by Axis Geospatial to support the acquisition of Light Detection and Ranging (LiDAR). The control network involved a total of 673 check points (294 NVA + 379 VVA). The points were a combination of the following ground cover classification: Open Terrain, Urban Terrain, Bare Earth, and High Grass. |
---|---|
Process Date/Time: | 2015-05-23 00:00:00 |
Process Step 2
Description: |
LiDAR Pre-processing: Airborne GPS and IMU data were merged to develop a Single Best Estimate (SBET) of the LiDAR system trajectory for each lift. LiDAR ranging data were initially calibrated using previous best parameters for this instrument and aircraft. Relative calibration was evaluated using advanced plane-matching analysis and parameter corrections derived. This process was repeated interactively until residual errors between overlapping swaths, across all project lifts, was reduced to 2 cm or less. Data was then block adjusted to match surveyed calibration control. Raw data NVA was checked using independently surveyed check points. Swath overage points were identified and tagged within each swath file. |
---|---|
Process Date/Time: | 2015-06-01 00:00:00 |
Process Step 3
Description: |
Noise Columns: The isolated dense erroneous points presenting as columns of noise both above and below the bare-earth surface are almost entirely in Blocks 1 and 2 (Affected Tiles shapefile attached). This type of noise is only present in the SN7123 ALS70 sensor acquired data in the southern half of the project area. A combination of the acquisition discriminator settings, flying height, FOV, terrain, and surface reflectance were the cause of these occurrences. In these instances the scanner’s nadir position (scanner nadir as opposed to the center of the acquired swath) in correlation to the planar surface of a roof or waterbody exhibited a bias in the digitized intensity from the low-gain channels. As the laser output is scanned through the point where the laser output is perpendicular to the roof or water surface with very low reflectance the increased sensitivity from the acquisition discriminator settings resulted in an increase of laser backscatter reflected into the receiver. That backscatter was represented as columns of erroneous points or noise, while this did not affect the laser returns at ground level it did effect the automated high noise filtering in the initial classification process. |
---|---|
Process Date/Time: | 2015-06-15 00:00:00 |
Process Step 4
Description: |
Initial processing of the GPS data was processed using Inertial Explorer. The solution file was generated and CloudPro software was used to generate georeferenced laser returns which were then processed in strip form allowing for the QC of the overlap between strips (lines). The data from each line were combined and automated classification routines run to determine the initial surface model. This initial surface model was then verified to the surveyed test points. |
---|---|
Process Date/Time: | 2015-06-01 00:00:00 |
Process Step 5
Description: |
LiDAR Post-Processing: The calibrated and controlled LiDAR swaths were processed using automatic point classification routines in TerraSolid software. These routines operate against the entire collection (all swaths, all lifts), eliminating character differences between files. Data were then distributed as virtual tiles to experienced LiDAR analysts for localized automatic classification, manual editing, and peer-based QC checks. Supervisory QC monitoring of work in progress and completed editing ensured consistency of classification character and adherence to project requirements across the entire project. All classification tags are stored in the original swath files. After completion of classification and final QC approval, the NVA and VVA for the project are calculated. Sample areas for each land cover type present in the project were extracted and forwarded to the client, along with the results of the accuracy tests. Upon acceptance, the complete classified LiDAR swath files were delivered to the client. |
---|---|
Process Date/Time: | 2015-06-10 00:00:00 |
Process Step 6
Description: |
LiDAR Classification: The calibrated LiDAR data was run through automated classification routines and then manually checked and edited. The data was classified into the following classes: 1-unclassified*, 2-ground, 7-low noise, 17-bridges, and 18-high noise |
---|---|
Process Date/Time: | 2015-07-01 00:00:00 |
Process Step 7
Description: |
LiDAR Intensity Imagery Creation: All LiDAR Intensity Imagery was created from the final calibrated and classified LiDAR Point Cloud. Intensity Images where produced from all classified points and are posted to a 1.0 meter cell size. Intensity Images where cut to match the provided Tile Index and have corresponding names to match tile names. |
---|---|
Process Date/Time: | 2015-07-01 00:00:00 |
Process Step 8
Description: |
Bare-Earth DEM Creation: Bare-Earth Digital Elevation Models (DEMs) were derived using bare-earth (ground) LiDAR points, all DEMs were created with a grid spacing of 1 meter. The DEMs were cut to tiles of 1500 meters X 1500 meters index, provided by Axis Geospatial. |
---|---|
Process Date/Time: | 2015-07-10 00:00:00 |
Process Step 9
Description: |
The NOAA Office for Coastal Management (OCM) downloaded 2782 las files from ftp://ftp.gis.ny.gov/elevation/LIDAR/NYSGPO_WarrenWashingtonEssex_2015/. The data were in UTM Zone 18 (NAD83 2011), meters coordinates and NAVD88 (Geoid12A) elevations in meters. The data were classified as: 1 - Unclassified, 2 - Ground, 7 - Low Noise, 9 - Water, 17 - Bridge Decks, 18 - High Noise. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 7, 9, 17, 18. Although not listed in the original contractor metadata, points classified as 9 - water are included. There were also a relatively low number of points that were classified with random classes. These values were for the most part very high or very low (blunder) elevations. These relatively few points with random classifications remain in the data set. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. The las files were converted from las format to laz format using laszip. 2. Internal OCM scripts were run to check the number of points by classification and by flight ID and the gps, elevation, and intensity ranges. 3. Internal OCM scripts were run on the laz files to: a. Convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid12A model b. Convert the laz files from UTM Zone 18 (NAD83 2011), meters coordinates to geographic coordinates c. Filter points with elevation values less than 0 meters and greater than 2500 meters. d. Filter points outside the geographic range of the bounding coordinates of -81, 40, -72, 45.5 degrees e. The filtering indicated that four files had points that were clipped out. Those files were: u_6300085100_2015, u_6165084650_2015, u_6120081050_2015, u_5745085100_2015 f. Assign the geokeys, sort the data by gps time and zip the data to database and to http. |
---|---|
Process Date/Time: | 2021-08-09 00:00:00 |
Process Contact: | Office for Coastal Management (OCM) |
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Data Set (DS) | Cross Reference |
2015 NYSGPO Lidar DEM: Warren, Washington, and Essex Counties, NY |
Catalog Details
Catalog Item ID: | 65055 |
---|---|
GUID: | gov.noaa.nmfs.inport:65055 |
Metadata Record Created By: | Rebecca Mataosky |
Metadata Record Created: | 2021-07-23 15:50+0000 |
Metadata Record Last Modified By: | SysAdmin InPortAdmin |
Metadata Record Last Modified: | 2023-10-17 16:12+0000 |
Metadata Record Published: | 2022-03-16 |
Owner Org: | OCMP |
Metadata Publication Status: | Published Externally |
Do Not Publish?: | N |
Metadata Last Review Date: | 2022-03-16 |
Metadata Review Frequency: | 1 Year |
Metadata Next Review Date: | 2023-03-16 |