tourism-information / README.md
paulwynter's picture
Publish Tourist Information Points (OSM) (v1)
eb763ae verified
|
Raw History Blame Contribute Delete
5.33 kB
metadata
pretty_name: Tourist Information Points (OSM) - 30,000-record Geospatial Sample
license: odbl
size_categories:
  - 10K<n<100K
task_categories:
  - tabular-classification
  - other
language:
  - en
tags:
  - geospatial
  - open-data
  - tabular
  - parquet
  - geojson
  - csv
  - tourism
  - travel
  - points-of-interest
  - openstreetmap
  - wayfinding
  - information

Tourist Information Points (OSM) - 30,000-record Geospatial Sample

A free, ready-to-use sample of 30,000 geolocated tourism information points (current openstreetmap snapshot), published by Outerview.

Tourist information boards, maps, guideposts and offices mapped by OpenStreetMap contributors, with coordinates and the original OSM tags preserved.

This is a 30,000-record sample of a much larger collection (about 1,454,000 source records). Need the full dataset, other places or years, or live search? See the Outerview atlas.

At a glance

Records 30,000
Period Current OpenStreetMap snapshot
Geometry Point, WGS 84 (EPSG:4326)
Formats Parquet, GeoJSON, CSV
Publisher Outerview

Quick start

from datasets import load_dataset

ds = load_dataset("parquet", data_files="hf://datasets/Outerview/tourism-information/data.parquet", split="train")
print(ds)
print(ds[0])
import pandas as pd
import json

df = pd.read_parquet("hf://datasets/Outerview/tourism-information/data.parquet")
df["properties"] = df["properties"].apply(json.loads)
df[["latitude", "longitude"]].describe()

Search millions more geographic features

Outerview provides developers and AI systems access to millions of geographic features and geolocated imagery spanning infrastructure, places, roads, buildings, nature and community issues.

Build with Outerview

  • Geographic Feature List — browse geographic features available through Outerview
  • Outerview — programmable infrastructure for Earth
  • Developer Documentation — APIs, tools, guides, and examples
  • SDK — build geographic capabilities directly into applications
  • CLI — work with geographic search and spatial data from the terminal
  • MCP — connect geographic search and spatial tools to AI agents

Use cases

  • Travel and destination-recommendation apps
  • Tourism infrastructure coverage studies
  • Wayfinding and visitor-experience research
  • Points-of-interest enrichment

Schema

Column Type Description
id string Stable identifier for the record in the source table.
sample boolean Reserved flag for optional image samples; false for source-table exports.
latitude float64 Latitude in decimal degrees (WGS 84).
longitude float64 Longitude in decimal degrees (WGS 84).
geometry_wkb binary Record geometry encoded as Well-Known Binary for spatial workflows.
media_url string URL of associated imagery when available; usually empty for this dataset.
attribution string Attribution text for the contributing source.
source string Source or provider label.
properties string JSON-encoded object with the source-specific fields (see Properties).

Properties

The properties column is a JSON string holding the original source attributes. The most common keys in this sample:

Key Example value
osm_id 389068254
tag_name amenity
label_name restaurant
tourism information
information office
highway rest_area
bicycle yes
amenity restaurant
name Casino UACH
hiking yes
ref MPM199
operator Maryland Transit Administration

Keys vary by record and source; not every field is populated for every row.

Files

Methodology

Records are exported directly from the Outerview geographic index, ordered by identifier and capped at 30,000 rows. Coordinates are WGS 84. Source fields are preserved in properties without reinterpretation. Inclusion means a record appeared in the contributing public dataset; it was not independently verified.

Sources and attribution

License

Contains information from OpenStreetMap, made available under the Open Database License (ODbL) 1.0. Attribute OpenStreetMap contributors and keep derived databases under ODbL.