Output · Reports

Map

Draws the input's geometry as a map over an offline basemap, styled in the Map tab, ready to place in a report.

Also known as: Choropleth, static map

How it works

Wire the table in and style the map in the Map tab under the canvas: the layer mode, colours, choropleth classes or markers. In the Attributes panel, Geometry column picks which geometry to draw; left blank, the map draws the input's last geometry column, which is the one a Buffer or Trade Areas step adds. The CRS is taken from the input. Heading and Commentary are optional and print above and under the map, with a Generate comment button for the commentary that reads Improve comment once there is text. The second input is optional: a lookup table of category values to logo file paths that the Markers mode reads. The map is rendered as a static image over the offline OpenStreetMap basemap, and the output is a section that Report Assembly places in the layout.

Inputs and outputs

Inputs

input_0 — Table
input_1 — Table

Outputs

section — File

Settings

The Attributes panel with a Map node selected.

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

The same settings, as the Assistant writes them

{
  heading: string
  commentary?: string
  geometryColumn?: string
}

heading titles the report section; geometryColumn picks which geometry column to draw (blank = the last one, e.g. a Buffer's added column)

Example

A catchment map for the store report. Wire the Trade Areas output, leave Geometry column blank so the rings are drawn rather than the store points, Heading "Catchment rings", and in the Map tab colour by ring_label.

Map