Open Source Places
- Category: Society
- Data Type: GIS Data Layer
- Steward(s): OpenStreetMap Contributors and UGRC
- Abstract: Utah Open Source Places contains a point representation of places of interest in Utah that have been derived from OpenStreetMap (OSM).
Open Source Places
This point data was generated and filtered from OpenStreetMap (OSM) and is intended to represent places of interest in the state of Utah. Per the OSM Wiki: "the [OSM] project…creates and distributes free geographic data for the world…because most maps you think of as free actually have legal or technical restrictions on their use, holding back people from using them in creative, productive, or unexpected ways." These data may include businesses, restaurants, places of worship, airports, parks, schools, event centers, apartment complexes, hotels, car dealerships…almost anything that you can find in OSM. There are over 23,000 features in the original dataset (March 2022) and users can directly contribute to it through openstreetmap.org. The data is updated approximately once every month and will likely continue to grow over time with additional user input and activity.
UGRC's creation of the Utah Open Source Places dataset does not imply endorsement by, or affiliation with, the OpenStreetMap Foundation
Data Creation Process
The Open Source Places layer is created by a Python script that pulls statewide OSM data from a nightly archive provided by Geofabrik. 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, open_hours, phone, website, cuisine, etc.) are pulled from the Overpass API and joined to the filtered data using the 'osm_id' field as the join key.
osm_id- the feature ID in the OSM database
name- the name of the feature in the OSM database
category- the feature's data class based on the 4-digit code and tags in the OSM database
county- 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)
osm_addr- the feature's address in the OSM database, if available
ugrc_addr- the nearest address (within 25 m) from the UGRC address point database
addr_dist- the distance (m) to the nearest UGRC address point within 25 m
disclaimer- a note from UGRC about the ugrc_addr field
lon- the approximate longitude of the feature, calculated in WGS84 [EPSG:4326] (for the most precision, it is recommended that the feature's geometry is used instead of this field)
lat- the approximate latitude of the feature, calculated in WGS84 [EPSG:4326] (for the most precision, it is recommended that the feature's geometry is used instead of this field)
amenity- the amenity available at the feature (if applicable), often similar to the category
cuisine- 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 applicable
website- the feature's website in the OSM database, if available
phone- the feature's phone number(s) in the OSM database, if available
open_hours- the feature's operating hours in the OSM database, if available
- The original bulk set of OSM data for the state of Utah is downloaded from Geofabrik:
- Additional attributes for the Utah features are gathered via the Overpass API using the following query:
Data License and Copyright
The Open Source Places data carries a different license than most UGRC data.
OpenStreetMap® is open data, licensed under the Open Data Commons Open Database License (ODbL) by the OpenStreetMap Foundation (OSMF).
You are free to copy, distribute, transmit and adapt our data, as long as you credit OpenStreetMap and its contributors. If you alter or build upon our data, you may distribute the result only under the same license. The full legal code explains your rights and responsibilities.
© OpenStreetMap contributors
For more information, visit openstreetmap.org/copyright, openstreetmap.org, and opendatacommons.org.
Comments, questions, compliments, or concerns can be directed to Erik Neemann from UGRC at ENeemann@utah.gov or 385-258-4299.
Downloads and Web Services
- May 24, 2023 - routine update (159 features added)
- May 9, 2023 - routine update (9 features added)
- April 26, 2023 - routine update (21 features added)
- April 12, 2023 - routine update (173 features added)
- March 29, 2023 - routine update (32 features added)
- March 14, 2023 - routine update (13 features added)
- March 1, 2023 - routine update (168 features added)
- February 15, 2023 - routine update (146 features added)
- February 1, 2023 - routine update (349 features added)
- January 18, 2023 - routine update (27 features added)