YAML Basics
CruisePlan uses YAML files to define cruise configurations. This guide covers the essential fields you need to know.
Basic Structure
# Cruise metadata
cruise_name: "North Atlantic Survey 2025"
start_date: "2025-06-15"
default_vessel_speed: 10.0
turnaround_time: 30.0
# Global catalog - define your operations
points:
- name: "STN_001"
latitude: 60.0
longitude: -30.0
operation_type: CTD
action: profile
lines:
- name: "ADCP_transect"
operation_type: underway
action: ADCP
route:
- latitude: 60.0
longitude: -30.0
- latitude: 60.0
longitude: -20.0
# Schedule organization
legs:
- name: "leg1"
departure_port: port_reykjavik
arrival_port: port_bergen
activities: ["STN_001", "ADCP_transect"]
Essential Fields
Cruise Metadata
Field |
Required |
Description |
|---|---|---|
|
Yes |
Name of your cruise |
|
Yes |
Start date (ISO format) |
|
No |
Ship speed in knots (default: 10) |
|
No |
Time between operations in minutes |
Point Operations
CTD stations, moorings, sample collection:
points:
- name: "MOOR_001"
operation_type: mooring
action: deployment
water_depth: 3500 # Optional - auto-added by 'process'
duration: 45 # Optional - in minutes
latitude: 60.0
longitude: -30.0
Line Operations
Transects, underway surveys:
lines:
- name: "transect_north"
operation_type: underway
action: ADCP
route:
- latitude: 60.0
longitude: -30.0
- latitude: 62.0
longitude: -25.0
Area Operations
Box surveys, mapping:
areas:
- name: "survey_box"
operation_type: survey
action: bathymetry
duration: 120 # minutes
corners:
- latitude: 60.5
longitude: -28.0
- latitude: 61.5
longitude: -28.0
- latitude: 61.5
longitude: -27.0
- latitude: 60.5
longitude: -27.0
Schedule Organization
Legs organize your cruise into phases:
legs:
- name: "leg 1"
departure_port: port_reykjavik
arrival_port: port_reykjavik
first_waypoint: MOOR_001
last_waypoint: survey_box
activities: ["MOOR_001", "MOOR_002", "survey_box"]
- name: "leg 2"
departure_port: port_reykjavik
arrival_port: port_bergen
first_waypoint: transect_north
last_waypoint: transect_north
activities: ["transect_north"]
Operation Types and Actions
Valid combinations of operation_type and action for different activities:
Point Operations:
Operation Type |
Valid Actions |
Use Case |
|---|---|---|
|
|
Water column profiling with CTD/rosette |
|
|
Water sampling operations |
|
|
Deploy/recover instruments (default: 999 hours) |
|
|
Equipment calibration |
|
|
Departure (mobilization) / arrival (demobilization) |
|
|
Navigation waypoints with optional operations |
Line Operations:
Operation Type |
Valid Actions |
Use Case |
|---|---|---|
|
|
Continuous measurements while in transit |
|
|
Towed instrument operations |
|
|
CTD sections (expandable to individual stations) |
Area Operations:
Operation Type |
Valid Actions |
Use Case |
|---|---|---|
|
|
Area surveys and mapping |
Coordinates
Latitude: -90 to 90 (negative = South)
Longitude: -180 to 180 OR 0 to 360 (negative = West)
Decimal degrees only (e.g., 60.5, not 60°30’)
Example: Atlantic stations - Latitude: 60.0 (60°N) - Longitude: -30.0 (30°W)
Common Workflow
Start with generated stub: Run
cruiseplan stationsto create a basic fileEdit operation types: Add appropriate
operation_typefieldsAdjust timing: Modify
durationif neededOrganize legs: Group activities into logical cruise phases
Process: Run
cruiseplan processto validate and enrich
For complete field reference, see YAML Configuration Reference.