Bright Sky
JSON API for DWD's open weather data.
The DWD (Deutscher Wetterdienst), as Germany's meteorological service, publishes a myriad of meteorological observations and calculations as part of their Open Data program.
Bright Sky is an open-source project aiming to make some of the more popular data — in particular weather observations from the DWD station network and weather forecasts from the MOSMIX model — available in a free, simple JSON API.
Looking for something specific?
I just want to retrieve some weather data
You can use the free public Bright Sky instance!
I want to run my own instance of Bright Sky
Check out the infrastructure repo!
I want to parse DWD weather files from the command line or in Python
The parsing core for Bright Sky is maintained in a separate package named
dwdparse, which has no dependencies
outside the standard library. If you find that's not quite serving your needs,
check out wetterdienst.
I want to contribute to Bright Sky's source code
Read on. :)
On Bright Sky's versioning
Starting from version 2.0, where we extracted the parsing core into a separate
package, Bright Sky is no longer
intended to be used as a Python library, but only as the service available at
brightsky.dev.
Consequentially, we adjust our version numbers from the perspective of that
service and its users – i.e., we will increase the major version number only
when we introduce backwards-incompatible (or otherwise very major) changes to
the actual JSON API interface, e.g. by changing URLs or parameters. This means
that increases of the minor version number may introduce
backwards-incompatible changes to the internals of the brightsky package,
including the database structure. If you use brightsky as a Python library,
please version-pin to a minor version, e.g. by putting brightsky==2.0.* in
your requirements.txt.
Quickstart
Running a full-fledged API instance
Note: These instructions are aimed at running a Bright Sky instance for development and testing. Check out our infrastructure repository if you want to set up a production-level API instance.
Just run docker-compose up and you should be good to go. This will set up a
PostgreSQL database (with persistent storage in .data), run a Redis server,
and start the Bright Sky worker and webserver. The worker periodically polls
the DWD Open Data Server for updates, parses them, and stores them in the
database. The webserver will be listening to API requests on port 5000.
Architecture
Bright Sky is a rather simple project consisting of four components:
-
The
brightskyworker, which leverages the logic contained in thebrightskyPython package to retrieve weather records from the DWD server, parse them, and store them in a database. It will periodically poll the DWD servers for new data. -
The
brightskywebserver (API), which serves as gate to our database and processes all queries for weather records coming from the outside world. -
A PostgreSQL database consisting of two relevant tables:
sourcescontains information on the locations for which we hold weather records, andweathercontains the history of actual meteorological measurements (or forecasts) for these locations.
The database structure can be set up by running the
migratecommand, which will simply apply all.sqlfiles found in themigrationsfolder. -
A Redis server, which is used as the backend of the worker's task queue.
Most of the tasks performed by the worker and webserver can also be performed
independently. Run docker-compose run --rm brightsky to get a list of
available commands.
Hacking
Constantly rebuilding the brightsky container while working on the code can
become cumbersome, and the default setting of parsing records dating all the
way back to 2010 will make your development database unnecessarily large. You
can set up a more lightweight development environment as follows:
-
Create a virtual environment and install our dependencies:
python -m virtualenv .venv && source .venv/bin/activate && pip install -r requirements.txt && pip install -e . -
Start a PostgreSQL container:
docker-compose run --rm -p 5432:5432 postgres -
Start a Redis container:
docker-compose run --rm -p 6379:6379 redis -
Point
brightskyto your containers, and configure a tighter date threshold for parsing DWD data, by adding the following.envfile:BRIGHTSKY_DATABASE_URL=postgres://postgres:pgpass@localhost BRIGHTSKY_BENCHMARK_DATABASE_URL=postgres://postgres:pgpass@localhost/benchmark BRIGHTSKY_REDIS_URL=redis://localhost BRIGHTSKY_MIN_DATE=2020-01-01
You should now be able to directly run brightsky commands via python -m brightsky, and changes to the source code should be effective immediately.
Tests
Large parts of our test suite run against a real Postgres database. By default,
these tests will be skipped. To enable them, make sure the
BRIGHTSKY_DATABASE_URL environment variable is set when calling pytest,
e.g. via:
BRIGHTSKY_DATABASE_URL=postgres://postgres:pgpass@localhost/brightsky_test pytest
Beware that adding this environment variable to your .env file will not work
as that file is not read by pytest. The database will be dropped and
recreated on every test run, so don't use your normal Bright Sky database. ;)
Acknowledgements
Bright Sky's development is boosted by the priceless guidance and support of the Open Knowledge Foundation's Prototype Fund program, and is generously funded by Germany's Federal Ministry of Education and Research. Obvious as it may be, it should be mentioned that none of this would be possible without the painstaking, never-ending effort of the Deutscher Wetterdienst.
1 maintainer
Metadata
1 maintainer
Release files for brightsky 2.2.10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| brightsky-2.2.10.tar.gz | 49.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| brightsky-2.2.10-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 90.7 kB
Release files / brightsky-2.2.10.tar.gz
| Download URL | brightsky-2.2.10.tar.gz |
|---|---|
| Size | 49.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
05a3ca3261c5808837bb171b90608922cc0197382553452951f8f7512c68bffd
|
|
BLAKE2b-256 checksum How to use checksums |
136fc1c1bdba8a501bb85b88a5f9e0399fae1c306915b64b5cf1e2e1c9f2dab8
|
| 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 2, 2026.
Transparency logRelease files / brightsky-2.2.10-py3-none-any.whl
| Download URL | brightsky-2.2.10-py3-none-any.whl |
|---|---|
| Size | 41.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
76dc6c1297eb1141d02cd9a07827bc5de06b01923da04ffce24f3065d4aa464a
|
|
BLAKE2b-256 checksum How to use checksums |
674309d7f387e7a049532eb39a34fd613ae8342bc2e61a14e5053036cd89e1e0
|
| 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 2, 2026.
Transparency log
