| 2012 USGS Lidar: Central Virginia Seismic (Louisa County) | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:50131 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: 2012 USGS Lidar: Central Virginia Seismic (Louisa County) alternateTitle: va2012_usgs_louisa_m2620_metadata date: (CI_Date) date: 2015-07-10 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 50131 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/50131 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: USGS Contract: G10PC00013 Task Order Number: G12PD00264 Prepared for USGS, Prepared by: Dewberry, 1000 Ashley Blvd., Suite 801, Tampa, Florida 33602-3718 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,000 meters by 1,000 meters and each State Plane tile covering an area of 2,500 feet by 2,500 feet. A total of 797 UTM tiles and 1,338 State Plane tiles were produced for the project encompassing an area of approximately 277 sq. miles. Classified points include: Class 1 (unclassified), Class 2 (ground), Class 7 (noise), Class 9 (water), Class 10 (ignored ground due to breakline proximity). This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: The primary purpose of this project was to develop a consistent and accurate surface elevation dataset derived from high-accuracy Light Detection and Ranging (LiDAR) technology for the USGS Louisa, Virginia Project Area. 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/2620/supplemental/va2012_usgs_louisa_m2620.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]: 2012 USGS Lidar: Central Virginia Seismic (Louisa County) [Data Date Range], https://www.fisheries.noaa.gov/inport/item/50131. 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: 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: 50131 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/50131.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.14545 eastBoundLongitude: -77.71609 southBoundLatitude: 37.7704 northBoundLatitude: 38.13649 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2012-03-09 endPosition: 2012-03-12 supplementalInformation: A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2620/supplemental/va2012_usgs_louisa_m2620.kmz A final project report is available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2620/supplemental/va2012_usgs_louisa_m2620_finalreport.pdf A qa/qc report is available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2620/supplemental/va2012_usgs_louisa_m2620_qualityreport.pdf An acquisition report is available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2620/supplemental/va2012_usgs_louisa_m2620_acquisitionreport.pdf 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=2620 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/2620/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: Not tested; Quantitative Value: 1.0 meters, Test that produced the value: Not tested, assuming 1.0 m result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: For the Louisa, Virginia LiDAR Project, all checkpoints were located in Open Terrain land cover type. The tested RMSEz for checkpoints in open terrain equaled 0.07 m compared with the 0.125 m specification; and the FVA computed using RMSEz x 1.9600 was equal to 0.13 m, compared with the 0.245 m specification. For the Louisa, Virginia LiDAR Project, the tested CVA computed using the 95th percentile was equal to 0.12 m, compared with the 0.363 m specification.; Quantitative Value: 0.13 meters, Test that produced the value: FVA computed using RMSEz x 1.9600 was equal to 13 cm result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: A visual qualitative assessment was performed to ensure data completeness and bare earth data cleanliness. No void or missing data, the bare earth surface is of good quality and data passes vertical accuracy specifications 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: Report completed: August 03, 2012; used as process date below. LiDAR mass points were produced to LAS 1.2 specifications, including the following LAS classification codes: Class 1 = Unclassified, and used for all other features that do not fit into the Classes 2, 7, 9, or 10, including vegetation, buildings, etc.; Class 2 = Ground, includes accurate LiDAR points in overlapping flight lines; Class 7 = Noise, low and high points; Class 9 = Water, points located within collected breaklines; Class 10 = Ignored Ground due to breakline proximity. The data was processed using GeoCue and TerraScan software. The initial step is the setup of the GeoCue project, which is done by importing a project defined tile boundary index encompassing the entire project area. The acquired 3D laser point clouds, in LAS binary format, were imported into the GeoCue project and tiled according to the project tile grid. Once tiled, the laser points were classified using a proprietary routine in TerraScan. This routine classifies any obvious outliers in the dataset to class 7. After points that could negatively affect the ground are removed from class 1, the ground layer is extracted from this remaining point cloud. The ground extraction process encompassed in this routine takes place by building an iterative surface model. This surface model is generated using three main parameters: building size, iteration angle and iteration distance. The initial model is based on low points being selected by a roaming window with the assumption that these are the ground points. The size of this roaming window is determined by the building size parameter. The low points are triangulated and the remaining points are evaluated and subsequently added to the model if they meet the iteration angle and distance constraints. This process is repeated until no additional points are added within iterations. A second critical parameter is the maximum terrain angle constraint, which determines the maximum terrain angle allowed within the classification model. The following fields within the LAS files are populated to the following precision: GPS Time (0.000001 second precision), Easting (0.003 meter precision), Northing (0.003 meter precision), Elevation (0.003 meter precision), Intensity (integer value - 12 bit dynamic range), Number of Returns (integer - range of 1-4), Return number (integer range of 1-4), Scan Direction Flag (integer - range 0-1), Classification (integer), Scan Angle Rank (integer), Edge of flight line (integer, range 0-1), User bit field (integer - flight line information encoded). The LAS file also contains a Variable length record in the file header that defines the projection, datums, and units. dateTime: DateTime: 2012-08-03T00:00:00 processStep: (LI_ProcessStep) description: Once the initial ground routine has been performed on the data, Dewberry creates Delta Z (DZ) orthos to check the relative accuracy of the LiDAR data. These orthos compare the elevations of LiDAR points from overlapping flight lines on a 1 meter pixel cell size basis. If the elevations of points within each pixel are within 5 cm of each other, the pixel is colored green. If the elevations of points within each pixel are between 5 cm and 10 cm of each other, the pixel is colored yellow, and if the elevations of points within each pixel are greater than 10 cm in difference, the pixel is colored red. Pixels that do not contain points from overlapping flight lines are colored according to their intensity values. DZ orthos can be created using the full point cloud or ground only points and are used to review and verify the calibration of the data is acceptable. Some areas are expected to show sections or portions of red, including terrain variations, slope changes, and vegetated areas or buildings if the full point cloud is used. However, large or continuous sections of yellow or red pixels can indicate the data was not calibrated correctly or that there were issues during acquisition that could affect the usability of the data. The DZ orthos for Louisa, Virginia showed that the data was calibrated correctly with no issues that would affect its usability. The figure below shows an example of the DZ orthos. Dewberry utilized a variety of software suites for data processing. The LAS dataset was received and imported into GeoCue task management software for processing in Terrascan. Each tile was imported into Terrascan and a surface model was created to examine the ground classification. Dewberry analysts visually reviewed the ground surface model and corrected errors in the ground classification such as vegetation, buildings, and bridges that were present following the initial processing conducted by Dewberry. Dewberry analysts employ 3D visualization techniques to view the point cloud at multiple angles and in profile to ensure that non-ground points are removed from the ground classification. 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 hydro features. The water classification routine selects ground points within the breakline polygons and automatically classifies them as class 9, water. The final classification routine applied to the dataset selects ground points within a specified distance of the water breaklines and classifies them as class 10, ignored ground due to breakline proximity. dateTime: DateTime: 2012-08-03T00: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: 2014-07-22T00: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-07-01T06:32:38 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |