| 2014 USGS Lidar: Central Virginia Seismic (Louisa County) | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:50136 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset contact: (CI_ResponsibleParty) organisationName: OCM Partners contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (missing) address: (CI_Address) role: (CI_RoleCode) resourceProvider contact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2022-08-09T17:11:38 metadataStandardName: ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data metadataStandardVersion: ISO 19115-2:2009(E) return to top spatialRepresentationInfo: return to top referenceSystemInfo: return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(2011) date: (CI_Date) date: 2008-11-12 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: European Petroleum Survey Group contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://apps.epsg.org/api/v1/CoordRefSystem/6318/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:6318 version: 6.18.3 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters alternateTitle: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters citedResponsibleParty: (CI_ResponsibleParty) organisationName: (withheld) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://apps.epsg.org/api/v1/VerticalCoordRefSystem/5703/?api_key=gml name: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters description: Link to Geographic Markup Language (GML) description of reference system. function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) resourceProvider citedResponsibleParty: (CI_ResponsibleParty) organisationName: European Petroleum Survey Group contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.epsg.org/ name: European Petroleum Survey Group Geodetic Parameter Registry description: Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured dataset of Coordinate Reference Systems and Coordinate Transformations. function: (CI_OnLineFunctionCode) search role: (CI_RoleCode) publisher VerticalCS: metaDataProperty: CommonMetaData: type: vertical informationSource: OGP revisionDate: 2006-11-28 isDeprecated: false identifier: urn:ogc:def:cs:EPSG::6499 name: Vertical CS. Axis: height (H). Orientation: up. UoM: meter. remarks: Used in vertical coordinate reference systems. axis: CoordinateSystemAxis: descriptionReference: urn:ogc:def:axis-name:EPSG::9904 identifier: urn:ogc:def:axis:EPSG::114 axisAbbrev: H axisDirection: up code: urn:ogc:def:crs:EPSG::5703 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2014 USGS Lidar: Central Virginia Seismic (Louisa County) alternateTitle: va2014_usgs_louisa_m4922_metadata date: (CI_Date) date: 2015-07-23 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 50136 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/50136 protocol: WWW:LINK-1.0-http--link name: Full Metadata Record description: View the complete metadata record on InPort for more information about this dataset. function: (CI_OnLineFunctionCode) information role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer protocol: WWW:LINK-1.0-http--link name: Citation URL description: Online Resource function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: Citation URL description: Online Resource function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (unknown) abstract: Laser Mapping Specialist, Inc (LMSI) collected 230 square miles in the Virginia counties of Fluvanna, Orange, Louisa, and Spotsylvania. The nominal pulse spacing for this project was no greater than 0.7 meters. Dewberry used proprietary procedures to classify the LAS into an initial ground surface. 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 both UTM and State Plane coordinates. The data was formatted according to tiles with each UTM tile covering an area of 1,500 meters by 1,500 meters and each State Plane tile covering an area of 5,000 feet by 5,000 feet. A total of 320 UTM tiles and 313 State Plane tiles were produced for the project encompassing an area of approximately 230 sq. miles. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. 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 and 2.5 foot cell size for State Plane. All products follow and comply with USGS Program Lidar Base Specification Version 1.0. status: (MD_ProgressCode) completed pointOfContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact pointOfContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) custodian resourceMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) asNeeded graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4922/supplemental/va2014_usgs_louisa_m4922.kmz fileDescription: The project area addressed by this report falls within the Virginia county of Louisa with actual data edges falling within Fluvanna, Goochland, and Spotsylvania. fileType: kmz descriptiveKeywords: (MD_Keywords) keyword: Surface keyword: Terrain type: (MD_KeywordTypeCode) theme descriptiveKeywords: (MD_Keywords) keyword: 2013 keyword: March type: (MD_KeywordTypeCode) temporal descriptiveKeywords: (MD_Keywords) keyword: Lidar - partner (no harvest) type: (MD_KeywordTypeCode) project thesaurusName: (CI_Citation) title: InPort date: (inapplicable) resourceConstraints: (MD_LegalConstraints) useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: Cite As: OCM Partners, [Date of Access]: 2014 USGS Lidar: Central Virginia Seismic (Louisa County) [Data Date Range], https://www.fisheries.noaa.gov/inport/item/50136. resourceConstraints: (MD_Constraints) useLimitation: 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. resourceConstraints: (MD_LegalConstraints) accessConstraints: (MD_RestrictionCode) otherRestrictions useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: Access Constraints: None | Use Constraints: This data was produced for the USGS according to specific project requirements. This information is provided "as is". Further documentation of this data can be obtained by contacting: USGS/NGTOC, 1400 Independence Road, Rolla, MO 65401. Telephone (573) 308-3587. 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. These data depict the heights at the time of the survey and are only accurate for that time. | Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of USGS, Dewberry, NOAA, the Office for Coastal Management or its partners. resourceConstraints: (MD_SecurityConstraints) classification: (MD_ClassificationCode) unclassified classificationSystem: (missing) handlingDescription: (missing) aggregationInfo: (MD_AggregateInformation) aggregateDataSetName: (CI_Citation) title: NOAA Data Management Plan (DMP) date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 50136 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/50136.pdf protocol: WWW:LINK-1.0-http--link name: NOAA Data Management Plan (DMP) description: NOAA Data Management Plan for this record on InPort. function: (CI_OnLineFunctionCode) information role: (inapplicable) associationType: (DS_AssociationTypeCode) crossReference spatialRepresentationType: (MD_SpatialRepresentationTypeCode) vector language: eng; US topicCategory: (MD_TopicCategoryCode) elevation extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -78.15526 eastBoundLongitude: -77.707851 southBoundLatitude: 37.766376 northBoundLatitude: 38.140154 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2014-05-06 endPosition: 2014-05-07 supplementalInformation: A complete description of this dataset is available in the Final Project Report submitted to the USGS is available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4922/supplemental/va2014_usgs_louisa_m4922_lidarreport.pdf A complete description of this dataset is available in the Survey Report submitted to the USGS is available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4922/supplemental/va2014_usgs_louisa_m4922_surveyreport.pdf A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4922/supplemental/va2014_usgs_louisa_m4922.kmz return to top contentInfo: (MD_FeatureCatalogueDescription) complianceCode: false language: LanguageCode: eng includedWithDataset: false featureCatalogueCitation: (CI_Citation) title: none date: (unavailable) return to top distributionInfo: (MD_Distribution) distributor: (MD_Distributor) distributorContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) distributor transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=4922 protocol: WWW:LINK-1.0-http--link name: Customized Download description: Create custom data files by choosing data area, product type, map projection, file format, datum, etc. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4922/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Simple download of data files. function: (CI_OnLineFunctionCode) download return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: The DEMs are derived from the source LiDAR and 3D breaklines created from the LiDAR. Horizontal accuracy is not performed on the DEMs or breaklines. Lidar source compiled to meet 1 meter horizontal accuracy.; Quantitative Value: 1.0 meters, Test that produced the value: The DEMs are derived from the source LiDAR and 3D breaklines created from the LiDAR. Horizontal accuracy is not performed on the DEMs, breaklines, or LiDAR. LiDAR vendors perform calibrations on the LiDAR sensor and compare data to adjoing flight lines to ensure LiDAR meets the 1 meter horizontal accuracy standard at the 95% confidence level. Please see the final project report delivered to the USGS for more details. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The DEMs are derived from the source LiDAR and 3D breaklines created from the LiDAR. The DEMs are created using controlled and tested methods to limit the amount of error introduced during DEM production so that any differences identified between the source LiDAR and final DEMs can be attributed to interpolation differences. DEMs are created by averaging several LiDAR points within each pixel which may result in slightly different elevation values at a given location when compared to the source LAS, which does not average several LiDAR points together but may interpolate (linearly) between two or three points to derive an elevation value. The vertical accuracy of the DEMS were tested by Dewberry with 62 independent survey checkpoints. The survey checkpoints were evenly distributed throughout the project area and were located in areas of bare earth and open terrain (21), urban terrain (20), and forest (21). The vertical accuracy is tested by comparing survey checkpoints to the final elevation values of the bare earth DEM surface. 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 will be used to compute the Fundamental Vertical Accuracy (FVA). Project specifications required a FVA of 18.2 cm based on a RMSEz 9.25 cm x 1.9600. All checkpoints will be used to compute the Consolidated Vertical Accuracy (CVA). Project specifications required a CVA of 26.9 cm 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 26.9 cm 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.; Quantitative Value: 0.125 meters, Test that produced the value: Based on the vertical accuracy testing conducted by Dewberry, 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 Central Virginia Seismic LiDAR project satisfies the criteria: DEM dataset tested 0.125 m vertical accuracy at 95% confidence level in open terrain, based on RMSEz (0.064 m) x 1.9600.; Quantitative Value: 0.17 meters, Test that produced the value: Based on the vertical accuracy testing conducted by Dewberry, using NDEP and ASPRS methodology, consolidated vertical accuracy (CVA) is computed using the 95th percentile method. The dataset for the Central Virginia Seismic LiDAR project satisfies the criteria: DEM dataset tested 0.17 m consolidated vertical accuracy at 95th percentile in all land cover categories combined. The 5% outliers consist of 4 checkpoints that are larger than the 95th percentile. These checkpoints have DZ values between 0.166 and 0.356 m.; Quantitative Value: 0.17 meters, Test that produced the value: Based on the vertical accuracy testing conducted by Dewberry, using NDEP and ASPRS methodology, supplemental vertical accuracy (SVA) is computed using the 95th percentile method. The dataset for the Central Virginia Seismic LiDAR project satisfies the criteria: DEM dataset tested 0.17 m supplemental vertical accuracy at 95th percentile in the forested and fully grown land cover category.; Quantitative Value: 0.31 meters, Test that produced the value: Based on the vertical accuracy testing conducted by Dewberry, using NDEP and ASPRS methodology, supplemental vertical accuracy (SVA) is computed using the 95th percentile method. The dataset for the Central Virginia Seismic LiDAR project satisfies the criteria: DEM dataset tested 0.31 m supplemental vertical accuracy at 95th percentile in the urban land cover category. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: A visual qualitative assessment was performed to ensure data completeness and full tiles. No void or missing data exists. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Data covers the tile scheme provided for the project area. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: Data for the Central Virginia Seismic LiDAR project was acquired by PAR using a ALTM NAV Flight Plan Optech ALTM3100EA LiDAR system Piper Navajo Aircraft. LIDAR acquisition began on May 6, 2014 (julian day 126) and was completed on May 7, 2014 (julian day 127). A total of 2 survey missions were flown to complete the project. PAR utilized a Lecia ALS70-CM for the acquisition. 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 186 flight lines required to complete the project. The calibrated data was processed to NAD83(2011) UTM 17, meters, NAVD88 (Geoid12A), meters. One base station was utilized VA_21. The base station coordinates are set forth below: VA_21 Latitude: 28 00 25.25513 Longitude: -77 58 24.21356 Ellipsoid Height: 112.461 Orthometric Height: 144.7978 4 kinematic cross sections and 11 static points were surveyed at various locations throughout the project to be utilized for quality control and adjustment of the LIDAR data. All airborne GPS trajectories were processed and checked on site. All trajectories were very high quality with forward/reverse separation rms between 1cm-3cm. All equipment performed within specifications with no unusual occurrences or anomalies. All data was of a very high quality and the project was executed as planned. Overall the LiDAR data products collected for Dewberry and Davis meet or exceed the requirements set out in the Statement of Work for this project. The quality control requirements of PARs Quality management program were adhered to throughout the acquisition stage of this project to ensure product quality. dateTime: DateTime: 2014-05-01T00:00:00 processStep: (LI_ProcessStep) 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 Dewberry 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 1 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 . This class 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) dateTime: DateTime: 2014-07-01T00:00:00 processStep: (LI_ProcessStep) description: Dewberry used GeoCue software to develop raster stereo models from the LiDAR intensity. The raster resolution was 0.3 meters. dateTime: DateTime: 2014-07-01T00:00:00 processStep: (LI_ProcessStep) description: LiDAR intensity stereopairs were viewed in 3-D stereo using Socet Set for ArcGIS softcopy photogrammetric software. The breaklines are collected directly into an ArcGIS file geodatabase to ensure correct topology. The LiDARgrammetry was performed under the direct supervision of an ASPRS Certified Photogrammetrist. The breaklines were stereo-compiled in accordance with the Data Dictionary. Inland Lakes and Ponds were collected according to specifications for the Central VA Seismic LiDAR Project. The data dictionary defines Inland Ponds and Lakes as a closed water body feature that is at a constant elevation. These polygon features should be collected at the land/water boundaries of constant elevation water bodies such as lakes, reservoirs, and ponds. Features shall be defined as closed polygons and contain an elevation value that reflects the best estimate of the water elevation at the time of data capture. Water body features will be captured for features 2 acres in size or greater. Donuts will exist where there are islands greater than 1/2 acre in size within a closed water body. Breaklines must be captured at or just below the elevations of the immediately surrounding terrain. Under no circumstances should a feature be elevated above surrounding LiDAR points. The compiler shall take care to ensure that the z-value remains consistent for all vertices placed on the water body. No Inland Streams, Rivers or Tidal Waters met the collection requirements within the project area. dateTime: DateTime: 2014-07-01T00:00:00 processStep: (LI_ProcessStep) description: Breaklines are reviewed against LiDAR intensity imagery to verify completeness of capture. All breaklines are then compared to ESRI terrains created from ground only points prior to water classification. The horizontal placement of breaklines is compared to terrain features and the breakline elevations are compared to LiDAR elevations to ensure all breaklines match the LiDAR within acceptable tolerances. Some deviation is expected between breakline and LiDAR elevations due to monotonicity, connectivity, and flattening rules that are enforced on the breaklines. Once completeness, horizontal placement, and vertical variance is reviewed, all breaklines are reviewed for topological consistency and data integrity using a combination of ESRI Data Reviewer tools and proprietary tools. Corrections are performed within the QC workflow and re-validated. dateTime: DateTime: 2014-07-01T00:00:00 processStep: (LI_ProcessStep) description: Class 2, ground, LiDAR points are exported from the LAS files into an Arc Geodatabase (GDB) in multipoint format. The 3D breaklines, Inland Lakes and Ponds are imported into the same GDB. An ESRI Terrain is generated from these inputs. The surface type of each input is as follows: Ground Multipoint: Masspoints Inland Lakes and Ponds: Hard Replace dateTime: DateTime: 2014-08-01T00:00:00 processStep: (LI_ProcessStep) description: The ESRI Terrain is converted to rasters. The rasters are created to pre-defined extents so that multiple rasters are created over the project area. Creating multiple rasters rather than one large raster over a large project area makes the data more maneageable to work with. The rasters are created with 2 tiles of overlap. This allows us to ensure seamless coverage and edge-matching in the final tiled product. These rasters were created with a 1 meter cell size. dateTime: DateTime: 2014-08-01T00:00:00 processStep: (LI_ProcessStep) description: The DEMs that are created over large areas are reviewed in ArcGIS with hillshades and in Global Mapper. Hillshades allow the analyst to view the DEMs in 3D and to more efficiently locate and identify potential issues. The first review is done on the area DEMs as this increases the efficiency of any corrections that may be performed. Performing corrections on area DEMs allows the analyst to perform corrections on multiple tiles at once and helps prevent errors from occurring along individual tile seamlines. Analysts review the area DEMs for incorrect water elevations and artifacts that are introduced during the raster creation process. dateTime: DateTime: 2014-08-01T00:00:00 processStep: (LI_ProcessStep) description: The corrected and final area DEMs are clipped to individual tiles. Dewberry uses a proprietary tool that clips the area DEMs to each tile located within the final Tile Grid, names the clipped DEM to the Tile Grid Cell name, and verifies that final extents are correct. All individual tiles are loaded into Global Mapper for the last review. During this last review, an analsyt checks to ensure full, complete coverage, no issues along tile boundaries, tiles seamlessly edge-match, and that there are no remaining processing artifacts in the dataset. dateTime: DateTime: 2014-08-01T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received the topographic/bathymetric files in LAS format from the University of William and Mary's Center for Geospatial Analysis. A number of LAS files were found to have corrupt GPS times and other unknown factors affecting header information. The files contained lidar easting, northing, elevation, intensity, return number, etc. The data was received in UTM coordinates, zone 18 North, referenced to the NAVD88 for vertical using the Geoid09 model. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The LAS files were converted to geographic horizontal coordinates and ellipsoidal vertical coordinates. 2. The LAS files were cleared of error points and variable length records removed. dateTime: DateTime: 2015-07-01T00:00:00 processStep: (LI_ProcessStep) description: The vertical values in this data set have been converted to reference North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters, using the GEOID18 grids provided by the National Geodetic Survey. Any datum and projection transformations were then done with the Office for Coastal Management 'datum_shift' program. Compression to an LAZ file was done with the LAStools 'laszip' program and can be unzipped with the same free program (laszip.org) Processing notes: dateTime: DateTime: 2023-08-01T05:47:11 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |