| 2025 Lidar: San Francisco Bay - Delta Estuary, CA | referenceSystemInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:80225 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset hierarchyLevelName: Elevation 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: 2026-07-23T15:42:45 metadataStandardName: ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data metadataStandardVersion: ISO 19115-2:2009(E) return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(2011) / UTM zone 10N 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/6339/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:6339 version: 6.18.3 return to top spatialRepresentationInfo: return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2025 Lidar: San Francisco Bay - Delta Estuary, CA alternateTitle: ca2025_sanfran_m14673 date: (CI_Date) date: 2025 dateType: (CI_DateTypeCode) creation date: (CI_Date) date: 2026 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 80225 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/80225 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://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/14673/ept.json protocol: WWW:LINK-1.0-http--link name: Entwine Point Tile (EPT) description: Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/14673/supplemental/San_Francisco_Baylands_LiDAR_Control_Survey_Report.pdf protocol: WWW:LINK-1.0-http--link name: Survey Report description: Link to the Guida Geospatial Solutions survey report function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/14673/supplemental/San_Francisco_Baylands_LiDAR_StatePlane_FOCUS_On_Accuracy.pdf protocol: WWW:LINK-1.0-http--link name: NV5 Accuracy Report description: Link to the NV5 FOCUS On Accuracy report function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/14673/supplemental/SFEI_SanFrancisco_Baylands_StatePlane_Lidar_Report.pdf protocol: WWW:LINK-1.0-http--link name: Lidar Report description: Link to the NV5 lidar report function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/lidar/viewer/v/noaapotree.html?r=https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/14673/ept.json protocol: WWW:LINK-1.0-http--link name: Potree 3D View description: Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer function: (CI_OnLineFunctionCode) download 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: NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) description: The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer. function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (unknown) abstract: Product: These lidar data are processed Classified LAS 1.4 files, formatted to individual 600 m x 600 m tiles; used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary. Geographic Extent: Parts of 14 counties in California, covering approximately 2097 total square miles. These counties are: Alameda, Contra Costa, Marin, Napa, Sacramento, San Francisco, San Joaquin, San Mateo, Santa Clara, Solano, Sonoma, Stanislaus, Sutter, Yolo. Dataset Description: The SanFrancisco_Baylands_Lidar project called for the planning, acquisition, processing, and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.29 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification, 2024 Rev. A. LiDAR data were delivered as processed Classified LAS 1.4 files formatted to individual 600 m x 600 m tiles, as tiled intensity imagery, and as tiled bare earth DEMs; all tiled to the same 600 m x 600 m schema. Continuous breaklines were produced in Esri file geodatabase format. Ground Conditions: LiDAR was collected in summer and fall 2025, while no snow was on the ground and rivers were at or below normal levels. In order to post process the LiDAR data to meet task order specifications and meet ASPRS vertical accuracy guidelines, NV5 Geospatial utilized a total of 51 ground control points that were used to calibrate the LiDAR to known ground locations established throughout the project area. An additional 115 independent accuracy checkpoints, 84 in Bare Earth and Urban landcovers (84 NVA points), 31 in Tall Weeds categories (31 VVA points), were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data. These data were provided to the NOAA Office for Coastal Management (OCM) from the San Francisco Estuary Institute (SFEI) for the purpose of making the data publicly available for custom and bulk downloads from the NOAA Digital Coast Data Access Viewer. This data set contains point cloud data(' in LAZ (compressed LAS) format', ''). The data may have been reprojected or otherwise modified from the original data in an automated process. Disregard projection information in this abstract and refer to the spatial reference section. purpose: To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments and elevation modeling, etc. Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create intensity images, breaklines and raster DEMs. The purpose of these LiDAR data was to produce high accuracy 3D hydro-flattened digital elevation models (DEMs) with a 1 foot cell size. These raw LiDAR point cloud data were used to create classified LiDAR LAS files, intensity images, 3D breaklines, and hydro-flattened DEMs as necessary. credit: Lidar collected with funding support from the Wetlands Regional Monitoring Program (awarded by the San Francisco Bay Restoration Authority), the Delta Stewardship Council, the California Department of Water Resources, the South Bay Salt Pond Restoration Project, and Valley Water (Santa Clara County). The project was jointly managed by the San Francisco Estuary Institute, California Department of Water Resources, and the Delta Stewardship Council. 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 2026-07-26 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) notPlanned descriptiveKeywords: (MD_Keywords) keyword: EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION keyword: EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Science Keywords date: (missing) edition: 23.3 descriptiveKeywords: (MD_Keywords) keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > CALIFORNIA keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > CALIFORNIA > SAN FRANCISCO keyword: VERTICAL LOCATION > LAND SURFACE type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Location Keywords date: (missing) edition: 23.3 descriptiveKeywords: (MD_Keywords) keyword: LIDAR > Light Detection and Ranging type: (MD_KeywordTypeCode) instrument thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Instrument Keywords date: (missing) edition: 23.3 descriptiveKeywords: (MD_Keywords) keyword: Airplane > Airplane type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) edition: 23.3 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: This data set was compiled dynamically. It will be removed 10 days after 2026-07-26 from the NOAA system. Cite As: OCM Partners, [Date of Access]: 2025 Lidar: San Francisco Bay - Delta Estuary, CA [Data Date Range], https://www.fisheries.noaa.gov/inport/item/80225. 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) useConstraints: (MD_RestrictionCode) license otherConstraints: Anchor: Universal (CC0 1.0) Public Domain Dedication To the extent possible under law, the U.S. Government has waived all copyright and related or neighboring rights to this dataset. resourceConstraints: (MD_LegalConstraints) accessConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2026-07-26 from the NOAA system. Access Constraints: None resourceConstraints: (MD_LegalConstraints) useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2026-07-26 from the NOAA system. 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. resourceConstraints: (MD_LegalConstraints) useLimitation: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2026-07-26 from the NOAA system. Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of 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: 2025 Lidar DEM (Hydro-flattened): San Francisco Bay - Delta Estuary, CA date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 80207 associationType: (DS_AssociationTypeCode) crossReference spatialRepresentationType: (MD_SpatialRepresentationTypeCode) vector language: eng; US topicCategory: (MD_TopicCategoryCode) elevation environmentDescription: MicroStation Connect; TerraScan Version 21.016; STRIPALIGN 2.21 ; TerraModeler Version 21.008; GeoCue Version 2020.1.22.1; Esri ArcGIS 10.6; Global Mapper 19/20; RiProcess 1.8.6; Windows 10 Operating System \\point_cloud\tilecls\*.las extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -122.667695313 eastBoundLongitude: -121.19246 southBoundLatitude: 37.362077 northBoundLatitude: 38.789152706 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2025-08-22 endPosition: 2025-10-06 supplementalInformation: CONTRACTOR: NV5 Geospatial The following are the USGS lidar fields in JSON: { "ldrinfo " :{ "ldrspec " :" USGS-NGP Base Specification 2024 Rev. A ", "ldrsens " :" Riegl VQ1560iiS ", "ldrmaxnr " :" unlimited ", "ldrnps " :" 0.29 ", "ldrdens " :" 12.0 ", "ldranps " :" 0.29 ", "ldradens " :" 12.0 ", "ldrfltht " :" 2067 ", "ldrfltsp " :" 145 ", "ldrscana " :" 29 ", "ldrscanr " :" 250 ", "ldrpulsr " :" 1882 ", "ldrpulsd " :" 3 ", "ldrpulsw " :" 0.37 ", "ldrwavel " :" 1064 ", "ldrmpia " :" 1 ", "ldrbmdiv " :" 0.18 ", "ldrswatw " :" 2292.0 ", "ldrswato " :" 50 ", "ldrgeoid " :" Geoid 18 ", "ldrcrs " :" NAD 1983 2011 StatePlane California II FIPS 0402 Ft US, Foot US " }, "ldraccur " :{ "ldrchacc " :" 0 ", "rawnva " :" 0.0 ", "rawnvan " :" 0 " }, "lasinfo " :{ "lasver " :" 1.4 ", "lasprf " :" 6 ", "laswheld " :" Withheld (ignore) points were identified in these files using the standard LAS Withheld bit. ", "lasolap " :" Any overage point deemed geometrically reliable will be used within the normal classification schema. Overage points are not specifically flagged with any special bit value. ", "lasintr " :" 16 ", "lasclass " :{ "clascode " :" 1 ", "clasitem " :" Processed, but Unclassified " }, "lasclass " :{ "clascode " :" 2 ", "clasitem " :" Bare-Earth Ground " }, "lasclass " :{ "clascode " :" 3 ", "clasitem " :" Low Vegetation " }, "lasclass " :{ "clascode " :" 4 ", "clasitem " :" Medium Vegetation " }, "lasclass " :{ "clascode " :" 5 ", "clasitem " :" High Vegetation " }, "lasclass " :{ "clascode " :" 6 ", "clasitem " :" Buildings " }, "lasclass " :{ "clascode " :" 7 ", "clasitem " :" Low Noise " }, "lasclass " :{ "clascode " :" 9 ", "clasitem " :" Water " }, "lasclass " :{ "clascode " :" 17 ", "clasitem " :" Bridge Decks " }, "lasclass " :{ "clascode " :" 18 ", "clasitem " :" High Noise " }, "lasclass " :{ "clascode " :" 20 ", "clasitem " :" Ignored Ground " }, "lasclass " :{ "clascode " :" 22 ", "clasitem " :" Temporal Exclusion (if applicable) " } } } return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: (inapplicable) version: (missing) fileDecompressionTechnique: Zip distributionFormat: (MD_Format) name: LAS/LAZ - LASer version: (missing) fileDecompressionTechnique: LAZ 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=14673 /details/14673 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. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/14673/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Bulk download of data files in LAZ format, projected coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document. They will be in an orthometric datum. 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: This data set was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 13 (cm) RMSEh Horizontal Accuracy Class which equates to Positional Horizontal Accuracy = +/- 22 cm at a 95% confidence level. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The specifications require that only nonvegetated vertical accuracy (NVA) be computed for raw LiDAR data swath files. The vertical accuracy was tested with 84 independent survey points located in open terrain. These check points were not used in the calibration or post processing of the LiDAR data. The survey check points were distributed throughout the project area. The survey check points were distributed throughout the project area. The 84 independent check points were surveyed using GPS techniques. See survey report for additional survey methodologies. Elevations from the unclassified LiDAR surface were measured for the x,y location of each checkpoint. Elevations interpolated from the LiDAR surface were then compared to the elevation values of the surveyed control points. The root mean square error vertical (RMSEz) was computed to be 0.0345 meters. AccuracyZ has been tested to meet 19.0 cm NVA at 95-percent confidence level using (RMSEz * 1.9600) as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using American Society of Photogrammetry and Remote Sensing (ASPRS) Guidelines. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: These LAS data files include all data points collected. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The raw point cloud is of good quality and the data pass Non-Vegetated Vertical Accuracy specifications. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Data cover the entire area specified for this project. result: (missing) lineage: (LI_Lineage) statement: The NOAA Office for Coastal Management (OCM) received the LAZ files from the San Francisco Estuary Institute (SFEI). processStep: (LI_ProcessStep) description: Raw Data and Boresight Processing: The boresight for each lift was done individually as the solution may change slightly from lift to lift. The following steps describe the Raw Data Processing and Boresight process: 1) Technicians processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source data for boresight. 2) Technicians first used NV5 Geospatial proprietary and commercial software to calculate initial boresight adjustment angles based on sample areas selected in the lift. These areas cover calibration flight lines collected in the lift, cross tie, and production flight lines. These areas are well distributed in the lift coverage and cover multiple terrain types that are necessary for boresight angle calculation. The technicians then analyzed the results and made any necessary additional adjustment until it was acceptable for the selected areas. 3) Once the boresight angle calculation was completed for the selected areas, the adjusted settings were applied to all of the flight lines of the lift and checked for consistency. The technicians utilized commercial and proprietary software packages to analyze how well flight line overlaps matched for the entire lift and adjusted as necessary until the results met the project specifications. 4) Once all lifts were completed with individual boresight adjustment, the technicians checked and corrected the vertical misalignment of all flight lines and also the matching between data and ground truth. The relative accuracy was less than or equal to 7 cm RMSEz within individual swaths and less than or equal to 10 cm RMSEz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed checkpoints after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. dateTime: DateTime: 2026-01-01T00:00:00 processStep: (LI_ProcessStep) description: LAS Point Classification: The point classification is performed as described below. The bare earth surface is then manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface is finalized, it is then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS Class 2) lidar data inside of the Lake Pond and Double Line Drain hydro flattening breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 0.5 feet was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 10). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (ASPRS Class 2) points were reclassified to the correct classification after the automated classification was completed. All overlap data was processed through automated functionality provided by TerraScan to classify the overlapping flight line data to approved classes by USGS. The overlap data was classified using standard LAS overlap bit. These classes were created through automated processes only and were not verified for classification accuracy. Due to software limitations within TerraScan, these classes were used to trip the withheld bit within various software packages. These processes were reviewed and accepted by USGS through numerous conference calls and pilot study areas. All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper us used as a final check of the bare earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files for both the All Point Cloud Data and the Bare Earth. Proprietary software was used to perform final statistical analysis of the classes in the LAS files, on a per tile level to verify final classification metrics and full LAS header information. dateTime: DateTime: 2026-01-01T00:00:00 processStep: (LI_ProcessStep) description: Maximum Surface Height Rasters were produced as ancillary data from the classified lidar point cloud in order to evaluate the withheld bit flag proof of performance for points that cannot be reasonably interpreted as valid surface returns. These were produced using all returns, withheld flagged points excluded, and using the highest elevation point value from each pixel. These rasters are 32-bit, floating point format and delivered as GeoTIFF files per tile. MSHR are generated from the point cloud data and will not be altered after creation nor will there be further maintenance on this product. dateTime: DateTime: 2026-01-01T00:00:00 processStep: (LI_ProcessStep) description: Swath Separation Imagery was produced for the entire project area. Swath separation images use color-coding to illustrate differences in elevation (z-) values where swaths overlap. The color-coded images are semi-transparent and overlay the lidar intensity image. They are ancillary data used as visual aids to more easily identify regions within point cloud datasets that may have suspect interswath alignment or other geometric issues. Imagery was created using last returns with all classification and bit flags, except for noise and withheld bit flag are included. SSI are generated from the point cloud data and will not be altered after creation nor will there be further maintenance on this product. dateTime: DateTime: 2026-01-01T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received LAZ files from the San Francisco Estuary Institute (SFEI). The data were in California State Plane Zones 2 and 3 (NAD83 2011), US survey feet coordinates and NAVD88 (Geoid18) elevations in feet. The data classes were: 1 - Unclassified, 2 - Ground, 3 - Low Vegetation ( less than or equal to 1.5 ft), 4 - Medium Vegetation (1.5 - 6.5 ft), 5 - High Vegetation (greater than or equal to 6.5 ft), 6 - Buildings, 7 - Low Noise, 9 - Water, 14 - Wires, 15 - Transmission Tower, 17 - Bridge Deck, 18 - High Noise, 20 - Ignored Ground, 22 - Temporal Exclusion, 80 - Fences, 81 - Vehicles, 90 - Poles. OCM noted that there were occurrences where vegetation is classified as buildings. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available in the DAV are: 1, 2, 3, 4, 5, 6, 7, 9, 14, 15, 17, 18, 20, 22, 80, 81, 90. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 2. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid18 model, to convert from California State Plane Zones 2 and 3 (NAD83 2011), US survey feet coordinates to geographic coordinates, and to convert from elevations in feet to meters. dateTime: DateTime: 2026-07-21T00:00:00 processor: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor source: (LI_Source) sourceCitation: (CI_Citation) title: San Francisco Estuary Institute (SFEI) LAZ Files date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: San Francisco Estuary Institute (SFEI) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.sfei.org/ protocol: WWW:LINK-1.0-http--link name: San Francisco Estuary Institute (SFEI) description: Source Citation URL function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) publisher processStep: (LI_ProcessStep) description: The dataset has been mosaiced, reprojected, and clipped as needed from the original input files using PDAL and GDAL commands. dateTime: DateTime: 2026-07-26 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor return to top acquisitionInformation: (MI_AcquisitionInformation) instrument: (MI_Instrument) identifier: (MD_Identifier) code: Riegl VQ-1560 II-S type: Lidar Sensor description: The RIEGL VQ-1560 II-S system has a rotating mirror design and high-output dual laser technology, allowing for data collection at a higher altitude and faster speed on large-scale mapping projects and corridor work. This system provides more dense, high-precision data with uniform point distribution and faster acquisition. | |