| 2020 SEWRPC Lidar DEM: Milwaukee County, WI | referenceSystemInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:70063 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-06-02T19:09:28 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) code: EPSG::6360 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) code: EPSG::6609 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2020 SEWRPC Lidar DEM: Milwaukee County, WI date: (CI_Date) date: 2020 dateType: (CI_DateTypeCode) creation date: (CI_Date) date: 2020-10-05 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 70063 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/70063 protocol: WWW:LINK-1.0-http--link name: Full Metadata Record description: View the complete metadata record on InPort for more information about this dataset. function: (CI_OnLineFunctionCode) information role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9842/details/9842 protocol: WWW:LINK-1.0-http--link name: Custom DEM Download description: Link to custom download, from the Data Access Viewer (DAV), the lidar point data from which these raster Digital Elevation Model (DEM) data were created. 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/9842/breaklines/index.html protocol: WWW:LINK-1.0-http--link name: Hydro Breaklines description: Link to the hydro breaklines in ESRI gdb and OGC GeoPackage formats. 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/9842/supplemental/SEWRPC_MilwaukeeCountyLidar_508OCM.pdf protocol: WWW:LINK-1.0-http--link name: Survey Report description: Link to the survey report. 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: This Southeastern Wisconsin Regional Planning Commission (SEWRPC) high density lidar project encompassed the entirety of Milwaukee County, Wisconsin, which covers approximately 250 square miles and includes a 333 foot buffer around the county boundary. The airborne lidar data was acquired at an aggregate nominal point density (ANPD) of 30 points per square meter. Project specifications are based on SEWRPC requirements. The data was developed and delivered in State Plane Coordinates, Wisconsin South zone, with a horizontal datum of NAD83(2011) and vertical datum of NAVD88 - Geoid12B, with horizontal and vertical units in US Survey Feet. LiDAR data was acquired using a Riegl VQ 1560i sensor, serial number 4040, from April 2, 2020 to April 3, 2020 in three total lifts. Lidar acquisition occurred with leaves absent from deciduous trees, when no snow was present on the ground and with rivers at or below normal levels. The lidar data was calibrated, processed, and delivered in 2020. The data deliverables include classified point cloud, breaklines, and a digital elevation model. The lidar data is not to be used for purposes other than those outlined by SEWRPC for its partners and stakeholders on this project. This metadata record supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). The NOAA Office for Coastal Management (OCM) received ERDAS Imagine (.img) raster files at a 1 ft grid spacing from the Milwaukee County Land Information Office. The data were processed to the NOAA Digital Coast Data Access Viewer (DAV) to make the data available for bulk and custom downloads. In addition to these bare earth Digital Elevation Model (DEM) data, the lidar point data that these DEM data were created from, are also available. These data are available for custom download at the link provided in the URL section of this metadata record. purpose: This data, along with its derivatives, is the result of a countywide elevation mapping with cooperative partnerships from Southeastern Wisconsin Regional Planning Commission (SEWRPC). This data was produced from lidar data collected in April 2020, which was processed and delivered in October 2020. credit: Ayres Associates, Southeastern Wisconsin Regional Planning Commission (SEWRPC) 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) notPlanned graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9842/supplemental/wi2020_milwaukee_m9842.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 > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION > DIGITAL ELEVATION/TERRAIN MODEL (DEM) 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 keyword: CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > WISCONSIN 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: DEMs - 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]: 2020 SEWRPC Lidar DEM: Milwaukee County, WI [Data Date Range], https://www.fisheries.noaa.gov/inport/item/70063. 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. The lidar data is not to be used for purposes other than those outlined by SEWRPC for its partners and stakeholders on this project. Acknowledgement of the Southeastern Wisconsin Regional Planning Commission (SEWRPC) would be appreciated for products derived from these data. | 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: 2020 SEWRPC Lidar: Milwaukee County, WI date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 70056 associationType: (DS_AssociationTypeCode) crossReference 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: 70063 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/70063.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) grid language: eng; US topicCategory: (MD_TopicCategoryCode) elevation environmentDescription: Terrasolid extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -88.075628 eastBoundLongitude: -87.811807 southBoundLatitude: 42.837963 northBoundLatitude: 43.195998 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2020-04-02 endPosition: 2020-04-03 supplementalInformation: Bit Depth/Pixel Type = 32-bit float Raster Cell Size = 1 foot Interpolation or Resampling Technique = Triangulated Irregular Network Required Vertical Accuracy = 9.8 cm NVA return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: Zip version: (missing) fileDecompressionTechnique: Zip distributionFormat: (MD_Format) name: GeoTIFF 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=9843/details/9843 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://chs.coast.noaa.gov/htdata/raster5/elevation/WI_Milwaukee_DEM_2020_9843 protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Bulk download of data files in Wisconsin South State Plane NAD83(2011) US Survey Feet coordinates and elevations in NAVD88 (Geoid12b) feet. 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 the accuracy (ACCz) of the derived DEM be calculated and reported in two ways: 1. The required NVA is: 9.8cm at a 95% confidence level, derived according to NSSDA, i.e., based on RMSE of 5 cm in the bare earth and urban land cover classes. This is a required accuracy. The NVA was tested with 11 checkpoints located in bare earth and urban (non-vegetated) areas. 2. Vegetated Vertical Accuracy (VVA): VVA shall be reported for brushlands/low trees and tall weeds/crops land cover classes. The target VVA is: 15 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 12 checkpoints located in tall weeds/crops and brushlands/low trees (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 9.8 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.124 feet NVA at a 95% confidence level (or 2 cm RMSE) 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 11 independent checkpoints located in the Bare Earth and Urban land cover categories. Tested 0.229 feet VVA at the 95th Percentile (or 7 cm RMSE) was calculated using 12 checkpoints located in the Brushlands and Low Trees and Tall Weeds and Crops 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: Datasets contain complete coverage of tiles. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. There are no void areas or missing data. The raw point cloud is of good quality and data passes Non-Vegetated Vertical Accuracy specifications. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Data covers the entire area specified for this project. result: (missing) lineage: (LI_Lineage) statement: Data were collected for the Southeastern Wisconsin Regional Planning Commission (SEWRPC) and were provided to the NOAA Office for Coastal Management (OCM) by the Milwaukee County Land Information Office. OCM processed the data to make it available for custom download from the NOAA Digital Coast Data Access Viewer (DAV) and for bulk download from https. processStep: (LI_ProcessStep) description: 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 RIEGL RiPROCESS 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 is 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 match 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 2 cm RMSEz within individual swaths and less than or equal to 5 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 check points after the z correction to ensure the requirement of NVA = 9.8 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification 1.3, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening. dateTime: DateTime: 2020-10-05T00:00:00 processStep: (LI_ProcessStep) description: Steps followed by Ayres for LAS Point Cloud Classification: LiDAR data processing for the point cloud deliverable consists of classifying the LiDAR using a combination of automated classification and manual edit/reclassification processes. On most projects the automated classification routines will correctly classify 90-95 percent of the LiDAR points. The remaining 5-10 percent of the bare earth ground class must undergo manual edit and reclassification. Because the classified points serve as the foundation for the Terrain, DEM and breakline products, it is necessary for the QA/QC supervisor to review the completed point cloud deliverables prior to the production of any additional products. The following workflow steps are followed for automated LiDAR classification: 1. Lead technicians review the group of LiDAR tiles to determine which automated classification routines will achieve the best results. Factors such as vegetation density, cultural features, and terrain can affect the accuracy of the automated classification. The lead technicians have the ability to edit or tailor specific routines in order to accommodate the factors mentioned above, and achieve the best results and address errors. 2. Distributive processing is used to maximize the available hardware resources and speed up the automated processing as this is a resource-intensive process. 3. Once the results of the automated classification have been reviewed and passed consistent checks, the supervisor then approves the data tiles for manual classification. The following workflow steps are followed for manual edits of the LiDAR bare earth ground classification: 1. LiDAR technicians review each tile for errors made by the automated routines and correctly address errors any points that are in the wrong classification. By methodically panning through each tile, the technicians view the LiDAR points in profile, with a TIN surface, and as a point cloud. 2. Any ancillary data available, such as Google Earth, is used to identify any features that may not be identifiable as points so that the technician can make the determination to which classification the feature belongs. The QA/QC processes for the LiDAR processing phase consist of: 1. The lead technician reviews all automated classification results and adjust the macros as necessary to achieve the optimal efficiency. This is an iterative process, and the technician may need to make several adjustments to the macros, depending upon the complexity of the features in the area being processed. During the manual editing process, the LiDAR technicians use a system of QA, whereby they check each other’s edits. This results in several benefits to the process: There is a greater chance of catching minor blunders It increases communication between technicians on technique and appearance Solutions to problems are communicated efficiently To ensure consistency across the project area, the supervisor reviews the data once the manual editing is complete. For this phase of a project, the following specifications are checked against: • Point cloud – all points must be classified according to the USGS classification standard for LAS. The all-return point cloud must be delivered in fully-compliant LAS version 1.4. • LAS files will use the Spatial Reference Framework according to project specification and all files shall be projected and defined. • General Point classifications: Class 1. Processed, but unclassified Class 2. Bare Earth Class 7. Noise Class 9. Water Class 17. Bridge Decks Class 18. High Noise Class 20. Ignored ground (Breakline proximity) • Outliers, noise, blunders, duplicates, geometrically unreliable points near the extreme edge of the swath, and other points deemed unusable are to be identified using the "Withheld" flag. This applies primarily to points which are identified during pre-processing or through automated post-processing routines. Subsequently ide dateTime: DateTime: 2021-01-14T00:00:00 processStep: (LI_ProcessStep) description: LiDAR processing utilizes several software packages, including GeoCue and the TerraSolid suite of processing components. The GeoCue software is a database management system for housing the LiDAR dataset (usually multiple gigabytes in size). GeoCue incorporates a thorough checklist of processing steps and quality assurance/quality control (QA/QC) procedures that assist in the LiDAR workflow. The TerraSolid software suite is used to automate the initial classification of the LiDAR point cloud based on a set of predetermined parameters. Lidar technicians refer to ground cover research (natural and cultural features) within the project area and determine algorithms most suitable for the initial automated LiDAR classification. (Some algorithms/filters recognize the ground in forests well, while others have greater capability in urban areas). During this process each point is given an initial classification (e.g., as ground, vegetation, or noise) based on the point's coordinates and the relation to its neighbors. Classifications to be assigned include all those outlined by ASPRS standards. The initial classifications produce a coarse and inexact dataset, but offer an adequate starting point for the subsequent manual classification procedure. During this step, "overlap" points are automatically classified (those originating from neighboring flightlines) using information gathered from the ABGPS and IMU data. Any duplicate points existing from adjacent flightlines are removed during this process. Hydrographic breaklines are collected using LiDARgrammetry to ensure hydroflattened water surfaces. This process involves manipulating the LiDAR data's intensity information to create a metrically sound stereo environment. From this generated "imagery", breaklines are photogrammetrically compiled. Breakline polygons are created to represent open water bodies. The LiDAR points that fall within these areas are classified as "water." All hydrographic breaklines include a 1 foot buffer, with the Class 2 (bare earth) points being re-classified as Class 20 (ignored ground). TerraSolid is further used for the subsequent manual classification of the LiDAR points allowing technicians to view the point cloud in a number of ways to ensure accuracy and consistency of points and uniformity of point coverage. The TIN was processed to create a GRID or digital elevation model (DEM) with 1 foot pixels. dateTime: DateTime: 2020-10-05T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received 1205 ERDAS Imagine (.img) raster files from the Milwaukee County Land Information Office. The data were in Wisconsin South State Plane (NAD83 2011), US Survey Feet coordinates and NAVD88 (Geoid12b) elevations in US Survey Feet. The bare earth hydro-flattened files were at a 1 ft grid spacing. OCM converted the raster files to cloud optimized files in GeoTiff format for Digital Coast storage and provisioning purposes. dateTime: DateTime: 2023-06-01T00:00:00 processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) sourceCitation: (CI_Citation) title: Data Received from the Milwaukee County Land Information Office date: (missing) citedResponsibleParty: (CI_ResponsibleParty) organisationName: Milwaukee County Land Information Office contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://county.milwaukee.gov/EN/Administrative-Services/Land-Information-Office protocol: WWW:LINK-1.0-http--link name: Milwaukee County Land Information Office description: Source Citation URL function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) publisher | |