| 2010 ARC Dekalb County Georgia Lidar | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:49728 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:37 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(NSRS2007) 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/4759/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:4759 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: 2010 ARC Dekalb County Georgia Lidar alternateTitle: ga2010_arc_dekalbcounty_m2527_metadata date: (CI_Date) date: 2012-08-13 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 49728 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/49728 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: This metadata record describes the DTM comprised of classified aerial lidar elevation points, photogrammetrically compiled breaklines and the derived TIN for Dekalb County, GA Original contact information: Contact Name: Stacy Grear Contact Org: Dekalb County GIS Department Title: Acting Director Phone: 404-371-3619 Email: scgrear@dekalbcountyga.gov will change to scgrear@dekalbcountyga.gov on July 1, 2010 This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: The lidar DEM data was collected for the Dekalb County, GA area. All lidar returns were classified using the default classes of Terrascan processing software for Unclassified Points (class 1), Ground points (class 2), Water points (class 9), Overlap points (class 12). The lidar ground points are supplemented with photogrammmetrically compiled breaklines from digital imagery collected during the same project time frame as the lidar. The ground class points, often refered to as "bald earth" are then used as an input to proprietary and publicly available processing software to generate a Triangulated Irregular Network (TIN) model. Classified lidar DEMs and derived TIN models are useful for a variety of applications, such as aiding in contour generation, development of digital surface models, 3D modeling, flood plane mapping, viewshed analysis and the production of orthophotos. credit: Please credit the Deklab County GIS Department Puget with support from the Atlanta Regional Commission with this data. 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 Jul 01, 2023 at https://coast.noaa.gov/dataviewer. 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) unknown graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2527/supplemental/ga2010_dekalbcounty.KMZ fileDescription: This graphic shows the lidar coverage for the 2010 Dekalb County Lidar Survey in Georgia. fileType: kmz descriptiveKeywords: (MD_Keywords) keyword: TIN keyword: Triangulated Irregular Network keyword: mapping type: (MD_KeywordTypeCode) theme 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]: 2010 ARC Dekalb County Georgia Lidar [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49728. 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 Kucera International, ARC, USGS, 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: 49728 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49728.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: -84.35091417 eastBoundLongitude: -84.02334971 southBoundLatitude: 33.61447836 northBoundLatitude: 33.97061816 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2010-01-02 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2010-01-03 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/2527/supplemental/ga2010_dekalbcounty.KMZ A Lidar Report from the vendor for this data set may be viewed here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2527/supplemental/ga2010_dekalbcounty_QC_Report.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=2527 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/2527/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_QuantitativeAttributeAccuracy) nameOfMeasure: Accuracy evaluationMethodDescription: Attribute accuracy is tested in the LiDAR processing stage. After classification of the LiDAR data, the 'bald earth' point class is compared to ground control collected within the project area. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: Horizontal positional accuracy for LiDAR is dependent upon the quality of the GPS/INS solution, sensor calibration and ground conditions at the time of data capture. The standard system results for horizontal accuracy are less than 1 meter.; Quantitative Value: 1 meters, Test that produced the value: This value is computed by comparing ground control to an intensity based image derived from the classified LiDAR data and represents the RMSE of residuals on controls within the project area. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: Vertical positional accuracy for LiDAR is dependent upon the quality of the GPS/INS solution, sensor calibration and ground conditions at the time of data capture. The vertical accuracy for this project was tested with a resultant RMSE of 0.057 meter (0.188 feet).; Quantitative Value: 0.057 meters, Test that produced the value: This value is computed by comparing ground control elevation to the classified LiDAR ground surface and represents the RMSE of residuals on controls within the project area. Units = meters. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: LiDAR data is collected for the project area. Post processing of the simultaneously acquired GPS/INS is performed and applied to the laser returns to output a point cloud in the specified project coordinate system and datums. The point cloud data is then subjected to automated classification routines to assign all points in the point cloud to ground, water, overlap and unclassified point classes. Anomalous laser returns that occur infrequently are removed entirely from the data set. The ground class points are then compared to surveyed ground control to develop an accuracy measure of the laser terrain data. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: LiDAR data is collected within the project area, processed and verified against control. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: At selected locations throughout the site, accurate GPS coordinates and elevations are surveyed and the points are marked with targets. dateTime: DateTime: 2010-01-01T00:00:00 processStep: (LI_ProcessStep) description: New LiDAR data is captured for the project area using a Leica ALS60 LiDAR instrument in conjunction with a POSAV Applanix GPS/INS system mounted within a Piper Navajo twin engine airplane. dateTime: DateTime: 2010-01-01T00:00:00 processStep: (LI_ProcessStep) description: New aerial digital imagery with airborne GPS/IMU data is acquired for the project area. dateTime: DateTime: 2010-01-01T00:00:00 processStep: (LI_ProcessStep) description: The airborne GPS data is processed in Terratec TerraPos software and then combined with the IMU data in Applanix PosPAC software to determine the LiDAR sensor's angle and orientation in the terrain (project) coordinate system and datums during the survey. The same GPS/IMU processing is performed for the digital imagery to define the orientation parameters of the images to be used in stereo compilation of terrain breaklines. dateTime: DateTime: 2010-01-01T00:00:00 processStep: (LI_ProcessStep) description: LiDAR data is processed using the GPS/INS solution. Data is classified to produce: Class 1: unclassified points Class 2: ground points Class 9: water points Class 12: overlap points dateTime: DateTime: 2010-01-01T00:00:00 processStep: (LI_ProcessStep) description: The ground class of the processed lidar data is then compared to the ground control and elevation differences between the lidar surface and surveyed elevation are recorded in tabular form. Vertical accuracy statistices are then developed to produce vertical RMSE and overall accuracy estimates and reports. dateTime: DateTime: 2010-01-01T00:00:00 processStep: (LI_ProcessStep) description: Photogrammetrically compiled breaklines are compiled to supplement the lidar ground points. dateTime: DateTime: 2010-01-01T00:00:00 processStep: (LI_ProcessStep) description: Water polygons are buffered to remove any lidar points within the polygon to flatten these surfaces. dateTime: DateTime: 2010-01-01T00:00:00 processStep: (LI_ProcessStep) description: Breaklines are buffered to remove lidar surface points on or near the breakline. dateTime: DateTime: 2010-01-01T00:00:00 processStep: (LI_ProcessStep) description: The Traingulated Irregular Network is generate with ESRI ArcGIS software. dateTime: DateTime: 2010-01-01T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received topographic files in LAS format. The files contained lidar elevation and intensity measurements. The data were received in projected Georgia State Plane West Zone 1002 coordinates and were vertically referenced to NAVD88. The vertical units of the data were feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The LAS files were processed through a lastools program known as LASGround, where an algorithm further processes any unclassified points to the ground class, ignoring pre-exisint ground points. 2. All files were then horizontally shifted from the projected GA_W (1002) state place coordinates (in feet) to geographic NAD83 coordinates (decimal degrees) 3. All files were then vertically shifted from from orthometric NAVD88 heights (feet) to ellipsoidal NAD83 (meters) using GEOID09 (assumed based on processing date) dateTime: DateTime: 2013-08-09T00:00:00 source: (LI_Source) description: Source Contribution: New digital aerial imagery and GPS/IMU data was recorded for the defined project area. | Source Geospatial Form: Remote sensing image | Type of Source Media: disc sourceCitation: (CI_Citation) title: Aerial Digital Imagery date: (missing) sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2010-02-18 source: (LI_Source) description: Source Contribution: Targeted ground control is used to create a digital control file and control report as well as QC check of LiDAR accuracy. Predefined points (NGS when available) within the project area are targeted. | Source Geospatial Form: tabular digital data | Type of Source Media: disc sourceCitation: (CI_Citation) title: Ground control date: (CI_Date) date: 2010-01-01 dateType: (CI_DateTypeCode) publication sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2010 source: (LI_Source) description: Source Contribution: Aerial LiDAR and GPS/IMU data was recorded for the defined project area. | Source Geospatial Form: Remote sensing image | Type of Source Media: disc sourceCitation: (CI_Citation) title: LiDAR Data date: (missing) sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2010-01-02 source: (LI_Source) description: Source Contribution: Using the lidar elevation points and compiled breaklines as inputs, a Triangulated Irregular Network (TIN) is generated using ESRI ArcGIS software. | Source Geospatial Form: Vector digital data | Type of Source Media: disc sourceCitation: (CI_Citation) title: Triangulated Irregular Network date: (CI_Date) date: 2010-01-01 dateType: (CI_DateTypeCode) publication sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2010 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:12:44 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |