Virtual Routes — Master Data

Read-only viewer (ABMS-61 §9.1): everything the route engine reads — geography hierarchy, stations, local transfers, ground connections, linked ports, and the sold ferry hops with their representative duration/price. Names/descriptions are translatable — currently 1/30 languages filled.

🔒 This page is a viewer/report — data cannot be added, edited, or deleted here. The master data lives in data/virtual-routes/locations.json (single source of truth for the engine and this page).

Geography — Continent → Country → Region

Regions map to the website's travel-region filter (§3.3).

Region	Country	Continent	Travel region (site filter)	Status

Locations

Ports are linked from the existing Ports metadata by code — an unresolved code means the snapshot doesn't know it (§3.4).

Location	Type	Region	Travel region	Ports (from Ports metadata)	Aliases	Status

Stations / Terminals

Station / terminal	Type	Location	Lat / Lng	Active

Local transfers — Hubs (station ⇄ port)

Entered once per location and reused by every connection and route (§3.6).

Transfer (station ⇄ port)	Location	Distance	Ways (mode · time · price · description)

Ground connections

Two mainland locations with no ferry between them; ferry hops are never entered here — the engine adds those (§3.7).

Connection	Options (mode · time · price → / ← · website · stations)

Sold ferry hops (engine ferry edges)

Direct active routes from the routes metadata between master-data ports, with representative figures enriched by the metadata cron (duration sampled from GTFS trips, price = cheapest). These are NOT live quotes — date-specific prices/schedules come from trip search.

From port	To port	Typical duration	Min price