What is COMPASS?
COMPASS (formally the Infrastructure Continuous Ordinance Mapping for Planning and Siting Systems, or “INFRA-COMPASS”) is an innovative software tool that harnesses the power of Large Language Models (LLMs) to automate the compilation and continued maintenance of an inventory of state and local codes and ordinances pertaining to energy infrastructure.
At a high level, COMPASS does two things: it retrieves the right ordinance documents for each jurisdiction you ask about, and then extracts structured data from those documents into a versioned database that downstream users can query as a CSV, Excel workbook, or GeoPackage.
What makes COMPASS different from simply asking ChatGPT for ordinance data is the architecture around the LLM call:
Structured, downstream-ready output — consistent CSV rows with stable column names, units, and feature labels that drop straight into siting and capacity-modeling tools like reV, GIS workflows, or any pipeline that needs setbacks, height limits, and noise thresholds as numbers rather than prose.
Hallucination guardrails — cleaned text is checked against the source and dropped if it drifts too far, so fabricated values never reach the database.
Source-URL traceability — every record carries a URL back to the original ordinance document, so any value can be audited or spot-checked.
Cost control — cheap heuristic filters reject obviously irrelevant text before any LLM call runs, making it tractable to extract data across hundreds of jurisdictions.
Read more about the tool in the documentation, check out summaries of the validation results in the validation report, or explore the data on the COMPASS website.
Where is the extracted ordinance data?
The National Laboratories of the Rockies (NLR) typically runs the COMPASS pipeline annually and publishes refreshed datasets to OpenEI. The latest published ordinance datasets are available here:
Geothermal Electricity: https://data.openei.org/submissions/8817
Geothermal Heat Pumps: https://data.openei.org/submissions/8816
Installing COMPASS
The quickest way to install COMPASS for users is from PyPI:
pip install infra-compass
If you would like to install and run COMPASS from source, we recommend using pixi:
git clone git@github.com:NatLabRockies/COMPASS.git; cd COMPASS
pixi run compass
For detailed instructions and troubleshooting, see the installation documentation.
Quickstart
To run a quick COMPASS demo, set up a personal OpenAI API key and run:
pixi run openai-solar-demo <your API key>
This will run a full extraction pipeline for two counties using gpt-4o-mini (costs ~$0.45). For more information on configuring a COMPASS run, see the execution basics example.
Development
Please see the Development Guidelines if you wish to contribute code to this repository.
Metadata
Release files for INFRA-COMPASS 0.31.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 |
|---|---|---|---|---|
| infra_compass-0.31.0.tar.gz | 1.1 MB | With provenance | Details for infra_compass-0.31.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| infra_compass-0.31.0-py3-none-any.whl | Python 3 | none | any | Details for infra_compass-0.31.0-py3-none-any.whl |
Total release size: 2.3 MB
Release files / infra_compass-0.31.0.tar.gz
| Download URL | infra_compass-0.31.0.tar.gz |
|---|---|
| Size | 1.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d0e0213b4fd42326e6582902c687d792874940666d2cfce3a3a563092bcda485
|
|
BLAKE2b-256 checksum How to use checksums |
b2757130cdfb0a94dfa4574d8046db29af360e2ce90ce787fd34ec2e04ac1d6d
|
| 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 4, 2026.
Transparency logRelease files / infra_compass-0.31.0-py3-none-any.whl
| Download URL | infra_compass-0.31.0-py3-none-any.whl |
|---|---|
| Size | 1.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f5ffc893c0bf71f4d76cca16414b5326ddfbd5e06e99e05615213e383c783c6c
|
|
BLAKE2b-256 checksum How to use checksums |
8462179e8c58f8f476121866db95684d0e13594cff0bc640c4ae78d71fa8485f
|
| 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 4, 2026.
Transparency logSecurity for INFRA-COMPASS 0.31.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
Both files in this release have been uploaded with provenance metadata.
Attestation for infra_compass-0.31.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 4, 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.