Agribalyse import
Load an Agribalyse SimaPro CSV
Start from an Agribalyse 3.2 SimaPro CSV export, make it visible in Volca, then inspect the resulting activities, exchanges, inventories, and impact views.
From file upload to a usable database
A database import is only useful if the result can be opened, searched, and checked. Volca turns a SimaPro CSV export into an inspectable workspace where activities, direct exchanges, inventories, and impact views remain close at hand.
Use this workflow when you have an Agribalyse export and want to move beyond the archive file: load the database, open a concrete activity, and follow the data from source records to calculated views.
What this workflow shows
- Volca exposes a database upload path for SimaPro CSV exports.
- Agribalyse 3.2 can be represented as a Volca database for browsing and inspection.
- The useful result continues past upload into concrete activity and exchange views.
Good fit for
- LCA practitioners with SimaPro-exported databases.
- Teams checking whether Volca can make a dataset easier to inspect.
- Workflows that combine Agribalyse metadata, transformed ingredients, and Python access.
Boundary
Database import and impact-method compatibility are separate questions. This page focuses on getting the Agribalyse database into an inspectable Volca workflow. Impact calculations require a compatible method setup, such as the adapted EF 3.1 context used in other Agribalyse examples.
Walkthrough
1. Start with the SimaPro CSV export
Prepare the Agribalyse 3.2 upload
Volca's database upload form accepts EcoSpold v1/v2 and SimaPro CSV files. In this walkthrough, the source artifact is an Agribalyse 3.2 SimaPro CSV export packaged as AGB32_final.CSV.zip.
Name the database, describe the source, and upload the SimaPro CSV archive. Once loaded, the same database can be searched and inspected through the normal Volca views.
2. Open the imported database
Open an activity and inspect direct upstream exchanges
The useful test is whether the resulting database supports everyday inspection: search an activity, open it, and inspect direct upstream exchanges from the database record.
This Agribalyse 3.2 capture shows the kind of inspection state the upload workflow should lead to.
3. Continue from source records to computed views
Inspect the life-cycle inventory after loading the database
Once the database is loaded, Volca can move from the source activity record to broader analysis views such as the full inventory for a selected reference flow.
This is the difference between storing an uploaded file and using the imported database as an inspectable working environment.
