Cruises
What v2 brings
Section titled “What v2 brings”Cruises are TravStats’ second first-class entity. The data model treats a cruise as a voyage with an ordered sequence of port calls:
- Voyage — ship, cruise line, departure port, return port, date range
- Port calls — each port has an arrival and departure timestamp; the gap between them is “time ashore”
Both are pulled in the same email-parser pipeline that already powers flights — paste a confirmation from MSC, AIDA, Costa, NCL or a similar operator and the parser extracts the itinerary.
What stays the same as flights
Section titled “What stays the same as flights”- One database, one dashboard. Flights and cruises render on the same map and globe.
- Statistics merge — total nautical miles sit alongside flight kilometres on the same overview.
- Achievements include cruise-specific awards (ports visited per region, repositioning crossings, etc.) without breaking the flight ones.
- Tags, trips, and import/export work identically. A trip can mix flights and cruises.
How to follow progress
Section titled “How to follow progress”- Code:
dev/multi-domain-v1on GitHub - Issues: issues tagged
domain:cruise - Beta builds:
ghcr.io/abrechen2/travstats:2.0.0-beta.Nonce a beta tag is cut
We’ll update this page as soon as the v2 stable tag lands.