Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Visuals

On this page (16)

One page per visual: visuals catalog.

Certified count#

The product's single visuals catalog has 46 data visuals + 4 layout elements = 50 items. The same catalog feeds the Insert tab (creates a new visual) and the Visual tab (changes the type of the selected one), with the same icons and colors.

The catalog has 50 items: 46 data visuals and 4 layout elements (text, shape, image, button).

No visual is a mock: all have a dedicated React component (Recharts or in-house SVG), and every catalog item requires a synthetic reference data sample — the suite fails if one is missing. Compared with Power BI, the ~40 native ones are matched/surpassed (including what are paid custom visuals there: sankey, marimekko, bullet), and the Brazil maps with the IBGE municipal mesh are superior to Power BI out of the box. This is equivalence per item, with evidence — we don't claim full parity.


The visuals system (template)#

  1. What it is — a family of 46 data visuals rendered in the browser, plus 4 layout elements.

  2. When to use it — every dashboard; the choice of type depends on the question (compare, compose, distribute, relate, map).

  3. How it works — data goes through a single row pipeline (sum/avg/min/max/last/count aggregations, Top-N, sorting) and the visual receives ready-made rows; a per-visual capability matrix (axes, legend, labels, stacking, sorting, reference lines, secondary axis, small multiples, totals, format) defines what each type supports.

  4. Prerequisites — a model/query that produces the dimension + up to 5 metrics per visual (field selector).

  5. How to validate — create "Revenue by category" (bars), add a 2nd metric, turn on labels and a reference line; check each option on the visual.

  6. Limits and caveats — the data transformation and geometry of each visual are covered by automated tests; the final appearance depends on the browser.

  7. Sample data (synthetic)

    categoryrevenue
    Bebidas250
    Limpeza90
    Higiene140
  8. Evidence — visuals catalog, row pipeline and per-visual capability matrix covered by a deterministic suite; each item requires a synthetic sample; the row pipeline is frozen by the reference test suite, with an identical result on every run.


Full catalog (46 data + 4 layout)#

Render: Recharts, in-house SVG (custom) or HTML. "How to validate each one": create the visual from the Insert tab with the indicated fields and check the result; each visual has a synthetic reference sample.

KPIs and cards (3)

#idVisualRenderMinimum fields to validate
1kpiKPIcustom1 metric (Receita)
2kpi-sparkKPI + trendcustom1 metric + 1 time
3multikpiMulti-KPIcustomseveral metrics

Comparison and trend (6)

#idVisualRenderMinimum fields to validate
4barBarsRechartsdimension + metric
5hbarHorizontal barsRechartsdimension + metric
6lineLineRechartstime + metric
7areaAreaRechartstime + metric
8comboBar + line comboRechartsdimension + 2 metrics
26combo-stackStacked columns + lineSVGdimension + series + metric

Composition and part-to-whole (7)

#idVisualRenderMinimum fields to validate
9piePieRechartsdimension + metric
10donutDonutRechartsdimension + metric
16treemapTreemapRechartsdimension + metric
11funnelFunnelRechartsstages + metric
17waterfallWaterfallcustomsteps + change
32mekkoMarimekko (share)SVG2 dimensions + metric
33ribbonRibbon (rank changes)SVGtime + category + metric

Gauges and targets (4)

#idVisualRenderMinimum fields to validate
12gaugeGaugeRecharts/custom1 metric + target
13thermometerThermometercustom1 metric + target
21bulletBullet (target)SVGmetric + target + bands
23progressProgress ringSVGmetric + target

Distribution and statistics (5)

#idVisualRenderMinimum fields to validate
18histogramHistogramcustom/Recharts1 continuous metric
19paretoPareto (80/20)customdimension + metric
20boxplotBox plotcustomgroup + metric
15scatterScatterRecharts2 metrics
22quadrantQuadrant scatterSVG2 metrics + cutoffs

Relationship and pairwise comparison (5)

#idVisualRenderMinimum fields to validate
14radarRadarRecharts/customaxes + series
24dumbbellDumbbell (before × after)SVGcategory + 2 values
30slopeSlope (before × after)SVG2 periods + metric
31tornadoTornado (mirrored)SVGcategory + 2 series
34networkNetwork (who links to whom)SVGnodes + edges

Time, flow and schedule (5)

#idVisualRenderMinimum fields to validate
25calendarCalendar (seasonality)SVGdate + metric
27ganttGantt (schedule)SVGtask + start + end
28sankeyFlow (source → target)SVGsource + target + flow
36timelineTimeline (period)SVGevent + period
44motionBubbles over time (animated)Recharts+anim2 metrics + time

Tables (4)

#idVisualRenderMinimum fields to validate
37tableTable (with totals)HTMLcolumns
38matrixMatrix (rows × columns)HTMLrows + columns + value
46pivotPivot table (drag)HTML+dragdraggable fields
39heatmapHeatmapHTML2 dimensions + metric

Showcase and data text (2)

#idVisualRenderMinimum fields to validate
29wordcloudWord cloudSVGterm + weight
35imagecardImage cardSVGlabel + image + metric

Brazil maps (5)

#idVisualRenderMinimum fields to validate
40mapBrazil map (state)in-house SVGstate (UF) + metric
41mapcityMap by municipalitySVG (IBGE)municipality + metric
42bubblemapBubble map (lat/long)SVGlat/long + metric
43geoheatGeographic heat mapSVGlat/long + intensity
45maplayersLayered mapSVGgeographic layers

Layout elements (4 — not data visuals)

#idElementRender
E1textTextcustom
E2shapeShapecustom
E3imageImagecustom
E4buttonButton (with actions)custom

Brazil maps (differentiator)#

  1. What it is — 5 native Brazil maps: by state (UF), by municipality (IBGE mesh), lat/long bubbles, geographic heat and layers.
  2. When to use it — regional distribution of sales/customers; density by city.
  3. How it works — the state map uses in-house SVG (27 states); the municipality map loads the state's mesh on demand through an internal route (/api/geo/br/[uf]) with a 30-day cache; the model's state/municipality data category guides the geographic join.
  4. Prerequisites — a column marked as state/municipality (see data category in Semantic model); for municipalities, the state's mesh needs to be fetched (network).
  5. How to validate — mark filiais.uf as a state (UF), create the state map of "Revenue by state" with SP/RJ/MG and check the fill; then open the municipality map for a state and confirm the mesh loads.
  6. Limits and caveats — the municipal mesh comes from IBGE and is cached: the first load of a state may take longer than the following ones.
  7. Sample data (synthetic) — Revenue by state: SP=250, RJ=90, MG=140.
  8. Evidence — map rendering and mesh geometry (state and municipality) covered by a deterministic suite; the municipal mesh is served through an internal route with a cache.

Layout elements (text, shape, image, button)#

  1. What it is — elements without data: text box, shape, image and button with actions.
  2. When to use it — titles, frames, logo, navigation by button.
  3. How it works — the button triggers actions (e.g., apply a bookmark, switch page); image/shape/text are purely visual.
  4. Prerequisites — none.
  5. How to validate — add a "Go to Detail" button that switches pages and confirm the navigation.
  6. Limits and caveats — they don't count as data visuals (hence 46, not 50).
  7. Sample data (synthetic) — title "Aurora Varejo — July/2026".
  8. Evidence — rendering and actions of the layout elements (text/shape/image/button) covered by the editor's tested logic.

About drill, tooltips and per-visual export: see Filters and interactions and Export and distribution.

Related links