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

Last update: August 20, 2024OverviewThis point data was generated and filtered from OpenStreetMap and is intended to represent places of interest in the state of Utah. These may include businesses, restaurants, places of worship, airports, parks, schools, event centers, apartment complexes, hotels, car dealerships…almost anything that you can find in OpenStreetMap (OSM). There are over 23,000 features in the original dataset (March 2022) and users can directly contribute to it through openstreetmap.org. This data is updated approximately once every month and will likely continue to grow over time with user activity.Data SourcesThe original bulk set of OSM data for the state of Utah is downloaded from Geofabrik: https://download.geofabrik.de/north-america/us/utah-latest-free.shp.zipAdditional attributes for the Utah features are gathered via the Overpass API using the following query: https://overpass-turbo.eu/s/1geRData Creation ProcessThe Open Source Places layer is created by a Python script that pulls statewide OSM data from a nightly archive provided by Geofabrik (https://www.geofabrik.de/data/download.html). The archive data contains nearly 20 shapefiles, some that are relevant to this dataset and some that aren't. The Open Source Places layer is built by filtering the polygon and point data in those shapefiles down to a single point feature class with specific categories and attributes that UGRC determines would be of widest interest. The polygon features (buildings, areas, complexes, etc.) are converted to points using an internal centroid. Spatial filtering is done as the data from multiple shapefiles is combined into a single layer to minimize the occurrence of duplicate features. (For example, a restaurant can be represented in OSM as both a point of interest and as a building polygon. The spatial filtering helps reduce the chances that both of these features are present in the final dataset.) Additional de-duplication is performed by using the 'block_id' field as a spatial index, to ensure that no two features of the same name exist within a census block. Then, additional fields are created and assigned from UGRC's SGID data (county, city, zip, nearby address, etc.) via point-in-polygon and near analyses. A numeric check is done on the 'name' field to remove features where the name is less than 3 characters long or more than 50% numeric characters. This eliminates several features derived from the buildings layer where the 'name' is simply an apartment complex building number (ex: 3A) or house number (ex: 1612). Finally, additional attributes (osm_addr, opening_hours, phone, website, cuisine, etc.) are pulled from the Overpass API (https://wiki.openstreetmap.org/wiki/Overpass_API) and joined to the filtered data using the 'osm_id' field as the join key.Field Descriptionsaddr_dist - the distance (m) to the nearest UGRC address point within 25 mosm_id - the feature ID in the OSM databasecategory - the feature's data class based on the 4-digit code and tags in the OSM databasename - the name of the feature in the OSM databasecounty - the county the feature is located in (assigned from UGRC's county boundaries)city - the city the feature is located in (assigned from UGRC's municipal boundaries)zip - the zip code of the feature (assigned from UGRC's approximation of zip code boundaries)block_id - the census block the feature is located in (assigned from UGRC's census block boundaries)ugrc_addr - the nearest address (within 25 m) from the UGRC address point databasedisclaimer - a note from UGRC about the ugrc_near_addr fieldlon - the approximate longitude of the feature, calculated in WGS84 EPSG:4326lat - the approximate latitude of the feature, calculated in WGS84 EPSG:4326amenity - the amenity available at the feature (if applicable), often similar to the categorycuisine - the type of food available (if applicable), multiple types are separated by semicolons (;)tourism - the type of tourist location, if applicable (zoo, viewpoint, hotel, attraction, etc.)shop - the type of shop, if applicablewebsite - the feature's website in the OSM database, if availablephone - the feature's phone number(s) in the OSM database, if availableopen_hours - the feature's operating hours in the OSM database, if availableosm_addr - the feature's address in the OSM database, if availableMore information can be found on the UGRC data page for this layer:https://gis.utah.gov/data/society/open-source-places/

Last update: June 28, 2021This dataset represents the primary Public Safety Answering Point (PSAP) locations in Utah. The Salt Lake County Sheriff Office PSAP is secondary. The dataset was initially created in December 2004 by geocoding the PSAP addresses provided by the E911 Executive Committee.

SGID10.LOCATION.Buildings was derived from building footprints generated by Microsoft for all 50 States https://github.com/Microsoft/USBuildingFootprints In some cases the pixel prediction algorithm used by Microsoft identified and created building footprints where no buildings existed. To flag potential errors, building footprints within 750 meters of known populated areas (SGID10.DEMOGRAPHIC.PopBlockAreas2010_Approx) and within 500 meters of an address point (SGID10.LOCATION.AddressPoints) were selected and indentified as being a likely structure, footprints falling outside these areas were identified as possible buildings in the 'TYPE' field. In addition, attributes were added for address, city, county, and zip where possible.

This data set represents eneregy resources depicted as points on the Energy Resources Map of Utah from which the data were digitized.

Lead-Based Paint Program. Lead-Based Paint (LBP) was banned for use in houses in 1978, however, in houses built before 1978, there is a possibility that LBP is still present. Dust from LBP is the leading cause of lead poisoning in children which is a serious and preventable environmental health problem for both children.The data for this dataset is drawn from the LIR parcels data and address points. The address-related attributes as well as geometry is pulled from the SGID10.LOCATION.AddressPoints. If this data is not available, then the script falls back to the LIR parcel data.

Demographic.PopBlockAreas2010_Approx contains areas of census blocks that just represent populated areas. This dataset was created by AGRC using the original 2010 census blocks. The blocks were cut when necessary to only cover residential and other developed areas. This was done using mainly aerial imagery and is just an approximation. This dataset was updated in 2015 using new aerial photography and address point locations.

Points representing municipalities, county seats, populated areas, and major junctions for cartographic purposes.

Last update: 08/19/2024This data represents Public Safety Answering Point (PSAP) boundaries in Utah that will be used for call-routing in the Next-Generation 911 system. PSAP jurisdictions related to county and municipal boundaries are based on the boundaries that were current on the date the data were last updated. The data also includes jurisdictional boundary representations of the Navajo Nation Tribal Lands, Hill Air Force Base, and Colorado City.More information can be found on the UGRC data page for this layer:https://gis.utah.gov/data/society/public-safety/

PLSSQuarterSections_GCDB is the third level of a hierarchical breakdown of the Public Land Survey System Rectangular surveys. This data is Version 2.3 2020 of the Utah PLSS Fabric. This data set represents the GIS Version of the Public Land Survey System. Updates are expected annually as horizontal control positions from published sources and global positioning system (GPS) observations are added. The primary source for the data is cadastral survey records housed by the BLM supplemented with local records and geographic control coordinates from states, counties as well as other federal agencies such as the USGS and USFS. This data was originally published on 1/3/2017. This is no longer a standard and is now published as a Reference layer. This data is derived from the Second Division of the PLSS which includes quarter, quarter-quarter, sixteenth or government lot division of the PLSS.Updates were made to Quarter Sections in Utah County to add quarter sections to areas that were not broken down less than the Section level. They were added using information from points collected by county surveyors, that is in the data and extrapolating information from adjoining sections wherever possible. They are still areas that could not be interpreted well enough and they were left empty, beyond the section level.Quarter Sections were consolidated from the Quarter Quarter Sections to better represent the four quarters in all Aliquot Part areas. Areas with Lots or Special Surveys remain as is. Updated 4/8/2022

A collection of populated places and 2010 census population estimates. for unincorporated areas, these estimates are based on AGRC's subjective assignment of census blocks to named places or to an other/unassigned generic holder.

The H3 indexing system provides a standardized and high-performance grid for aggregating data at various levels. This layer contains the spatial representation of the IDs that cover the state of Utah. While it can be used for normal GIS point-in-polygon operations, you will get much better performance using the H3 API to assign a hex ID to your points, aggregating/analyzing your points based on ID, and then joining your aggregated data to this layer on the hex IDs.Our H3 blog post provides an overview of the system, an explanation of how we created these geometries, and an example analysis. Once the geometries were created in EPSG 4326 (WGS 84 lon/lat), they were projected to EPSG 26912 (UTM 12N) using the NAD_1983_To_WGS_1984_5 transformation.

This layer contains data from the Geographic Names Information System (GNIS) which was developed by the USGS in partnership with other government and interested organizations "to meet major national needs regarding geographic names and their standardization and dissemination". The data consist of point locations with corresponding feature names. All point entities are categorized by feature type. This data is representative of data from 2019 for mapping feature names and was last updated on 4/3/2019.

The H3 indexing system provides a standardized and high-performance grid for aggregating data at various levels. This layer contains the spatial representation of the IDs that cover the state of Utah. While it can be used for normal GIS point-in-polygon operations, you will get much better performance using the H3 API to assign a hex ID to your points, aggregating/analyzing your points based on ID, and then joining your aggregated data to this layer on the hex IDs.Our H3 blog post provides an overview of the system, an explanation of how we created these geometries, and an example analysis. Once the geometries were created in EPSG 4326 (WGS 84 lon/lat), they were projected to EPSG 26912 (UTM 12N) using the NAD_1983_To_WGS_1984_5 transformation.

NOTE: This dataset is an older dataset that we have removed from the SGID and 'shelved' in ArcGIS Online. There may (or may not) be a newer vintage of this dataset in the SGID.

This point occurrence data set represents the current mineral and selected energy resources of Utah. The data set coordinates were derived from USGS topographic maps at a scale of 1:62,500 and 1:24,000. The coordinates of some of the energy resources were calculated from their cadastral location. This data set has 152 data fields; some of which contain multiple values with multiple delimiters.

The H3 indexing system provides a standardized and high-performance grid for aggregating data at various levels. This layer contains the spatial representation of the IDs that cover the state of Utah. While it can be used for normal GIS point-in-polygon operations, you will get much better performance using the H3 API to assign a hex ID to your points, aggregating/analyzing your points based on ID, and then joining your aggregated data to this layer on the hex IDs.Our H3 blog post provides an overview of the system, an explanation of how we created these geometries, and an example analysis. Once the geometries were created in EPSG 4326 (WGS 84 lon/lat), they were projected to EPSG 26912 (UTM 12N) using the NAD_1983_To_WGS_1984_5 transformation.

Locations for each of Utah’s alpine ski areas and resorts are represented as points for Alta, Beaver Mountain, Brian Head, Brighton, Cherry Peak, Deer Valley, Eagle Point, Park City, Powder Mountain, Snowbasin, Snowbird, Solitude, Sundance and Wolf Mountain. Points have been placed on or near base area parking/facilities when possible, but are designed for use in statewide or other small-scale maps, and as use for label points.

This dataset reflects current locations for the 2016-17 season and was created by digitizing points on top of high resolution aerial photography.

This dataset depicts the location of liquor stores and package agencies controlled by the Department of Alcoholic Beverage Control of Utah. Points have been placed on DABC facilities. Locations are current as of April 2017.

This SDE data layer contains coordinates of Facility UST sites. The coordinate data have been created and utilized by the DERR for the plotting of Facility UST sites on maps depicting the State and several counties. The data used to produce these maps have been reviewed by DERR staff and found to be adequate for DERR’s purposes which require the depiction of general site locations. The accuracy of these locations may not be sufficient for other purposes. Persons relying upon these maps do so at their own risk. The DERR assumes no responsibility or liability for the accuracy of these points.