| 2008 MN DNR Lidar: Southeast Minnesota | referenceSystemInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:68818 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-02-21T18:41:16 metadataStandardName: ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data metadataStandardVersion: ISO 19115-2:2009(E) 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 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 spatialRepresentationInfo: return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2008 MN DNR Lidar: Southeast Minnesota alternateTitle: mn2008_se_minn_m9684_metadata date: (CI_Date) date: 2008 dateType: (CI_DateTypeCode) creation date: (CI_Date) date: (missing) dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 68818 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/68818 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://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/9684/ept.json protocol: WWW:LINK-1.0-http--link name: Entwine Point Tiles (EPT) description: Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/lidar/viewer/v/noaapotree.html?m=9684&g=geoid18 protocol: WWW:LINK-1.0-http--link name: NOAA Potree 3D View description: Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer. 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) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9684/supplemental/mn2008_southeast_m9684.kmz protocol: WWW:LINK-1.0-http--link name: Browse Graphic description: This graphic shows the lidar coverage for the 2008 lidar acquisition for Southeast Minnesota. function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (unknown) abstract: This high accuracy, bare-earth processed lidar data includes one-meter resolution DEMs, two-foot contours, edge-of-water breaklines and LAS points for nine counties in Southeast Minnesota: Dodge, Fillmore, Freeborn, Houston, Mower, Olmsted, Steele, Wabasha, and Winona. The project was coordinated by the Minnesota Department of Natural Resources and several partners including the U.S. Geological Survey, the Minnesota Department of Transportation, and staff from the affected counties. The data was collected by AeroMetric, Inc. (now Quantum Spatial) in November 2008 and was delivered in tiles that covered an area 1/16th of a 1:24,000-scale USGS quadrangle (approximately 3.25 square miles). DNR conducted the QA/QC starting April 2009. As part of the processing, one- and three-meter county mosaic DEMs were created and used for visual quality assessment. The original metadata record was created at the Minnesota Geospatial Information Office by combining information supplied by AeroMetric and the DNR. This metadata record reflects the Southeast Minnesota data that are available from the NOAA Digital Coast Data Access Viewer (DAV). The NOAA Office for Coastal Management (OCM) downloaded 1545 laz point data files from this USGS site: https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/MN_SEMN_2008/laz/ The data were processed to the NOAA Digital Coast Data Access Viewer (DAV) to make the data available for custom downloads and to AWS S3 for bulk downloads. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: The Southeast Minnesota lidar project's goal was to provide high accuracy, bare-earth processed lidar data suitable for the FEMA National Flood Insurance Program. In August 2007, the nine counties had experienced a major rainfall event with over 10 inches of rain that caused extensive flooding. The Minnesota Legislature appropriated money to aid in flood relief and to provide mitigation against future floods including the acquisition of high-resolution elevation data using lidar technology. credit: AeroMetric, Inc. and the Minnesota Department of Natural Resources 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) asNeeded descriptiveKeywords: (MD_Keywords) keyword: EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN 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 keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > MINNESOTA 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: 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]: 2008 MN DNR Lidar: Southeast Minnesota [Data Date Range], https://www.fisheries.noaa.gov/inport/item/68818. 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: 1. Minnesota Department of Natural Resources General Geographic Data License Agreement: https://www.dnr.state.mn.us/sitetools/data_software_license.html 2. MnGeo's data disclaimer: https://www.mngeo.state.mn.us/chouse/disclaimer.html 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: 68818 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/68818.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: -93.437889 eastBoundLongitude: -91.19341 southBoundLatitude: 43.496441 northBoundLatitude: 44.484934 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2011-11-18 endPosition: 2011-11-24 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: 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=9684/details/9684 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://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9684/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: All these data products were acquired at 2400 meters above mean terrain (AMT) and have a horizontal accuracy of 0.40 meters, with a nominal point spacing of 1.0 meters. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: 1. AeroMetric's Tests: The Fundamental Vertical Accuracy (FVA) of the TIN achieved 0.161 meters at a 95% confidence level in the 'Open Terrain' land cover category. 26 control points were used in this evaluation. The Consolidated Vertical Accuracy (CVA) of the TIN achieved 0.36 meters at a 95% confidence level according to ASPRS Guidelines, Vertical Accuracy Reporting for lidar for all land cover categories. 127 points covering 5 land cover categories were tested. Land Cover categories are the following: Open Terrain, Tall Weeds and crops, Brush lands and low trees, Forested areas fully covered by trees, and Urban areas with dense man-made structures. Supplemental Vertical Accuracy (SVA) of the TIN are shown below at a 95% confidence level, derived by the ASPRS Guidelines, Vertical Accuracy Report for Lidar Data based on the 95th percentile error in all of the individual land cover categories. Below are the land cover categories with the achieved accuracy reported at a 95th percentile error and the number of test points: Open Terrain: 0.144m, 26 Tall Weeds and crops: 0.240m, 23 Brush lands and low trees: 0.248m, 22 Forested areas fully covered by trees: 0.165m, 22 Urban areas with dense man-made structures: 0.216m, 34 2. MnDNR's Tests: Accuracy of the dataset was verified by a second set of ground control points provided and tested by MnDNR. The Consolidated Vertical Accuracy (CVA) of the TIN as tested by MnDNR achieved 0.287 meters at a 95% confidence level of all land cover categories. 1009 control points covering the 5 land classes were used in this evaluation. The vertical RMSE and sample count per county as tested by MnDNR is as follows: Dodge 0.129m, 121; Fillmore 0.155m, 128; Houston 0.110m, 134; Mower 0.161m, 115; Olmsted 0.117m, 125; Steele 0.125m, 137; Wabasha 0.106m, 97; Winona 0.161m, 176. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: Complete result: (missing) lineage: (LI_Lineage) statement: Data were collected and processed by AeroMetric, Inc. and made available on the USGS ftp site. The data were downloaded from the USGS ftp site by the NOAA Office for Coastal Management (OCM) where the data were processed to make it available for custom download from the NOAA Digital Coast Data Access Viewer (DAV) and for bulk download from AWS S3. processStep: (LI_ProcessStep) description: The lidar data was captured using fixed wing aircraft equipped with lidar systems. The lidar system included a differential GPS unit and inertial measurement system to provide superior accuracy. Both AeroMetric, Inc. and Surdex Corporation acquired lidar data over the project area. Surdex's data was post-processed to a raw point cloud by Surdex and then delivered to AeroMetric to be merged into one raw point cloud dataset. Acquisition parameters: 1. Scanners - Optech ALTM Gemini (AeroMetric) and Leica ALS50-2 (Surdex) 2. Flight Height - 2400 meters above mean terrain 3. Swath Width - 32 degrees 4. Sidelap - 60% 5. Nominal Post Spacing - 1.0 meter GPS and IMU processing parameters: 1. Processing Programs - AeroMetric= Applanix - POSGPS and POSProc; Surdex= GravNav GNSS and Leica IPAS 2. Maximum baseline length - Not greater than 30km. 3. Number of base stations during lidar collection - A minimum of 2 MnDOT CORS stations were occupied during any of the lifts to acquire the lidar data. The following were the occupied base stations: BLUE, CLDN, DDGC, ELKT, EYTA, LCHI, LCRS, NALB, PRSP, REDW, RSHF, STWV, TWNL, WBSH, WINO, and WSCA. 4. GPS and IMU processing monitored for consistency and smoothness - Yes. Point Cloud Processing: 1. Program - AeroMetric= Optech Dashmap; Surdex= Leica ALS Post Processor 2. Horizontal Datum - NAD83(NSRS2007) 3. Horizontal Coordinates - UTM, Zone 15, in meters 4. Vertical Datum - NAVD88 5. Geoid Model used to reduce satellite derived elevations to orthometric heights - NGS Geoid03. processStep: (LI_ProcessStep) description: Lidar Processing: 1. Processing Programs and versions - TerraSolid TerraScan (version 009.010), TerraModeler (version 009.002) and TerraMatch (version 009.003) and Intergraph MicroStation (version.08.01.02.15). 2. Point Cloud data was imported to TerraScan in a Microstation V8 (V) CAD environment. 3. The data is projected to the horizontal project coordinate system of UTM - Zone 15 in meters. 4. Analyzed the data for overall completeness and consistency. This was to ensure that there are no voids in the data collection. 5. Inspected for calibration errors in the dataset using the TerraMatch software. This was accomplished by sampling the data collected across all flight lines and classifying the individual lines to ground. The software used the ground-classified lines to compute corrections (Heading, Pitch, Roll, and Scale). 6. Orientation corrections (i.e., calibration corrections) were then applied to the entire dataset. 7. Automatic ground classification was performed using algorithms with customized parameters to best fit the project area. Several areas of varying relief and planimetric features were inspected to verify the final ground surface. 8. AeroMetric provided Quality Assurance and Quality Control (QA/QC) data for this project. AeroMetric captured 127 QA/QC points in multiple land cover categories that were used to test the accuracy of the lidar ground surface. TerraScan's Output Control Report (OCR) was used to compare the QA/QC data to the lidar data. This routine searches the lidar dataset by X and Y coordinate, finds the closest lidar point and compares the vertical (Z) values to the known data collected in the field. Based on the QA/QC data, a bias adjustment was determined, and the results were applied to the lidar data. A final OCR was performed with a resulting RMSE of 0.109 meters. 9. Once the automatic processing and the testing of lidar was complete, AeroMetric meticulously reviewed the generated bare-earth surface data to insure that proper classification was achieved as part of a Quality Control process. 10. Final deliverables were generated and cut out according to the MnDNR tiling and naming scheme (1/16 USGS 7.5 minute quadrangles). processStep: (LI_ProcessStep) description: Geodatabase Creation: 1. The final geodatabase for each of the 1544 tiles (1/16 USGS 7.5 minute quadrangles) was created using Esri ArcInfo software. 2. Each MicroStation contour file was converted into shapefile format. The contours were created using only the keypoint point features from the LAS data files. 3. The shapefile was inserted into the geodatabase as a feature class named 'Contours' inside the defined feature dataset 'Contour_Data'. 4. Topology checks were done to look for dangles, crossing and intersecting contours, as well as other anomalies. All errors were fixed and a second topology check was done to verify an error free dataset. 5. The contour features have two attributes, 'Contour_Type', which identifies the contour type (index, intermediate, depression, and depression_index) and 'ELEVATION' which indicates the contour elevation in U.S. feet. 6. The BareEarth data within the LAS point files was imported into a feature class named 'Bare_Earth_Points' inside the defined feature dataset 'Terrain_Data'. The points were created as multipoint features which group the LAS points into blocks of data in order to reduce the number of records in the geodatabase. 7. The breaklines were imported as polylines into a feature class named 'Hydro_Breaklines' inside the defined feature dataset 'Terrain_Data'. 8. The 1.0 meter DEM data was imported as raster points into the defined feature dataset 'DEM01'. Each point in the DEM file became a pixel with an assigned elevation in meters. processStep: (LI_ProcessStep) description: Final Deliverables: 1. One paper copy of the Lidar Accuracy Assessment Report. 2. One firewire hard drive containing the following data: a. Point Cloud Data in LAS 1.1 format for each of the 1544 tiles (1/16 USGS 7.5 minute quadrangles). x=Easting (0.01 resolution), y=Northing (0.01 resolution), z=Elevation (0.01 resolution), i=Intensity (0.1 resolution) LAS data classified using the following codes: 0, 2, 5, 6, 8, 9, 10, 12 according to ASPRS LAS format classification table. Units in meters. b. Geodatabase files for each of the 1544 tiles (1/16 USGS 7.5 minute quadrangles) including the following feature classes: i. Bare_Earth_Points - LAS Point Cloud Data ii. Hydro_Breaklines - Water/shoreline breakline data iii. Hydro_Breaklines - Enhanced breakline data included, but was not limited to, retaining walls, road edges, ridge lines, dams for Project Area B only. iv. DEM01 - Bare-Earth DEM raster at 1.0 meter resolution per tile. Vertical units in meters at 0.01 meter resolution. v. Contours - Vector contours at 2 foot intervals represented in U.S. feet vertically and meters horizontally. 3. FGDC Compliant metadata for the Point Cloud Data LAS delivery. 4. FGDC Compliant metadata for the Geodatabase delivery. MnDNR reviewed the deliverables for content and accuracy. Any needed corrections to the content of the dataset were addressed and corrected by AeroMetric and redelivered. MnDNR created the 3-meter DEM using the following method: - Step 1: Mosaic all the tiles that make up the county into a file geodatabase. - Step 2: The 1-meter grid is then "filled" to fill in any NO DATA cells that have data around them. This is common when grid tiles are merged. The commmand that was used is the focalmean tool within the con tool in the Spatial Analyst | Map Algebra tool. The equation used is: con(isnull(dem01),focalmean dem01,rectangle,3,3,data),dem01). The DEM01 grid is then deleted and replaced with the output from this step. - Step 3: The filled raster is then reduced to 3-meter resolution using the Spatial Analyst, Aggregate Tool. A 3x3 window of 1-meter cells are combined into one 3x3 meter cell and assigned a value based on the mean of the 9 cells. processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) downloaded 1545 laz point data files from this USGS site: https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/MN_SEMN_2008/laz/ The data were in UTM Zone 15N NAD83 (NSRS2007), meters coordinates and NAVD88 (Geoid03) elevations in meters. The data were classified as: 0 - Never Classified, 2 - Ground, 5 - Vegetation, 6 - Buildings, 8 - Model Key Point, 9 - Water, 10 - Bridge Decks, 12 - Overlap. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 0,2,5,6,8,9,10,12. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Internal OCM scripts were run to check the number of points by classification and by flight ID and the gps, elevation, and intensity ranges. 2. Internal OCM scripts were run on the laz files to: a. Convert from orthometric (NAVD88) elevations to NAD83 (2011) ellipsoid elevations using the Geoid03 model b. Convert the laz files from UTM Zone 15N NAD83 (NSRS2007) meters coordinates to geographic coordinates c. Assign the geokeys, sort the data by gps time and zip the data to database. dateTime: DateTime: 2022-12-14T00:00:00 processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) sourceCitation: (CI_Citation) title: USGS date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: USGS contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/ protocol: WWW:LINK-1.0-http--link name: USGS Rockyweb download site description: Source Citation URL function: (CI_OnLineFunctionCode) information 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: 2023-08-01T07:38:35 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |