ecosemantic-databases
The sources a background database installs from, each read from its own release files and written as an openLCA JSON-LD bundle the core installs: the ecoinvent builder with its release profiles, the USLCI source, the BAFU source, and the reader for an openLCA .zolca database.
Names it publishes
ecosemantic.databases.ecoinvent— the builder: a release's EcoSpold2 datasets, its MasterData and its LCIA implementation, read and nothing else; no Brightway, no bw2io. It downloads the release, probes what it holds against what a build reads, writes one openLCA JSON-LD bundle, and validates the bundle against ecoinvent's published results.releases/beside it holds one profile per validated release: file hashes, workbook layouts, the decisions the probe asked for, and the measured validation numbers.ecosemantic.databases.uslci— the USLCI source: the release the profile pins, downloaded from the Federal LCA Commons throughlca-data-interface, with its profile, its two lists and its notices.ecosemantic.databases.bafu— the BAFU source: the release the profile pins, read through an openLCA Nexus session, with its profile and the terms an install accepts.ecosemantic.databases.zolca— the reader for an openLCA.zolcadatabase.ecosemantic.databases.profiles,lists,checksandscores— the profiles a source pins, the lists a release is filed under, the checks a bundle passes and the scores it is validated against.- The
ecosemantic-databasescommand, over thebafu,ecoinventanduslcigroups.
The command
ecosemantic-databases runs one step of an ecoinvent build on its own, for a person who wants the files; setup ecoinvent runs the same steps and installs what they build.
ecosemantic-databases ecoinvent download 3.12 --system-model cutoff
ecosemantic-databases ecoinvent probe 3.12 --system-model cutoff
ecosemantic-databases ecoinvent build 3.12 --system-model cutoff --out builds
ecosemantic-databases ecoinvent validate 3.12 --system-model cutoff --bundle builds/ecoinvent-3.12-cutoff.zip
download fetches the release's five files and prints each path with the SHA-256 of every file a build reads; probe lists what the release holds against what a build reads and the gaps between them; build writes <dir>/ecoinvent-<version>-<model>.zip; validate compiles the bundle for the engine and compares its scores with the matrix export and the cumulative LCIA workbook. build and validate read releases/<version>-<model>.yaml when the release has one, and take the default layout with --no-profile. uslci and bafu take the same four steps over their own releases.
What it depends on
ecosemantic-engine and ecosemantic-core at the same version; lca-data-interface for the openLCA Nexus and Federal LCA Commons clients; and pydantic, olca-schema, pyyaml, numpy and scipy. The ecoinvent extra adds ecoinvent_interface and python-calamine.
Credentials
ecoinvent_interface reads EI_USERNAME and EI_PASSWORD from the environment, and a download refuses with Unavailable when either is absent. The BAFU source reads NEXUS_USERNAME and NEXUS_PASSWORD, and NEXUS_TOKEN for an account with a second factor.
Where the files live
Downloaded releases stay in ecoinvent_interface's cache, ~/.local/share/EcoinventInterface/cache, and built bundles go to the directory build takes. Neither is tracked. releases/<version>-<model>.yaml holds one profile per validated release, and no release data enters this distribution.
Installing it
pip install ecosemantic installs this distribution with the other five, its ecoinvent extra included, and the ecosemantic command. pip install "ecosemantic-databases[ecoinvent]" installs the builder alone, with the dependencies an ecoinvent build needs.
Licence
PolyForm Noncommercial License 1.0.0, copyright Carlos Gaete-Morales: LICENSE and NOTICE in this distribution. Any noncommercial purpose is permitted, by individuals and by charities, schools, public research and government bodies; commercial use needs a separate licence from him (cdgaete@gmail.com). EcoSemantic is his trademark, and the licence grants no right to use that name (TRADEMARK.md in the repository). This distribution handles licensed data and credentials and carries no release data. The code is published from https://github.com/cdgaete/ecosemantic.
Metadata
Release files for ecosemantic-databases 0.1.14
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 |
|---|---|---|---|---|
| ecosemantic_databases-0.1.14.tar.gz | 458.7 kB | Without provenance | Details for ecosemantic_databases-0.1.14.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ecosemantic_databases-0.1.14-py3-none-any.whl | Python 3 | none | any | Details for ecosemantic_databases-0.1.14-py3-none-any.whl |
Total release size: 951.0 kB
Release files / ecosemantic_databases-0.1.14.tar.gz
| Download URL | ecosemantic_databases-0.1.14.tar.gz |
|---|---|
| Size | 458.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
309d82ea99a019454db6ebf43be07c974f92e99aa45c1e034703f200e5357d08
|
|
BLAKE2b-256 checksum How to use checksums |
76939419877855104b50342ec6e319b88c00b1bc3ed55e88b3da8c4da36bb1ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Release files / ecosemantic_databases-0.1.14-py3-none-any.whl
| Download URL | ecosemantic_databases-0.1.14-py3-none-any.whl |
|---|---|
| Size | 492.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c98c896fa27f4d1415f80d04189e19c0aff350caca3f494aadcb3aefe94469d5
|
|
BLAKE2b-256 checksum How to use checksums |
df41ed45e3b28282a082f6cde17482c04412f3874bb81fe0d2c096d344b4ac7c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for ecosemantic-databases 0.1.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.