Geospatial data about Utah Address Points. Export to CAD, GIS, PDF, CSV and access via API.

AddressPoints is a statewide dataset that contains address point data from all 29 Utah Counties. This dataset is a work in progress and some counties are more complete than others. One person in each county has been identified as the Master Address List (MAL) Authority to eliminate duplication of address point data and clarify the main person of contact. AGRC is working with each MAL Authority to continually improve this data and work toward quarterly updates.

Geospatial data about Washington County, Utah Addresses. Export to CAD, GIS, PDF, CSV and access via API.

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/.

Geospatial data about Salt Lake County, Utah Addresses. Export to CAD, GIS, PDF, CSV and access via API.

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 filewith no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independentdata set, or they can be combined to cover the entire nation. The Address Range / Feature Name Relationship File (ADDRFN.dbf) contains a record for each address range / linear feature name relationship. The purpose of this relationship file is to identify all street names associated with each address range. An edge can have several feature names; an address range located on an edge can be associated with one or any combination of the available feature names (an address range can be linked to multiple feature names). The address range is identified by the address range identifier (ARID) attribute that can be used to link to the Address Ranges Relationship File (ADDR.dbf). The linear feature name is identified by the linear feature identifier (LINEARID) attribute that can be used to link to the Feature Names Relationship File (FEATNAMES.dbf).

This dataset represents statewide address point locations provided by Utah counties and aggregated by the AGRC for the Master Address List (MAL) grant initiative. This dataset is an ongoing effort bwtween the AGRC, counties, and municipalities to provide accurate and timely address information. Updates are provided quarterly by counties. Last updated 6/23/2014.

Saved as a web map to be included in the base map selector.

Comprehensive dataset of 338 State government offices in Utah, United States as of July, 2025. Includes verified contact information (email, phone), geocoded addresses, customer ratings, reviews, business categories, and operational details. Perfect for market research, lead generation, competitive analysis, and business intelligence. Download a complimentary sample to evaluate data quality and completeness.

This dataset represents an ongoing effort to approximate the geographic extents of 5 digit zip codes. The dataset was produced using a combination of methods and is based on several sets of source data. Methods include: 1) using local zip code polygon data obtained from counties and cities contained within these counties; 2) Identifying place locations (city, town, places) from the postal service website and address information system (AIS) and as a last result, building theissen polygons around usps places in unpopulated areas; and 3) editing line work using the 2000 Census TIGER line file's zip code attributes. In addition, AGRC has used the locations of mailing addresses known to be valid to fine tune this dataset.

Last update: April 4, 2023Added the Mammoth address system in Juab county. Additional minor edits to account for annexations in Utah (Springville, Lehi) and Box Elder (Willard, Garland) counties, April 2023.Added several address grids in Beaver county (Elk Meadows, Ponderosa, Greenville, Adamsville, Sulphurdale). Made major updates to grids in Utah, Cache, Tooele, and Box Elder Counties. Renamed 'NSL' to 'North Salt Lake' and 'East Carbon City' to 'East Carbon', December 2022. Minor adjustment to quadrants in Bluff.Added Rocky Ridge address grid in northern Juab county, August 2022.Updates were made near Elsinore/Central Valley/Monroe corners due to recent Elsinore annexation and inputs from Sevier County, September 2021.Improvements were made to Brigham City, Millville, Logan, and Providence, February 2016.Improvements were made to the Heber, Hyde Park, Logan, and Woodland address system boundaries; updated the American Fork, Fielding, Payson, and Saratoga Springs address system boundaries to reflect recent annexations, January 2016Improvements were made to the Hyde Park and Logan address system boundary, November 2015Improvements were made to the Hyrum and Logan address system boundary, November 2015Updated the American Fork address system boundary to reflect recent annexations, October 2015Improvements were made to the Brigham City, Fishlake, Fremont, Garland, Loa, Lyman, Mantua, Tremonton, and Willard address system boundaries; updated the Lehi and Santa Clara address system boundaries to reflect recent annexations, August 2015Improvements were made to the Price and Wellington address system boundaries; updated the Lehi and Provo address system boundaries to reflect recent annexations, July 2015Improvements were made to the Layton and HAFB address system boundaries; updated the Provo and Spanish Fork address system boundaries to reflect recent annexations, June 2015Updated address system boundaries to reflect annexations in Lehi, Lewiston, and Snowville, May 2015Improvements were made to the Orderville address system boundary to match the municipal boundary, February 2015Updated address system boundaries to match annexations in American Fork, Farmington, Elk Ridge, Grantsville, Lehi, Mendon, Mount Pleasant, Payson, Provo, Spanish Fork, and Washington, January 2015 Improvements were made to the Elmo and Cleveland address system boundaries, December 2014Improvements were made to the Wellington address system boundaries, July 2014Improvements were made to the NSL (North Salt Lake) and Bountiful address system boundaries, June 2014.Changed address system name East Carbon-Sunnyside to East Carbon City, May 2014Updated address system boundaries to match annexations in northern Utah County; misc improvements in Davis County; adjusted Laketown/Garden City boundary, April 2014Merged East Carbon and Sunnyside to create the East Carbon-Sunnyside address system, February 2014.Improvements were made to the Iron County address system quadrant boundaries and topological errors were corrected statewide, January 2014. Improvements were made to Garfield County and Washington County address system quadrant boundaries, August 2013.More information can be found on the UGRC data page for this layer:https://gis.utah.gov/data/location/address-data/

Comprehensive dataset of 7 Straits in Utah, United States as of July, 2025. Includes verified contact information (email, phone), geocoded addresses, customer ratings, reviews, business categories, and operational details. Perfect for market research, lead generation, competitive analysis, and business intelligence. Download a complimentary sample to evaluate data quality and completeness.

Comprehensive dataset of 31 Courthouses in Utah, United States as of July, 2025. Includes verified contact information (email, phone), geocoded addresses, customer ratings, reviews, business categories, and operational details. Perfect for market research, lead generation, competitive analysis, and business intelligence. Download a complimentary sample to evaluate data quality and completeness.

Comprehensive dataset of 51 Stadia in Utah, United States as of July, 2025. Includes verified contact information (email, phone), geocoded addresses, customer ratings, reviews, business categories, and operational details. Perfect for market research, lead generation, competitive analysis, and business intelligence. Download a complimentary sample to evaluate data quality and completeness.

Comprehensive dataset of 33 Group homes in Utah, United States as of July, 2025. Includes verified contact information (email, phone), geocoded addresses, customer ratings, reviews, business categories, and operational details. Perfect for market research, lead generation, competitive analysis, and business intelligence. Download a complimentary sample to evaluate data quality and completeness.

Comprehensive dataset of 17 Foundries in Utah, United States as of August, 2025. Includes verified contact information (email, phone), geocoded addresses, customer ratings, reviews, business categories, and operational details. Perfect for market research, lead generation, competitive analysis, and business intelligence. Download a complimentary sample to evaluate data quality and completeness.

Comprehensive dataset of 1,127 Hotels in Utah, United States as of July, 2025. Includes verified contact information (email, phone), geocoded addresses, customer ratings, reviews, business categories, and operational details. Perfect for market research, lead generation, competitive analysis, and business intelligence. Download a complimentary sample to evaluate data quality and completeness.

Comprehensive dataset of 36 Stables in Utah, United States as of July, 2025. Includes verified contact information (email, phone), geocoded addresses, customer ratings, reviews, business categories, and operational details. Perfect for market research, lead generation, competitive analysis, and business intelligence. Download a complimentary sample to evaluate data quality and completeness.

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. Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2010 Census blocks nest within every other 2010 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.

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 Address Ranges Feature Shapefile (ADDRFEAT.dbf) contains the geospatial edge geometry and attributes of all unsuppressed address ranges for a county or county equivalent area. The term "address range" refers to the collection of all possible structure numbers from the first structure number to the last structure number and all numbers of a specified parity in between along an edge side relative to the direction in which the edge is coded. Single-address address ranges have been suppressed to maintain the confidentiality of the addresses they describe. Multiple coincident address range feature edge records are represented in the shapefile if more than one left or right address ranges are associated to the edge. The ADDRFEAT shapefile contains a record for each address range to street name combination. Address range associated to more than one street name are also represented by multiple coincident address range feature edge records. Note that the ADDRFEAT shapefile includes all unsuppressed address ranges compared to the All Lines Shapefile (EDGES.shp) which only includes the most inclusive address range associated with each side of a street edge. The TIGER/Line shapefile contain potential address ranges, not individual addresses. The address ranges in the TIGER/Line Files are potential ranges that include the full range of possible structure numbers even though the actual structures may not exist.