| Wayne and Washtenaw Counties 1.0 PPSM LiDAR | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:49798 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(NSRS2007) / 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/3723/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:3723 version: 6.18.3 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: Wayne and Washtenaw Counties 1.0 PPSM LiDAR alternateTitle: mi2009_usgs_wayne_washtenaw_m4809_metadata date: (CI_Date) date: 2015-02-09 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 49798 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/49798 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: TASK NAME: Wayne and Washtenaw Counties 1.0 PPSM LiDAR LiDAR Data Acquisition and Processing Production Task USGS CONTRACT: 07CRCN0006 TASK ORDER NUMBER: G09PD00300 CONTRACTOR: Woolpert, Inc. LiDAR data is a remotely sensed high resolution elevation data collected by an airborne platform. The LiDAR sensor uses a combination of laser range finding, GPS positioning, and inertial measurement technologies.The LiDAR systems collect data point clouds that are used to produce highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures, and vegetation. This data was collected at a resolution of one point per square meter. The final products include reflective surface, first, last, and at least one intermediate return, a bare earth model, and intensity data in separate files. The reflective surface data represents the DEM created by the laser energy reflected from the first surface encountered by the laser pulse. Some energy may continue beyond this initial surface, to be reflected by a subsequent surface as represented by the last return data. Intensity information is captured from the reflective surface pulse and indicates the relative energy returned to the sensor, as compared to the energy transmitted. The intensity image is not calibrated or normalized but indicates differences in energy absorption due to the the interaction of the surface materials with laser energy, at the wavelength transmitted by the sensor. The bare earth model is created by identifying the returns that fall on the ground surface and by interpolating a surface between these points. In this manner, buildings and vegetation are removed from the bare earth model. This data set does not include bridges and overpasses in the bare earth model as the delineation point for these structures is not reliably discernible in the LiDAR data. 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: This task order consisted of LiDAR data acquisition and processing for Wayne and Washtenaw Counties in southeastern Michigan. The task order area of interest encompasses approximately 1324 square miles. The task required the LiDAR data to be collected at a minimum of one (1) point per square meter (1.0 meter GSD). The LiDAR data was collected to meet a vertical accuracy requirement of 18.0 cm (0.59 ft) RMSE, or better, so that when combined with breaklines, the data adequately supports the generation of two (2) foot FEMA compliant contours. The final LiDAR data was delivered as 5,000' x 5,000' tiles, aligned to even 5,000' coordinates. The LAS files are comprised of the full class data. 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/4809/supplemental/mi2009_usgs_wayne_washtenaw_m4809.kmz fileDescription: This graphic shows the lidar coverage for the 2009 USGS lidar collection of Wayne and Washtenaw Counties, Michigan. fileType: kmz descriptiveKeywords: (MD_Keywords) keyword: Wayne and Washtenaw County type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Michigan date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Ground keyword: Terrain 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-01 from the NOAA system. Cite As: OCM Partners, [Date of Access]: Wayne and Washtenaw Counties 1.0 PPSM LiDAR [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49798. 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-01 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-01 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. These data depict the heights at the time of the survey and are only accurate for that time. resourceConstraints: (MD_LegalConstraints) useLimitation: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2025-06-01 from the NOAA system. Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of Woolpert, USGS, 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: 49798 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49798.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: -84.158227 eastBoundLongitude: -82.859494 southBoundLatitude: 42.011439 northBoundLatitude: 42.473937 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2009-04-16 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2009-04-17 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2009-04-18 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2009-04-23 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2009-04-24 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2009-05-03 supplementalInformation: Reports for this project are available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4809/supplemental/mi2009_usgs_wayne_washtenaw_m4809_surveyreport.pdf https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4809/supplemental/mi2009_usgs_wayne_m4809_surveyreport.pdf A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4809/supplemental/mi2009_usgs_wayne_washtenaw_m4809.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=4809 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/4809/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: The LiDAR collected for this task order was collected at a vertical accuracy of 18.0 cm (0.59 ft) Root Mean Squared (RMSE), or better, so that when combined with breaklines, it will adequately support the generation of two (2) foot FEMA compliant contours. | Quantitative Value: 18.0 cm (0.59 ft) RMSE | Quantitative Test Explanation: Points measured will produce an error less than 18.0 cm (0.59 ft) RMSE. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: Horizontal accuracy is +/- 1.158 meters at the 95% confidence level using RMSE(r) x 1.7308 as defined by the FGDC Geospatial Positional Accuracy Standards, Part 3: NSSDA.; Quantitative Value: 0.669 meters, Test that produced the value: 66.9 cm RMSE result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The LiDAR data vertical accuracy RMSE is 8.84 cm. The data collected under this Task Order meets the National Standard for Spatial Database Accuracy (NSSDA) accuracy standards. The NSSDA standards specify that vertical accuracy be reported at the 95 percent confidence level for data tested by an independent source of higher accuracy. (http://www.fgdc.gov/standards/projects/FGDC-standards-projects/accuracy/part3/index_html). The Fundamental Vertical Accuracy (FVA) of the TIN: 36.3 cm (1.19 ft) at a 95% confidence level, derived according to NSSDA, i.e., based on RMSE of 18.5 cm in the "open terrain" land cover category. This data set tested to 0.56 ft. The Supplemental Vertical Accuracy (SVA) of the TIN: 36.3 cm (1.19 ft) at a 95% confidence level, derived according to American Society for Photogrammetry and Remote Sensing (ASPRS) Guidelines, Vertical Accuracy Reporting for LiDAR Data, i.e., based on the 95th percentile error in each of the individual other land cover categories. This criterion is a target value; larger errors in category could be offset by smaller errors in other categories so long as the overall consolidated vertical accuracy (CVA) is satisfied.This data set tested to 0.56 ft. for all categories. The Consolidated Vertical Accuracy (CVA): 36.3 cm (1.19 ft) at a 95% confidence level, derived according to ASPRS Guidelines, Vertical Accuracy Reporting for LiDAR Data, i.e., based on the 95th percentile error in all land cover categories combined. This data set tested to 0.56 ft. for all categories.; Quantitative Value: 0.0884 meters, Test that produced the value: 8.84 cm RMSEz result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: The LIDAR data is visually inspected for completeness to ensure that are no gaps between flight lines. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: All formatted data are validated using commercial GIS software to ensure proper formatting and loading prior to delivery. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: Using a LH Systems ALS50 Light Detection And Ranging (LiDAR) system, 135 flight lines of high density data, one point per square meter, were collected over Wayne and Washtenaw Counties (approximately 1,324 square miles). Multiple returns were recorded for each laser pulse along with an intensity value for each return. A total of six missions were flown over an 18 day period: April 16, 2009 through May 3, 2009. A minimum of two airborne global positioning system (GPS) base stations were used in support of the LiDAR data acquisition. The mean baseline length was 28 miles, with a maximum baseline length of 52 miles. In addition, 31 ground control points were surveyed through static methods. The geoid used to reduce satellite derived elevations to orthometric heights was Geoid03. All data for the task order is referenced to Michigan State Plane South Zone (2113), NAD83/2007, NAVD88, in international feet. Airborne GPS data was differentially processed and integrated with the post processed IMU data to derive a smoothed best estimate of trajectory (SBET). The SBET was used to reduce the LiDAR slant range measurements to a raw reflective surface for each flight line. The coverage was classified to extract a bare earth digital elevation model (DEM) and separate last returns. Four layers of coverage were delivered in the ArcINFO ArcGrid binary format: reflective surface, bare-earth, last return and intensity. System Parameters: - Type of Scanner = LH Systems ALS50 - Data Acquisition Height = 7,000-feet AGL - Scanner Field of View = 14 degrees - Scan Frequency = 65.3 Hertz - Pulse Repetition Rate - 114.6 Kilohertz - Aircraft Speed = 120 Knots - Swath Width = 1,719-feet - Number of Returns Per Pulse = Maximum of 4 - Distance Between Flight Lines = 1,289-feet dateTime: DateTime: 2009-08-31T00:00:00 processStep: (LI_ProcessStep) description: The ALS50 calibration and system performance is verified on a periodic basis using Woolpert's calibration range. The calibration range consists of a large building and runway. The edges of the building and control points along the runway have been located using conventional survey methods. Inertial measurement unit (IMU) misalignment angles and horizontal accuracy are calculated by comparing the position of the building edges between opposing flight lines. The scanner scale factor and vertical accuracy is calculated through comparison of LiDAR data against control points along the runway. Field calibration is performed on all flight lines to refine the IMU misalignment angles. IMU misalignment angles are calculated from the relative displacement of features within the overlap region of adjacent (and opposing) flight lines. The raw LiDAR data is reduced using the refined misalignment angles. dateTime: DateTime: 2009-08-31T00:00:00 processStep: (LI_ProcessStep) description: Once the data acquisition and GPS processing phases are complete, the LiDAR data was processed immediately to verify the coverage had no voids. The GPS and IMU data was post processed using differential and Kalman filter algorithms to derive a best estimate of trajectory. The quality of the solution was verified to be consistent with the accuracy requirements of the project. dateTime: DateTime: 2009-08-31T00:00:00 processStep: (LI_ProcessStep) description: The individual flight lines were inspected to ensure the systematic and residual errors have been identified and removed. Then, the flight lines were compared to adjacent flight lines for any mismatches to obtain a homogeneous coverage throughout the project area. The point cloud underwent a classification process to determine bare-earth points and non-ground points utilizing "first and only" as well as "last of many" LiDAR returns. This process determined bare-earth points (Class 2), model keypoints (Class 8), overlap (Class 12) and unclassified data (Class 1). The bare-earth (Class 2 - Ground) LiDAR points underwent a manual QA/QC step to verify that artifacts have been removed from the bare-earth surface. The surveyed ground control points are used to perform the accuracy checks and statistical analysis of the LiDAR dataset. dateTime: DateTime: 2009-08-31T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received the files in laz format from USGS via an FTP online repository. The files contained lidar elevation and intensity measurements. The data were in State Plane MI 2113 South, NAVD88 (orthometric) international feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from State Plane coordinates to geographic coordinates. 2. The data were converted from NAVD88 (orthometric) heights in international feet to GRS80 (ellipsoid) heights in meters using Geoid 03. 3. The LAS data were sorted by latitude and the headers were updated. 4. Erroneous elevations were removed. dateTime: DateTime: 2015-01-20T00:00:00 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-01 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |