Greece - ferries. #193

Open
opened 2026-08-20 14:38:10 +00:00 by art · 1 comment
Owner

Implement the ferries layer for Greece.

Implement the ferries layer for Greece.
Author
Owner

Issue #193 asked for the ferries layer. The catalogue (issue #171) records ferries as ABSENT — the Ministry of Shipping's sailing_traffic is tabular schedules with no route geometry. Since that verdict was wrong twice before (roads #180, rail #179), I re-checked the absence on 2026-08-20 from the same vantage points:

  • data.gov.gr, full CKAN sweep — the only ferry-ish items with geometry are regional: the 2003 Crete spatial framework's Θαλάσσιες Συνδέσεις (searoad_arc, Decentralized Administration of Crete, licence None) and municipal Λιμάνια point layers. Planning lines for one region from a 2003 plan — not a national network.
  • data.europa.eu — ferry × Greece is exactly one dataset: the NAP maritime-transport XLSX, tabular, licence unset.
  • ΥΠΕΝ services — neither WFS workspace (WFD_geodata_50K, floods_rev1) nor the INSPIRE GeoNetwork catalogue (geoportal.ypen.gr, CSW-swept) carries a ferry layer; the tourism spatial framework RAR (2009) has sea-tourism points and ports, no route lines.
  • Transport sources — Egnatia Odos TEN-T is roads only (five classes, checked in the staged dbf); the ΔΜΕΟ regional clips have no ferry class (Crete roa_lin_roads schema checked); HNHS free data is coastline/DTM/gazetteer; the archived geodata.gov.gr (785 dataset pages) has no national ferry dataset, only the regional Μεγανήσι - Ακτοπλοϊκή συγκοινωνία fragment.

Verdict: ABSENT stands. No official, non-OSM, permissively-licensed national ferry-route geometry exists to import, and deriving lines from sailing_traffic port pairs would invent geometry the source does not distinguish (the R137 rule that keeps water_bodies lakes-only).

What I need to implement this issue (either is a written ask, not code): a national ΔΜΕΟ assembly that includes the road-network πορθμεία (#180 options 2/3 — the same shape as SE/FI/PL, whose ferries all come from the national road dataset), or ΥΝΑΝΠ publishing route geometry for the coastal network. Until then Greece contributes no ferries partition — the contract's supported "a country has no data for this layer" state.

The re-check is recorded in docs/country-gr.md (new Ferries section) on branch issue-193-gr-ferries so the search is not repeated. Recommendation: close this issue as absence-confirmed, or authorize the derived straight-line layer from official schedule data as an explicitly cartographic layer.

Issue #193 asked for the ferries layer. The catalogue (issue #171) records ferries as ABSENT — the Ministry of Shipping's `sailing_traffic` is tabular schedules with no route geometry. Since that verdict was wrong twice before (roads #180, rail #179), I re-checked the absence on 2026-08-20 from the same vantage points: - **data.gov.gr, full CKAN sweep** — the only ferry-ish items with geometry are regional: the 2003 Crete spatial framework's `Θαλάσσιες Συνδέσεις` (`searoad_arc`, Decentralized Administration of Crete, licence None) and municipal `Λιμάνια` point layers. Planning lines for one region from a 2003 plan — not a national network. - **data.europa.eu** — `ferry` × Greece is exactly one dataset: the NAP maritime-transport XLSX, tabular, licence unset. - **ΥΠΕΝ services** — neither WFS workspace (`WFD_geodata_50K`, `floods_rev1`) nor the INSPIRE GeoNetwork catalogue (geoportal.ypen.gr, CSW-swept) carries a ferry layer; the tourism spatial framework RAR (2009) has sea-tourism points and ports, no route lines. - **Transport sources** — Egnatia Odos TEN-T is roads only (five classes, checked in the staged dbf); the ΔΜΕΟ regional clips have no ferry class (Crete `roa_lin_roads` schema checked); HNHS free data is coastline/DTM/gazetteer; the archived geodata.gov.gr (785 dataset pages) has no national ferry dataset, only the regional `Μεγανήσι - Ακτοπλοϊκή συγκοινωνία` fragment. **Verdict: ABSENT stands.** No official, non-OSM, permissively-licensed national ferry-route geometry exists to import, and deriving lines from `sailing_traffic` port pairs would invent geometry the source does not distinguish (the R137 rule that keeps `water_bodies` lakes-only). **What I need to implement this issue** (either is a written ask, not code): a national ΔΜΕΟ assembly that includes the road-network πορθμεία (#180 options 2/3 — the same shape as SE/FI/PL, whose ferries all come from the national road dataset), or ΥΝΑΝΠ publishing route geometry for the coastal network. Until then Greece contributes no `ferries` partition — the contract's supported "a country has no data for this layer" state. The re-check is recorded in docs/country-gr.md (new *Ferries* section) on branch `issue-193-gr-ferries` so the search is not repeated. Recommendation: close this issue as absence-confirmed, or authorize the derived straight-line layer from official schedule data as an explicitly cartographic layer.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
art/ismap#193
No description provided.