| 2018 USGS Lidar: Ottawa NF, MI | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:58790 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: Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2020-09-15T00: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: (MD_VectorSpatialRepresentation) topologyLevel: (MD_TopologyLevelCode) geometricObjects: (MD_GeometricObjects) geometricObjectType: (MD_GeometricObjectTypeCode) point geometricObjectCount: 52863005585 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(NSRS2007) 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/4759/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:4759 version: 6.18.3 (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: 2018 USGS Lidar: Ottawa NF, MI alternateTitle: 2018_Ottawa_MI_9013 date: (CI_Date) date: 2018-12-11 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 58790 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: Product: This lidar data set includes classified LAS 1.4 files, with unclassified (1), ground (2), low vegetation (3), medium vegetation (4), high vegetation (5), building (6), noise (7), water (9), ignored ground (10), withheld (11), and bridge (17). Geographic Extent: Four counties in Michigan, covering approximately 2,563 total square miles. Dataset Description: The Ottawa National Forest, MI, 2017 LiDAR project called for the planning, acquisition, processing, and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification, Version 1.2. The data were developed based on a horizontal projection/datum of NAD83 (2011), State Plane Michigan North FIPS 2111, Intl feet and vertical datum of NAVD88 (GEOID12B), Intl feet. LiDAR data were delivered as processed Classified LAS 1.4 files formatted to 11,799 individual 2,500 feet x 2,500 feet tiles, as tiled intensity imagery, and as tiled bare earth DEMs; all tiled to the same 2,500 feet x 2,500 feet schema. Continuous breaklines were produced in Esri file geodatabase format. Ground Conditions: LiDAR was collected in spring of 2018, while no snow was on the ground and rivers were at or below normal levels. In order to post process the LiDAR data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Quantum Spatial, Inc. utilized a total of 59 ground control points that were used to calibrate the LiDAR to known ground locations established throughout the project area. An additional 143 independent accuracy checkpoints, 81 in Bare Earth and Urban landcovers (81 NVA points), 62 in Tall Weeds categories (62 VVA points), were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data. Tiled and mosaicked hydro-flattened bare-earth DEMs, continuous breaklines, and tiled and mosaicked intensity imagery are available from USGS National Map. 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 elevation modeling, etc. Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create intensity images, breaklines and raster DEMs. The purpose of these LiDAR data was to produce high accuracy 3D hydro-flattened digital elevation models (DEMs) with a 2.5-foot cell size. These raw LiDAR point cloud data were used to create classified LiDAR LAS files, intensity images, 3D breaklines, and hydro-flattened DEMs as necessary. credit: USGS, State of Michigan, Quantum Spatial, Inc. 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 Oct 20, 2020 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: 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: Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) custodian resourceMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) notPlanned graphicOverview: (MD_BrowseGraphic) fileName: https://coast.noaa.gov/htdata/lidar3_z/geoid12b/data/9013/supplemental/extent_Ottawa_MI_m9013.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 > Bathymetry/Seafloor Topography > Bathymetry > Coastal Bathymetry 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) descriptiveKeywords: (MD_Keywords) keyword: Continent > North America > United States Of America keyword: Continent > North America > United States Of America > Michigan keyword: Continent > North America > United States Of America > Michigan > Gogebic County keyword: Continent > North America > United States Of America > Michigan > Houghton County keyword: Continent > North America > United States Of America > Michigan > Iron County keyword: Continent > North America > United States Of America > Michigan > Ontonagon County keyword: Continent > North America > United States Of America > U.S. Coastline keyword: Vertical Location > Land Surface keyword: Vertical Location > Seafloor type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Location Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Earth Remote Sensing Instruments > Active Remote Sensing > Profilers/Sounders > Lidar/Laser Sounders > LIDAR > Light Detection and Ranging type: (MD_KeywordTypeCode) instrument thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Instrument Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Aircraft > Aircraft type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Lidar - partner (no harvest) type: (MD_KeywordTypeCode) project thesaurusName: (CI_Citation) title: InPort date: (inapplicable) resourceConstraints: (MD_Constraints) useLimitation: NOAA provides no warranty, nor accepts any liability occurring from any incomplete, incorrect, or misleading data, or from any incorrect, incomplete, or misleading use of the data. It is the responsibility of the user to determine whether or not the data is suitable for the intended purpose. resourceConstraints: (MD_LegalConstraints) accessConstraints: (MD_RestrictionCode) otherRestrictions useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: Access Constraints: None | Use Constraints: Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations. | Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of 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: 58790 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/58790.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 spatialResolution: (MD_Resolution) distance: Distance: .3 language: eng; US topicCategory: (MD_TopicCategoryCode) elevation topicCategory: (MD_TopicCategoryCode) elevation extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -90.24306067 eastBoundLongitude: -88.6095749 southBoundLatitude: 46.01211535 northBoundLatitude: 46.77110143 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2018-05-15 endPosition: 2018-10-24 supplementalInformation: USGS Contract No. G16PC00016, Task Order No. 140G0218F00167; CONTRACTOR: Quantum Spatial, Inc. The following are the USGS lidar fields in JSON: { "ldrinfo" : { "ldrspec" : "USGS-NGP Base Specification v1.2", "ldrsens" : "Leica ALS70", "ldrmaxnr" : "4", "ldrnps" : "0.6", "ldrdens" : "2.8", "ldranps" : "0.6", "ldradens" : "2.8", "ldrfltht" : "2000", "ldrfltsp" : "150", "ldrscana" : "18", "ldrscanr" : "56", "ldrpulsr" : "278", "ldrpulsd" : "4", "ldrpulsw" : "0.44", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.22", "ldrswatw" : "1300", "ldrswato" : "26", "ldrgeoid" : "GEOID12B", "ldrcrs" : "NAD83 (2011) State Plane Michigan North FIPS 2111, Intl feet" }, "ldrinfo" : { "ldrspec" : "USGS-NGP Base Specification v1.2", "ldrsens" : "Leica ALS80", "ldrmaxnr" : "Unlimited", "ldrnps" : "0.62", "ldrdens" : "2.63", "ldranps" : "0.62", "ldradens" : "2.63", "ldrfltht" : "1900", "ldrfltsp" : "160", "ldrscana" : "19", "ldrscanr" : "53.3", "ldrpulsr" : "282.8", "ldrpulsd" : "4", "ldrpulsw" : "0.42", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.22", "ldrswatw" : "1308", "ldrswato" : "35", "ldrgeoid" : "GEOID12B", "ldrcrs" : "NAD83 (2011) State Plane Michigan North FIPS 2111, Intl feet" }, "ldraccur" : { "ldrchacc" : "0", "rawnva" : "0.849", "rawnvan" : "81" }, "lasinfo" : { "lasver" : "1.4", "lasprf" : "6", "laswheld" : "Withheld (ignore) points were identified in these files using the standard LAS Withheld bit", "lasolap" : "Swath "overage" points were identified in these files using the standard LAS overlap bit", "lasintr" : "16", "lasclass" : { "clascode" : "1", "clasitem" : "Processed, but Unclassified" }, "lasclass" : { "clascode" : "2", "clasitem" : "Bare-Earth Ground" }, "lasclass" : { "clascode" : "3", "clasitem" : "Low Vegetation" }, "lasclass" : { "clascode" : "4", "clasitem" : "Medium Vegetation" }, "lasclass" : { "clascode" : "5", "clasitem" : "High Vegetation" }, "lasclass" : { "clascode" : "6", "clasitem" : "Buildings" }, "lasclass" : { "clascode" : "7", "clasitem" : "Low Noise" }, "lasclass" : { "clascode" : "9", "clasitem" : "Water" }, "lasclass" : { "clascode" : "10", "clasitem" : "Ignored Ground" }, "lasclass" : { "clascode" : "11", "clasitem" : "Withheld/Reserved Points" }, "lasclass" : { "clascode" : "17", "clasitem" : "Bridge Decks" }, "lasclass" : { "clascode" : "18", "clasitem" : "High Noise" } }} return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: Zip version: (missing) fileDecompressionTechnique: Zip 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: 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=9013 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. Change to an orthometric vertical datum is one of the many options. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/lidar3_z/geoid18/data/9013 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. They will be in an orthometric datum. function: (CI_OnLineFunctionCode) download return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The project specifications require that only Non-Vegetated Vertical Accuracy (NVA) be computed for raw LiDAR point cloud swath files. The required accuracy (ACCz) is: 19.6 cm at a 95% confidence level, derived according to NSSDA, i.e., based on RMSE of 10 cm in the "bare earth" and "urban" land cover classes. The NVA was tested with 81 checkpoints located in bare earth and urban (non-vegetated) areas. These checkpoints were not used in the calibration or post processing of the LiDAR point cloud data. The checkpoints were distributed throughout the project area and were surveyed using GPS techniques. See survey report for additional survey methodologies. Elevations from the unclassified LiDAR surface were measured for the x,y location of each checkpoint. Elevations interpolated from the LiDAR surface were then compared to the elevation values of the surveyed control points. AccuracyZ has been tested to meet 19.6 cm or better Non-Vegetated Vertical Accuracy at 95% 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)/ASRPS Guidelines. The project specifications require the accuracy (ACCz) of the derived DEM be calculated and reported in two ways: 1. The required NVA is: 19.6 cm at a 95% confidence level, derived according to NSSDA, i.e., based on RMSE of 10 cm in the "bare earth" and "urban" land cover classes. This is a required accuracy. The NVA was tested with 81 checkpoints located in bare earth and urban (non-vegetated) areas. 2. Vegetated Vertical Accuracy (VVA): VVA shall be reported for "tall weeds" land cover classes. The target VVA is: 29.4 cm at the 95th percentile, derived according to ASPRS Guidelines, Vertical Accuracy Reporting for LiDAR Data, i.e., based on the 95th percentile error in all vegetated land cover classes combined. This is a target accuracy. The VVA was tested with 62 checkpoints located in forested and tall weeds (vegetated) areas. The checkpoints were distributed throughout the project area and were surveyed using GPS techniques. See survey report for additional survey methodologies. AccuracyZ has been tested to meet 19.6 cm or better Non-Vegetated Vertical Accuracy at 95% 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)/ASRPS Guidelines. Tested 0.849 meters NVA at a 95% confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA). The NVA of the raw LiDAR point cloud swath files was calculated against TINs derived from the final calibrated and controlled swath data using 81 independent checkpoints located in Bare Earth and Urban land cover classes. Tested 0.845 meters NVA at a 95% confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA). The NVA of the DEM was calculated using 81 independent checkpoints located in the Bare Earth and Urban land cover categories. Tested 1.37 meters VVA was calculated using 62 checkpoints located in the Forested and Tall Weeds land cover categories at the 95th percentile, derived according to ASPRS Guidelines, Vertical Accuracy Reporting for LiDAR Data. Tested against the DEM. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: All files are inspected to ensure that they conform to the specified file naming conventions, all files load in their correct geographic position, all files conform to the project specifications for file standard and content. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Data cover the entire area specified for this project. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: Raw Data and Boresight Processing: The boresight for each lift was done individually as the solution may change slightly from lift to lift. The following steps describe the Raw Data Processing and Boresight process: 1) Technicians processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source data for boresight. 2) Technicians first used Quantum Spatial, Inc. proprietary and commercial software to calculate initial boresight adjustment angles based on sample areas selected in the lift. These areas cover calibration flight lines collected in the lift, cross tie, and production flight lines. These areas are well distributed in the lift coverage and cover multiple terrain types that are necessary for boresight angle calculation. The technician then analyzed the results and made any necessary additional adjustment until it was acceptable for the selected areas. 3) Once the boresight angle calculation was completed for the selected areas, the adjusted settings were applied to all of the flight lines of the lift and checked for consistency. The technicians utilized commercial and proprietary software packages to analyze how well flight line overlaps matched for the entire lift and adjusted as necessary until the results met the project specifications. 4) Once all lifts were completed with individual boresight adjustment, the technicians checked and corrected the vertical misalignment of all flight lines and also the matching between data and ground truth. The relative accuracy was less than or equal to 7 cm RMSEz within individual swaths and less than or equal to 10 cm RMSEz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed checkpoints after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. dateTime: DateTime: 2018-01-01T00:00:00 processStep: (LI_ProcessStep) description: LAS Point Classification: The point classification was performed as described below. The bare earth surface was manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface was finalized, it was then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS Class 2) LiDAR data inside of the Lake Pond and Double Line Drain hydro-flattened breaklines were then classified to Water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 1 meter was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 10). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (ASPRS Class 2) points were reclassified to the correct classification after the automated classification was completed. All overlap data was processed through automated functionality provided by TerraScan to classify the overlapping flight line data to approved classes by USGS. The overlap data was classified using standard LAS overlap bit. These classes were created through automated processes only and were not verified for classification accuracy. Due to software limitations within TerraScan, these classes were used to trip the withheld bit within various software packages. These processes were reviewed and accepted by USGS through numerous conference calls and pilot study areas. All data were manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper was used as a final check of the bare earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files for both the All Point Cloud Data and the Bare Earth. Quantum Spatial, Inc. proprietary software was used to perform final statistical analysis of the classes in the LAS files, on a per tile level to verify final classification metrics and full LAS header information. dateTime: DateTime: 2018-01-01T00:00:00 processStep: (LI_ProcessStep) description: Hydro-Flattened Breakline Processing: Class 2 (ground) LiDAR points were used to create a bare earth surface model. The surface model was then used to heads-up digitize 2D breaklines of inland streams and rivers with a 100-foot nominal width and inland ponds and lakes of 2 acres or greater surface area. Elevation values were assigned to all Inland Ponds and Lakes, Inland Pond and Lake Islands, Inland Stream and River Islands, using TerraModeler functionality. Elevation values were assigned to all inland streams and rivers using Quantum Spatial, Inc. proprietary software. All Ground (ASPRS Class 2) LiDAR data inside of the collected inland breaklines were then classified to Water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 1 meter was also used around each hydro-flattened feature. These points were moved from ground (ASPRS Class 2) to Ignored Ground (ASPRS Class 10). The breakline files were then translated to Esri file geodatabase format using Esri conversion tools. Breaklines were reviewed against LiDAR intensity imagery to verify completeness of capture. All breaklines were then compared to TINs (triangular irregular networks) created from ground only points prior to water classification. The horizontal placement of breaklines was compared to terrain features and the breakline elevations were compared to LiDAR elevations to ensure all breaklines matched the LiDAR within acceptable tolerances. Some deviation was expected between breakline and LiDAR elevations due to monotonicity, connectivity, and flattening rules that were enforced on the breaklines. Once completeness, horizontal placement, and vertical variance were reviewed, all breaklines were reviewed for topological consistency and data integrity using a combination of Esri Data Reviewer tools and proprietary tools. dateTime: DateTime: 2018-01-01T00:00:00 processStep: (LI_ProcessStep) description: Hydro-Flattened Raster DEM Processing: Class 2 (Ground) LiDAR points in conjunction with the hydro-breaklines were used to create a 2.5-foot hydro-flattened raster DEM. Using automated scripting routines within ArcMap, an ERDAS Imagine .IMG file was created for each tile. Each surface was reviewed using Global Mapper to check for any surface anomalies or incorrect elevations found within the surface. dateTime: DateTime: 2018-01-01T00:00:00 processStep: (LI_ProcessStep) description: Intensity Image Generation Processing: GeoCue software was used to create the deliverable intensity images. All overlap classes were ignored during this process. This helps to ensure a more aesthetically pleasing image. The GeoCue software was then used to verify full project coverage as well. TIF/TWF files were then provided as the deliverable for this dataset requirement. dateTime: DateTime: 2018-01-01T00:00:00 processStep: (LI_ProcessStep) description: Tile Index Processing: Tiles were created using a 0,0 origin point to ensure proper divisibility of raster and image cells. A 2,500 feet x 2,500 feet tile size was used as called for in the Task Order. Tile index was output in Esri shapefile format. Tile names are derived from the US National Grid. dateTime: DateTime: 2018-01-01T00:00:00 processStep: (LI_ProcessStep) description: QC Checkpoint Processing: Please see the survey report for more information on control point location methodologies. The QC checkpoint shapefiles were generated from XYZ text files using a combination of Global Mapper and ArcMap software. dateTime: DateTime: 2018-01-01T00:00:00 processStep: (LI_ProcessStep) description: Processing Boundary Processing: The processing boundary was created using the original client-provided AOI shapefile. The original file was buffered by 100 meters in order to meet task order requirements for data coverage. dateTime: DateTime: 2018-01-01T00:00:00 processStep: (LI_ProcessStep) description: Calibration Point Processing: Please see the survey report for more information on control point location methodologies. The calibration control point shapefiles were generated from XYZ text files using a combination of Global Mapper and ArcMap software. dateTime: DateTime: 2018-01-01T00:00:00 processStep: (LI_ProcessStep) description: NOAA OCM downloaded 11800 laz files from the USGS rockyftp site. The files were in Michigan State Plane North projection NAD83(2011) and NAVD88 geoid12b, with all units in feet. OCM processed the files to the Digital Coastd using internal scripts. For provisioning purposes the files were converted to geographic projection and ellipsoidal heights by reversing the application of geoid12b, with units in meters. processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) sourceCitation: (CI_Citation) title: Raw Lidar date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: Quantum Spatial role: (CI_RoleCode) originator 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: 2020-10-20T05:11:49 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |