Map
Saved view
The table’s rows as pins on a map, each opening to the row’s details.
When to use
Section titled “When to use”The question is WHERE — sites, pubs, deliveries, visits — rather than how many.
When not to use
Section titled “When not to use”You want counts per place; a bar chart of rows per town says that more precisely.
What the table needs
Section titled “What the table needs”Two number columns holding latitude and longitude (named lat/lon, latitude/longitude or similar). A table with only addresses needs a Geocode step in the flow that fills it first.
Asking the AI
Section titled “Asking the AI”Describe it in a sentence — for example “put the pubs on a map”.
A map is a saved view drawn as pins, not a chart, so the drafter checks the table has coordinates and opens the map builder, which asks you to confirm the two columns.
From another AI
Section titled “From another AI”An assistant connected to Routario over MCP (Claude, ChatGPT) makes it with map_create, then puts it on a board with dashboard_tile_add.
Settings
Section titled “Settings”- Coordinates — The two number columns that place each pin: latitude and longitude.
Auto-generated from the tile registry (core/custom_tables/tile_registry.py) — the same text the chart editor and the AI drafter read. Do not edit by hand.