Database import · openLCA package
Import openLCA packages
Load an openLCA package as openLCA would compute it: amounts in each flow's reference unit, formulas evaluated, processes allocated by their own method, and inputs linked to a producer as openLCA links them by default.
What is openLCA package?
An openLCA package is the JSON-LD ZIP that openLCA and the LCA Collaboration Server export: one JSON document per process, flow, flow property, unit group, location, and parameter, linked by their identifiers, with openlca.json at its root.
Files VoLCA accepts
- A ZIP of schema version 2 or 3 with openlca.json at its root, as openLCA or the LCA Collaboration Server exports it.
VoLCA recognises the package from the openlca.json file at the root of the archive, and refuses a schema version it does not know rather than guessing.
What is imported
- processes, product, waste, and elementary flows, and locations
- amounts converted to each flow's reference unit, and formulas computed in openLCA's formula language, with global and process parameters
- physical, economic, and causal allocation, each process by its own default method
- default providers, and links to a producer as openLCA makes them where a line names none
Upload once, inspect through any VoLCA interface
The upload endpoint detects the database format, stages the source, and makes it available to load. The same imported database can then be used from the UI, HTTP API, Python client, CLI, or MCP endpoint.
CLI
Upload the local file
volca --config volca.toml database upload ./database-openlca.zip \
--name "my-database" The engine accepts ZIP, 7z, tar.gz, tar.xz, XML, CSV, and supported .xlsx database inputs, with the exact choice depending on the source format.
Python
Use the same upload endpoint
from volca import Client
client = Client("http://localhost:8080")
client.upload_database("database-openlca.zip", name="my-database") Replace the local URL with the address of your VoLCA server and provide credentials when required.
Interpretation boundaries
- Uncertainty distributions, data quality entries, social aspects, and costs are not read yet. The load counts them, so you can see what was left out.
- Where several processes produce an input and none is named as its provider, the load links one and names the tie, so you can check the choice.
- The package imports inventory data. An openLCA impact method is loaded separately, and its flow mapping still needs review.
Frequently asked questions
Does VoLCA compute the same inventories as openLCA?
That is the aim of the reader, and it was checked against openLCA itself. On USLCI and CORRIM packages written by VoLCA, openLCA computed the same inventory as VoLCA for every process. On a package exported by openLCA, a product with several suppliers can be linked differently, so a few processes may differ; the load names each such tie. Check the load notices for what was left out or chosen for you.
Other database import formats
Database import
ILCD
Import an ILCD process database from an archive containing processes, flows, flow properties, and unit groups.
Database import
EcoSpold 2
Import EcoSpold 2 .spold datasets for search, exchange inspection, supply-chain tracing, and LCA calculation.
Database import
EcoSpold 1
Import EcoSpold 1 XML datasets and inspect activities, exchanges, inventories, links, and calculation results.
Database import
SimaPro CSV
Import a SimaPro CSV database export for fast search, activity inspection, inventories, impacts, and automation.
Database import
Brightway Excel
Import a Brightway Excel .xlsx inventory workbook while preserving activities, exchanges, units, and database links.