Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under Basic Parcels."Database containing parcel boundary, parcel identifier, parcel address, owner type, and county recorder contact information" - HB113. The intent of the bill was to not include any attributes that the counties rely on for data sales. If you want other attributes associated with the parcels you need to contact the county recorder.Users should be aware the owner type field 'OWN_TYPE' in the parcel polygons is a very generalized ownership type (Federal, Private, State, Tribal). It is populated with the value of the 'OWNER' field where the parcel's centroid intersects the CADASTRE.LandOwnership polygon layer.This dataset is a snapshot in time and may not be the most current. For the most current data contact the county recorder.

Subdivision boundaries in Salt Lake County maintained by the Salt Lake County Surveyor's Office.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, stairways, and winter trails.

The Address Points dataset shows Utah address points for all twenty-nine Utah counties. An address point represents a geographic location that has been assigned a US Postal Service (USPS) address by the local address authority (i.e., county or municipality) but does not necessarily receive mail. Address points may include several pieces of information about the structure or location that’s being mapped, such as:the full address (i.e., the USPS mailing address, if the address is for a physical location [rather than a PO box]);the landmark name; whether the location is a building;the type of unit;the city and ZIP code; unique code identifiers of the specific geographic location, including the Federal Information Processing Standard Publication (FIPS) county code and the US National Grid (USNG) spatial address;the address source; andthe date that the address point was loaded into the map layer.This dataset is mapping grade; it is a framework layer that receives regular updates. As with all our datasets, the Utah Geospatial Resource Center (UGRC) works to ensure the quality and accuracy of our data to the best of our abilities. Maintaining the dataset is now an ongoing effort between UGRC, counties, and municipalities. Specifically, UGRC works with each county or municipality’s Master Address List (MAL) authority to continually improve the address point data. Counties have been placed on an update schedule depending on the rate of new development and change within them. Populous counties, such as Weber, Davis, Salt Lake, Utah, and Washington, are more complete and are updated monthly, while rural or less populous counties may be updated quarterly or every six months.The information in the Address Points dataset was originally compiled by Utah counties and municipalities and was aggregated by UGRC for the MAL grant initiative in 2012. The purpose of this initiative was to make sure that all state entities were using the same verified, accurate county and municipal address information. Since 2012, more data has been added to the Address Points GIS data and is used for geocoding, 911 response, and analysis and planning purposes. The Address Point data is also used as reference data for the api.mapserv.utah.gov geocoding endpoint, and you can find the address points in many web mapping applications. This dataset is updated monthly and can also be found at: https://gis.utah.gov/data/location/address-data/.

The State of Utah, including the Utah Automated Geographic Reference Center, Utah Geological Survey, and the Utah Division of Emergency Management, along with local and federal partners, including Salt Lake County and local cities, the Federal Emergency Management Agency, the U.S. Geological Survey, and the U.S. Environmental Protection Agency, have funded and collected over 8380 km² (3236 mi²) of high-resolution (0.5 or 1 meter) Lidar data across the state since 2011, in support of a diverse set of flood mapping, geologic, transportation, infrastructure, solar energy, and vegetation projects. The datasets include point cloud, first return digital surface model (DSM), and bare-earth digital terrain/elevation model (DEM) data, along with appropriate metadata (XML, project tile indexes, and area completion reports).

This 0.5-meter 2013-2014 Wasatch Front dataset includes most of the Salt Lake and Utah Valleys (Utah), and the Wasatch (Utah and Idaho), and West Valley fault zones (Utah).

Other recently acquired State of Utah data include the 2011 Utah Geological Survey Lidar dataset covering Cedar and Parowan Valleys, the east shore/wetlands of Great Salt Lake, the Hurricane fault zone, the west half of Ogden Valley, North Ogden, and part of the Wasatch Plateau in Utah.

This dataset contains the urban growth simulation results of future land use in 2040 of the Wasatch Range Metropolitan Area (WRMA) .In this study, we defined the WRMA as a broad, ten-county region that surrounds the Wasatch Mountain Range east of the Great Salt Lake and Salt Lake City in Utah. This region encompasses four Wasatch Front counties west of the mountain range (Weber County, Davis County, Salt Lake County, and Utah County), three Wasatch Back counties east of the mountain range (Morgan County, Summit County, and Wasatch County), and three counties neighboring the Wasatch Front (Cache County, Box Elder County, and Tooele County).

SLEUTH-3r urban growth simulation model is used to generate this dataset. Detailed SLEUTH model protocol can be found at: http://www.ncgia.ucsb.edu/projects/gig/index.html. The data used to run the SLEUTH-3r model include National Land Cover Database 2001, 2006, and 2011, US Census TIGER/Line shapefile for 2000 and 2011, United States Geological Survey 7.5 min elevation model, and Utah Landownership map from Utah Automated Geographic Reference Center.

Three alternative scenarios were developed to explore how conserving Utah’s agriculturale land and maintaining healthy watersheds would affect the patterns and trajectories of urban development: 1) The first scenario is a “Business as Usual” scenario. In this scenario, federal, state, and local parks, conservation easement areas, and surface water bodies, were completely excluded (value = 100) from development, and all the remaining lands are were naively assumed as developable (value = 0). This is the same excluded layer that was also used during model calibration. Under this scenario, we hypothesized that future urban grow will occur following the historical growth behaviors and trajectories and no changes in land designation or policies to restrict future growth will be implemented. 2) The second scenario is an “Agricultural Conservation” scenario. Within the developable areas that we identified earlier, we then identified places that are classified by the United States Department of Agriculture (USDA) as prime farmland, unique farmland, farmland of statewide importance, farmland of local importance, prime farmland if irrigated, and prime farmland if irrigated and drained. Each of these classes were assigned with an exclusion value from urban development of 100, 80, 70, 60, 50, and 40 respectively. These exclusion values reflect the relative importance of each farmland classification and preservation priorities. By doing so, the model discourages but does not totally eliminate growth from occurring on agricultural lands, which reflects a general policy position to conserve agricultural landscapes while respecting landowners’ rights to sell private property. 3) A “Healthy Watershed” scenario aims to direct urban growth away from areas prone to flooding and areas critical for maintaining healthy watersheds. First, we made a 200-meter buffer around existing surface water bodies and wetlands and assigned these areas an exclusion value of 100 to keep growth from occurring there. In addition, we assigned areas that have frequent, occasional, rare and no-recorded flooding events with exclusion values of 100, 70, 40 and 0 accordingly. We also incorporated the critical watershed restoration areas identified by the Watershed Restoration Initiative of Utah Division of Wildlife Resources (https://wri.utah.gov/wri/) into this scenario. These watershed restoration areas are priority places for improving water quality and yield, reducing catastrophic wildfires, restoring the structure and function of watersheds following wildfire, and increasing habitat for wildlife populations and forage for sustainable agriculture. However, there are not yet legal provisions for protecting them from urbanization, so we assigned these areas a value of 70 to explore the potential urban expansion outcomes if growth were encouraged elsewhere.

Future land use projections of 2040 are in GIF format, which can be reprojected and georeferenced in ArcGIS or QGIS, or be read directly as a picture.

Shapefile giving geographic boundaries of the Great Salt Lake Basins. There are 6 features in this shapefile - The lake itself. This is at a nominal high extent as extracted from common data sources - Bear River Basin - Weber River Basin (Which includes Davis County) - Jordan/Provo River River Basin - West Desert - Strawberry

Strawberry is not topographically within the Great Salt Lake drainage, but is the area draining to Strawberry reservoir that supplies water to the GSL basin through the central Utah Project.

The west desert was delineated from digital elevation model analysis separating out the area more adjacent to the lake from a larger area that extends much further south but deemed not relevant for Great Salt Lake hydrology studies.

The original source of this data is not known. For a more precise and current basin delineation I suggest referring to the USGS watershed boundary dataset. This data is the underling data for maps in the following papers Mohammed, I. N. and D. G. Tarboton, (2012), "An examination of the sensitivity of the Great Salt Lake to changes in inputs," Water Resour. Res., 48(11): W11511, http://dx.doi.org/10.1029/2012WR011908. Mohammed, I. N. and D. G. Tarboton, (2011), "On the Interaction between Bathymetry and Climate in the System Dynamics and Preferred Levels of the Great Salt Lake," Water Resour. Res., 47: W02525, http://dx.doi.org/10.1029/2010WR009561.

Salt Lake County Municipal Boundaries, including Cities, Metro Townships and Unincorporated areas.Source:Salt Lake County Surveyor's Office