🌊 Comprehensive Oceanographic Research Cruise Planning System — Streamlining the process of planning oceanographic research expeditions.

The Challenge: Oceanographic cruise planning involves complex route and timing calculations, frequent unit conversions (nautical miles <-> kilometers, decimal degrees <-> degrees decimal minutes), and rapid plan updates. Different people may need different formats--spreadsheets for quick calculations, degrees/decimal minutes for navigation, kilometers for station spacing, knots for voyage timing. Using historical station locations may be preferred, but can be tricky to access.

• Fragmented Tools: Scattered spreadsheets, manual calculations, custom code snippets
• Time-Intensive Processes: Semi-manual station planning, timing calculations, and proposal formatting
• Error-Prone Workflows: Manual depth lookups, coordinate formatting, and schedule validation

The Solution: CruisePlan provides an integrated, semi-automated system for an efficient cruise-planning workflow.

Primary Users:

• 🔬 Oceanographic Researchers: Principal investigators designing research expeditions
• 📊 Students: Graduate students learning cruise planning methodology
• 📋 Proposal Writers: Scientists preparing funding proposals with detailed cruise plans

Research Domains: The primary development of CruisePlan is for physical oceanographers, with CTD stations, mooring deployments and glider operations as default. However, it is possible to incorporate any type of point, line or area operation of a ship with a specified manual duration based on your own experience.

CruisePlan transforms complex cruise planning from a weeks-long manual process into a structured, validated workflow that produces proposal-ready documentation with some checks on operational feasibility.

⚠️ Breaking Changes in v0.3.0: Commands cruiseplan download and cruiseplan pandoi have been removed. Parameter names shortened (--bathymetry-* → --bathy-*). See MIGRATION_v0.3.0.md for migration guide and CHANGELOG.md for complete changes.

⚠️ Breaking Changes in v0.3.3: YAML configuration now uses transects: instead of transits: for scientific line operations and waypoints: instead of stations: for point operations.

⚠️ Breaking Changes in v0.3.6: Major architecture refactoring - module renaming for improved clarity:

• cruiseplan.schema → cruiseplan.config (Configuration schemas and validation)
• cruiseplan.core → cruiseplan.runtime (Business logic and data processing)
• cruiseplan.calculators → cruiseplan.timeline (Scheduling algorithms and timeline generation)

Disclaimer: This software is provided "as is" without warranty of any kind. Users are responsible for validating all calculations, timing estimates, and operational feasibility for their specific cruise requirements. Always consult with marine operations staff and verify all outputs before finalizing cruise plans.

📘 Full documentation available at:
👉 https://ocean-uhh.github.io/cruiseplan/

• ✅ Interactive station planning: Click-to-place stations on bathymetric maps with real-time depth feedback
• 📓 PANGAEA integration: Browse and incorporate past cruise data for context
• 📄 Multi-format outputs: Generate NetCDF, LaTeX reports, PNG maps, KML files, and CSV data
• 🔍 Cruise validation: Automated checking of cruise configurations and operational feasibility
• 🎨 Documentation: Sphinx-based docs with API references and usage guides
• 📦 Modern Python packaging: Complete with testing, linting, and CI/CD workflows
• 🧾 Scientific citation support: CITATION.cff for academic attribution

CruisePlan follows a modular architecture with clear separation of concerns:

• cruiseplan.config: Configuration schemas and validation (CruiseConfig, activities, ports)
• cruiseplan.runtime: Business logic and data processing (CruiseInstance, enrichment, validation)
• cruiseplan.timeline: Scheduling algorithms and timeline generation

CruisePlan provides both programmatic API and command-line interface:

import cruiseplan

# Notebook-friendly API
timeline, files = cruiseplan.schedule(config_file="cruise.yaml", format="html")

# Advanced usage
from cruiseplan.runtime.cruise import CruiseInstance
from cruiseplan.timeline.scheduler import generate_timeline

cruiseplan/
├── .github/workflows/          # CI/CD: tests, docs, PyPI publishing
├── docs/                       # Sphinx documentation (when available)
├── notebooks/                  # Example notebooks and demos
├── cruiseplan/                 # Main Python package
│   ├── api/                    # High-level API functions
│   ├── cli/                    # Command-line interface modules  
│   ├── config/                 # 🆕 Configuration schemas and validation
│   │   └── exceptions.py       # Custom exception classes
│   ├── runtime/                # 🆕 Business logic and data processing
│   ├── timeline/               # 🆕 Scheduling and timeline generation
│   ├── data/                   # Bathymetry and PANGAEA data handling
│   ├── interactive/            # Interactive station picking tools
│   ├── output/                 # Multi-format output generators
│   └── utils/                  # Utilities and coordinate handling
├── tests/                      # Comprehensive pytest test suite
│   ├── api/, cli/, core/       # Organized test modules
│   ├── fixtures/               # Test data and configurations
│   ├── integration/            # End-to-end workflow tests
│   └── unit/                   # Fast unit tests
├── data/                       # Sample bathymetry datasets
└── Configuration files...      # .gitignore, pyproject.toml, etc.

Key Improvements in v0.3.6:

• ✅ Clear module boundaries: Config → Runtime → Timeline data flow
• ✅ Better discoverability: Module names match main data types (CruiseConfig, CruiseInstance, CruiseSchedule)
• ✅ Hierarchical organization: Cruise → Leg → Cluster → Operations
• ✅ Pydantic validation: Type-safe configuration throughout

For general use, install the latest stable release from PyPI. Note: CruisePlan is in active development (0.x versions) with occasional breaking changes.

# Create virtual environment
python -m venv .venv
source .venv/bin/activate  # Windows: .venv\Scripts\activate

# Install CruisePlan
pip install cruiseplan

For the latest features and bug fixes:

# Create virtual environment
python -m venv .venv
source .venv/bin/activate  # Windows: .venv\Scripts\activate

# Install directly from GitHub
pip install git+https://github.com/ocean-uhh/cruiseplan.git

For development or contributing to CruisePlan:

# Clone the repository
git clone https://github.com/ocean-uhh/cruiseplan.git
cd cruiseplan

# Option A: Using conda/mamba
conda env create -f environment.yml
conda activate cruiseplan
pip install -e ".[dev]"

# Option B: Using pip with virtual environment
python -m venv .venv
source .venv/bin/activate  # Windows: .venv\Scripts\activate
pip install -e ".[dev]"

Dependencies: Core packages are listed in requirements.txt, development tools in requirements-dev.txt. The conda environment.yml loads from these files automatically.

To run tests:

pytest tests/

To build the documentation locally:

cd docs
make html

• Installation Guide
• Usage Guide
• API Reference
• Development Roadmap

Contributions are welcome! Please see our Contributing Guidelines for details on how to get started.

For information about planned improvements and development priorities, see our Development Roadmap.

The original timing algorithms were developed by Yves Sorge and Sunke Trace-Kleeberg. CruisePlan initial software development by Yves Sorge and redesigned by Eleanor Frajka-Williams.

If you use CruisePlan in your research, please cite it using the information in CITATION.cff.

The following cruise planning tools may also be of interest (Disclaimer: We have not tested these):

Python/GIS:

• cruisetools - Python plugin for QGIS.

Python:

• dreamcoat - Personal tools for cruise planning

R:

• cruisePlanning - R package for cruise planning based on DFO's AZMP
• cruisePlanningStatic - similar to the above
• cruisetrack-planner - Cruise track planning in R plus Shiny App (https://seaflow.shinyapps.io/cruisetrackplanner/)

MATLAB:

• PlanCampanha - Cruise planning with CSV as input