# What's on land?

> Cruise itineraries, ship catalogues and port timetables from a finite collected snapshot.

## Access

Every content page advertises static Markdown and JSON using HTML link rel="alternate" elements. Append index.md or index.json to a directory-style page URL. JSON has schema_version, title, type, canonical url, collected date and alternates; data contains named fields. Port data is scoped to the displayed month and pagination page. Follow months and pagination links for more records. Empty results mean no calls collected, not no ship activity. Times are local as reported; do not infer a timezone or docking confirmation.

## Entry points

- [Home](/index.md)
- [Ports by country](/ports/index.md)
- [Cruise lines](/lines/index.md)
- [Coverage and reliability](/coverage/index.md)
- [Attribution](/attribution/index.md)
- [Complete page inventory (JSON)](/llms.json)

## Feeds

Ship and port pages advertise RSS 2.0 feeds at index.xml (port-month pages share the canonical port feed). Feeds include current and upcoming collected entries, including sailings ending today. Publication dates use collection time, not future sailing dates. Stable item GUIDs identify schedule entries; these are not a history of detected changes.

## Interpretation

Official timing observations take priority; otherwise a strict majority of distinct aggregators, then completeness and configured source priority. Tender icons need call-specific source evidence; unmarked is unknown. Voyage evidence pages expose retained observations and selection decisions. Data is a demonstration snapshot, not an authoritative sailing notice; check the operator for travel decisions. Source attribution and terms apply equally to these representations.