Build one or more filters. Pick comparison values from the layer or type them manually.
Configure the published dashboard header — title, search bar, and theme-aware logos.
Displayed in the center of the dashboard header.
Optional display-only search field in the header.
Upload separate marks for light and dark header themes. The dashboard switches automatically when viewers toggle dark mode.
Configure the published dashboard sidebar — overlay layers, administrative boundaries, basemaps, theme, and default selection.
Choose which GeoServer layers appear in the TOC, grouped by workspace. Check On by default for layers that should be visible when the dashboard opens.
Map each TOC level to a published layer and the attribute used for boundary names.
Compact thumbnail grid in the dashboard TOC. Bundled previews are used by default; upload optional custom thumbnails per basemap.
Dark mode toggle and blue color palettes for light and dark themes on the published dashboard.
Blue palette when viewers use light mode.
Blue palette when viewers use dark mode.
Optional pre-selected boundary when the dashboard first loads.
Design KPI metric cards, overview spider chart, card chrome, and the published dashboard grid layout.
Border and background for KPI metric cards and the Overview card on the published dashboard.
Select a card to edit. Overview stays first and cannot be deleted. Use Show to include cards on the published dashboard.
Select a KPI card from the list.
The Overview card is always listed first. Its title and value come from the selected administrative boundary. Configure description, spider indicators, and chart style below.
Choose which levels show the spider chart when a boundary is selected.
Each radar axis: label, normalized field (0–100), and raw value field (tooltip) per admin boundary layer from TOC.
Value field comes from the administrative boundary layer configured in TOC.
Unit, decimals, and optional power-of-10 scaling for the numeric value.
Rich text shown when viewers click the ? button on the published KPI card.
Set rows and columns, assign each Show-enabled card to a cell, and merge neighboring cells for larger cards (e.g. Overview spanning two rows).
Choose which map toolbar buttons appear on the published dashboard — top-right overlay on /dashboard/.
Zoom, reset view, and fullscreen controls.
Refresh map tiles from GeoServer.
Click features on the map and clear highlights.
Scale bar and cursor coordinates — same position as the portal map. Shown below the basemap picker when the basemap gallery is enabled.
Distance and area tools on the published dashboard map.
Define chart queries and appearance here. Charts are not drawn in the manager. On the published dashboard, each chart loads data filtered by the selected administrative boundary in the TOC (same as KPI cards). Use ↑ / ↓ on each chart in the list to set dashboard order within the active chart tab.
Select a chart from the list or add a new chart.
Bar charts: drop shadow on each bar (color, blur, offset below).
Cabinet oblique (like PieChart_3D.png): vertical walls (straight down), flat elliptical top. Defaults — wall 30px, top scale 0.40, azimuth 52°, rotation 38°. Enable shadow for ground shadow.
ZIP may contain a shapefile (one .shp) or an Esri File Geodatabase (.gdb folder). After upload,
import rows are filled from the dataset (GDB: one row per feature class; feature dataset name suggests schema). Edit any
cell, then import.
| Schema | Table name | Import mode | Source SRID | Target SRID | Source layer (GDB) |
|---|
| Datastore (PostGIS) | Workspace | Layer Name | Declared SRS | Publish to WMS | Publish to WFS | SLD (optional) |
|---|
Pick a datastore (schema.table); workspace and layer name fill from the part before and after
. (editable). Add rows to publish several layers in one run. Per row you may attach a
.sld file: it is validated (well-formed XML with
StyledLayerDescriptor root) before any GeoServer step for that row; the style is uploaded to the
same workspace as the layer and named after the file name without extension
(safe identifier). The layer’s default style is set to that style.
| Layer key | Display name | GeoServer layer name | Queryable | Visible by default | Has legend |
|---|---|---|---|---|---|
Catalogue rows from layers_catalogue with GeoServer / PostGIS status. Destructive actions
require two steps: confirm the warning, then type the exact layer_key (catalogue rows) or
schema.table (unpublished tables). Removing a catalogue row deletes its
layers_catalogue entry (and permissions). Dropping PostGIS also removes the GeoServer layer
first when a layer name is set.
| Layer key | Display name | PostGIS table | GeoServer layer | On GeoServer | Actions |
|---|
Geometry-backed tables not referenced by any layers_catalogue.table_name. Drop only when you
are sure they are unused.
| Qualified table | Geom column | Actions |
|---|
Select PostGIS tables (already imported), then run a compatibility check. Reproject or re-import from the PostGIS Import tab if SRID or geometry type must change outside the supported conversion rules.
Selected fields: —
Any selected field that is missing on a table will be stored as NULL for that table in a
combined historical model.
Set a target SRID (dropdown or custom) and resolve geometry type (or agree to unified Multi* type) in Define historical layers to enable this step.