MIKE IO: input/output of MIKE files in Python
Read, write and manipulate dfs0, dfs1, dfs2, dfs3, dfsu and mesh files.
MIKE IO facilitates common data processing workflows for MIKE files using Python.
Requirements
- Windows or Linux operating system
- Python x64 3.12 - 3.14
- (Windows) VC++ redistributables (already installed if you have MIKE)
Installation
pip install mikeio
:warning: Don't use conda to install MIKE IO! The version on conda-forge is several major versions behind.
Getting started
Read a file into a Dataset — a collection of named DataArrays sharing time and geometry:
>>> import mikeio
>>> ds = mikeio.read("HD2D.dfsu")
>>> ds
<mikeio.Dataset>
title: Output 1
dims: (time:9, element:884)
time: 1985-08-06 07:00:00 - 1985-08-07 03:00:00 (9 records)
geometry: Dfsu2D (884 elements, 529 nodes)
items:
0: Surface elevation <Surface Elevation> (meter)
1: U velocity <u velocity component> (meter per sec)
2: V velocity <v velocity component> (meter per sec)
3: Current speed <Current Speed> (meter per sec)
Select an item and extract a time series at a point:
>>> da = ds["Surface elevation"]
>>> da.sel(x=606200, y=6905480)
<mikeio.DataArray>
name: Surface elevation
dims: (time:9)
time: 1985-08-06 07:00:00 - 1985-08-07 03:00:00 (9 records)
geometry: GeometryPoint2D(x=606202.7806372638, y=6905474.639383219)
values: [0.4595, 0.807, ..., -0.6322]
Convert to pandas, or write the result back to a dfs file:
>>> df = mikeio.read("da_diagnostic.dfs0").to_dataframe()
>>> ds.to_dfs("output.dfsu")
See the user guide for more.
Where can I get help?
- Documentation - https://dhi.github.io/mikeio/
- General help, new ideas and feature requests - GitHub Discussions
- Bugs - GitHub Issues
- Course material: Getting started with Dfs files in Python using MIKE IO
Testing
MIKE IO is tested extensively, with an overall statement coverage of ~95%. The test suite runs on every pull request against Python 3.12 and 3.14, and on a schedule on both Linux and Windows.
uv run pytest --cov=mikeio
Contributing
Contributions are welcome — see CONTRIBUTING.md. Key architectural decisions are documented as ADRs.
License
1 maintainer
Release files for mikeio 3.3.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 | |
|---|---|---|---|
| mikeio-3.3.0.tar.gz | 133.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mikeio-3.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 296.9 kB
Release files / mikeio-3.3.0.tar.gz
| Download URL | mikeio-3.3.0.tar.gz |
|---|---|
| Size | 133.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9563a38e4f3f36f922a808703bce5ddeace067ff875f5889c2a611806ccb485f
|
|
BLAKE2b-256 checksum How to use checksums |
f0b68a5183c96653c1bcec1201ddc87ce2995ec8bc0b9cccd03f7f6da1e82ddb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 10, 2026.
Transparency logRelease files / mikeio-3.3.0-py3-none-any.whl
| Download URL | mikeio-3.3.0-py3-none-any.whl |
|---|---|
| Size | 163.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bbc18eb623bf3d7e50d9d930e58d1434123686ce01fac0d183df81ac211a8139
|
|
BLAKE2b-256 checksum How to use checksums |
cdf1f839277dcb3472a69c0780c3e0097a20eed2fbd1b2c5c079b784faaddc24
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 10, 2026.
Transparency log
