Events¶
An event is a scheduled period attached to a single station, typically maintenance work or another planned interruption. It carries a subject line, an optional longer message, a time range, and an availability impact. Events serve two purposes at once: they inform drivers in advance that something is planned, and they can override the station's computed availability status for as long as they run.
What an Event Carries¶
| Field | Meaning |
|---|---|
| Station | The one station the event takes place on. |
| Subject | A concise description (up to 140 characters), shown publicly. |
| Message | An optional longer description of the event. |
| Start | When the event begins. |
| End | When the event ends. Optional: an event without an end is open-ended and runs until an end is set. |
| Start of customer notifications | Optional point in time from which the event becomes publicly visible. If unset, the event is visible to the public immediately. |
| Availability impact | Whether and how the event overrides the station's availability status while it runs. |
How an Event Overrides the Status¶
The availability impact is the manual-override input of the status computation. While an event with an impact is ongoing, the override replaces the signal-based status for the station, even if real-time signals continue to arrive, and even if they are stale or missing.
When you create or edit an event in the Portal, you can choose from these impacts:
| Impact | Public status while the event runs |
|---|---|
| No override | The event is informational only. Signals determine the status as usual. |
| Limitedly available | limitedly-available |
| In maintenance | unavailable |
Alongside the event itself, the Map and the Export API publish the expected availability status derived from the impact, so drivers and data users can see in advance whether refuelling will be possible during the event.
Two events that override the status differently cannot overlap on the same station. The Portal rejects such an event when you try to save it.
Lifecycle¶
An event's lifecycle status is not stored. It is derived from the event's timestamps whenever it is needed:
| Status | When |
|---|---|
| Scheduled | The event has not started, and its notification time lies in the future. |
| Scheduled and announced | The event has not started, but it is already publicly visible (the notification time has passed, or none was set). |
| In progress | The event has started and has not yet ended. Only now does its availability impact override the status. |
| Expired | The event's end lies in the past. |
An open-ended event (no end time) never expires on its own. It stays in progress, and its override stays in effect, until an end time is set.
Public Visibility¶
The Map and the Export API show an event once it is announced, that is, once its notification time has passed, immediately if no notification time was set, or in any case once the event has started. Expired events disappear from both. Everything public about an event is public: subject, message, time range, and the expected availability impact.
Times¶
Event times are entered and published in the station's local time zone. When an operator schedules an event in the Portal, the start, end, and notification times are interpreted in the time zone of the selected station. The Map and the Export API likewise report event times in station-local time.