Utah Open Source Places

Last update: April 3, 2026 Overview This 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 Sources The 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.zip Additional attributes for the Utah features are gathered via the Overpass API using the following query: https://overpass-turbo.eu/s/1geR 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 (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 Descriptions addr_dist - the distance (m) to the nearest UGRC address point within 25 m osm_id - the feature ID in the OSM database category - the feature's data class based on the 4-digit code and tags in the OSM database name - the name of the feature 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) ugrc_addr - the nearest address (within 25 m) from the UGRC address point database disclaimer - a note from UGRC about the ugrc_near_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 osm_addr - the feature's address in the OSM database, if available More information can be found on the UGRC data page for this layer: https://gis.utah.gov/data/society/open-source-places/最后更新时间：2026年4月3日 概述 本点位数据源自开放街道地图（OpenStreetMap，简称OSM）的生成与筛选工作，旨在代表犹他州境内的各类兴趣点（POI），涵盖商业门店、餐厅、宗教场所、机场、公园、学校、活动中心、公寓综合体、酒店、汽车经销商等——几乎包含开放街道地图中可找到的所有类型实体。原始数据集（2022年3月版）包含超过23000个要素，用户可通过openstreetmap.org直接为其贡献内容。本数据约每月更新一次，且将随着用户活跃度的提升持续扩充。 数据来源 犹他州的原始批量OSM数据下载自Geofabrik平台：https://download.geofabrik.de/north-america/us/utah-latest-free.shp.zip。犹他州兴趣点的额外属性则通过Overpass API结合以下查询获取：https://overpass-turbo.eu/s/1geR 数据制作流程 本开源兴趣点图层由Python脚本生成，该脚本从Geofabrik提供的每日更新归档文件（https://www.geofabrik.de/data/download.html）中拉取全州范围的OSM数据。该归档文件包含近20个形状文件（SHP），其中部分与本数据集相关，部分则无关。开源兴趣点图层的构建流程为：先从这些形状文件中筛选多边形与点位数据，将其整合为单一要素类，并根据犹他州地理信息委员会（UGRC）认定的最具广泛关注度的类别与属性进行过滤。对于建筑物、区域、综合体等多边形要素，通过内部质心转换为点位。在将多个形状文件的数据合并为单一图层的过程中，会执行空间筛选以尽量减少重复要素的出现（例如，餐厅可在OSM中同时以兴趣点和建筑多边形两种形式存在，空间筛选可降低最终数据集中同时保留这两类要素的概率）。此外，还会以'block_id'字段作为空间索引进行额外去重，确保同一普查区块内不存在同名的两个要素。随后，通过点在多边形分析与邻近分析，从UGRC的SGID数据中为要素补充县、市、邮政编码、邻近地址等字段。同时会对'name'字段执行数值检查，移除名称长度不足3个字符，或名称中数字占比超过50%的要素，以此剔除源自建筑图层、仅以公寓楼号（如3A）或门牌号（如1612）作为名称的要素。最后，通过Overpass API（https://wiki.openstreetmap.org/wiki/Overpass_API）拉取osm_addr、opening_hours、phone、website、cuisine等额外属性，并以'osm_id'字段作为连接键，将其与筛选后的数据进行关联。 字段说明 addr_dist：距25米范围内最近的UGRC地址点位的距离（单位：米） osm_id：OSM数据库中的要素ID category：基于OSM数据库中的4位代码与标签确定的要素数据类别 name：OSM数据库中记录的要素名称 county：要素所在的县（由UGRC的县界数据赋值） city：要素所在的城市（由UGRC的市政边界数据赋值） zip：要素所在的邮政编码（由UGRC的邮政编码边界近似数据赋值） block_id：要素所在的普查区块（由UGRC的普查区块边界数据赋值） ugrc_addr：UGRC地址点位数据库中距要素最近的地址（25米范围内） disclaimer：UGRC关于ugrc_near_addr字段的说明 lon：要素的近似经度，基于世界大地测量系统1984（WGS84）[EPSG:4326]计算（如需最高精度，建议直接使用要素的几何信息而非该字段） lat：要素的近似纬度，基于世界大地测量系统1984（WGS84）[EPSG:4326]计算（如需最高精度，建议直接使用要素的几何信息而非该字段） amenity：要素提供的便民设施（如适用），通常与类别类似 cuisine：要素提供的餐食类型（如适用），多种类型以分号（;）分隔 tourism：要素所属的旅游景点类型（如适用，包括动物园、观景台、酒店、旅游景点等） shop：要素所属的店铺类型（如适用） website：OSM数据库中记录的要素官方网站（如可获取） phone：OSM数据库中记录的要素联系电话（如可获取） open_hours：OSM数据库中记录的要素营业时间（如可获取） osm_addr：OSM数据库中记录的要素地址（如可获取） 更多信息可查阅UGRC关于本图层的数据页面：https://gis.utah.gov/data/society/open-source-places/