| Lidar for the Pocomoke and Atlantic Coastal Watersheds in Maryland | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:51633 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset hierarchyLevelName: GIS Files 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: Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (missing) address: (CI_Address) deliveryPoint: 2234 South Hobson Avenue city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: (missing) onlineResource: (CI_OnlineResource) linkage: https://www.coast.noaa.gov/ protocol: WWW:LINK-1.0-http--link name: Office for Coastal Management Website description: Website listed for Office for Coastal Management function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2024-02-29T00:00:00 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: (MD_VectorSpatialRepresentation) topologyLevel: (MD_TopologyLevelCode) geometricObjects: (MD_GeometricObjects) geometricObjectType: (MD_GeometricObjectTypeCode) point geometricObjectCount: 1149847022 return to top referenceSystemInfo: return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(HARN) / 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/3748/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:3748 version: 6.18.3 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: Lidar for the Pocomoke and Atlantic Coastal Watersheds in Maryland alternateTitle: 2011 USDA lidar: Pocomoke and Atlantic Coastal date: (CI_Date) date: 2018 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 51633 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/51633 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: http://imap.maryland.gov/Pages/lidar-download-files.aspx protocol: WWW:LINK-1.0-http--link name: Maryland iMAP description: Location of the originating point clouds. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/digitalcoast protocol: WWW:LINK-1.0-http--link name: Digital Coast description: Online Resource function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (CI_PresentationFormCode) mapDigital abstract: This Light Detection and Ranging (LiDAR) dataset is a survey of the Pocomoke and Atlantic Coastal Watersheds in Maryland. The project area consists of approximately 500 square miles. The project design of the LiDAR data acquisition was developed to support a nominal post spacing of 0.70 meter. Fugro EarthData, Inc. acquired 151 flight lines in eight lifts on February 6, 7, 9, 13, 15, and 16, 2011; in tidal areas, data was collected within 2 hours (before or after) of mean low tide. The data was divided into 1500 by 1500 meter cells that serve as the tiling scheme. LiDAR data collection was performed with a Piper Navajo twin engine aircraft, utilizing a Leica ALS60 MPiA sensor, collecting multiple return x, y, and z as well as intensity data. LiDAR data is remotely sensed high-resolution elevation data collected by an airborne collection platform. This data of the Pocomoke and Atlantic Coastal Watersheds in Maryland, was collected at sufficient resolution to provide a nominal point spacing of 0.70 meter for collected points. Up to 4 returns were recorded for each pulse in addition to an intensity value. 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 data was collected for the NRCS, whose mission is Helping People Help the Land. NRCS provides products and services that enable people to be good stewards of their soil, water, and related natural resources. With their assistance, people are better able to conserve, maintain, or improve their natural resources. credit: Fugro Earthdata, USDA-NRCS 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-25 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: Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (missing) address: (CI_Address) deliveryPoint: 2234 South Hobson Avenue city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: (missing) onlineResource: (CI_OnlineResource) linkage: https://www.coast.noaa.gov/ protocol: WWW:LINK-1.0-http--link name: Office for Coastal Management Website description: Website listed for Office for Coastal Management function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) custodian resourceMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) asNeeded descriptiveKeywords: (MD_Keywords) keyword: Maryland keyword: Pocomoke and Atlantic Coastal Watersheds type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Geographic Names Information System date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Light Detection and Ranging keyword: bare earth keyword: bare ground keyword: high-resolution type: (MD_KeywordTypeCode) theme 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-25 from the NOAA system. Cite As: OCM Partners, [Date of Access]: Lidar for the Pocomoke and Atlantic Coastal Watersheds in Maryland [Data Date Range], https://www.fisheries.noaa.gov/inport/item/51633. 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-25 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-25 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-25 from the NOAA system. Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of the State of Maryland, 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: 51633 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/51633.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 spatialResolution: (MD_Resolution) distance: Distance: .7 language: eng; US topicCategory: (MD_TopicCategoryCode) elevation extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -75.691501 eastBoundLongitude: -75.225534 southBoundLatitude: 37.952398 northBoundLatitude: 38.453581 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2011-02-01 endPosition: 2011-06-01 return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: LAS/LAZ - LASer version: (missing) fileDecompressionTechnique: Zip distributor: (MD_Distributor) distributorContact: (CI_ResponsibleParty) organisationName: Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (missing) address: (CI_Address) deliveryPoint: 2234 South Hobson Avenue city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: (missing) onlineResource: (CI_OnlineResource) linkage: https://www.coast.noaa.gov/ protocol: WWW:LINK-1.0-http--link name: Office for Coastal Management Website description: Website listed for Office for Coastal Management function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) distributor transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8484 protocol: WWW:LINK-1.0-http--link name: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8484 description: Customizable download of point cloud data and derived products. 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 minimum expected vertical accuracy was tested to meet or exceed the National Standard for Spatial Data Accuracy. When compared to GPS survey grade points in generally flat non-vegetated areas, at least 95% of the positions had an error less than or equal to 18 cm (equivalent to root mean square error of 9.25 cm if errors were normally distributed). result: (missing) lineage: (LI_Lineage) statement: Original acquisition and processing of lidar data was completed by Fugro EarthData, Inc. and delivered to NRCS and Maryland. NOAA OCM obtained the data from Maryland iMAP and modified for ingest into the Digital Coast system. processStep: (LI_ProcessStep) description: Fugro EarthData utilized commercial software as well as proprietary software for automatic filtering. The parameters used in the process were customized for each terrain type to obtain optimum results. Once the automated filtering was completed, the files were run through a visual inspection to ensure that the filtering was not too aggressive or not aggressive enough. In cases where the filtering was too aggressive and important terrain features were filtered out, the data was either run through a different filter or was corrected during the manual filtering process. Interactive editing was then completed in 3D visualization software which also provides manual and automatic point classification tools. Vegetation and artifacts remaining after automatic data post-processing were reclassified manually through interactive editing. The hard edges of ground features that were automatically filtered out during the automatic filtering process were brought back into ground class during manual editing. Auto-filtering routines were utilized as much as possible within fenced areas during interactive editing for efficiency. The technician reviewed the LiDAR points with color shaded TINs for anomalies in ground class during interactive filtering. Upon the completion of peer review and finalization of bare earth filtering, the classified LiDAR point cloud work tiles went through a water classification routine. Upon the completion of finalization of the classified LiDAR point cloud work tiles, the tiles were reprojected to NAD83 (HARN), UTM zone 18 north, meters; NAVD88, meters, using GEOID09 and cut to the approved tile layout in LAS format. dateTime: DateTime: 2011-06-27T00:00:00 processStep: (LI_ProcessStep) description: The hydrographic features were collected as vector linework using classified LiDAR datasets, intensity images, shaded-relief TIN surfaces, and contours. These features were classified as Inland Ponds and Lakes, Inland Streams and Rivers (single line), Inland Streams and Rivers (double line), Non-Tidal Boundary Waters, and Tidal Waters. After initial collection, linework was then checked for the following topological and attribution rules: non-bank lines must be digitized from an uphill to downhill direction, lines must be attributed with the correct feature code, dangles must exist only at the upstream headwater end of streams and at the downstream outfall, line intersections must be at nodes, non-bankline features must form a dendritic collection network, lakes that have a digitized inflow path must have a centerline as well, lakes that have a digitized outflow path but do not have a digitized inflow path should not have a centerline, isolated ponds that are not part of the drainage network should not have centerlines; lake and stream banklines must form closed polygons, single streams should not fall within bankline polygons and lake and stream connector lines should not fall outside of bankline polygons. Hydro features were collected as vector linework using LiDAR and its derived products listed above. This linework is initially 2D, meaning that it does not have elevation values assigned to individual line vertices. Vertex elevation values were assigned using a distance weighted distribution of LiDAR points closest to each vertex. After the initial 'drape', the linework elevation values were further adjusted based on the following rules: lake feature vertices were re-assigned (flattened) to lowest draped vertex value; lake connector line vertices were re-assigned (flattened) to lowest draped vertex value of the surrounding lake bankline, single stream and stream connector line vertices were adjusted so that subsequent vertices are lower than previous ones based on line direction, and double stream bankline vertices were re-assigned based on the vertices of the closest adjusted double stream connector line. After assignment of 3D values, the stream network is checked to ensure the following does not exist: large differences between initial drape and adjusted elevation values, elevation differences between nodes, and elevation values flowing in an 'uphill' direction. Data was provided to the terrain department for hydro-enforcement of the DEM. dateTime: DateTime: 2011-06-24T00:00:00 processStep: (LI_ProcessStep) description: NOAA OCM downloaded the data from Maryland iMAP as zip files by Block. dateTime: DateTime: 2017-10-16T00:00:00 processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor processStep: (LI_ProcessStep) description: Lidar data were changed from NAVD88 (Geoid09) vertical coordinates to ellipsoid heights using the GEOID09 grids. The class scheme was not described in the original metadata, but research on the related data for the Worcester coastal area suggests class 10 is ignored ground near breaklines and class 11 is withheld. Examination of the data supports that hypothesis. Data were then ingested into the Digital Coast Data Access Viewer system for distribution. dateTime: DateTime: 2018-02-26T00:00:00 processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) description: Source Contribution: Point cloud data repository for Maryland sourceCitation: (CI_Citation) title: Lidar data from Maryland iMAP date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: http://imap.maryland.gov/Pages/default.aspx 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: 2011-02-06 endPosition: 2011-02-16 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-25 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: Leica ALS60 type: lidar description: Multipulse in air lidar sensor | |