MacroTrace
MacroTrace is a Python library for collecting, storing, and analyzing macroeconomic time-series vintages. It is designed for research workflows where the revision history matters just as much as the latest published value.
Documentation: https://john-ramsey.github.io/macrotrace/
Instead of treating a series as a single final dataset, MacroTrace helps you work with the sequence of releases that were available in real time. This makes it easier to study data revisions, reproduce historical analyses, and compare what was known at different publication dates.
Features
- Fetch vintage-aware macroeconomic time series from FRED, ONS, the Philadelphia Fed's Real-Time Data Set (RTDSM), and historical World Development Indicators (WDI) editions
- Store releases locally in SQLite for reproducible, offline-friendly workflows
- Retrieve series as they were known on a specific date with
as_of(...) - Filter both vintage windows and data windows when loading a series
- Recover which release an undated block of data came from with
identify_vintage(...) - Export to pandas DataFrames or Series and Darts
TimeSeriesobjects - Plot vintages and revision comparisons with built-in Plotly tooling
Installation
Install the package from PyPI:
pip install macrotrace
Install the optional ONS Textual interface:
pip install "macrotrace[ons-tui]"
Requirements
- Python 3.11+
- A FRED API key for FRED-backed series
Set your FRED API key before loading FRED series:
export FRED_API_KEY="your_api_key_here"
Quick Start
from macrotrace import MTTimeSeries
payems = MTTimeSeries(
dataset_id="PAYEMS",
source="FRED",
)
print(payems)
july_2020 = payems.as_of("2020-07-15")
df = july_2020.to_dataframe()
MacroTrace stores fetched releases in a local SQLite database named MacroTrace.db, making repeated loads faster and keeping vintage histories available for later analysis.
For multi-dimensional datasets such as ONS releases, provide a series_key to select a specific slice of the dataset:
from macrotrace import MTTimeSeries
gdp = MTTimeSeries(
dataset_id="gdp-to-four-decimal-places",
source="ONS",
series_key={
"geography": "K02000001",
"unofficialstandardindustrialclassification": "A--T",
},
)
The Philadelphia Fed's Real-Time Data Set (RTDSM) needs no API key. Use the series mnemonic as the dataset_id and select the vintage frequency with the series_key:
from macrotrace import MTTimeSeries
routput = MTTimeSeries(
dataset_id="ROUTPUT",
source="RTDSM",
series_key={"frequency": "Q"},
)
See the RTDSM source guide for the full list of series and details on vintage frequencies.
Historical World Development Indicators editions are public and need no API key. Use a WDI indicator code and select one World Bank entity with the series_key:
from macrotrace import MTTimeSeries
gdp_per_capita = MTTimeSeries(
dataset_id="NY.GDP.PCAP.KD",
source="WDI",
series_key={"country": "USA"},
vintage_start_date="2014-04-01",
vintage_end_date="2014-07-31",
)
See the WDI archive guide for exact edition retrieval, month-precision semantics, bulk panels, and cache behavior.
Identifying an Unknown Vintage
If you have a block of observations with no release date attached — for example, a series lifted from a replication package — identify_vintage compares it against every stored vintage and reports which release(s) it is consistent with:
from macrotrace import MTTimeSeries
routput = MTTimeSeries(
dataset_id="ROUTPUT",
source="RTDSM",
series_key={"frequency": "Q"},
)
# `unknown` is a date-indexed pandas Series whose vintage you want to recover
match = routput.identify_vintage(unknown)
if match.is_ambiguous:
print(f"Ambiguous — consistent with {len(match.release_dates)} vintages")
elif match.matched:
print(f"Matches the {match.release_date.date()} vintage")
else:
print(f"No matching vintage found (failed on: {match.failure_reason})")
Command-Line Tools
MacroTrace includes command-line tools for exploring ONS datasets:
macrotrace ons explorer
If you installed the optional TUI extra, you can also run:
macrotrace ons tui
Development
For local development, we use uv for dependency management and environment execution.
Install the project with the development, docs, and optional TUI dependencies:
uv sync --extra ons-tui --group dev --group docs
Run tests inside the managed environment with:
uv run pytest
Code formatting is handled with black:
uv run black .
Project Status
MacroTrace is under active development as part of a PhD research project on macroeconomic data revisions.
License
MacroTrace is licensed under the GNU General Public License v3.0 or later (GPL-3.0-or-later).
Release files for macrotrace 0.4.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 | |
|---|---|---|---|
| macrotrace-0.4.0.tar.gz | 494.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| macrotrace-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 624.8 kB
Release files / macrotrace-0.4.0.tar.gz
| Download URL | macrotrace-0.4.0.tar.gz |
|---|---|
| Size | 494.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d848b4c3e3c6c897b5405679e6b8c2fc37227c849669e97908be8351f9a28faf
|
|
BLAKE2b-256 checksum How to use checksums |
8fac042e4fd749a42b41d3151a26e0b6dc3b499604d4cd8e113b3811728891c7
|
| 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 5, 2026.
Transparency logRelease files / macrotrace-0.4.0-py3-none-any.whl
| Download URL | macrotrace-0.4.0-py3-none-any.whl |
|---|---|
| Size | 130.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8d742d4e07f7f3cce16e1fc455ba8e24635a9e922434da60f758169f23596cde
|
|
BLAKE2b-256 checksum How to use checksums |
479bd40a087d4a6601141fd8719f86d4d0abc8614551898159cbac77cfa5a8a3
|
| 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 5, 2026.
Transparency log