liander-open-data
A lightweight SQLite database and Python API for the Liander open data SBI load profiles: 15-minute electricity profiles per SBI code (Dutch Standard Industrial Classification), together with Liander's dictionary of the recommended profile per SBI code.
- One portable
.dbfile holding all profiles and the SBI dictionary, which any SQLite tool can open. - A small Python API that returns
pandasDataFrames. - A
liander-open-datacommand line tool. - The SBI dictionary (1,427 codes) ships with the package and works without any download.
Installation
pip install liander-open-data
# optional extras: read the original .xlsx dictionary / export Parquet
pip install "liander-open-data[excel,parquet]"
Quick start
The profile CSVs (<SBI code>.csv, ~1.2 GB) are not bundled. Download them
from Liander and build the database once:
liander-open-data build data/Profiles -o liander_profiles.db
Then query it from Python:
from liander_open_data import ProfileDatabase
with ProfileDatabase("liander_profiles.db") as db:
db.lookup("8411") # dictionary entry for an SBI code
df = db.get_profile("8411", columns=["mean", "p90"])
rec = db.recommended_profile("84111") # Liander's recommended profile
wide = db.get_profiles(["01", "8411"], column="mean", start="2023-06-01")
Or from the command line:
liander-open-data lookup 8411
liander-open-data search onderwijs --with-profile
liander-open-data export 8411 -o 8411.csv --columns mean p90
Or with plain SQL:
SELECT code, AVG(mean) AS avg_load
FROM profile_timeseries
WHERE timestamp BETWEEN '2023-07-01' AND '2023-08-01'
GROUP BY code ORDER BY avg_load DESC;
Documentation
Full documentation, covering the data model, CLI reference, API reference and
the release guide, is in the docs/ folder. To browse it as a
website locally, run uv run mkdocs serve.
Development
uv sync --all-groups
uv run pytest
uv run mkdocs serve # live documentation preview
Data and license
The code is released under the MIT license. The profiles and SBI dictionary are published by Liander N.V. as open data; check Liander's terms before redistributing them.
Metadata
Release files for liander-open-data 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 | |
|---|---|---|---|
| liander_open_data-0.1.0.tar.gz | 52.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| liander_open_data-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 95.5 kB
Release files / liander_open_data-0.1.0.tar.gz
| Download URL | liander_open_data-0.1.0.tar.gz |
|---|---|
| Size | 52.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c476d69066e0e059bb860ed7ffed2000a8753fcf9546dc3ebb094567691ea2ed
|
|
BLAKE2b-256 checksum How to use checksums |
6a693142ce0a72392f0cdf48f180a51eb94119ee49c96ae90eafa75d8f85f6d2
|
| 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 Oct 10, 2026.
Transparency logRelease files / liander_open_data-0.1.0-py3-none-any.whl
| Download URL | liander_open_data-0.1.0-py3-none-any.whl |
|---|---|
| Size | 42.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
876e3805ecace7169899f20811a3be6087b00f9b0285920d31d52cc05cda91b7
|
|
BLAKE2b-256 checksum How to use checksums |
eae8441f58cd8b043ad3e6985a9ef93b7d4b135d9b03dfec802a055b64d03067
|
| 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 Oct 10, 2026.
Transparency log