| 2010 U.S. Geological Survey (USGS) Topographic LiDAR: San Francisco Bay, California | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:50115 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(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 U.S. Geological Survey (USGS) Topographic LiDAR: San Francisco Bay, California alternateTitle: usgs2010_SanFranBay_m1406_metadata date: (CI_Date) date: 2011-03 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 50115 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/50115 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) presentationForm: (unknown) abstract: 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 San Francisco Coastal LiDAR project area. The LiDAR data were processed to a bare-earth digital terrain model (DTM). Detailed breaklines and bare-earth DEMs were produced for the project area. Data was formatted according to tiles with each tile covering an area of 1500 m by 1500 m. A total of 712 tiles were produced for the project encompassing an area of approximately 610 sq. miles. This metadata relates to LAS that were classified in the following classes: Class 1 = Unclassified. This class includes vegetation, buildings, noise etc. Class 2 = Ground Class 7= Noise Class 9 = Water Class 10= Ignored Ground (due to proximity to breakline) Original contact information: Contact Name: Robert Kelly Contact Org: USGS Title: USGS NGTOC Phone: (573) 308-3612 Email: ckelly@usgs.gov 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 and 2 m cell size hydro flattened Digital Elevation Models (DEMs). 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/1406/supplemental/usgs2010_SanFranBay_Footprint.KMZ fileDescription: This graphic shows the lidar coverage for the San Francisco Bay Area, California. fileType: kmz 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 U.S. Geological Survey (USGS) Topographic LiDAR: San Francisco Bay, California [Data Date Range], https://www.fisheries.noaa.gov/inport/item/50115. 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 Terrapoint, 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: 50115 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/50115.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 7 Professional; ESRI ArcCatalog 10.0 extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -123.029672 eastBoundLongitude: -121.894576 southBoundLatitude: 37.384922 northBoundLatitude: 38.14676 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2010-06-11 endPosition: 2011-03-04 supplementalInformation: The final report for this data set may be accessed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1406/supplemental/usgs2010_SanFranBay_ProjectReport.pdf The survey control report for this data set may be accessed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1406/supplemental/usgs2010_SanFranBay_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/1406/supplemental/usgs2010_SanFranBay_Footprint.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=1406 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/1406/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: Dewberry does not perform horizontal accuracy on the LiDAR. Compiled to meet 2.0 meter horizontal accuracy at the 95 percent confidence level by Terrapoint. ; Quantitative Value: 2.0 meters, Test that produced the value: Dewberry does not perform horizontal accuracy on the LiDAR. Compiled to meet 2.0 meter horizontal accuracy at the 95 percent confidence level by Terrapoint. Please see the final project report delivered to the USGS for more details. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: Vertical Lidar data accuracy was tested against 21 independently surveyed check points. The result of the test is an RMSEz = 0.06 meters (0.12 meters at 95 percent confidence level). ; Quantitative Value: 0.06 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 USGS San Francisco Coastal LiDAR project satisfies the criteria: Lidar dataset tested 0.12 meters vertical accuracy at 95% confidence level for all land cover types, based on consolidated RMSEz (0.06 m) x 1.9600. 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: - Establishment of survey points to support the LiDAR data collection. Three existing published CGPS stations (CHAB, P181, P222) were observed in a GPS control network and used to establish three new points for the primary control for this site. 101U01,101U02, 101U04,AY0887 and AY1499 were observed and used to control all flight missions and static ground surveys. The following are the final coordinates of the control points used for this project: Station Id;Latitude;Longitude;Easting;Northing;Ellipsoidal_Height; 1010601; 37 30 52.26391; -122 29 41.86434; -16.6617 1010602; 37 27 16.57733; -122 06 37.48309; -29.7404 1010603; 37 39 48.24857; -122 07 23.10831; -23.1470 1010604; 37 59 35.03464; -122 03 44.26783; -26.2030 1010605; 37 59 49.29391; -122 45 33.01378; 50.3610 dateTime: DateTime: 2010-11-01T00:00:00 processStep: (LI_ProcessStep) description: - Airborne acquisition of Lidar Terrapoint used one Optech ALTM 3100EA system to collect the data. The Optech System was configured in the following method: Aircraft Speed 150 knots Data Acquisition Height 1300 m AGL Swath Width 755 m Distance between Flight Lines 377 m Overlap 50 % Scanner Field Of View 19.2 +/- degrees Pulse Repetition Rate 70 KHz LiDAR Scan Frequency 38.7 Hz Number of Returns per Pulse 4 Discrete returns Beam Divergence 0.3 mRad Flight Line Length <30km Base Station Distance <35km Resultant Raw Point Density ~2 point pt/m2 with overlap 2 missions (o110292a, o110293a) were flown at higher altitude with different parameters to accommodate air traffic control restrictions Aircraft Speed 125 knots Data Acquisition Height 2300 m AGL Overlap 50 % Scanner Field Of View 15 +/- degrees Pulse Repetition Rate 50 KHz LiDAR Scan Frequency 25.5 Hz Number of Returns per Pulse 4 Discrete returns Beam Divergence 0.3 mRad Resultant Raw Point Density ~2 point pt/m2 with overlap Aircraft platforms were used in the collection of this project: A Piper Navaho aircraft, registered as FVTL was used to conduct the aerial survey. The Navaho is a fixed wing aircraft that have an endurance of approximately 6-7 hours. -GPS-IMU: High accuracy IMU and GPS information concerning the attitude and position of the sensor were acquired at the same time as the Laser data. Ground based GPS stations also acquired consecutive GPS information for the duration of the flights. A combination of Sokkia GSR 2600 and NovAtel DL-4+ dual-frequency GPS receivers were used to support the airborne operations of this survey. -Number of Flights A total of 14 missions were flown total under good meteorological and GPS conditions to provide complete coverage. The LiDAR data were collected under tidal restrictions at or below Mean Lower Low Water. 10 missions were acquired during spring 2010 (between June 11, 2010 and June 30, 2010) and 4 missions were acquired during fall (between October 19, 2010 and November 7, 2010) dateTime: DateTime: 2010-01-01T00:00:00 processStep: (LI_ProcessStep) description: - Airborne GPS Kinematic processing 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 4. Distances from base station to aircraft were kept to a maximum of 30 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 3cm average but no larger than 10 cm being recorded. The Geoid09 geoid model, published by the NGS, was used to transform all ellipsoidal heights to orthometric. dateTime: DateTime: 2010-01-01T00:00:00 processStep: (LI_ProcessStep) description: - Generation and Calibration of laser points Laser data points are generated using Terrapoint's proprietary laser post-processing software for Midrange data and using Optech's software Dashmap for data acquired with Optech systems. Those software combine the raw laser range and angle data file with the finalized GPS/IMU trajectory information. Each mission is evaluated in Terrasolid's Terramatch software to correct any residual roll pitch heading misalignments, if necessary those values are to the data. The resulting point cloud is projected into the desired coordinate system and created in LAS format. One file per swath. On a project level, a coverage check is carried out to ensure no slivers are present. dateTime: DateTime: 2010-01-01T00:00:00 processStep: (LI_ProcessStep) description: - Mission to mission adjustments of Lidar data All missions are validated and adjusted against the adjoining missions for relative vertical biases and collected GPS kinematic ground truthing points for absolute vertical accuracy purposes. The following adjustments were applied to the data (vertical shifts in meters, + means raise the Lidar points and - means lower the Lidar points) o110163a, Dz= 0.05 o110164a, Dz= 0.15 o110173a, Dz= -0.25 o110178a, Dz= -0.1 o110179a, Dz= 0.05 o110292a, Dz= 0.2 o110293a, Dz= 0.2 o110305a, Dz= 0.2 o110306a line 30608 - 30615, Dz= 0.15 o110306a line 30616 - 30623, Dz= 0.2 o110306a line 30602 - 30607, Dz= 0.05 dateTime: DateTime: 2010-01-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 project defined tile boundary index encompassing the entire project areas. The acquired 3D laser point clouds, in LAS binary format, were imported into the TerraScan project and divided into file size optimized tiles. 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 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 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 iteration. A second critical parameter is the maximum terrain angle constraint, which determines the maximum terrain angle allowed within the classification model. dateTime: DateTime: 2010-11-01T00:00:00 processStep: (LI_ProcessStep) description: -Deliverable Product Generation >Tiling Index Classified point cloud products were delivered in 695 tiles based on provided a tile scheme given by the client. >Raw LIDAR Point Cloud Raw LiDAR point cloud, was provided in the following formats/parameters: - LAS V1.2, point record format 1, georeferencing information populated in header - The following fields are included in the LAS file: 1. Adjusted GPS time reported to the nearest microsecond 2. Flight line ID 3. Easting (reported to the nearest 0.01m) 4. Northing (reported to the nearest 0.01m) 5. Elevation (reported to the nearest 0.01m) 6. intensity 7. Echo number 8. Classification 9. Scan angle 10. Edge of scan 11. Scan direction - Full swaths, all collected points delivered (except planned cut-off and discarded flightline) - 1 file per swath, 1 swath per file (except when swath had to be divided in section for size or calibration) >Classified LIDAR Point Cloud, tiled Classified LiDAR point cloud, was provided in the following formats/parameters: - LAS V1.2, point record format 1, georeferencing information populated in header - The LAS files adhere to the ASPRS classification scheme as outlined below: 1 : Unclassified, 2 : Ground, 7 : Noise, - The following fields are included in the LAS file: 1. Adjusted GPS time reported to the nearest microsecond 2. Flight line ID 3. Easting (reported to the nearest 0.01m) 4. Northing (reported to the nearest 0.01m) 5. Elevation (reported to the nearest 0.01m) 6. intensity 7. Echo number 8. Classification 9. Scan angle 10. Edge of scan 11. Scan direction dateTime: DateTime: 2010-12-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. GeoCue allows the data to retain its delivered tiling scheme (1500 m by 1500 m). After the a review of the Terrapoint ground classification was 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 which are in close proximity (0.5 m) to the hydrographic features are moved to class 10, an ignored ground. In addition to classes 1, 2, 9, and 10, the project allows for 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 Ground The LAS header information was verified to contain the following: Class (Integer) GPS Week Time (0.0001 seconds) Easting (0.001 m) Northing (0.001 m) Elevation (0.001 m) Echo Number (Integer 1 to 4) Echo (Integer 1 to 4) Intensity (8 bit integer) Flight Line (Integer) LiDAR Scan Angle (Integer degree) dateTime: DateTime: 2011-03-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 UTM Zones 10 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 topographic las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid09. dateTime: DateTime: 2012-10-01T00:00:00 source: (LI_Source) description: Source Contribution: LiDAR data representing the USGS San Francisco Coastal LiDAR Task Order to be used for various analysis and research purposes. | Source Geospatial Form: map | Type of Source Media: Hard Drive sourceCitation: (CI_Citation) title: USGS San Francisco Coastal LiDAR date: (CI_Date) date: 2011-03-04 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: http://dewberry.com protocol: WWW:LINK-1.0-http--link name: Source Citation URL description: Source Citation URL function: (CI_OnLineFunctionCode) information role: (inapplicable) sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimePeriod: beginPosition: 2010-06-11 endPosition: 2011-03-04 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-01T05:51:15 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |