Input · Context data
Overture Maps
Fetches open map data from Overture Maps inside a box you draw: places, buildings, roads, land use or addresses. Places can be narrowed by category, such as restaurants.
Also known as: POIs, building footprints
How it works
Layer picks the theme: Places (POIs), Buildings, Roads & transit segments, Land use or Addresses. Bounding box (WGS84 degrees) takes top-left and bottom-right corners as lat, lon, or you press Draw on map…. For places, Categories narrows the result; a broad category includes everything beneath it, and blank means every category. Release is Latest available by default; Overture keeps only its two most recent releases, so a pinned one stops working within weeks. Row limit caps the rows, blank meaning no limit. The data is scanned in place from public object storage, and every row carries the release that answered in overture_release. Places come with name, category, confidence, address and geom.
Inputs and outputs
Inputs
None — this node starts a workflow.
Outputs
data— Table
Settings
The Attributes panel of Overture Maps, as in the app: the controls work, but nothing runs — there is no data behind it.
The same settings, as the Assistant writes them
{
theme: "places" | "buildings" | "transportation" | "land_use" | "addresses"
minLon: string
minLat: string
maxLon: string
maxLat: string
release?: "latest" | a published release id such as "2026-09-23.1" (prefer "latest": older releases are deleted from the bucket)
categories?: string
rowLimit?: string
extentMode?: "bounds" | "buffer"
pointSource?: "geometry" | "latlon"
pointGeometry?: string
pointLon?: string
pointLat?: string
searchArea?: "radius" | "shape"
radiusSource?: "fixed" | "column"
radiusMeters?: string
radiusColumn?: string
keyColumn?: string
}bbox in WGS84 degrees; categories is a comma-separated list, places only. extentMode "buffer" ignores the bbox, takes a points table on its input and returns the features within the radius (metres) of each point, carrying the point's keyColumn (or point_id) and distance_m; with pointSource "geometry" and searchArea "shape" it needs no radius and returns the features inside each input polygon (a Buffer's or a trade area's), distance_m 0
Example
A competitor scan around a candidate site: Layer Places (POIs), a box a few kilometres across drawn on the map, Categories restaurant. Feed the result to Spatial Join against your Trade Areas.