| 2025 SCDVA Lidar: Charleston County, SC | referenceSystemInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:78496 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset hierarchyLevelName: Elevation contact: (CI_ResponsibleParty) organisationName: Office for Coastal Management 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: 2025-12-12T19:19:08 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 17N 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/6346/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:6346 version: 6.18.3 return to top spatialRepresentationInfo: return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2025 SCDVA Lidar: Charleston County, SC alternateTitle: sc2025_chs_cnty_m13754 date: (CI_Date) date: 2025 dateType: (CI_DateTypeCode) creation date: (CI_Date) date: 2025 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 78496 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/78496 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/13754/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/13754/supplemental/Charleston_County_2025_LiDAR_Report.pdf protocol: WWW:LINK-1.0-http--link name: Lidar Report description: Link to the Woolpert lidar 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/13754/breaklines/index.html protocol: WWW:LINK-1.0-http--link name: Breaklines description: Link to the breaklines in Esri gdb and OGC GeoPackage formats. 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/13754/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: BERKELEY, CHARLESTON, ORANGEBURG LIDAR DATA COLLECTION Lidar Data Acquisition and Processing Production Task - Charleston County Contract Number: 6004 RFQ Number: 6004-25C Woolpert Order No: 10020258 CONTRACTOR: Woolpert Lidar data is a remotely sensed high-resolution elevation data collected by an airborne platform. The lidar sensor uses a combination of laser range finding, GPS positioning, and inertial measurement technologies. The lidar systems collect data point clouds that are used to produce highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures, and vegetation. This task order requires lidar data to be acquired over Charleston County (+/- 1,197 square miles). This lidar data set is comprised of lidar point cloud data, raster DEMs, raster DSMs, raster intensity imagery, and GPS flight line trajectory data. The task required the lidar data to be collected at a nominal pulse spacing (NPS) of 1.15 feet. The lidar dataset was produced using a horizontal datum/projection of NAD83, State Plane South Carolina, International Feet and a vertical datum of NAVD88 (Geoid 18), International Feet. Tidal areas in Charleston's data acquisition were collected within +/- 2 hours of low tide. Additional deliverables include control data and tile index in Esri shapefile format, lidar processing and survey reports in PDF format, and project-level FGDC CSDGM metadata in XML format. This data was provided to the NOAA Office for Coastal Management (OCM) by the Charleston County Public Works Department, 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: The objective of this effort is to acquire new Light Detection and Ranging (lidar) data for Charleston County Public Works in association with Joint Base Charleston, via a Military Enhancement Grant Program. Charleston, Berkeley and Orangeburg counties will receive a copy of their county's data and Joint Base Charleston receives a full set of data. This data is being delivered in typical formats used by the Air Force installation mapping, visualization, and operations initiative known as GeoBase. credit: South Carolina Department of Veteran's Affairs (SCDVA), Charleston County Public Works Department 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 2025-12-30 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: 17.0 descriptiveKeywords: (MD_Keywords) keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > SOUTH CAROLINA keyword: VERTICAL LOCATION > LAND SURFACE type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Location Keywords date: (missing) edition: 20.8 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: 17.2 descriptiveKeywords: (MD_Keywords) keyword: Airplane > Airplane type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) edition: 17.2 descriptiveKeywords: (MD_Keywords) keyword: DOC/NOAA/NOS/OCM > Office of Coastal Management, National Ocean Service, NOAA, U.S. Department of Commerce type: (MD_KeywordTypeCode) dataCentre thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Data Center Keywords date: (CI_Date) date: 2017-04-24 dateType: (CI_DateTypeCode) publication edition: 8.5 citedResponsibleParty: GCMD Landing Page descriptiveKeywords: (MD_Keywords) keyword: Lidar 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 2025-12-30 from the NOAA system. Cite As: Office for Coastal Management, [Date of Access]: 2025 SCDVA Lidar: Charleston County, SC [Data Date Range], https://www.fisheries.noaa.gov/inport/item/78496. 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 2025-12-30 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 2025-12-30 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 2025-12-30 from the NOAA system. Distribution Liability: The information contained in these data is dynamic and may change over time. The data are not better than the original sources from which they were derived. It is the responsibility of the data user to use the data appropriately and within the limitations of the data for which it was requested and prepared, in general, and these data in particular. The related graphics are intended to aid the data user in acquiring relevant data. It is not appropriate to use the related graphics as data. Woolpert gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of these data. It is strongly recommended that these data are directly acquired from a Woolpert server, and not indirectly through other sources which may have changed the data in some way. Although these data have been processed successfully upon Woolpert's computer system, no warranty, expressed or implied, is made regarding the utility of the data on another system, or for general or scientific purposes; nor shall the act of distribution constitute any such warranty. This disclaimer applies both to individual use of the data and aggregate use with other data. 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 SCDVA Lidar DEM: Charleston County, SC date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 77722 associationType: (DS_AssociationTypeCode) crossReference 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: 78496 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocm/dmp/pdf/78496.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 10 Version 1607 (Build 14393.2189); ArcMap 10.4; ArcCatalog 10.4; TerraScan ver. 17; TerraModeler ver. 17; Geocue 2017.2.20.0. extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -80.46342 eastBoundLongitude: -79.26 southBoundLatitude: 32.46 northBoundLatitude: 33.22 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2025-01-12 endPosition: 2025-01-30 return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: LAS/LAZ - LASer version: (missing) fileDecompressionTechnique: LAZ distributionFormat: (MD_Format) name: (inapplicable) version: (missing) fileDecompressionTechnique: Zip 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://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/13754/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Bulk download of data files in LAZ format, SC State Plane NAD83 international feet coordinates and elevations in NAVD88 (GEOID18) feet. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=13754/details/13754 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 return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The project specifications require that vertical accuracy be computed for raw lidar point cloud swath files. The required accuracy is less than or equal to 0.492 feet RMSEz. Accuracy was tested with 15 checkpoints. The checkpoints were distributed throughout the project area and were surveyed using GPS techniques. Elevations from the unclassified lidar surface were measured for the x,y location of each check point. Elevations interpolated from the lidar surface were then compared to the elevation values of the surveyed control points. The tested vertical accuracy was 0.180 ft RMSE (or 5.5 cm RMSE). result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: The lidar data is visually inspected for completeness to ensure that are no void areas or missing data. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: All formatted data cover the entire area specified for this project and are validated using a combination of commercial lidar processing software, GIS software, and proprietary programs to ensure proper formatting and loading prior to delivery. result: (missing) lineage: (LI_Lineage) statement: This data was provided to the NOAA Office for Coastal Management (OCM) by the Charleston County Public Works Department, for the purpose of making the data publicly available for custom and bulk downloads from the NOAA Digital Coast Data Access Viewer. processStep: (LI_ProcessStep) description: Ground Control Points: Woolpert utilized 3 Trimble Navigation R12i Model GNSS dual-frequency GPS receivers, and 3 TSC7 data collectors for this project. The purpose of this survey was to establish three-dimensional coordinates for 31 NVA (non-vegetated vertical accuracy point), 21 VVA (vegetated vertical accuracy point), and 13 LiDAR control points. The points were collected per the flight layout and were uniformly dispersed over the project area. The field crew utilized Real-Time Kinematic (RTK) GPS surveying throughout the ground control data collection process. Using RTK GPS techniques, observations were performed on a total of 13 LiDAR control points, 31 NVA (non-vegetated vertical accuracy point), 21 VVA (vegetated vertical accuracy point). The survey was conducted using a 1-second epoch rate, in a fixed solution RTK mode, with each observation lasting between 60 to 180 seconds. Each station was occupied twice to insure the necessary horizontal and vertical accuracies were being met for this LiDAR / photogrammetric project. The “Virtual Reference Station” (VRS) concept is based on having a network (spaced at 50-60kms) of GNSS (GPS or GPS/GLONASS) reference stations permanently connected to the control center via the Internet. The networked stations collectively and precisely, model ionospheric errors for the individual GNSS rover in the network coverage area. The rover interprets and uses the VRS network-correction data as if it is operating with a single physical base station on a very short baseline which increases the RTK performance. Corrections (vectors) are from the closest base, but because the ionospheric error (which is traditionally baseline dependent) is practically negated, the rover's degradation in accuracy due to baseline length starts when the rover is first initialized, that is, at the work site. Thus, accuracies are increased and more consistent throughout the working region The field crew chief processed all session baselines each day using Trimble Navigation’s Trimble Business Center (TBC) Version 2024.10 baseline processor with the accompanying broadcast ephemeris. Daily processing ensured the integrity of the network as it was constructed and allowed the field crews to immediately reschedule observations of poor baselines. The spatial reference system for all the AOI’s is South Carolina State Plane. The datum shall be NAD83 (2011) epoch 2010.00 horizontal. Orthometric heights referenced to Geoid 18. Units for both the horizontal and vertical datums will be expressed in International Feet to three (3) decimal places. Existing NGS published benchmarks were surveyed to assure that there were no discrepancies in the field observation data. Close examinations of the residuals showed no distortions in orientation or scale. The ground control data meets positional accuracies necessary to support 1.0 point per 0.3 meters squared (1’ GSD) data at 95% confidence level as outlined in the Geospatial Positioning Accuracy Standards, Part 3: National Standard for Spatial Data Accuracy (NSSDA), published by the Federal Geographic Data Committee (FGDC-STD-007.3-1998). dateTime: DateTime: 2025-06-01T00:00:00 processStep: (LI_ProcessStep) description: Airborne Lidar Data: The lidar data was acquired with a Leica City Mapper Airborne Lidar System (S/N 95519), onboard Woolpert’s aircraft. The Leica City Mapper system, developed by Leica of Herrburgg, Switzerland includes the simultaneous first, intermediate and last pulse data capture module, the extended altitude range module, and the target signal intensity capture module. dateTime: DateTime: 2025-06-01T00:00:00 processStep: (LI_ProcessStep) description: Lidar Calibration: The individual flight lines were inspected to ensure the systematic and residual errors have been identified and removed. Then, the flight lines were compared to adjacent flight lines for any mismatches to obtain a homogeneous coverage throughout the project area. dateTime: DateTime: 2025-06-01T00:00:00 processStep: (LI_ProcessStep) description: LAS Point Cloud Classification: The point cloud underwent a classification process to determine bare-earth points and non-ground points utilizing "first and only" as well as "last of many" lidar returns. This process determined Default (Class 1), Ground (Class 2), Overlap Default (Class 12). The bare-earth (Class 2 - Ground) lidar points underwent a manual QA/QC step to verify the quality of the DEM as well as a peer-based QC review. This included a review of the DEM surface to remove artifacts and ensure topographic quality. The overlap class was determined by first identifying the overlapping areas and reclassifying the LAS data by offset from a corridor. This allows the returns located on the edge of the swath to be removed from the bare earth coverage in an effort to produce a more uniform data density. dateTime: DateTime: 2025-06-01T00:00:00 processStep: (LI_ProcessStep) description: Vertical Adjustments: The surveyed ground control points are used to make vertical adjustments to the data set and to perform the accuracy checks and statistical analysis of the lidar dataset. Supervisory QC monitoring of work in progress and completed editing ensured consistency of classification character and adherence to project requirements across the entire project area. dateTime: DateTime: 2025-06-01T00:00:00 processStep: (LI_ProcessStep) description: Tile Index: A tile index with a tile size of 2,500-feet by 2,500-feet was created in Esri shapefile format. dateTime: DateTime: 2025-06-01T00:00:00 processStep: (LI_ProcessStep) description: Deliverable Creation: The resulting deliverables for this task order consist of classified lidar point cloud data in LAS 1.4 format, 2-foot bare-earth digital elevation (DEM) data tiles in ERDAS IMG format, 2-foot digital surface model (DSM) data in raster data tiles in ERDAS IMG format, and 2-foot 8-bit intensity imagery tiles in GeoTIFF format. dateTime: DateTime: 2025-06-01T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received 5327 las files from the Charleston County Public Works Department. The files were in SC State Plane NAD83 international feet coordinates and the elevations were in NAVD88 (GEOID18) international feet. The LAS files had these classifications: 1 = unclassified; 2 = ground (or Bare Earth); 5 = vegetation; 6 = buildings; 9 = water; 17 = bridges; 20 = ignored ground. NOAA OCM processed all of the point classes to the Digital Coast Data Access Viewer (DAV). OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Internal OCM scripts were run to check the number of points by classification and by flight ID and the gps, elevation, and intensity ranges. 2. The LAS files were converted to LAZ format using laszip 3. Internal OCM scripts were run on the LAZ files to: a. Convert from orthometric (NAVD88) elevations to ellipsoid elevations using the GEOID18 model b. Convert from SC State Plane NAD83 international feet coordinates to geographic coordinates c. Convert from elevations in feet to elevations in meters d. Assign the geokeys, to sort the data by gps time and zip the data to database and to AWS S3. dateTime: DateTime: 2025-12-12T00: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) description: Source Contribution: This data source was used to georeference and perform accuracy testing on the lidar point cloud data. sourceCitation: (CI_Citation) title: Ground Control Points date: (CI_Date) date: 2025-06-01 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Woolpert role: (inapplicable) sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimePeriod: beginPosition: 2025-01-12 endPosition: 2025-01-30 source: (LI_Source) description: Source Contribution: This data source was used to create the classified lidar point cloud data. sourceCitation: (CI_Citation) title: Raw Lidar Point Cloud Data date: (CI_Date) date: 2025-06-01 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Woolpert role: (inapplicable) sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimePeriod: beginPosition: 2025-01-12 endPosition: 2025-01-30 source: (LI_Source) description: Source Contribution: This data set was used to create tiled deliverable products. sourceCitation: (CI_Citation) title: Tile Index date: (CI_Date) date: 2025-06-01 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Woolpert role: (inapplicable) sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimePeriod: beginPosition: 2025-01-12 endPosition: 2025-01-30 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: 2025-12-30 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |