oceanicospy
oceanicospy is an open-source, user-friendly Python library that serves as a framework for automating and standardizing the scientific workflow in numerical wave and hydrodynamic modelling at the coastal scale
Features
- Observations — read data from RBR, AQUAlogger, AWAC, CTD, weather stations, and more.
- Analysis — temporal and spectral techniques, including
WaveSpectralAnalyzerand tidal analysis. - Models — preprocessing automation for numerical models (SWAN, WW3, XBeach).
- Retrievals — automated downloads from ERA5, Copernicus Marine (CMEMS), and UHSLC real-time data.
- GIS — geospatial utilities for coastal data (shapefiles, XYZ grids, projections).
- Plots — quick, publication-ready visualizations of oceanographic variables.
- Utils — shared helper functions used across all subpackages.
Installation
oceanicospy is currently in beta. The pre-release flag is required to install the latest version.
Local environment
Create a Python environment (conda, venv, or similar) and install from PyPI:
pip install oceanicospy
Verify the installation:
pip show oceanicospy
Expected output:
Name: oceanicospy
Version: 0.1.0
Summary: Python library that serves as a framework for automating and standardizing the scientific workflow in numerical wave and hydrodynamic modelling at the coastal scale.
Home-page: https://github.com/oceanicos-dev-org/oceanicospy
Author:
Author-email: OCEANICOS developer team <oceanicos_med@unal.edu.co>
License: GNU GENERAL PUBLIC LICENSE
Google Colab
Install the latest stable version in a Colab notebook:
!pip install oceanicospy
A runtime restart may be required after installation due to dependency conflicts with Colab's pre-installed packages.
Package structure
oceanicospy/
├── analysis/ # temporal and spectral analysis (WaveSpectralAnalyzer, tidal analysis, …)
├── gis/ # geospatial utilities (shapefiles, XYZ data, projections)
├── models/ # numerical model preprocessing (SWAN, WW3, XBeach)
├── observations/ # instrument readers (RBR, AQUAlogger, AWAC, CTD, …)
├── plots/ # visualization utilities
├── retrievals/ # automated data retrieval (ERA5, CMEMS, UHSLC)
└── utils/ # shared helpers
Quick start
Import the full package:
import oceanicospy
Or import only what you need:
from oceanicospy.observations.pressure_sensors import RBR
from oceanicospy.analysis import WaveSpectralAnalyzer
Wildcard imports (
from oceanicospy.analysis import *) are convenient for exploration but can shadow names from other libraries. Prefer explicit imports in scripts.
Contributing
Contributions are welcome. The workflow follows the standard GitHub fork-and-pull-request model.
1. Fork the repository
Go to github.com/oceanicos-dev-org/oceanicospy and click Fork.
2. Set up SSH authentication
Follow the GitHub SSH guide if you haven't already.
3. Clone your fork
git clone git@github.com:YOUR-USERNAME/oceanicospy.git
cd oceanicospy
Optionally add the upstream remote to stay in sync:
git remote add upstream git@github.com:oceanicos-dev-org/oceanicospy.git
4. Install in editable mode
pip install -e .
Install optional dependency groups for documentation or development:
pip install -e ".[docs]" # sphinx, sphinx-book-theme, nbsphinx, myst-nb
pip install -e ".[dev]" # pytest, build, twine
5. Create a feature branch
Never commit directly to main or integration:
git checkout -b YOUR-USERNAME/my-feature
6. Commit and push
git add path/to/changed_file.py
git commit -m "add some particular feature to certain module"
git push origin YOUR-USERNAME/my-feature
7. Open a pull request
On GitHub, navigate to your fork and click Contribute → Open a pull request. Provide a clear title and description of what changed and why.
License
Distributed under the GNU General Public License v3 (GPLv3). See LICENSE for details.
Contact
OCEANICOS developer team — oceanicos_med@unal.edu.co
Metadata
Release files for oceanicospy 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| oceanicospy-0.1.0.tar.gz | 511.4 kB | Without provenance | Details for oceanicospy-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| oceanicospy-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for oceanicospy-0.1.0-py3-none-any.whl |
Total release size: 1.0 MB
Release files / oceanicospy-0.1.0.tar.gz
| Download URL | oceanicospy-0.1.0.tar.gz |
|---|---|
| Size | 511.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b5bbab48a9baafc989f787e50300bb33e737b4bf97f02c0e7d86d563e5190676
|
|
BLAKE2b-256 checksum How to use checksums |
27cfdb6b683df573ff150fdbf055926e0f9ef10b9a193db01e69bb20e1108fbb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.9
|
Release files / oceanicospy-0.1.0-py3-none-any.whl
| Download URL | oceanicospy-0.1.0-py3-none-any.whl |
|---|---|
| Size | 535.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e993304335eaa2433d5baa3ed6e45395e48523a2670b428ca8ac36bea279a4ab
|
|
BLAKE2b-256 checksum How to use checksums |
2863d2b98a825ab42eb66e58df59972023b872289f79faceac5e69b1b9b2742c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.9
|
Security for oceanicospy 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.