| 2006 Maryland Department of Natural Resources Lidar: Caroline, Kent and Queen Anne Counties | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:49784 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset contact: (CI_ResponsibleParty) organisationName: OCM Partners contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (missing) address: (CI_Address) role: (CI_RoleCode) resourceProvider contact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2022-08-09T17:11:36 metadataStandardName: ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data metadataStandardVersion: ISO 19115-2:2009(E) return to top spatialRepresentationInfo: return to top referenceSystemInfo: return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(HARN) 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/4152/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:4152 version: 6.18.3 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters alternateTitle: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters citedResponsibleParty: (CI_ResponsibleParty) organisationName: (withheld) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://apps.epsg.org/api/v1/VerticalCoordRefSystem/5703/?api_key=gml name: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters description: Link to Geographic Markup Language (GML) description of reference system. function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) resourceProvider citedResponsibleParty: (CI_ResponsibleParty) organisationName: European Petroleum Survey Group contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.epsg.org/ name: European Petroleum Survey Group Geodetic Parameter Registry description: Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured dataset of Coordinate Reference Systems and Coordinate Transformations. function: (CI_OnLineFunctionCode) search role: (CI_RoleCode) publisher VerticalCS: metaDataProperty: CommonMetaData: type: vertical informationSource: OGP revisionDate: 2006-11-28 isDeprecated: false identifier: urn:ogc:def:cs:EPSG::6499 name: Vertical CS. Axis: height (H). Orientation: up. UoM: meter. remarks: Used in vertical coordinate reference systems. axis: CoordinateSystemAxis: descriptionReference: urn:ogc:def:axis-name:EPSG::9904 identifier: urn:ogc:def:axis:EPSG::114 axisAbbrev: H axisDirection: up code: urn:ogc:def:crs:EPSG::5703 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2006 Maryland Department of Natural Resources Lidar: Caroline, Kent and Queen Anne Counties alternateTitle: md2006_m103_metadata date: (CI_Date) date: 2006-10-05 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 49784 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/49784 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://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: Citation URL description: Online Resource 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: Citation URL description: Online Resource function: (CI_OnLineFunctionCode) download role: (inapplicable) abstract: Maryland Department of Natural Resources requested the collection of LIDAR data over Kent, Queen Anne and Caroline Counties, MD. In response, EarthData acquired the data from March 18 through April 6, 2006. Airborne lidar data was acquired at an altitude of 5,500'(1676.4 m) above mean terrain with a swath width of 40 degrees, which yields an average post spacing of lidar points of no greater than 6.56 ft (2 m). The project was designed to achieve a vertical accuracy of the lidar points at 7.09 in (18 cm) root mean square error (RMSE). The flight design included a total of seventy-seven flight lines with approximately 2,246 total line miles (3614.59 km). The lidar data was acquired prior to the emergence of deciduous foliage. This is a bare earth data set. Light Detection and Ranging (LIDAR) is a method of locating objects on the ground using aerial-borne equipment. It is similar to RADAR or SONAR in that the two-way travel time of an energy beam reflected off an object is precisely measured, but this technology uses laser light instead of radio or sound waves. This technology has proven very useful in remote sensing of the earth. It can be used for determining elevations of both the earth's surface and items (natural and man-made) on the surface. Analysis of LiDAR data is used in detailed modeling of the earth's surface for drainage and floodplain studies, determining how a new structure will affect views from various locations, shoreline erosion studies, and other reasons. "First returns" are the first elevation value that the LiDAR sensor recorded for a given x,y coordinate. Likewise, "last returns" are the last elevation value that the LiDAR sensor recorded for a given x,y coordinate. The Bare Earth Mass Points are point elevations that represent the "bare earth." Features that are above the ground - such as buildings, bridges, tree tops, etc. - are not included in these data. The Gridded DEM is a model of the surface of the earth (no above-surface features such as buildings, tree tops, etc) with a point at every 2 meters representing the average surface elevation of that area. The LIDAR Intensity Imagery are similar to aerial photography. While not as sharp as traditional aerial photos, they offer a good visual representation of the surface and various features. Original contact information: Contact Name: Kevin Boone Contact Org: Maryland Department of Natural Resources Title: Chief GIS Officer Phone: 410-260-8753 Email: kboone@dnr.state.md.us This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: The LIDAR-derived data were collected by the Maryland Department of Natural Resources in support of shore erosion studies along the shorelines of the Chesapeake Bay. It also supports the Federal Emergency Management Agency's specifications for mapping floodplains. These efforts required detailed elevation data and models, such as those available from LIDAR sensing. The data have also been made available to aid in other projects that require detailed surface, vegetation and/or structure elevations. 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) unknown descriptiveKeywords: (MD_Keywords) keyword: ASCII keyword: Bare earth keyword: Intensity image 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: Cite As: OCM Partners, [Date of Access]: 2006 Maryland Department of Natural Resources Lidar: Caroline, Kent and Queen Anne Counties [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49784. resourceConstraints: (MD_Constraints) useLimitation: NOAA provides no warranty, nor accepts any liability occurring from any incomplete, incorrect, or misleading data, or from any incorrect, incomplete, or misleading use of the data. It is the responsibility of the user to determine whether or not the data is suitable for the intended purpose. resourceConstraints: (MD_LegalConstraints) accessConstraints: (MD_RestrictionCode) otherRestrictions useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: Access Constraints: None | Use Constraints: Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations. | Distribution Liability: Any conclusions drawn for the analysis of this information are not the responsibility of the Maryland Department of Natural Resources, 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: 49784 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49784.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 extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -76.300698 eastBoundLongitude: -75.688478 southBoundLatitude: 38.729653 northBoundLatitude: 39.383359 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2006-03-18 endPosition: 2006-04-06 supplementalInformation: The Lidar QA/QC Assessment Report for Maryland Department of Natural Resources for Caroline, Kent and Queen Anne Counties may be viewed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/103/supplemental/MD_DNR_LIDAR_QA_Report_2006_caro_kent_queen.pdf return to top distributionInfo: (MD_Distribution) distributor: (MD_Distributor) distributorContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) distributor transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=103 protocol: WWW:LINK-1.0-http--link name: Customized Download description: Create custom data files by choosing data area, product type, map projection, file format, datum, etc. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/103/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Simple download of data files. function: (CI_OnLineFunctionCode) download return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_QuantitativeAttributeAccuracy) nameOfMeasure: Accuracy evaluationMethodDescription: Airborne lidar data was acquired at an altitude of 5,500'(1676.4 m) above mean terrain with a swath width of 40 degrees, which yields an average post spacing of lidar points of no greater than 6.56 ft (2 m). The project was designed to achieve a vertical accuracy of the lidar points at 7.09 in (18 cm) root mean square error (RMSE). The flight design includes a total of seventy-seven flight lines with approximately 2,246 total line miles (3614.59 km). The lidar data will be acquired prior to the emergence of deciduous foliage. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: The lidar data fully comply with FEMA guidance as published in Appendix A, April, 2003. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The lidar data fully comply with FEMA guidance as published in Appendix A, April 2003 and National Standard for Spatial Accuracy (NSSDA). When compared to GPS survey grade points in generally flat non-vegetated areas, at least 95% of the positions have an error less than or equal to 36.3 cm (equivalent to root mean square error of 18.5 cm if errors were normally distributed). result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Measure evaluationMethodDescription: Cloud Cover: 0 result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: 1. EarthData's proprietary software, Checkedb, for verification against ground survey points. 2. Terrascan, for verification of automated and manual editing and final QC of products. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Compliance with the accuracy standard was ensured by the placement of GPS ground control prior to the acquisition of lidar data. The following checks were performed: 1. The ground control and airborne GPS data stream were validated through a fully analytical boresight adjustment. 2. The DTM (Digital Terrain Model) data were checked against the project control. 3. Lidar elevation data was validated through an inspection of edge matching and visual inspection for quality (artifact removal). result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: EarthData has developed a unique method for processing lidar data to identify and remove elevation points falling on vegetation, buildings, and other aboveground structures. The algorithms for filtering data were utilized within EarthData's proprietary software and commercial software written by TerraSolid. This software suite of tools provides efficient processing for small to large-scale, projects and has been incorporated into ISO 9001 compliant production work flows. The following is a step-by-step breakdown of the process: 1. Using the lidar data set provided by EarthData, the technician performs calibrations on the data set. 2. Using the lidar data set provided by EarthData, the technician performed a visual inspection of the data to verify that the flight lines overlap correctly. The technician also verified that there were no voids, and that the data covered the project limits. The technician then selected a series of areas from the data set and inspected them where adjacent flight lines overlapped. These overlapping areas were merged and a process which utilizes 3-D Analyst and EarthData's proprietary software was run to detect and color code the differences in elevation values and profiles. The technician reviewed these plots and located the areas that contained systematic errors or distortions that were introduced by the lidar sensor. 3. Systematic distortions highlighted in step 2 were removed and the data was re-inspected. Corrections and adjustments can involve the application of angular deflection or compensation for curvature of the ground surface that can be introduced by crossing from one type of land cover to another. 4. The lidar data for each flight line was trimmed in batch for the removal of the overlap areas between flight lines. The data was checked against a control network to ensure that vertical requirements were maintained. Conversion to the client-specified datum and projections were then completed. The lidar flight line data sets were then segmented into adjoining tiles for batch processing and data management. 5. The initial batch-processing run removed 95% of points falling on vegetation. The algorithm also removed the points that fell on the edge of hard features such as structures, elevated roadways and bridges. 6. The operator interactively processed the data using lidar editing tools. During this final phase the operator generated a TIN based on a desired thematic layer to evaluate the automated classification performed in step 5. This allowed the operator to quickly re-classify points from one layer to another and recreate the TIN surface to see the effects of edits. Geo-referenced images were toggled on or off to aid the operator in identifying problem areas. The data was also examined with an automated profiling tool to aid the operator in the reclassification. 7. The final DEM was written to an LAS 1.0 format and also converted to ASCII 8. The point cloud data were also delivered in LAS 1.0 format and also converted to ASCII. dateTime: DateTime: 2006-10-05T00:00:00 processStep: (LI_ProcessStep) description: EarthData utilizes a combination of proprietary and COTS processes to generate intensity images from the lidar data. Intensity images are generated from the full points cloud (minus noise points) and the pixel width is typically matched to the post spacing of the lidar data to achieve the best resolution. The following steps are used to produce the intensity: 1) Lidar point cloud is tiled to the deliverable tile layout. 2) All noise points, spikes, and wells are deleted out of the tiles. 3) An EarthData proprietary piece of software, EEBN2TIF is then used to process out the intensity values of the lidar. At this point, the pixel size is selected based on best fit or to match the client specification if noted in the SOW. 4) The software then generates TIF and .TFW files for each tile. 5) ArcView is used to review and QC the tiles before delivery. dateTime: DateTime: 2006-11-20T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received the files in las and ASCII format. The data were in Maryland State Plane Projection, NAVD88 vertical datum and the vertical units of measure were meters. OCM performed the following processing to the las data to make it available within Digital Coast: 1. The data were converted from Maryland State Plane coordinates to geographic coordinates. 2. The data were converted from NAVD88 (orthometric) heights to GRS80 (ellipsoid) heights using Geoid 03. 3. The LAS data were sorted by latitude and the headers were updated. dateTime: DateTime: 2008-11-03T00:00:00 source: (LI_Source) description: Source Contribution: Maryland Department of Natural Resources requested the collection of LIDAR data over Kent, Queen Anne and Caroline Counties, MD. In response EarthData acquired the data from March 18 through April 6, 2006 using its aircraft with tail number N62912. LIDAR data was captured using an ALS50 LIDAR system, including an inertial measuring unit (IMU) and a dual frequency GPS receiver. An additional GPS receiver was in constant operation over a published control point set by EarthData at the base of operations airport which is a secondary Airport Control Station. During the data acquisition, the receivers collected phase data at an epoch rate of 1 Hz. The use of the Airport base station ensured that all data capture was performed within 50 miles of a base station. The solutions from Kent, Queen Anne and Caroline counties were found to be of high integrity and met the accuracy requirements for the project. These accuracy checks also verified that the data meets the guidelines outlined in FEMA's Guidelines and Specifications for Flood Hazard Mapping Partners and Appendix 4B, Airborne Light Detection and Ranging Systems. Airspeed - 140 knots Laser Pulse Rate - 52700 kHz Field of View - 40 degrees ScanRate - 30 Hz | Source Geospatial Form: Model | Type of Source Media: Firewire Drive sourceCitation: (CI_Citation) title: Aerial Acquisition of Lidar Data for Kent, Queen Anne & Caroline Counties, MD date: (CI_Date) date: 2006-11-08 dateType: (CI_DateTypeCode) publication sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimePeriod: beginPosition: 2006-03-18 endPosition: 2006-04-06 source: (LI_Source) description: Source Contribution: Earthdata International was contracted to provide LIDAR mapping services in the area of Caroline, Kent, and Queen Anne's Counties, Maryland. Earthdata subcontracted the ground survey tasks to TerraSurv, Inc. The Global Positioning System (GPS) was used to establish the control network. The horizontal datum was the North American Datum of 1983, CORS adjustment (NAD 1983 CORS). The vertical datum was the North American Vertical Datum of 1988(NAVD 1988). There were a total of 27 stations occupied for this project. There were 19 new LIDAR control stations, 2 temporary GPS base stations, 3 existing NSRS control stations, 2 CORS stations, and 1 airborne GPS base station used by the flight crew. The network was observed in a radial configuration. A base receiver was established on a random point and run throughout the observations in each area. Due to the large area covered, multiple base locations were used. The temporary base stations were tied to the CORS and NSRS control stations. | Source Geospatial Form: Diagram | Type of Source Media: Electronic mail system sourceCitation: (CI_Citation) title: Report of Survey for Caroline, Kent & Queen Anne's Counties date: (CI_Date) date: 2006-07-12 dateType: (CI_DateTypeCode) publication sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2006-06-30 processStep: (LI_ProcessStep) description: The vertical values in this data set have been converted to reference North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters, using the GEOID18 grids provided by the National Geodetic Survey. Any datum and projection transformations were then done with the Office for Coastal Management 'datum_shift' program. Compression to an LAZ file was done with the LAStools 'laszip' program and can be unzipped with the same free program (laszip.org) Processing notes: dateTime: DateTime: 2023-07-01T05:34:14 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |