pyromap.md

Pyromap

:maxdepth: 2
:hidden:

Contracts <pyromap-contracts>
Runbooks <pyromap-runbooks>

Pyromap publishes camera coverage data as a privacy-aware GeoJSON artifact for map consumers.

It is split by package responsibility:

• sources defines the reusable Pyronear API dlt source.
• pyromap.ingestion runs dlt ingestion for backend camera records.
• the transformation layer reads typed records, aggregates H3 cells, and applies privacy rules outside dlt.
• publishers write the stable camera-cells.geojson artifact locally or to S3-compatible storage.
• pyromap.orchestration wraps the publication path in a Prefect flow for local orchestration runs.

Use local sample data for development and tests. In the CLI this is called --source fixture; it reads synthetic camera records directly and bypasses dlt because the input is local demo data, not a production source.

Use API mode for production publication. It runs backend camera ingestion through dlt, reads the ingested rows, transforms them into public cells, and publishes the artifact.

Use pyro-analytics pyromap orchestrate when the publication should run through Prefect locally. The orchestrated path calls the same synchronous publication function as the direct publish command. It does not duplicate ingestion, transformation, privacy, or publisher behavior.

For stable output behavior, see Contracts. For operator-facing publishing steps, see Runbooks.