This point data was generated and filtered from OpenStreetMap (OSM) and is intended to represent places of interest in the state of Utah. 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 were over 23,000 features in the original dataset (March 2022) and users can directly contribute to it through openstreetmap.org. , opens in a new tab The data is updated approximately once every month and will likely continue to grow over time with additional user input and activity.

Data Creation Process

The Open Source Places layer is created by a Python script that downloads 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.

Field Descriptions

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 meters) from the UGRC address point database.

addr_dist

The distance (meters) to the nearest UGRC address point within 25 meters.

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.

Data Sources

• The source data and global OSM data is available for downloaded from Geofabrik , opens in a new tab as well as downloads specifically for Utah , opens in a new tab .
• Additional attributes for the Utah features are gathered via the Overpass API , opens in a new tab using the following query https://overpass-turbo.eu/s/1geR , opens in a new tab .

          area[name="Utah"]->.utah;
          nwr[!highway][name](area.utah);
          out center;