The analytics dock puts live summaries of your layers on the map: counts, sums, distributions, and trends that recalculate as the data changes and as you move the map. Widgets are two-way — click a bar and the map filters to match, and every other widget requeries. It is the fastest way to turn a layer into an answer without exporting anything.
Add a widget
Open the toolbar "Analytics" menu and pick what you want: a "Statistic" for a single number, a "Bar chart" to break a field down by category, a "Histogram" for how a numeric field is distributed, or a "Time series" for change over time.
Then configure it in the panel — which "Layer", which "Field", and what to "Show" (a count, a sum, an average, and so on). The rows change to suit the widget: a bar chart asks what to group by, a histogram how many bins, a time series which date field and what interval.
A live "Preview" updates as you go. Click "Add widget" when it looks right.
On the "Harbourview Network Buildout" project, a "Statistic" counting "Hydrants" plus a "Bar chart" of "Distribution Mains" by material summarizes the map in under a minute.
Scope a widget
Two header toggles on each widget card control what it counts:
- "In view" — binds the widget to the current map viewport; pan or zoom and it recalculates.
- "Selected" — binds it to the current spatial selection geometry.
When a widget is narrowed, a chip shows how much of the layer it's actually reading.
Crossfilter the map
Click a bar in a bar chart, or brush a range on a histogram or time series. Two things happen at once: the map filters the affected layers to the matching features, and every other widget requeries against the filtered result.
Active filters appear as chips in the filter bar — "<Field>: <values>" for categories, "<Field>: <min> – <max>" for ranges. Remove one with its chip (tooltip "Remove filter") or drop them all with "Clear".
Manage widgets
Drag a widget by its grip to reorder, and double-click its title to rename it in place. Its menu covers the rest — change the field, duplicate it, recolour it.
Minimize the dock to a small pill when you want the map back; click it to return.
Pinned AI insights
When Tamaat AI answers with a chart, "Pin" keeps it as a widget on the layer, sitting alongside the ones you built yourself — and marked so you can see where the number came from. See Insights and Saved Results.
Widgets in published web maps
Your widgets travel with a published map. Viewers get live values and can filter with them, but the widgets themselves stay as you built them. See Publish Web Maps.
Widgets are not dashboards
These two look alike and are deliberately separate things.
Widgets annotate a map. They live in the dock, on top of the project you are working in, and they travel with that map when you publish it. They are part of the map.
A dashboard is a page in its own right, where the numbers are the subject and a map is one element among charts, indicators, lists and a details pane. It is created from a map, but published, versioned and promoted separately — and building one changes nothing about the map or its widgets.
Reach for a widget when you want to understand a layer while you work it. Reach for a dashboard when someone else needs to read the answer without opening a map at all.
Demo data: City of Vancouver Open Data — street trees, zoning districts, bikeways, and local area boundaries.
- Spatial Analysis Tools — when a summary isn't enough and you need a result layer
- Spatial Selection — build the selections that "Selected" scoping reads
- Publish Web Maps