Schema

Impact Assessment

Type: Node


The emissions, resource uses, and environmental impacts created during the production of one unit of a Product from a Cycle. The functional unit is defined by the units of the product. If there are more than one Product in the Cycle, allocation is used to apportion these impacts across the Products.


Field Type Required Definition
name string No

The name of the Impact Assessment.

version string No

The version of the Impact Assessment.

versionDetails string No

A text description of the version of the Impact Assessment.

organisation Organisation No

A reference to the node describing the Organisation that produced the Product.

cycle Cycle No

A reference to the node describing the production Cycle.

endDate string Yes

The end date or year of production in ISO 8601 format (YYYY-MM-DD, YYYY-MM, or YYYY).

startDate string No

The start date of production in ISO 8601 format (YYYY-MM-DD, YYYY-MM, or YYYY).

site Site No

A reference to the node describing the Site where production occurred.

country Term Yes

The country name from the Glossary, following GADM naming conventions.

region Term No

The lowest level GADM region available following the naming convention used in the Glossary.

product Term Yes

A reference to the Term describing the Product produced during the production Cycle, which is the target of this Impact Assessment.

functionalUnitQuantity number Yes

The quantity of the product that this Impact Assessment is expressed per. The units are determined by the Term of the product (e.g., 1kg for Wheat, grain, or 1 head for a Pig).

Possible values are: 1

allocationMethod string Yes

The method used to allocate environmental impacts between Products.

Possible values are: economic,mass,energy,none,noneRequired,systemExpansion

source Source No

The Source for the data in the Impact Assessment. Not required (but reccomended) if dataPrivate = true.

emissionsResourceUse List[Indicator] No

A list of emissions and resource uses.

emissionsResourceUse cannot be duplicated. The following fields determine whether an Indicator is unique: term.@id,inputs.@id,operation.@id,methodModel.@id,transformation.@id

impacts List[Indicator] No

The mid-point environmental impact Indicators. These are calculated from emissions and resourceUse by applying characterisation factors to generate a characterised impact indicator.

impacts cannot be duplicated. The following fields determine whether an Indicator is unique: term.@id,methodModel.@id

endpoints List[Indicator] No

The end-point environmental impact Indicators. These are calculated from the mid-point impacts by applying characterisation factors to generate an end-point impact indicator.

endpoints cannot be duplicated. The following fields determine whether an Indicator is unique: term.@id,methodModel.@id

dataPrivate boolean Yes

If these data stored in this file are private.


Internal Properties

Field Type Definition
@context string The location of the JSON-LD context file.
@id string The unique ID assigned to the Node by Hestia.
@type string Impact Assessment
organic boolean

If the Cycle has an organic label. Used by the aggregation engine only.

irrigated boolean

If the Cycle was irrigated. Used by the aggregation engine only.

autoGenerated boolean

If this node was autogenerated during upload.

originalId string

The identifier for these data in the source database (e.g. if the data were converted from openLCA or ecoinvent, the id field from that database).

schemaVersion string

The version of the schema when these data were created.

added array[string]

A list of fields that have been added to the original dataset.

addedVersion array[string]

A list of versions of the model used to add these fields.

updated array[string]

A list of fields that have been updated on the original dataset.

updatedVersion array[string]

A list of versions of the model used to update these fields.

aggregated boolean

If this Cycle has been 'aggregated' using data from multiple Cycles.

aggregatedVersion string

A version of the aggregation engine corresponding to this Cycle.


JSON-LD Example 1