| 2023 Maryland Lidar: Charles County, MD | referenceSystemInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:75409 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: 2025-05-06T18:03:48 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 18N 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/6347/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:6347 version: 6.18.3 return to top spatialRepresentationInfo: return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2023 Maryland Lidar: Charles County, MD alternateTitle: md2023_charles_m10312_metadata date: (CI_Date) date: 2023 dateType: (CI_DateTypeCode) creation date: (CI_Date) date: 2023-10-23 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 75409 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/75409 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/10312/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://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=10327/details/10327 protocol: WWW:LINK-1.0-http--link name: Custom DEM Download description: Link to custom download, from the Data Access Viewer (DAV), the raster Digital Elevation Model (DEM) data that were created from these lidar point data. 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?m=10312&g=geoid18 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: Original Product: These lidar data are processed Classified LAS 1.4 files, formatted to individual 4000 ft x 6000 ft tiles clipped to the DPA; used to create intensity images, 3D breaklines, and hydro-flattened DEMs. Original Dataset Geographic Extent: Charles County Maryland, covering approximately 477 square miles. Original Dataset Description: The 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.7 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification. The data was developed based on a horizontal projection/datum of NAD83 (2011), Maryland State Plane, Feet and vertical datum of NAVD88 (GEOID18), Feet. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to 644 individual 4000 ft x 6000 ft tiles clipped to the DPA, as tiled Intensity Images and as tiled bare-earth DEMs; all tiled to the same 4000 ft x 6000 ft schema. Original Dataset Ground Conditions: Lidar was collected in March 2023, 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, Sanborn Map Company, Inc., established a total of 11 ground control points that were used to calibrate the lidar to known ground locations established throughout the project area. An additional 53 independent accuracy check points, 31 in Bare Earth and Urban landcovers (31 NVA points), 22 in Tall Grass and Brushland/Low Trees categories (22 VVA points), were used to assess the vertical accuracy of the data. These check points were not used to calibrate or post process the data. This metadata record references the data downloaded by the NOAA Office for Coastal Management (OCM) and processed to make it available for custom download from the NOAA Digital Coast Data Access Viewer (DAV) and for bulk download from S3 AWS. 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 DEM. The purpose of these lidar data was to produce high accuracy 3D hydro-flattened Digital Elevation Model (DEM) with a 2 ft cell size. These lidar point cloud data were used to create intensity images, 3D breaklines, hydro-flattened DEMs, and all-return MSHRs as necessary. credit: Sanborn Map Company, Inc., Charles County, MD, MD DoIT (Department of Information Technology) 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-06-05 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 graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/10312/supplemental/md2023_charles_m10312.kmz fileDescription: This graphic shows the lidar coverage for the 2023 Charles County, MD lidar project. fileType: kmz 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 > MARYLAND 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: 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 2025-06-05 from the NOAA system. Cite As: OCM Partners, [Date of Access]: 2023 Maryland Lidar: Charles County, MD [Data Date Range], https://www.fisheries.noaa.gov/inport/item/75409. 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 otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2025-06-05 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-06-05 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-06-05 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: 2023 Maryland Lidar DEM: Charles County, MD date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 75713 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: 75409 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/75409.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: Riegl RiProcess; GeoCue; Windows 10 Operating System extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -77.275966 eastBoundLongitude: -76.670576 southBoundLatitude: 38.253521 northBoundLatitude: 38.691466 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: Date of data collection | Currentness: Ground Condition timePosition: 2023-03-08 supplementalInformation: CONTRACTOR: Sanborn Map Company, Inc. The following are the USGS lidar fields in JSON: { "ldrinfo" : { "ldrspec" : "U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v2.1", "ldrsens" : "Leica TerrainMapper", "ldrmaxnr" : "15", "ldrnps" : "0.67", "ldrdens" : "2.25", "ldranps" : "0.5", "ldradens" : "5.3", "ldrfltht" : "3300", "ldrfltsp" : "160", "ldrscana" : "40", "ldrscanr" : "86.6", "ldrpulsr" : "710", "ldrpulsd" : "4", "ldrpulsw" : "0.77", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.25", "ldrswatw" : "2402", "ldrswato" : "20", "ldrgeoid" : "National Geodetic Survey (NGS) Geoid18" }, "ldraccur" : { "ldrchacc" : "0.5", "rawnva" : "0.0", "rawnvan" : "0", "clsnva" : "0.0", "clsnvan" : "0", "clsvva" : "0.0", "clsvvan" : "0" }, "lasinfo" : { "lasver" : "1.4", "lasprf" : "6", "laswheld" : "Withheld (ignore) points were identified in these files using the standard LAS Withheld bit.", "lasolap" : "Swath "overage" points were not identified in these files using the standard LAS overlap bit.", "lasintr" : "16", "lasclass" : { "clascode" : "1", "clasitem" : "Processed, but Unclassified" }, "lasclass" : { "clascode" : "2", "clasitem" : "Bare Earth Ground" }, "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" } }} 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=10312/details/10312 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/10312/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Bulk download of data files in LAZ format, geographic 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: Vertical Positional Accuracy evaluationMethodDescription: This data set was tested to meet ASPRS Positional Accuracy Standard for Digital Geospatial Data (2014) for a 10 cm RMSEz Vertical Accuracy Class. 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 data passes Non-Vegetated Vertical Accuracy specifications. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Data covers the pilot specified for this project. result: (missing) lineage: (LI_Lineage) statement: Data were collected by the Sanborn Mapping Company for Charles County, MD. The data were downloaded from the MD DoIT site by the NOAA Office for Coastal Management (OCM) and processed to make it available for custom download from the NOAA Digital Coast Data Access Viewer (DAV) and for bulk download from S3 AWS. processStep: (LI_ProcessStep) description: The boresight was completed prior to project execution. The following steps describe the Raw Data Processing process: 1) Technicians processed the raw data to LAS format flight lines using the final GNSS/IMU solution. This LAS data set was used as source data for lidar matching. 2) Technicians utilized commercial and proprietary software packages to analyze how well flight line overlaps match for the entire lift and adjusted as necessary until the results met the project specifications. 3) Once all lifts were completed with lidar matching, 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 6 cm RMSEz within individual swaths and less than or equal to 8 cm RMSEz or within swath overlap (between adjacent swaths). 4) The technicians ran a final vertical accuracy check of the flight lines against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification v2.1, and breaklines were collected for water features. Bare-earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening. dateTime: DateTime: 2023-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 Class 2 (Ground) lidar data inside of the Lake Pond and Double Line Drain hydro-flattened breaklines were then classified to Class 9 (Water) using LP360 functionality. A buffer of 2 ft was also used around each hydro-flattened feature to classify these Class 2 (Ground) points to Class 20 (Ignored Ground). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the Class 2 (Ground) points were reclassified to the correct classification after the automated classification was completed. All data was manually reviewed and any remaining artifacts removed using functionality provided by LP360, TerraScan and TerraModeler. Global Mapper was used as a final check of the bare-earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files. Sanborn Map Company, Inc. 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: 2023-01-01T00:00:00 processStep: (LI_ProcessStep) description: Data was tested at 0.5 meter aggregate nominal pulse spacing and at 5.3 aggregate points per meter. The aggregate nominal pulse spacing was tested on classified tiled LAS using geometrically reliable first-return points without overlap. ANPS was tested using Delaunay Triangulation that produced average point spacing between all nearest neighbors. dateTime: DateTime: 2023-01-01T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) downloaded laz point data files from the Maryland Department of Information Technology (DoIT). The data were in Maryland State Plane (NAD83 2011), US feet coordinates and NAVD88 (Geoid18) elevations in feet. The data were classified as: 1 - Unclassified, 2 - Ground, 7 - Low Noise, 9 - Water, 17 - Bridge Decks, 18 - High Noise, 20 - Ignored Ground. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV), the classes available on the DAV are: 1, 2, 9, 17, 20. 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. Internal OCM scripts were run on the laz files to: a. Convert from orthometric (NAVD88) elevations to NAD83 (2011) ellipsoid elevations using the Geoid18 model b. Convert the laz files from Maryland State Plane (NAD83 2011), US feet coordinates to geographic coordinates c. Convert the laz files from elevations in feet to elevations in meters. d. Remove Class 7 and 18 points because the withheld bit flag was set. e. Assign the geokeys, sort the data by gps time and zip the data to database and to S3 AWS. dateTime: DateTime: 2025-03-27T00:00:00 processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) sourceCitation: (CI_Citation) title: LAZ Files from the MD DoIT - Block 1 date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: MD iMAP contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://doitdataservices.maryland.gov/s/N9xGBYPKq4QSZNq/download?path=%2FCharles%20County%2F2023%2FLAS&files=Block1.zip protocol: WWW:LINK-1.0-http--link name: LAZ Files from the MD DoIT for Block 1 description: Source Citation URL function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) publisher source: (LI_Source) sourceCitation: (CI_Citation) title: LAZ Files from the MD DoIT - Block 2 date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: MD iMAP contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://doitdataservices.maryland.gov/s/N9xGBYPKq4QSZNq/download?path=%2FCharles%20County%2F2023%2FLAS&files=Block2.zip protocol: WWW:LINK-1.0-http--link name: LAZ Files from the MD DoIT for Block 2 description: Source Citation URL function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) publisher source: (LI_Source) sourceCitation: (CI_Citation) title: LAZ Files from the MD DoIT - Block 3 date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: MD iMAP contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://doitdataservices.maryland.gov/s/N9xGBYPKq4QSZNq/download?path=%2FCharles%20County%2F2023%2FLAS&files=Block3.zip protocol: WWW:LINK-1.0-http--link name: LAZ Files from the MD DoIT for Block 3 description: Source Citation URL function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) publisher source: (LI_Source) sourceCitation: (CI_Citation) title: LAZ Files from the MD DoIT - Block 4 date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: MD iMAP contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://doitdataservices.maryland.gov/s/N9xGBYPKq4QSZNq/download?path=%2FCharles%20County%2F2023%2FLAS&files=Block4.zip protocol: WWW:LINK-1.0-http--link name: LAZ Files from the MD DoIT - Block 4 description: Source Citation URL function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) publisher source: (LI_Source) sourceCitation: (CI_Citation) title: LAZ Files from the MD DoIT - Block 5 date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: MD iMAP contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://doitdataservices.maryland.gov/s/N9xGBYPKq4QSZNq/download?path=%2FCharles%20County%2F2023%2FLAS&files=Block5.zip protocol: WWW:LINK-1.0-http--link name: LAZ Files from the MD DoIT for Block 5 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: 2025-06-05 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |