Access Denied
This account cannot sign in to the platform. Contact your administrator if you believe this is an error.
Build one or more filters. Pick comparison values from the layer or type them manually.
Configure shared dashboard options and per-interface definitions (login picker, header switcher, and color themes).
Constant title shown in the dashboard header for all interfaces.
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.
Ministry mark on the hero panel and BGC mark in the sign-in footer. Leave empty to use bundled defaults.
Full-bleed image behind the login (and Access Denied) screen. Leave empty to use the bundled default.
Copy for the login screen (not per-interface). Leave blank to keep current defaults. Optional font sizes use rem units.
Title appears in the login picker and dashboard header dropdown. Subtitle is shown on the login page only.
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 default theme on load. Color palettes are configured per interface on the Dashboard tab.
Optional pre-selected boundary when the dashboard first loads.
Design KPI panel tabs per interface — each tab has its own title, cards, appearance, and dashboard grid.
Add tabs for this interface. The selected tab’s cards and grid appear below. On the published dashboard, tabs appear under the header.
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.
Choose Value field (attribute on the administrative boundary layer from TOC) or By query (named query from the Queries tab, aggregated inside the selected boundary).
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 named queries on portal catalogue layers (attribute filters). Queries are shared by all interfaces. Use them in KPI value mappings (By query + aggregate). Prefer layers with a PostGIS table (not WMS-only). Results are clipped to the selected administrative boundary on the published dashboard. Attribute filters: type in the field/value menus to narrow the list; values load as unique values of the selected field (type + Enter for a custom value, e.g. LIKE patterns).
Select a query from the list or add a new query.
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.
Build time-series line or bar charts from administrative boundary attributes. For each TOC admin level (Governorates / Wilayats / Towns), map fields of that boundary layer to years. On the published dashboard, selecting a boundary shows values from that feature’s fields. Charts appear in the Charts panel with Charts-tab charts; optional Display order places them among those charts.
Select a time-series chart from the list or add a new one.
Manage Arabic copy for text that appears on the published dashboard. English is taken from the current dashboard draft. Saving here does not change Dashboard Manager configuration. Reload after you add, edit, or remove KPIs, charts, or login text.
|
Schema
|
Table name | Import mode | Source SRID | Target SRID |
|---|
| Datastore (PostGIS) | Workspace | Layer Name | Declared SRS | SLD (optional) |
|---|
| 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 Import Dataset 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.