Skip to content

What the platform does

One Laravel application, one PostgreSQL/PostGIS database, one Docker container, four surfaces. All four are built, and each is listed here with its status against every feature.

Public site

Seven server-rendered pages that need no JavaScript to read: this page, the home page, standards, the Saku pilot description, the demonstrator landing page, the FAQ and contact.

  • Server-rendered HTML with semantic headings, one h1 per page, a unique title and meta description, a canonical URL and Open Graph tags
  • The Inter typeface is bundled with the application; no third-party font origin, no content delivery network, no analytics and no third-party script
  • One source of entity facts in configuration, read by every page
  • English only for this delivery

Bağcılar demonstrator

Six pages on seeded demonstration data, in Turkish, English and Estonian, served under /demo.

  • Overview: district totals, map, and the demonstration-data banner
  • Population: a resident register, masked by default, with a per-row control that reveals one record at a time
  • Services: a citizen-services catalogue with delivery records
  • Infrastructure: a building inventory with risk banding
  • Scenarios: illustrative flood, fire and wind-storm models. Nothing on this page dispatches anything.
  • Reports & Analytics: engagement, demographic and demonstration impact figures
  • Every write endpoint, and the unmasked resident record, require a sign-in with the operator role

Saku municipality workspace

Saku valla olukorrapilt: a decision-support awareness dashboard for the municipality, built only from public data. The route space, the sign-in, the role gate, the Estonian and English interface and the public-data capabilities below are all in the current build.

  • Sign-in, one role per account, and project isolation across every Saku route and endpoint
  • Estonian by default with an English toggle
  • Overview: warnings in force, nearest-station observations, settlement count, boundary snapshot date, and the number of layers with verified provenance
  • Warnings panel with type, level, area, validity, upstream timestamp and retrieval time, an explicit empty state, and a stale state when the upstream cannot be reached
  • Observations panel for the two or three nearest national stations, each value time-stamped
  • Map: the national base map with attribution, plus the Saku boundary and settlement polygons from the official register
  • Toggleable public overlay layers — buildings, roads, hydrography — each carrying its attribution and licence
  • Fire-weather index for the current day from Copernicus EFFIS
  • Flood-hazard areas, only if the public service endpoint is confirmed
  • Data sources: a provenance registry naming provider, dataset, URL, licence, attribution, data class, refresh policy, last retrieval and known limitations for every feed
  • Export: any layer as GeoJSON or CSV, each file carrying a provenance header block
  • Situation snapshot: one text or CSV summary of warnings, observations, settlement count and layers shown, for pasting into a crisis-committee note
  • Settlement summary: buildings per settlement and population per settlement, labelled DERIVED with the method stated
  • Incident and decision log: role-gated, append-only, timestamped, exported as CSV, and labelled a demonstration log rather than the municipality's record

Saku citizen view

Saku elaniku info: a public-information view of the same public data, with preparedness guidance that links to the official sources rather than republishing them. The route space, the role gate and the content below are all in the current build.

  • Official weather warnings in force for Harju maakond, in Estonian and English, with time stamps
  • A read-only map subset: the Saku boundary, the settlements and the public base map, with no log and no export
  • Preparedness guidance that links to Päästeamet, olevalmis.ee, 112 and Riigi Ilmateenistus
  • The same data-sources registry, in citizen wording
  • One saved home location per account, stored server-side and private to that account, with an on-screen alert preview permanently labelled a demonstration
  • No registration, no push notification, no personalised routing, and no citizen data beyond the optional saved point

Interfaces for other systems

Standards and formats are set out in full on the standards page. The two machine interfaces beyond the exports are listed here with their status.

  • A read-only NGSI-LD-formatted JSON-LD export of Saku entities, labelled a formatted export
  • A machine-readable dataset provenance endpoint listing every imported dataset and its version

Roadmap

Nothing in this section exists in the software, and nothing here is committed to a date. It is listed so that the rest of the site never has to mention it.

  • An NGSI-LD context broker (FIWARE Orion-LD), rather than the formatted export described on the standards page.
  • CityGML model exchange.
  • National alert systems, including EE-ALARM, as trigger inputs.
  • Utility and municipal data under agreements — outage status, hazardous establishments, shelters, municipal contacts and assets.
  • Calibrated hazard scenarios, validated with municipalities.
  • A Horizon Europe disaster-resilience project is under preparation. No proposal has been submitted, no consortium is finalised, no funding has been applied for or awarded, no coordinating role is claimed, and no municipality is stated or implied to be taking part.