FERC XBRL Extractor
Overview
The Federal Energy Regulatory Commission (FERC) has moved to collecting and distributing data using XBRL. XBRL is primarily designed for financial reporting, and has been adopted by regulators in the US and other countries. Much of the tooling in the XBRL ecosystem is targeted towards filers, and rendering individual filings in a human readable way, but there is very little targeted towards accessing and analyzing large collections of filings.
The FERC XBRL Extractor is designed to provide that functionality for FERC XBRL data. The library can extract data from a set of XBRL filings, and write that data to SQLite or DuckDB databases whose structure is derived from an XBRL Taxonomy. While each XBRL instance contains a reference to a taxonomy, this tool requires a path to a single taxonomy that will be used to interpret all instances being processed. This means even if instances were created from different versions of a taxonomy, the provided taxonomy will be used when processing all of these instances, so the output database will have a consistent structure. For more information on the technical details of the XBRL extraction, see the docs.
Catalyst Cooperative is currently using this tool to extract and publish the following FERC data. These outputs are updatded at least annually, and typically quarterly.
FERC Form |
Taxonomy |
Raw Data |
SQLite |
DuckDB |
|---|---|---|---|---|
Usage
Installation
The package can be installed from PyPI or conda-forge using your package manager of choice:
From PyPI
pip install catalystcoop.ferc-xbrl-extractor
uv pip install catalystcoop.ferc-xbrl-extractorFrom conda-forge
conda install catalystcoop.ferc_xbrl_extractor
mamba install catalystcoop.ferc_xbrl_extractor
pixi install catalystcoop.ferc_xbrl_extractorInput Data
The FERC XBRL Extractor is generally intended to consume raw XBRL filings and taxonomy information from one of the archives Catalyst Cooperative has published on Zenodo. Each supported form has its own archive lineage, with new snapshots captured from FERC’s XBRL filing RSS feeds on a regular basis (see links in the table above). The tool also expects to receive a zipfile containing archived taxonomies.
The archived filings and taxonomies are both produced using the pudl-archiver. The extractor will parse all taxonomies in the archive, then use the taxonomy referenced in each filing while parsing it.
CLI
This tool can be used as a library, as it is in PUDL. There is also a CLI provided for interacting with XBRL data. The only required options for the CLI are a path to the filings to be extracted, and a path to the output database. The path to the filings must point to a zipfile of XBRL filings, or a directory of already-unzipped filings that still includes the rssfeed metadata file FERC’s archiving process bundles into the zip alongside the filings (useful for local debugging, where it’s convenient to edit filings directly rather than repackaging them into a zip after every change). Each filing’s publication time and taxonomy version are derived from that file, so a single bare filing with no rssfeed of its own isn’t supported. If the specified output database already exists, it will be overwritten.
xbrl_extract {path_to_filings} --sqlite-path {path_to_database}This repo contains a small selection of FERC Form 1 filings from 2021, along with an archive of taxonomies in the examples directory. To test the tool on these filings, use the command:
xbrl_extract examples/ferc1-2021-sample.zip \
--sqlite-path ./ferc1-2021-sample.sqlite \
--taxonomy examples/ferc1-xbrl-taxonomies.zipParsing XBRL filings can be a time consuming and CPU heavy task, so this tool implements some basic multiprocessing to speed this up. It uses a process pool to do this. There are two options for configuring the process pool, --batch-size and --workers. The batch size configures how many filings will be processed by each child process at a time, and workers specifies how many child processes to create in the pool. It may take some experimentation to get these options optimally configured. The following command will use 5 worker processes to process batches of 50 filings at a time. It will also output both SQLite and DuckDB.
xbrl_extract examples/ferc1-2021-sample.zip \
--sqlite-path ferc1-2021-sample.sqlite \
--duckdb-path ferc1-2021-sample.duckdb \
--taxonomy examples/ferc1-xbrl-taxonomies.zip \
--workers 5 \
--batch-size 50You can also pass the --metadata-path option, which writes extensive taxonomy metadata to a json file, grouped by table name. See the ferc_xbrl_extractor.arelle_interface module for more info on the extracted metadata.
xbrl_extract examples/ferc1-2021-sample.zip \
--sqlite-path /ferc1-2021-sample.sqlite \
--taxonomy examples/ferc1-xbrl-taxonomies.zip \
--metadata-path metadata.jsonContributing / Development
This project uses uv for dependency management and Hatch for environment and task management. It also includes several git pre-commit hooks that help enforce standard coding practices. To set up the environment for development first ensure you have uv installed and then:
# Clone the repository to your local machine
git clone https://github.com/catalyst-cooperative/ferc-xbrl-extractor.git
cd ferc-xbrl-extractor
# Create the development environment with hatch
uv tool install hatch
hatch env create
# Install the pre-commit hooks, run via prek (https://prek.j178.dev/)
hatch run prek installAll available development environments and commands can be shown with:
hatch env showSome of the available commands:
# Run all tests and collect coverage
hatch run test:all
# Run only unit tests
hatch run test:unit
# Run only integration tests
hatch run test:integration
# Run linters and formatters
hatch run lint:all
# Check code without modifying
hatch run lint:check
# Format code
hatch run lint:format
# Type check with pyrefly
hatch run types:check
# Check type annotation coverage stays at or above 95%
hatch run types:coverage-check
# Print a human-readable type coverage report, module by module
hatch run types:coverage-report
# Build documentation
hatch run docs:build
# Check documentation formatting
hatch run docs:checkCode style is enforced using ruff, and type checked using pyrefly, both configured in pyproject.toml.
Type annotations are encouraged but not required everywhere – this is a gradually typed codebase, not a strictly typed one. Annotating a function or variable is optional, but whatever annotations are present must be internally consistent, or pyrefly check will fail; it’s a blocking check in both pre-commit and CI, along with a floor of 95% type annotation coverage across src/, enforced by pyrefly coverage check.
PUDL Sustainers
This package is part of the Public Utility Data Liberation (PUDL) project.
The PUDL Sustainers provide ongoing financial support to ensure the open data keeps flowing, and the project is sustainable long term. They’re also involved in our quarterly planning process. To learn more see the PUDL Project on Open Collective.
3 maintainers
Release files for catalystcoop.ferc-xbrl-extractor 1.11.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| catalystcoop_ferc_xbrl_extractor-1.11.1.tar.gz | 30.4 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| catalystcoop_ferc_xbrl_extractor-1.11.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.4 MB
Release files / catalystcoop_ferc_xbrl_extractor-1.11.1.tar.gz
| Download URL | catalystcoop_ferc_xbrl_extractor-1.11.1.tar.gz |
|---|---|
| Size | 30.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1bd72a7ad31021daf54f29cca23373e5d3ff43fb6fffc32f17d2d55c3c04821c
|
|
BLAKE2b-256 checksum How to use checksums |
aade06f28c83d576a3e1aa8ef81289ff2b6b1ba59e8199dc50d6ea8080e5a8e6
|
| 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 19, 2026.
Transparency logRelease files / catalystcoop_ferc_xbrl_extractor-1.11.1-py3-none-any.whl
| Download URL | catalystcoop_ferc_xbrl_extractor-1.11.1-py3-none-any.whl |
|---|---|
| Size | 36.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
63f82b8faacd82f5e173c6aceb4315b9fec73aca9468248d1c0819c7d1bee898
|
|
BLAKE2b-256 checksum How to use checksums |
e5bc5849ab21711d567b0a8033fb994f4314aa00610cf8fdc7a4de7e6d62655d
|
| 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 19, 2026.
Transparency log
