Input · Context data

OSM Overpass

Asks live OpenStreetMap for features that match tag filters inside your area, such as amenity=cafe or shop=supermarket.

Also known as: OpenStreetMap query

How it works

Tag filters is a list of rows, each a key and an optional value: amenity=cafe matches that tag, a bare shop matches any value, and the rows are OR-ed together. Add a group drops in a ready-made set such as Food & drink or Retail. Bounding box (WGS84 degrees) limits the area, typed or drawn on the map. Features chooses Points & areas (default), Points only or Areas & lines; multipolygon relations are never queried, so a park built from several ways will be missing. Endpoint is the public Overpass API unless you pick Custom / self-hosted…, and Timeout (seconds) defaults to 60. The output has osm_id, osm_type, name, one column per filtered tag key and geom.

Inputs and outputs

Inputs

None — this node starts a workflow.

Outputs

  • data — Table

Settings

The Attributes panel of OSM Overpass, as in the app: the controls work, but nothing runs — there is no data behind it.

The same settings, as the Assistant writes them
{
  minLon: string
  minLat: string
  maxLon: string
  maxLat: string
  tagFilters: string (comma-separated "key=value" or bare "key")
  elementTypes?: "node" | "way" | "both"
  endpoint?: string
  timeoutSeconds?: string
}

bbox in WGS84 degrees; relations are not queried

Example

Grocery competitors in a district: filters shop=supermarket and shop=convenience, Features Points & areas, a box drawn around the district.