This workspace recomputes the Thessaloniki shore-power demand curve in your browser from every port call in the model. Nothing is sent anywhere; settings and overrides stay in this browser.
How the curve is built
- Calls come from https://webportal.thpa.gr/ctreport/vessel/schedule (2024-01 to 2026-11). Excluded: planned-only times, anchorage and roads rows, service craft, stays under 0.5 h or over 30 days, duplicates.
- Start times include a pre-berth offset where the source times arrival before all-fast (cruise 0.0 h, other 0.0 h).
- A ship connects a fixed delay after berthing and disconnects a fixed lead before departure (30 and 30 min by default).
- Each call draws a constant average kW from the Valencia category models (size bin by GT, TEU or DWT), shaped within the call by a profile that keeps the call's energy unchanged.
- Values are averages over each interval, timestamp = start of interval, local time Europe/Athens. Partial first and last intervals count pro rata.
- Peak potential is the sum of each connected ship's peak kW, an upper bound for instantaneous demand.
What is assumed
- Power values are literature-based (TNO 2025 R12590, IMO 4th GHG, ICCT 2017, EMSA), not metered at this port. Low to high spans about a factor of four.
- Full adoption: 100% of merchant calls connect. It is an upper bound.
- FuelEU / AFIR 2030 set: container, ropax and cruise above 5,000 GT; unknown GT counts as in scope.
- Phased: a deterministic share of FuelEU vessels (by a hash of the vessel key), 0% in 2026 to 100% in 2030.
- Current confirmed: vessels with operational OPS at a terminal with an operational connection; no connection register exists for this port yet.
- Vessel categories and sizes outside the source are mapped or imputed (see the quality notes and the Method page); berth compatibility and connection limits are not applied.
- Baseline port load is a constant placeholder (zero by default).
Overrides
Vessel overrides are level 1 of the evidence waterfall. A kW override applies to all power levels, and peak kW scales with it. Ops status "absent" removes the vessel from every case except full adoption. Export them as registers/overrides.csv rows; exclusion is written as avg_kw = 0 with the reason prefixed "[exclude]".