| 2006 USACE Topobathy Lidar: Lake Michigan (IN), Lake Erie (OH,PA), Lake Huron (MI) | |
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:50058 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: 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: return to top referenceSystemInfo: return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(HARN) / UTM zone 16N 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/3746/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:3746 version: 6.18.3 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2006 USACE Topobathy Lidar: Lake Michigan (IN), Lake Erie (OH,PA), Lake Huron (MI) alternateTitle: usace2006_gl_m40_metadata date: (CI_Date) date: 2007-03-22 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 50058 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/50058 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: The U.S. Army Corps of Engineers collects and maintains LiDAR data including orthophotos in coastal areas of the United States and its territories. The Corps acquires this data in the course of performing its mission of Flood Control, Navigation, Environmental Engineering, and support for the Army and others. These data were collected along the Indiana, Michigan, Ohio and Pennsylvania coasts of the Great Lakes using the CHARTS (Compact Hydrographic Airborne Rapid Total Survey) system and industry based coastal mapping and charting systems. Original contact information: Contact Org: NOAA Office for Coastal Management Phone: 843-740-1202 Email: coastal.info@noaa.gov 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 purpose of this survey was to collect topographic and hydrographic elevations to obtain the existing conditions of the beach and near shore in support of the Joint Airborne LiDAR Bathymetric Technical Center of Expertise National Coastal Mapping Program. However, depths were not attained in many areas due to water clarity. credit: Acknowledgment of JALBTCX would be appreciated in any publications or derived products. 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-03-17 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) asNeeded descriptiveKeywords: (MD_Keywords) keyword: June 2006 keyword: September 2006 type: (MD_KeywordTypeCode) temporal 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-03-17 from the NOAA system. Cite As: OCM Partners, [Date of Access]: 2006 USACE Topobathy Lidar: Lake Michigan (IN), Lake Erie (OH,PA), Lake Huron (MI) [Data Date Range], https://www.fisheries.noaa.gov/inport/item/50058. 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-03-17 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-03-17 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 it's limitations. resourceConstraints: (MD_LegalConstraints) useLimitation: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2025-03-17 from the NOAA system. Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of the US Army Corp of Engineers, the Joint Airborne Lidar Bathymetry Center of Expertise(JALBTCX), NOAA, the Office for Coastal Management or it's 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: 50058 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/50058.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: -87.2 eastBoundLongitude: -79.98 southBoundLatitude: 41.37 northBoundLatitude: 44.08 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2006-06-14 endPosition: 2006-09-26 return to top contentInfo: (MD_FeatureCatalogueDescription) complianceCode: false language: LanguageCode: eng includedWithDataset: false featureCatalogueCitation: (CI_Citation) title: none date: (unavailable) 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=40 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/40/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: N/A result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: The data has been collected and compiled to meet the +/- 3 m (2 sigma) accuracy specification.; Quantitative Value: 3.0 meters, Test that produced the value: Compiled to meet result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The data has been collected and compiled to meet the +/- 30 cm (2 sigma) accuracy specification.; Quantitative Value: 0.3 meters, Test that produced the value: Compiled to meet result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: See Process Step result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: N/A result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: Acquisition - Data were acquired using a SHOALS-1000T. Sensor orientation was measured using a POS AV 410, while images were acquired at 1Hz using a Duncantech DT4000 digital camera. Prior to survey PDOP was checked and missions planned to avoid PDOP greater than 3.5. During survey the plane was always within 30km of a GPS ground control point, to provide a good quality position solution. Final positions were determined using a post-processed inertially aided Kinematic GPS (KGPS) solution. GPS ground control data were acquired at 1Hz. Data received by the airborne system were continually monitored for data quality during acquisition operations. Display windows showed coverage and information about the system status. In addition, center waveforms at 5Hz were shown. All of this information allowed the airborne operator to assess the quality of data being collected. The data were collected and processed in geographic coordinates and ellipsoid heights. The positions are relative to NAD83 in decimal degrees of longitude and latitude. The heights were converted from ellipsoid to geoid heights (NAVD88) using the Geoid03 model with the results in meters. Data were processed in the field to verify coverage and data quality. processStep: (LI_ProcessStep) description: Processing - Data were processed using the SHOALS Ground Control System (GCS). The GCS includes links to Applanix POSPac software for GPS and inertial processing, and IVS Fledermaus software for data visualization, 3D editing and tie-line analysis. Data were processed in NAD83 horizontal and vertical datum. Data were later converted to the NAVD88 vertical datum using the GEOID03 model. The date and time of each point are also MM:SS.SSSSSS. Fugro in-house utilities were used to extract XYZ data from the native LiDAR files and split the data in to pre-defined boxes, each covering approximately 5km of shoreline. ASCII files include: Longitude, Latitude, Elevation, Date, Time, and Intensity. processStep: (LI_ProcessStep) description: Files converted to LDART LAS format (geographic coords, ellipsoid heights,using GEOID03), sorted by latitude and filtered to eliminate outliers. dateTime: DateTime: 2007-06-15T00:00:00 processStep: (LI_ProcessStep) description: Times had originally been stored as POSIX seconds when converted to LAS. This was switched to adjusted GPS time (GPS seconds - 1e9) to conform to the LAS 1.2 standard. dateTime: DateTime: 2014-01-09T00:00:00 processStep: (LI_ProcessStep) description: NOAA OCM received the data in LAS v1.2 format. For data storage and Digital Coast provisioning purposes, the data were processed as follows: 1. Heights were converted Ellipsoid heights, horizontal coordinates were converted to geographic coordinates. 2. lastools's Lasground processed the all unclassifed points to have ground classified points as well. 3. LAS files were converted to LAZ and sorted. dateTime: DateTime: 2013-07-01T00:00:00 source: (LI_Source) description: Source Contribution: Fugro Pelagos, Inc. | Type of Source Media: Electronic Mail System sourceCitation: (CI_Citation) title: 2006 USACE National Coastal Mapping Program, Great Lakes Topo/Bathy LiDAR date: (missing) sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2006-09-25 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-03-17 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |