| 2012 USACE Great Lakes Topobathy Lidar: Lake Michigan | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:49736 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:37 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(2011) 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/6318/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:6318 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: 2012 USACE Great Lakes Topobathy Lidar: Lake Michigan alternateTitle: gl2012_usace_lakemichigan_m2644_metadata date: (CI_Date) date: 2014-07-02 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 49736 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/49736 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/dataviewer 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 protocol: WWW:LINK-1.0-http--link name: Citation URL description: Online Resource function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (unknown) abstract: These files contain classified topographic and bathymetric lidar data as unclassified valid topographic data (1), valid topographic data classified as ground (2), invalid topographic data classified as lowpoints (7), valid bathymetric data (11), and valid topographic data acquired with the bathymetric sensor (14). Classes 1, 2, and 7 are defined in accordance with the American Society for Photogrammetry and Remote Sensing (ASPRS) classification standards, while classes 11 and 14 are classes specific to the NOAA Digital Coast Data Access Viewer (DAV).These data were collected with a RIEGL VQ-480 airborne lidar system along the Lake Michigan shoreline. Data coverage generally extends along the shoreline from the waterline to 500 meters onshore. The VQ-480 sensor has a pulse repetition rate of 150 kHz at near infrared laser wavelength. Native lidar data are not generally in a format accessible to most Geographical Information Systems (GIS). Specialized in-house and commercial software packages are used to process the native lidar data into 3-dimensional positions that can be exported to standard formats and imported into GIS software for visualization and further analysis. Horizontal positions, provided in Geographic Coordinates in decimal degrees, are referenced to the NAD83 (2011) Epoch 2010 datum. Vertical elevations in meters are also referenced to this datum (GRS80 ellipsoidal height). The 3-D position data are sub-divided into a series of LAS files. The National Geodetic Surveys (NGS) GEOID03 model is used to transform the vertical positions from ellipsoid to orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88). The 3-D position data are sub-divided into a series of LAS files, each covering approximately 5 kilometers of shoreline. Note: The NOAA Office for Coastal Management was unable to determine the exact dates of collection due to corrupt GPS times in at least of the LAS files. Classifications listed from the original metadata above may have changed during processes at NOAA OCM. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: These data were collected as a part of the NCMP to depict the elevations ABOVE AND/OR BELOW the water. 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 graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2644/supplemental/gl2012_usace_lakemichigan_m2644.kmz fileDescription: This graphic shows the coverage of the 2012 USACE Lake Michigan lidar. fileType: kmz 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]: 2012 USACE Great Lakes Topobathy Lidar: Lake Michigan [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49736. 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. These data depict the heights at the time of the survey and are only accurate for that time. | Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of USACE, JALBTCX, 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: NOAA Data Management Plan (DMP) date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 49736 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49736.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.9458693 eastBoundLongitude: -84.6843231741 southBoundLatitude: 41.5996674 northBoundLatitude: 46.1156698822 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-09-02 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-09-03 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-09-07 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-09-08 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-09-09 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-09-10 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-09-12 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-09-13 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-09-14 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-09-23 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-09-25 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-09-26 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-09-27 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-09-28 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-09-29 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-10-01 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-10-02 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-10-03 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-10-06 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-10-15 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-10-16 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-10-17 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-10-18 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-10-19 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2013-11-05 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2013-11-06 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2013-11-11 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2013-11-18 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2013-11-26 supplementalInformation: A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2644/supplemental/gl2012_usace_lakemichigan_m2644.kmz 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=2644 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/2644/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_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: The data point positions were obtained using post processed KGPS methods. The horizontal accuracy of the data is better than +/- 0.50 m; Quantitative Value: 0.50 meters, Test that produced the value: RMSE 95% Conf. Units in meters. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The data point positions were obtained using post processed KGPS methods. The vertical accuracy of the data is better than +/- 0.15 m; Quantitative Value: 0.15 meters, Test that produced the value: RMSE 95% Conf. Units in meters. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: This data set covers the spatial extent of bathymetric and topographic lidar data obtained during this survey. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Differences between a DEM created from the lidar data representing bare ground and the ground truth point data is unbiased and within +/- 15 cm (RMSE) in flat terrain and within +/-30 cm (RMSE) in hilly terrain result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: The flightline LAS files are imported into GeoCue [V7.0.3.5], which is a geospatial workflow production and management software tool employed by JALBTCX to perform and monitor production of data products. Upon import into GeoCue, the flightline LAS files are divided into a series of boxes, each of which are 1500 meters in length and width. A customized classification macro, built upon the TerraScan [V11] module within Microstation V8i, classifies valid topographic data as ground points (2) and unclassified points (1). Upon completion the macro, the classification results undergo quality control and any misclassified points are manually edited. In areas of dense vegetation the bare earth ground points might be incorrectly classified due to the inability of the laser to penetrate the canopy and reach the bare ground. In these areas, JALBTCX defaults to the algorithm ground surface instead of manually reclassifying those points. The final classification results are comprised of individual lidar points with classifications of ground (2) or unclassified (1). They are partitioned into a series of 5km delivery boxes, one Classified LAS file per box. The format of the file is LAS version [1.2]. Data are classified as 1 (valid non-ground topographic data), 2 (valid ground topographic data), 21 (valid topographic data acquired with the bathymetric sensor), 27 (invalid topographic and bathymetric data), 29 (valid bathymetric data) processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received the topographic/bathymetric files in LAS format from USACE. The files contained lidar easting, northing, elevation, intensity, return number, etc. Some GPS times in the LAS files appeared to be corrupt. the data was received in Geographic Coordinates (decimal degrees). The vertical coordinates were referenced to IGLD85 in meters. using the Geoid03 model. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. Class 29 points (bathymetry) were reclassified to Class 11 (bathymetry). 2. Class 21 points (green topography) were reclassified to Class 14 (green topography). 3. Tile '2012_NCMP_MI_Michigan_05_Geoclassified_IGLD' was found to have erroneous points outside of the header's bounding box. These points were removed using LAStools' lasclip software. 4. The LAS files were then converted from IGLD85 orthometric heights to NAD83 (GRS80) ellipsoidal heights using NOAA's VDatum v3.3. 5. On March 30, 2015 tiles were added from an additional delivery from USACE following the same process. dateTime: DateTime: 2015-03-30T00:00:00 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-01T06:34:20 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |