gov.noaa.nmfs.inport:71559 eng UTF8 dataset Elevation OCM Partners resourceProvider NOAA Office for Coastal Management (843) 740-1202 2234 South Hobson Ave Charleston SC 29405-2413 coastal.info@noaa.gov https://coast.noaa.gov WWW:LINK-1.0-http--link NOAA Office for Coastal Management Website NOAA Office for Coastal Management Home Page information pointOfContact 2026-04-30T00:00:00 ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data ISO 19115-2:2009(E) point 52125084866 NAD83(2011) / UTM zone 18N2008-11-12publicationEuropean Petroleum Survey Grouphttps://apps.epsg.org/api/v1/CoordRefSystem/6347/export/?format=gmlurn:ogc:def:crs:EPSG:63476.18.3 2018 USGS Lidar: Upper Middle Neck, VA 2023-11-29 creation 2020-07-27 publication NOAA/NMFS/EDM 71559 https://www.fisheries.noaa.gov/inport/item/71559 WWW:LINK-1.0-http--link Full Metadata Record View the complete metadata record on InPort for more information about this dataset. information https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/9895/ept.json WWW:LINK-1.0-http--link Entwine Point Tiles 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. download https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/VA_UpperMiddleNeck_2018_D18/ WWW:LINK-1.0-http--link USGS Additional Info Link to the reports, breaklines, metadata, and spatial metadata. download https://coast.noaa.gov/lidar/viewer/v/noaapotree.html?r=https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/9895/ept.json WWW:LINK-1.0-http--link Potree Viewer (3D Point Cloud) Link to view the point cloud, using the Entwine Point Tile (EPT) format, in the 3D Potree viewer. download https://coast.noaa.gov/dataviewer/ WWW:LINK-1.0-http--link NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) 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. download https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/VA_UpperMiddleNeck_2018_D18/Vertical_Accuracy/USGS/VA_UpperMiddleNeck_2018_D18_VA.txt WWW:LINK-1.0-http--link USGS Vertical Accuracy Report USGS compiled vertical accuracy statistics. download https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/VA_UpperMiddleNeck_2018_D18/Vertical_Accuracy/contractor_provided/vertical_accuracy_B3/accuracy_report/VA_UpperMiddleNeck_2018_D18_Accuracy_Report_VA_Counties.pdf WWW:LINK-1.0-http--link Vertical Accuracy Report, Contractor Provided Vertical Accuracy report from Fugro for Block03. download Products: This VA_UpperMiddleNeck_2018_D18 project called for the planning, acquisition, processing, and derivative products of lidar data to be collected at an aggregate nominal pulse spacing (ANPS) of 0.71 meters (2ppsm). Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.3. The original data was developed based on a horizontal projection/datum of NAD83 (2011), Albers Equal Area, meters and vertical datum of NAVD88 (GEOID12B), meters. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to individual 1000 m x 1000 m tiles. This data set contains point cloud data(' in LAZ (compressed LAS) format', ''). The data may have been reprojected or otherwise modified from the original data in an automated process. Disregard projection information in this abstract and refer to the spatial reference section. This high resolution lidar data will support the United States Geological Survey (USGS) initiatives. USGS, Fugro The custom download may be cited as National Oceanic and Atmospheric Administration (NOAA) Digital Coast Data Access Viewer. Charleston, SC: NOAA Office for Coastal Management. Accessed 2026-07-02 at https://coast.noaa.gov/dataviewer. completed NOAA Office for Coastal Management (843) 740-1202 2234 South Hobson Ave Charleston SC 29405-2413 coastal.info@noaa.gov https://coast.noaa.gov WWW:LINK-1.0-http--link NOAA Office for Coastal Management Website NOAA Office for Coastal Management Home Page information pointOfContact NOAA Office for Coastal Management (843) 740-1202 2234 South Hobson Ave Charleston SC 29405-2413 coastal.info@noaa.gov https://coast.noaa.gov WWW:LINK-1.0-http--link NOAA Office for Coastal Management Website NOAA Office for Coastal Management Home Page information custodian notPlanned https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/GEOID18/9895/supplemental/extent_UpperMiddle_VA_m9895.kmz This graphic displays the footprint for this lidar data set. KML EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION theme Global Change Master Directory (GCMD) Science Keywords 23.3 CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA VERTICAL LOCATION > LAND SURFACE place Global Change Master Directory (GCMD) Location Keywords 23.3 LIDAR > Light Detection and Ranging instrument Global Change Master Directory (GCMD) Instrument Keywords 23.3 Airplane > Airplane platform Global Change Master Directory (GCMD) Platform Keywords 23.3 Lidar - partner (no harvest) project InPort otherRestrictions This data set was compiled dynamically. It will be removed 10 days after 2026-07-02 from the NOAA system. Cite As: OCM Partners, [Date of Access]: 2018 USGS Lidar: Upper Middle Neck, VA [Data Date Range], https://www.fisheries.noaa.gov/inport/item/71559. NOAA provides no warranty, nor accepts any liability occurring from any incomplete, incorrect, or misleading data, or from any incorrect, incomplete, or misleading use of the data. It is the responsibility of the user to determine whether or not the data is suitable for the intended purpose. otherRestrictions This data set was compiled dynamically. It will be removed 10 days after 2026-07-02 from the NOAA system. Access Constraints: None otherRestrictions This data set was compiled dynamically. It will be removed 10 days after 2026-07-02 from the NOAA system. 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. otherRestrictions This data set was compiled dynamically. It will be removed 10 days after 2026-07-02 from the NOAA system. 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 unclassified vector .35 eng; US elevation POSGNS 5.2; POSPac 6.2; RiProcess 1.8.3; RiWorld 5.0.2; RiAnalyze 6.2; RiServer 1.99.5; Microstation CONNECT 10.00.00.25; TerraScan 017.039 and 016.013; TerraModeler 016.001; Lasedit 1.35.07; GeoCue 2014.1.21.5; ArcMap 10.3; Global Mapper 17.1.2; ERDAS Imagine 2016; PhotoShop CS8; Fugro proprietary software; Windows 7 64-bit Operating System \\server\directory path\*.las \\server\directory path\*.las \\server\directory path\*.img \\server\directory path\*.gdb \\server\directory path\*.tif/tfw 1440 GB -77.5877 -76.2012 36.5229 38.3029 | Currentness: Ground Condition 2018 USGS Contract No. G17PC00015 CONTRACTOR: Fugro Geospatial, Inc. SUBCONTRACTOR: Terrasurv, Inc. Ground control and checkpoints collected by Terrasurv, Inc. All processing was completed by the prime contractor. Point Cloud File Type = LAS v1.4 Point Record Format 6, 7, 8, 9, or 10 including "File Source ID" The following are the USGS lidar fields in JSON: { "ldrinfo" : { "ldrspec" : "USGS-NGP Base Lidar Specification v1.3", "ldrsens" : "ALS80", "ldrmaxnr" : "5", "ldrnps" : "0.5", "ldrdens" : "4", "ldranps" : "0.35", "ldradens" : "8", "ldrfltht" : "2650", "ldrfltsp" : "150", "ldrscana" : "26.5", "ldrscanr" : "55", "ldrpulsr" : "534", "ldrpulsd" : "2.5", "ldrpulsw" : "0.75", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.2", "ldrswatw" : "1150", "ldrswato" : "56", "ldrgeoid" : "National Geodetic Survey (NGS) GEOID12B" }, "ldraccur" : { "ldrchacc" : "0.309", "rawnva" : "0.102", "rawnvan" : "107" }, "lasinfo" : { "lasver" : "1.4", "lasprf" : "6", "laswheld" : "There were no withheld points identified in this project. All points were used in the classification.", "lasolap" : "Swath "overage" points were identified in these files using the standard LAS overlap bit.", "lasintr" : "16 bit", "lasclass" : { "clascode" : "1", "clasitem" : "Processed but unclassified" }, "lasclass" : { "clascode" : "2", "clasitem" : "Bare-earth ground" }, "lasclass" : { "clascode" : "7", "clasitem" : "Low Noise" }, "lasclass" : { "clascode" : "9", "clasitem" : "Water" }, "lasclass" : { "clascode" : "17", "clasitem" : "Bridge Decks" }, "lasclass" : { "clascode" : "18", "clasitem" : "High Noise" }, "lasclass" : { "clascode" : "20", "clasitem" : "Ignored Ground (breakline proximity)" } }} Zip LAS/LAZ - LASer LAZ NOAA Office for Coastal Management (843) 740-1202 2234 South Hobson Ave Charleston SC 29405-2413 coastal.info@noaa.gov https://coast.noaa.gov WWW:LINK-1.0-http--link NOAA Office for Coastal Management Website NOAA Office for Coastal Management Home Page information distributor https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9895/details/9895 WWW:LINK-1.0-http--link Customized Download 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. download https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9895/index.html WWW:LINK-1.0-http--link Bulk Download 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. download dataset Horizontal Positional Accuracy The horizontal errors in lidar data are largely a function of the Global Navigation Satellite System (GNSS) positional errors, the Inertial Measurement Unit (IMU) angular errors, and the flying altitude. If the accuracy of the GNSS/IMU solution is known for the specific POS system, using the flying altitude of the project the expected horizontal errors in the LiDAR data can be estimated. Following the formula in the ASPRS Positional Accuracy Standards for Digital Geospatial Data (Edition 1, Version 1.0. - November, 2014), using the specifications of the POS system used and 2651 m flying altitude above ground, the estimated horizontal accuracy is RMSEr = 0.34 m. 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. The USGS values are as follows: The number of Checkpoints tested for NVA : 145 The NVA RMSEz= 5.22 cm The NVA Accuracy z at 95% confidence interval (RMSEz * 1.96) = 10.23 cm Completeness Report A complete iteration of processing (GPS/IMU Processing, Raw Lidar Data Processing, and Verification of Coverage and Data Quality) was performed to ensure that the acquired data was complete, uncorrupted, and that the entire project area had been covered without gaps between flight lines. No void areas or missing data exist. The raw point cloud is of good quality and data passes Vertical Accuracy requirements. The Classified Point Cloud data files include all data points collected except the ones from Cross ties and Calibration lines. The points that have been removed or excluded are the points fall outside the project delivery boundary. Points are classified. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The classified point cloud is of good quality and data passes Vertical Accuracy requirements. The Intensity Image files cover the entire project delivery boundary. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The Intensity Image product is of good quality. The Hydro Breaklines cover the entire project delivery boundary and extend beyond the boundary in a few locations. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The Hydro Breakline product is of good quality. The DEM raster files cover the entire project delivery boundary. The pixels that fall outside the project delivery boundary are set to Void with a unique “NODATA” value. The value is identified in the file headers. There are no void pixels inside the project boundary. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The bare earth surface is of good quality and passes Vertical Accuracy requirements. Conceptual Consistency Compliance with the accuracy standard was ensured by the collection of ground control and the establishment of GPS base stations in the project area. The following checks were performed: 1) The lidar data accuracy was validated by performing a full boresight adjustment and then checking it against the ground control prior to generating a digital terrain model (DTM) or other products. 2) Lidar elevation data was validated through an inspection of edge matching and visual inspection for quality (artifact removal). The following software was used for the validation: 1) RiProcess 1.8.3, RiWorld 5.0.2, RiAnalyze 6.2, RiServer 1.99.5; and 2) Fugro proprietary software; 20171231. Once boresighting was complete for the project, the project was first set up for automatic classification. The lidar data was cut to production tiles. The low noise points, high noise points and ground points were classified automatically in this process. Fugro utilized commercial software, as well as proprietary, in-house developed software for automatic filtering. The parameters used in the process were customized for each terrain type to obtain optimum results. Once the automated filtering was completed, the files were run through a visual inspection to ensure that the filtering was not too aggressive or not aggressive enough. In cases where the filtering was too aggressive and important terrain were filtered out, the data was either run through a different filter within local area or was corrected during the manual filtering process. Bridge deck points were classified as well during the interactive editing process. Interactive editing was completed in visualization software that provides manual and automatic point classification tools. Fugro utilized commercial and proprietary software for this process. All manually inspected tiles went through a peer review to ensure proper editing and consistency. After the manual editing and peer review, all tiles went through another final automated classification routine. This process ensures only the required classifications are used in the final product (all points classified into any temporary classes during manual editing will be re-classified into the project specified classifications). Once manual inspection, QC and final autofilter is complete for the lidar tiles, the LAS data was packaged to the project specified tiling scheme, clipped to project re-projected to Albers Equal Area; NAD83 (2011), meters; NAVD88 (GEOID12B), meters. The file header was formatted to meet the project specification with File Source ID assigned. This Classified Point Cloud product was used for the generation of derived products. This product was delivered in fully compliant LAS v1.4, Point Record Format 6 with Adjusted Standard GPS Time at a precision sufficient to allow unique timestamps for each pulse. Correct and properly formatted georeference information as Open Geospatial Consortium (OGC) well known text (WKT) was assigned in all LAS file headers. Each tile has unique File Source ID assigned. The Point Source ID matches to the flight line ID in the flight trajectory files. Intensity values are included for each point, normalized to 16-bit. The following classifications are included: Class 1 – Processed, but unclassified; Class 2 – Bare earth ground; Class 7 – Low Noise; Class 9 – Water; Class 17 – Bridge Decks; Class 18 – High Noise; Class 20 - Ignored Ground (breakline proximity). The classified point cloud data was delivered in tiles without overlap using the project tiling scheme. 2020-02-10T00:00:00 The NOAA Office for Coastal Management (OCM) downloaded this data set from the USGS RockyWeb portal. The total number of files downloaded and processed was 11,503. The data were in Albers and UTM18 (NAD83 2011), meters, and NAVD88 (Geoid12B) elevations in meters. The data were classified as: 1 - Unclassified, 2 - Ground,, 7 - Noise, 9 - Water, 17 - Bridge Decks, and 20 - Ignored Ground. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 2. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid12B model, to convert to geographic coordinates, to assign the geokeys, to sort the data by gps time and zip the data to database and to http. 2023-11-28T00:00:00 Office for Coastal Management processor Collected and Processed Lidar Fugro originator The dataset has been mosaiced, reprojected, and clipped as needed from the original input files using PDAL and GDAL commands. 2026-07-02NOAA Office for Coastal Managementcoastal.info@noaa.govprocessor