Color: [255, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Segoe UI Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 77, 168, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Segoe UI Font Style: normal Font Weight: normal Font Decoration: none
Color: [255, 255, 255, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Segoe UI Font Style: normal Font Weight: normal Font Decoration: none
Description: The overall outside boundary is considered the Control Area. Inside that control area, there are project areas that are created when a property owner decides to be part of MIDA. For updates, contact MIDA. They are maintaining this feature and this copy should match what they have.
Color: [132, 0, 168, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Segoe UI Font Style: normal Font Weight: normal Font Decoration: none
Description: Project areas represent a group of parcels that join MIDA and the date they joined. The date is important because it determines the base tax year. This base year tax value is used to calculate the part of the taxes that the county gets and what MIDA gets.Two maps are created from this feature. One is the Project Areas and the other is the Land Use Control Map.MIDA maintains this feature. If you need an update, reach out to them to get the latest data.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Segoe UI Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Segoe UI Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Segoe UI Font Style: normal Font Weight: normal Font Decoration: none
Description: General administration boundaries for planning. Developed for the internal use of Wasatch County. State Park Boundaries were updated using a shape file from them in 2010. This affected the Jordanelle and Snake Creek areas. May 2016, recieved a boundary file from Forest Service and updated this dataset to match what they show as their administration area.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Description: This area is basically all the A-20 zones in the county, minus a 100 foot buffer around some roads. For more details, look at ordinance 22-23, recorded on 16 December 2022.
Description: This data was sent to Wasatch County by Mark Jensen at the Division of Drinking Water on 1/21/2015. The data was modified by having some of the fields striped out. Two zones were added from our old DWSP layer that were not included in the state data. These two zones were discovered through local sources and are being checked by the state. For more information, go to https://enviro.deq.utah.gov/ Utah Admin Code 309-600-9
Service Item Id: 4e0ce7dc44ba4b11914a1e849c6953a6
Copyright Text: Department of Environmental Quality
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Segoe UI Font Style: normal Font Weight: normal Font Decoration: none
Description: Shallow groundwater flood hazard area, as mapped at 1:24,000 scale in the UGS's OFR-319 ("Flood Hazards, Earthquake Hazards, and Problem Soils, Western Wasatch County, Utah"). Shallowest expected depth to water table 0-10 feet. Relevant map plates are 2A, 2B, 2C, and 2D. The RMF error was 0.0008 in digitizer units.
Description: Data provided to Wasatch County by FEMA as part of the 2006 flood plane study. This was adopted October 2012. Zone and DescriptionA: No base flood elevation determinedAE: Base flood elevation determinedAO: Flood depths of 1 to 3 feet (usually sheet flow on sloping terrain); average depths determined. For areas of alluvial fan flooding, velocities also determined.AR:Special Flood Hazard Area formerly protected from the 1% annual chance flood by a flood control system that was subsequently decertified. Zone AR indicates that the former flood control system is being restored to provide protection from the 1% annual chance or greater flood.A99: Area to be protected from 1% annual chance flood by a Federal flood protec tion sys tem unde r const ruc tion; no Base Flood Elevat ions determined.V: Coastal flood zone with velocity hazard (wave action); no Base Flood Elevations determined.VE: Coas tal flood zone with veloci ty hazard (wave action); Base Flood Elevations determined.X: Areas of 0.2% annual chance flood; areas of 1% annual chance flood with average depths of less than 1 foot or with drainage areas less than 1 square mile; and areas protected by levees from 1% annual chance flood.D: Areas of 0.2% annual chance flood; areas of 1% annual chance flood with average depths of less than 1 foot or with drainage areas less than 1 square mile; and areas protected by levees from 1% annual chance flood.
Description: This data set represents the extent, approximate location and type of wetlands and deepwater habitats in the United States and its Territories. These data delineate the areal extent of wetlands and surface waters as defined by Cowardin et al. (1979). The National Wetlands Inventory - Version 2, Surface Waters and Wetlands Inventory was derived by retaining the wetland and deepwater polygons that compose the NWI digital wetlands spatial data layer and reintroducing any linear wetland or surface water features that were orphaned from the original NWI hard copy maps by converting them to narrow polygonal features. Additionally, the data are supplemented with hydrography data, buffered to become polygonal features, as a secondary source for any single-line stream features not mapped by the NWI and to complete segmented connections. Wetland mapping conducted in WA, OR, CA, NV and ID after 2012 and most other projects mapped after 2015 were mapped to include all surface water features and are not derived data. The linear hydrography dataset used to derive Version 2 was the U.S. Geological Survey's National Hydrography Dataset (NHD). Specific information on the NHD version used to derive Version 2 and where Version 2 was mapped can be found in the 'comments' field of the Wetlands_Project_Metadata feature class. Certain wetland habitats are excluded from the National mapping program because of the limitations of aerial imagery as the primary data source used to detect wetlands. These habitats include seagrasses or submerged aquatic vegetation that are found in the intertidal and subtidal zones of estuaries and near shore coastal waters. Some deepwater reef communities (coral or tuberficid worm reefs) have also been excluded from the inventory. These habitats, because of their depth, go undetected by aerial imagery. By policy, the Service also excludes certain types of "farmed wetlands" as may be defined by the Food Security Act or that do not coincide with the Cowardin et al. definition. Contact the Service's Regional Wetland Coordinator for additional information on what types of farmed wetlands are included on wetland maps. This dataset should be used in conjunction with the Wetlands_Project_Metadata layer, which contains project specific wetlands mapping procedures and information on dates, scales and emulsion of imagery used to map the wetlands within specific project boundaries.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Segoe UI Font Style: normal Font Weight: normal Font Decoration: none
Description: The process that was followed was taking surface data that was projected into State Plane NAD83, Ft, Utah Central Zone. All the cell elevations were calculated to feet if they were not already, Then 10 foot contours were created from the surfaces. Then the contours were converted back to a surface and finally, that surface was used to create the slope surface.The 10 foot contours were created from the original data. Then the Topo To Raster tool was used to create the 1 band, 32 bit floating, 20 foot cells. Then the surfaces were joined together using the Mosaic to New Raster tool. After that the final product was clipped to the county boundary. The Heber valley area was clipped to the boundary of that data before the two was joined together. This made the edges where the two came together look seamless.--- Data Used ---The 2018, .5 meter, LIDAR data for the valley and foothills. This data was created by the state for the FIMA flood remapping project.The USGS 1 meter LIDAR data was used for the rest of the county.Created April 24th 2026