| 2007 USGS Lidar: Canyon Fire (CA) | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:49639 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: 2007 USGS Lidar: Canyon Fire (CA) alternateTitle: ca2007_usgs_canyon_fire_m5028_metadata date: (CI_Date) date: 2013-01 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 49639 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/49639 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 Southern California Light Detection and Ranging (LiDAR) data is to provide high accuracy LIDAR data. These datasets will be the initial acquisition to support FEMA and other Federal Response to the Southern California Wild Fires. LIDAR data is remotely sensed high-resolution elevation data collected by an airborne collection platform. By positioning laser range finding with the use of 1 second GPS with 100hz inertial measurement unit corrections; Terrapoint's LIDAR instruments are able to make highly detailed geospatial elevation products of the ground, man-made structures and vegetation. The LiDAR flightlines for this project were planned for a 55% acquisition overlap. The nominal resolution of this project without overlap is 0.57m. Four returns were recorded for each pulse in addition to an intensity value. GPS Week Time, Intensity, Flightline and number attributes were recorded for each LiDAR point. Positional values were recorded to the centimeter level, while GPS is recorded to a 10th of a millisecond. Scan angle was recorded to the nearest angle, Intensity is recorded as an 8 Bit integer value and echo is recorded as an integer valuefrom 1 to 4. Data is provided as random points, in LAS v1.2 format, classified according to the following ASPRS Class Codes: Class 1 Unclassified Class 2 Ground Class 7 Noise Class 9 Water Please note all LiDAR points outside of the task order area was classified as Unclassified (Class 1). This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: This data was collected to support emergency relief for the wildfires in the Canyon (47.7 square kilometers), in Southern California, December, 2007 credit: U.S. Geological Survey 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) asNeeded graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/5028/supplemental/ca2007_usgs_canyon_fire_m5028.kmz fileDescription: This graphic shows the lidar coverage of the canyon fire area in California from 2007. fileType: kmz descriptiveKeywords: (MD_Keywords) keyword: California type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: US DOC, 1987, Codes for Identification of the States, Wash, DC and outlying areas of US and associated areas, Fed Info Processing Standard (FIPS) 5-2: Wash, DC, NIST. date: (missing) descriptiveKeywords: (MD_Keywords) keyword: US type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: US DOC, 1995, Countries, dependencies, areas of special sovereignty, and their principal admin divisions, Fed Info Processing Standard (FIPS) 10-4: Wash DC, NIST. date: (missing) 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]: 2007 USGS Lidar: Canyon Fire (CA) [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49639. 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 Northrop Grumman, USGS, 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: 49639 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49639.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 environmentDescription: Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.1.4000 extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -118.777719 eastBoundLongitude: -118.764501 southBoundLatitude: 34.029936 northBoundLatitude: 34.040941 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2007-12-02 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/5028/supplemental/ca2007_usgs_canyon_fire_m5028.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=5028 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/5028/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: According to Terrapoint standards; the following aspects of the LiDAR data was verified during the course of the project processing: -Data accuracy and errors -Anomaly checks through full-feature hillshades -Post automated classification Bare-earth verification -Final quality control of deliverable products ensuring integrity, graphical quality result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: Compiled to meet 1 meter horizontal accuracy at the 95 percent confidence level result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: Independent accuracy testing was performed by Dewberry using 8 high accuracy quality control checkpoints distributed throughout the project on near level open bare terrain, gravel roads, concrete pads, roads, parking lots. Dewberry used testing procedures consistent with those specified in the National Standard for Spatial Data Accuracy (NSSDA) resulting in a tested accuracy of 0.072 m at 95 percent confidence level. Terrapoint conducted a primary internal check that gave a vertical accuracy of 0.149 meters at 95 percent confidence level. ; Quantitative Value: 0.072 meters, Test that produced the value: This LiDAR dataset was tested to have an RMSEz of 0.072 m (calculated from a Fundamental Vertical Accuracy at 95 percent confidence). Consolidated Vertical Accuracy of 0.705 m (RMSEz (0.036 m) x 1.9600). result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: According to Terrapoint standards, data completeness and integrity was verified. Conformance to Terrapoint standards are met for all delivered products. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: All LAS formatted LIDAR data are validated to ensure that data on delivery media is in correct physical format and is readable and correctly georeferenced and projected. Note that LiDAR intensity is not calibrated or normalized. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: - Airborne GPS Kinematic Airborne GPS kinematic data was processed on-site using GrafNav kinematic On-The-Fly (OTF) software. Flights were flown with a minimum of 6 satellites in view (13o above the horizon) and with a PDOP of better than 3.5. Distances from base station to aircraft (differential baselines) were kept to a maximum of 30 km while the mean is 6.8 km, to ensure a strong OTF (On-The-Fly) solution. For all flights, the GPS data can be classified as excellent, with GPS residuals of 5cm average but no larger than10 cm being recorded. - Generation and Calibration of laser points (raw data) The initial step of calibration is to verify availability and status of all needed GPS and Laser data against field notes and compile any data if not complete. Subsequently the mission points are output using Optech's Dashmap, initially with default values from Optech or the last mission calibrated for system. The initial point generation for each mission calibration is verified within Microstation/Terrascan for calibration errors. If a calibration error greater than specification is observed within the mission, the roll pitch and scanner scale corrections that need to be applied are calculated. The missions with the new calibration values are regenerated and validated internally once again to ensure quality. All missions are validated against the adjoining missions for relative vertical biases and collected GPS kinematic ground truthing points for absolute vertical accuracy purposes. On a project level, a coverage check is carried out to ensure no slivers are present. dateTime: DateTime: 2007-12-01T00:00:00 processStep: (LI_ProcessStep) description: - Data Classification and Editing The data was processed using the software TerraScan, and following the methodology described herein. The initial step is the setup of the TerraScan project, which is done by importing client provided tile boundary index (converted to the native UTM zone for processing)encompassing the entire project areas. The 3D laser point clouds, in binary format, were imported into the TerraScan project and divided in 495 USGS DOQQ derived tiles in LAS 1.0 format. Once tiled, the laser points were classified using a proprietary routine in TerraScan. This routine removes any obvious outliers from the dataset following which the ground layer is extracted from the oint 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 is 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 an iteration. A second critical parameter is the maximum terrain angle constraint, which determines the maximum terrain angle allowed within the classification model. The data is then manually quality controlled with the use of hillshading, cross-sections and profiles. Any points found to be of class vegetation, building or error during the quality control process, are removed from the ground model and placed on the appropriate layer. An integrity check is also performed simultaneously to verify that ground features such as rock cuts, elevated roads and crests are present. Once data has been cleaned and complete, it is then by a supervisor via manual inspection and through the use of a hillshade mosaic of the entire project area. - Deliverable Product Generation >Deliverable Tiling Scheme All files were converted to LAS 1.1, in the specified projection and units and were delivered in the client provided tiling scheme with a total of 128 tiles. >LAS 1.1 Files LiDAR point data in LAS 1.1 ASPRS classfication scheme Class 1 Non-ground Class 2 Ground Class 7 Noise Class 9 Water Contains the following fields of information: Class, GPS WeekTime, Easting, Northing, Elevation, Echo Number, Echo, Intensity, Flightline, Scan Angle All points outside project area were assigned to Class 1 - Non-Ground (Unclassified). dateTime: DateTime: 2007-12-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 NAD83 UTM Zone 15 Coordinates and were vertically referenced to NAVD88 using the Geoid09 model. The vertical units of the data were meters. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The LAS files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid03. 2. The LAS files were converted from UTM Zone 11 (meters) to Geographic coordinates (decimal degrees). 3. The LAS files were converted to Adjusted GPS time rather than the delivered GPS week seconds (1457). dateTime: DateTime: 2016-03-20T00: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-01T07:33:02 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |