Data
Compatibility and data
Volca is built to work with serious environmental datasets. Public demos and examples rely on data that can be shared legally, while many real workflows also involve licensed or private data.
In brief
- Public demos and examples use legally shareable datasets such as BAFU.
- Volca can also support licensed datasets such as Ecoinvent and Agribalyse.
- Compatibility matters most when gaps, mappings, and coverage are visible instead of hidden.
Public demo data
BAFU is a strong foundation for public demos, screenshots, walkthroughs, and examples because it is both shareable and credible.
Licensed and restricted data
Volca can work with important licensed datasets such as Ecoinvent and Agribalyse, while public examples stay grounded in datasets that can be shared openly.
Visible compatibility
Mapping visibility, characterization coverage, and explicit handling of gaps are part of what makes a workflow trustworthy.
What you can inspect
- which data was loaded successfully
- which mappings or references remain unresolved
- which method or conversion path was used
- which caveats still matter for interpretation
Why visible gaps matter
Compatibility is rarely all-or-nothing. Volca exposes gaps, ambiguity, and partial coverage so teams can judge what is trustworthy now and what still needs work.
Honest coverage
Volca does not pretend that every dataset, method, and mapping is complete everywhere. The useful part is knowing what is covered, what is partial, and where extra review is needed.