effis-client
Async Python client for the public services of EFFIS, the European Forest Fire Information System (Copernicus Emergency Management Service):
- burnt-area perimeters, from the WFS (
nrt.ba.poly); - the official Fire Weather Index chain (FWI, FFMC, DMC, DC, ISI, BUI) as raw float values from the WMS, sampled at any point.
No account and no API key: both services are public.
Why a library for two HTTP calls
Because the EFFIS endpoints are MapServer, not GeoServer, and every GeoServer habit fails differently — usually without an error:
| You try | What happens |
|---|---|
/gwis/ows |
the request hangs (use /gwis) |
a wrong typeName |
the connection closes mid-response, no 404 |
CQL_FILTER for dates |
silently ignored: you get every fire ever |
bbox + filter together |
the connection dies |
| camelCase WFS parameters | refused by MapServer's WFS 1.1.0 |
ecmwf007.fwi (the layer in the EFFIS docs) |
LayerNotDefined |
| any error | HTTP 200 with an XML body |
| FWI for a day past the forecast | HTTP 200 with a raster of zeros |
The last one is the dangerous one: an all-zero FWI raster reads as "no fire
danger anywhere" when it means "no data". This library returns None for
it. Each of these was found the hard way, and checked again against the live
service on 2 November 2026.
Install
pip install effis-client # perimeters
pip install "effis-client[raster]" # + FWI sampling (numpy, rasterio)
Use
The fetch functions take your httpx.AsyncClient, so timeouts, retries,
proxies and connection pooling stay yours. Network errors propagate; an
error disguised as a 200 raises EffisError.
import asyncio
from datetime import date
import httpx
from effis_client import fetch_fwi, fetch_perimeters
async def main() -> None:
async with httpx.AsyncClient(timeout=60) as client:
# Bounding boxes are (west, south, east, north), EPSG:4326.
perimeters = await fetch_perimeters(
client,
(16.5, 40.3, 16.8, 40.6),
start=date(2021, 1, 1),
end=date(2026, 12, 31),
)
print(len(perimeters.features), "fires since 2021")
fwi = await fetch_fwi(
client,
date(2026, 11, 1),
points=[(16.6, 40.6)], # (lon, lat)
bbox=(15.0, 39.5, 17.5, 41.5),
)
print(fwi) # {(16.6, 40.6): 10.34...} — or None if EFFIS has no data
asyncio.run(main())
Dates are filtered locally, because MapServer cannot filter them server
side; one bbox returns the whole history (an Italian region is a few hundred
perimeters, a few hundred KB). If the response hits max_features,
perimeters.truncated is True: shrink the bbox rather than trusting the
gap.
Bring your own HTTP
Everything the fetch functions do is also exposed as pure functions, for callers with their own HTTP layer:
from effis_client import WFS_URL, perimeters_params, parse_perimeters
from effis_client import WMS_URL, fwi_params, check_tiff, sample_fwi
Data licence
EFFIS data are © European Union, Copernicus Emergency Management Service, published under CC BY 4.0. Anything you publish from them must say so. The test fixtures are small EFFIS responses under the same licence.
Extracted from Limen,
which uses the perimeters as the truth set for its wildfire backtest and the
FWI rasters to check its own FWI chain
(fwi-chain).
Development
uv sync
make check
License
Code: Apache-2.0.
Metadata
Release files for effis-client 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 |
|---|---|---|---|---|
| effis_client-0.1.0.tar.gz | 12.3 kB | With provenance | Details for effis_client-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| effis_client-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for effis_client-0.1.0-py3-none-any.whl |
Total release size: 25.9 kB
Release files / effis_client-0.1.0.tar.gz
| Download URL | effis_client-0.1.0.tar.gz |
|---|---|
| Size | 12.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0a471170282b42e3eb986a7820e6faf38b8798ed925bbc0261de8bbe96d00b7c
|
|
BLAKE2b-256 checksum How to use checksums |
f3d0a0f7ae41177f7350151c454f6891f880b34582598cccabbdc31ca54a369a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 2, 2026.
Transparency logRelease files / effis_client-0.1.0-py3-none-any.whl
| Download URL | effis_client-0.1.0-py3-none-any.whl |
|---|---|
| Size | 13.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
55a966c3e36c9919535cb3a758620ebdcbbbe551550c3997fdc7fb71f08fc6a9
|
|
BLAKE2b-256 checksum How to use checksums |
f59a151807c616209ffb26c594ffda53dba98d70ab853419e91afb907ee446db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 2, 2026.
Transparency logSecurity for effis-client 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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for effis_client-0.1.0.tar.gz
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 Nov 2, 2026.
Transparency logA 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.