Build one or more filters. Pick comparison values from the layer or type them manually.
Layer subset (grouped by GeoServer workspace). Map loads with no overlays on.
Template-style thumbnails in the dashboard TOC. Bundled previews are used by default; upload optional custom thumbnails per basemap.
Select a KPI card from the list.
The Overview card is always listed first and cannot be deleted. Use the Show checkbox in the card list to include or hide it on the published dashboard. Its title and value come from the selected administrative boundary (Governorate / Wilayat / Town name). Configure the description and spider chart style below. Use the up/down arrows on other KPI cards to change their order on the dashboard. Metric values for the spider chart are taken automatically from all other KPI cards.
Map controls (portal equivalents):
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).
Select a chart from the list or add a new chart.
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.