olca_ref_data

supplies an Antelope archive that contains the ref data.

OlcaRefQuantityImplementation

Bases: BasicImplementation, QuantityInterface

factors(quantity, flowable=None, context=None, **kwargs)

always retrieving these from file when asked allows the files to be updated but maybe it would be smrter just to add them locally what would be smrtest would be to just store them in a dumb rdbms instead of from file. but think of the immediate use case. that is all for qdb

Parameters:

Name	Type	Description	Default
quantity			required
flowable			None
context			None
kwargs			{}

Returns:

Type	Description
	generate Characterization objects

OpenLcaRefData

Bases: BasicArchive

Modern OLCA data format should be easy to use. We are ignoring their unit conversions (which, fair, should be incorporated) ... categories is gone ... and they hve no flow properties to speak of (that I can find) so we simply do what we did below, adapted to the simpler data format.

first flow properties then we replicate the meta-quantities load sequence from json-LD and we do on-demand CF synthesis via a custom Quantity implementation and we're done

factors_to_csv(quantity, filepath)

Utility to output processed CFs to a file for easy analysis, debug unit conversions, duplicate CFs, etc

Parameters:

Name	Type	Description	Default
quantity			required
filepath			required

Returns:

Type	Description