| 2016 FEMA Michigan Lidar: Part 1 (Muskegon County) | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:56271 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset hierarchyLevelName: Elevation 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: 2023-05-30T18:10:31 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: 2016 FEMA Michigan Lidar: Part 1 (Muskegon County) alternateTitle: mi2016_fema_m8731_metadata.xml date: (CI_Date) date: 2016 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 56271 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/56271 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: NOAA's Office for Coastal Management (OCM) website description: Information on the NOAA Office for Coastal Management (OCM) function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/8731/supplemental/Final_Report_Michigan_LiDAR_Spring_2016.docx protocol: WWW:LINK-1.0-http--link name: Dataset report description: Link to data set report. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/8731/breaklines/ protocol: WWW:LINK-1.0-http--link name: Citation URL description: Link to the data set breaklines. 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: NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) description: The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer. function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (unknown) abstract: The State of Michigan (DTMB) contracted with Sanborn to provide LiDAR mapping services for 10 counties in the State of Michigan. These counties include Clare, Lake, Mecosta, Missaukee, Montcalm, Muskegon, Newaygo, Osceola, Roscommon, and Wexford. Utilizing multi-return systems, Light Detection and Ranging (LiDAR) data in the form of 3-dimensional positions of a dense set of mass points was collected for the 10 counties in April and May of 2016. All systems consist of geodetic GPS positioning, orientation derived from high-end inertial sensors and highly-accurate lasers. The sensor is mounted inside an aircraft and emits rapid pulses of light, through an opening in the fuselage, that are used to determine distances between the plane and terrain below. The Leica ALS70-HP was used to collect data for the survey campaign. The LiDAR systems are calibrated by conducting flight passes over a known ground surface before and after each LiDAR mission. During final data processing, the calibration parameters are inserted into post-processing software. The NOAA Office for Coastal Management (OCM) downloaded the Muskegon County portion of this data set from this USGS site: ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_MI_Muskegon_2015_LAS_2018/ and processed the data to the Data Access Viewer (DAV) and https. Muskegon County: 2509 laz files covering approximately 527 square miles. Hydro breaklines are also available. These data are available for download at the link provided in the URL section of this metadata record. Please note that these products have not been reviewed by the NOAA Office for Coastal Management (OCM) and any conclusions drawn from the analysis of this information are not the responsibility of NOAA or OCM. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments, and hydrologic modeling. LAS data products are suitable for 1 foot contour generation. USGS LiDAR Base Specification 1.2, QL2. 19.6 cm NVA. credit: State of Michigan (SOM) 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 Aug 01, 2023 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) unknown graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/8731/supplemental/mi2016_fema_m8731.kmz fileDescription: This graphic displays the footprint for this lidar data set. fileType: KML descriptiveKeywords: (MD_Keywords) keyword: EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION keyword: EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Science Keywords date: (missing) edition: 12.3 descriptiveKeywords: (MD_Keywords) keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > MICHIGAN keyword: VERTICAL LOCATION > LAND SURFACE type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Location Keywords date: (missing) edition: 12.3 descriptiveKeywords: (MD_Keywords) keyword: LIDAR > Light Detection and Ranging type: (MD_KeywordTypeCode) instrument thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Instrument Keywords date: (missing) edition: 14.9 descriptiveKeywords: (MD_Keywords) keyword: Airplane > Airplane type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) edition: 14.9 descriptiveKeywords: (MD_Keywords) keyword: ALS70 keyword: Bare Earth keyword: Contour keyword: Digital Elevation Model (DEM) keyword: Digital Surface Model (DSM) keyword: Digital Terrain Model (DTM) keyword: First Return keyword: Grid keyword: IMG keyword: Intensity return keyword: LAS keyword: LiDAR keyword: Overlap points keyword: Unclassified points keyword: Water points keyword: ground points keyword: mapping keyword: point cloud type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: MI date: (missing) descriptiveKeywords: (MD_Keywords) keyword: beach keyword: erosion 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]: 2016 FEMA Michigan Lidar: Part 1 (Muskegon County) [Data Date Range], https://www.fisheries.noaa.gov/inport/item/56271. 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: The State of Michigan Geographic Information Systems digital data have been tested and their documentation carefully reviewed. However, the State of Michigan and its representatives make no warranty or representation, either expressed or implied, with respect to the digital data and their documentation, their quality, performance, merchantability, or fitness for a particular purpose. The digital data are distributed on "as is" basis, and the user assumes all risk to their quality, the results obtained from their use, and the performance of the data. In no event will the State of Michigan or its representatives be liable for any direct, indirect, special, incidental or consequential damages resulting from and defect in the State of Michigan or in their documentation. This disclaimer of warranty is exclusive and in lieu of all others, oral or written, express or implied. No agent or employee is authorized to make any modification, extension, or addition to this warranty. Any conclusions drawn from the analysis of this information are not the responsibility of the State of Michigan, 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: 56271 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/56271.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 language: eng; US topicCategory: (MD_TopicCategoryCode) elevation environmentDescription: Microsoft Windows 7; ESRI ArcCatalog 9.3.1.1850 extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -86.4603 eastBoundLongitude: -85.79142 southBoundLatitude: 43.114456 northBoundLatitude: 43.468881 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2016-04-14 endPosition: 2016-04-16 supplementalInformation: Project Projection, Datums and Units. Projection - State Plane Michigan South. Horizontal datum - North American Datum of 1983 (NAD83 (2011)). Vertical datum - North American Vertical Datum of 1988 (NAVD88) using the latest geoid (Geoid12a) for converting ellipsoidal heights to orthometric heights. Units - intl feet The following are the USGS lidar fields in JSON: { "ldrinfo" : { "ldrspec" : "USGS Base Specification 1.2, QL2 meeting 19.6cm FVA", "ldrsens" : "Leica ALS70", "ldrmaxnr" : "4", "ldrnps" : "0.65", "ldrdens" : "1.67", "ldradens" : "2.2", "ldranps" : "0.71", "ldrfltht" : "2250", "ldrfltsp" : "135", "ldrscana" : "32", "ldrscanr" : "64", "ldrpulsr" : "167", "ldrpulsd" : "10", "ldrpulsw" : "3", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.3", "ldrswatw" : "1222", "ldrswato" : "30", "ldrcrs" : "NAD_1983_2011_State_Plane_Michigan_South_2113_Ft_Intl", "ldrgeoid" : "NGS Geoid12a" }, "ldraccur" : { "ldrchacc" : "0.196", "rawnva" : "0.137", "rawnvan" : "183", "clsnva" : "0.156", "clsnvan" : "183", "clsvva" : "0.169", "clsvvan" : "211" }, "lasinfo" : { "lasver" : "1.4", "lasprf" : "1", "laswheld" : "Withheld points were identified in these files with the withheld flag", "lasolap" : "Overlap points were identified in these files with the overlap flag", "lasintr" : "10", "lasclass" : { "clascode" : "1", "clasitem" : "Unclassified" }, "lasclass" : { "clascode" : "2", "clasitem" : "Bare earth" }, "lasclass" : { "clascode" : "7", "clasitem" : "Noise" }, "lasclass" : { "clascode" : "9", "clasitem" : "Water" }, "lasclass" : { "clascode" : "10", "clasitem" : "Ignored Ground (Breakline Proximity)" }, "lasclass" : { "clascode" : "17", "clasitem" : "Bridges" }, "lasclass" : { "clascode" : "18", "clasitem" : "High Noise" } }} return to top contentInfo: (MD_FeatureCatalogueDescription) complianceCode: false language: LanguageCode: eng includedWithDataset: false featureCatalogueCitation: (CI_Citation) title: USGS Base Specification 1.2, QL2 meeting 19.6 cm FVA date: (unavailable) return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: LAZ version: (missing) 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=8731 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. A new metadata will be produced to reflect your request using this record as a base. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/8731/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Bulk download of data files in LAZ format, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document. 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: Horizontal positional accuracy for the 10 counties is dependent upon the quality of the GPS/INS solution, sensor calibration and ground conditions at the time of data capture. The standard system results for horizontal accuracy meet or exceed the project specified 1.0 meter RMSE. For the 10 counties, this value is computed by comparing ground control to a DEM derived from the classified LiDAR data and represents the RMSE of residuals on controls within the project area. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: For the DEM data derived from the classified point cloud, the NVA and VVA were computed. The vertical accuracy was tested with independent survey check points located in various terrain types within the 10 counties. These check points were not used in the calibration or post processing of the lidar point cloud data. The survey check points were distributed throughout the block area. Specifications for this project require that the FVA be 19.6 cm or better @ 95 percent confidence level. Raw NVA 0.070m RMSE, or 0.137m NVA @ 95 percent Confidence Level The raw NVA was tested using 183 independent survey check points located in flat terrain types within the 10 counties. The survey checkpoints were distributed throughout the block area. The 183 independent check points were surveyed using static GPS base stations collecting point location for 20 minute intervals. Elevations were measured for the x,y,z location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.070 m. AccuracyZ has been tested to meet 10 cm Nonvegetated Vertical Accuracy at 95 Percent confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASPRS Guidelines. NVA 0.070m RMSE, or 0.156m NVA @ 95th Percentile The NVA was tested using 183 independent survey check points located in bare earth terrain types within the 10 counties. The 183 independent check points contained all NVA points and were surveyed using static GPS base stations collecting point location for 20 minute intervals. Elevations were measured for the x,y,z location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.070m, or 0.156m @ 95th Percentile defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines. VVA 0.078m RMSE, or 0.169m VVA @ 95th Percentile The VVA was tested using 211 independent survey check points located in various vegetation terrain types within the 10 counties. The 211 independent check points were surveyed using static GPS base stations collecting point location for 20 minute intervals. Elevations were measured for the x,y,z location of each check point. Elevations interpolated from the DEM surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.078m, or 0.169m @ 95th Percentile defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: LiDAR data is collected for the project area. Post processing of the simultaneously acquired GPS/INS is performed and applied to the laser returns to output a point cloud in the specified project coordinate system and datums. The point cloud data is then subjected to automated classification routines to assign all points in the point cloud to ground, water, overlap and unclassified point classes. Anomalous laser returns that occur infrequently are removed entirely from the data set. Once clean bare earth points are established, DEMs are created using bare earth points and hydro features. The DEM surface is then compared to the survey checkpoints. These accuracies must pass the Fundamental Vertical Accuracy, Supplemental Vertical Accuracy, and Consolidated Vertical Accuracy specifications. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: LiDAR data is collected within the project area and processed. After the DEMs were created, the dataset was verified against control. Control was collected in 10 adjoining counties in Michigan. These counties include: Clare, Lake, Mecosta, Missaukee, Montcalm, Muskegon, Newaygo, Osceola, Roscommon, and Wexford. Accuracy is reported for all 10 counties combined. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: At selected locations throughout the site, accurate GPS coordinates and elevations are surveyed and the points are marked with targets. dateTime: DateTime: 2016-01-01T00:00:00 processStep: (LI_ProcessStep) description: New LiDAR data is captured for the project area using a Leica ALS70 LiDAR instrument an integrated IPAS20 GPS/INS system mounted within a Aero Commander twin engine airplane. dateTime: DateTime: 2016-01-01T00:00:00 processStep: (LI_ProcessStep) description: The airborne GPS data is post-processed in Inertial Explorer software and LEICA CloudPro software to determine the LiDAR sensor's angle and orientation in the terrain (project) coordinate system and datums during the survey. dateTime: DateTime: 2016-01-01T00:00:00 processStep: (LI_ProcessStep) description: The post processed GPS/INS solution is applied to the raw lidar data to orient and project the data points into the project area reference system as an unclassified point cloud. dateTime: DateTime: 2016-01-01T00:00:00 processStep: (LI_ProcessStep) description: The georeferenced lidar data is then classified and edited in Terrasolid Terrascan software. Data is classified to produce: Class 1: unclassified, Class 2: ground, Class 7: low point, Class 9: water, Class 10: ignored ground, Class 11: withheld. dateTime: DateTime: 2016-01-01T00:00:00 processStep: (LI_ProcessStep) description: The classified lidar data is exported as 2500 X 2500 foot tiles in the LAS format with any or all classes required to produce derivative products. dateTime: DateTime: 2016-01-01T00:00:00 processStep: (LI_ProcessStep) description: For Muskegon County, the NOAA Office for Coastal Management (OCM) downloaded 2509 laz files from this USGS site: ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/USGS_LPC_MI_Muskegon_2015_LAS_2018/. The data were in State Plane Michigan South NAD83 2011 coordinates (international feet) and NAVD88 (Geoid12A) elevations in feet. The data were classified as: 1 - Unclassified, 2 - Ground, 7 - Low Noise, 9 - Water, 10 - Ignored Ground, 17 - Bridge Decks, 18 - High Noise. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 7, 9, 10, 17, 18. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. The LAStools software scripts lasinfo and lasvalidate were run on the laz files to check for errors. 2. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 3. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid 12A model, to convert from State Plane Michigan South NAD83 2011coordinates in international feet to geographic coordinates, to convert from vertical elevations in feet to meters, to assign the geokeys, to sort the data by gps time and zip the data to database and to http. dateTime: DateTime: 2019-05-09T00:00:00 processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) description: Source Contribution: The classified lidar point cloud is used to derive various data products such as, but not limited to, bare earth gridded DEM, triangulated irregular networks (TIN), contours, digital surface models (DSM). The output format is fully compliant LAS v1.4, Point Record Format 6 scaleDenominator: (MD_RepresentativeFraction) denominator: 1200 sourceCitation: (CI_Citation) title: Classified lidar date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: Sanborn Map Company Inc. role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2016 source: (LI_Source) description: Source Contribution: Targeted ground control is used to create a digital control file and control report as well as QC check of LiDAR accuracy. Predefined points (NGS when available) within the project area are targeted. sourceCitation: (CI_Citation) title: Ground control date: (CI_Date) date: 2010-01-01 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Sanborn Map Company Inc. role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2016 source: (LI_Source) description: Source Contribution: Aerial LiDAR and GPS/IMU data are recorded for the defined project area at an altitude, flight speed, scanner swath width and scanner pulse frequency to achieve the design goals of the project. sourceCitation: (CI_Citation) title: LiDAR Data date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: Sanborn Map Company Inc. role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2016 source: (LI_Source) description: Source Contribution: Post processed GPS/INS is applied to the lidar point data to georeference each point in the project coordinate system scaleDenominator: (MD_RepresentativeFraction) denominator: 1200 sourceCitation: (CI_Citation) title: Post processed GPS/INS date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: Sanborn Map Company Inc. role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2016 source: (LI_Source) description: Source Contribution: The post processed lidar data has been projected and oriented in the specified coordinate system as an un-classified point cloud. scaleDenominator: (MD_RepresentativeFraction) denominator: 1200 sourceCitation: (CI_Citation) title: Post processed lidar date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: Sanborn Map Company Inc. role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2016 source: (LI_Source) description: Source Contribution: The tile definition defines discreet non-overlapping rectangular areas used as cut lines to break up the large classified lidar dataset into smaller, more manageable data tiles. Each tile is 2500ft by 2500ft in dimension. scaleDenominator: (MD_RepresentativeFraction) denominator: 1200 sourceCitation: (CI_Citation) title: Tile Definition date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: State of Michigan role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2016 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-08-01T06:41:56 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |