Schema

Transformation

Type: Blank Node

View examples

The Transformation of one Product to a new Product in the same Cycle. This is useful for representing processes such as excreta management, grain drying, or crop grading. One Transformations can follow another and they can be linked using transformationId.

Field Type Required Definition
transformationId string Yes

An identifier for each Transformation which must be unique within the Cycle.
term Term Yes

A reference to the Term describing the process or operation for transforming the Product.

description string No

A description of the Transformation process or operation, including information not captured with other fields.

startDate string No

The start date of the Transformation if different from the start date of the Cycle in ISO 8601 format (YYYY-MM-DD, YYYY-MM, or YYYY).

endDate string No

The end date of the Transformation if different from the end date of the Cycle in ISO 8601 format (YYYY-MM-DD, YYYY-MM, or YYYY).

transformationDuration number No

The duration of the Transformation in days. Defaulting to cycleDuration when not provided.

previousTransformationId string No

The transformationId of the previous Transformation. This is used to link Transformations, so that a share of the products from the previous Transformation become the inputs of the current Transformation. If this field is not specified, the inputs of the Transformation come from the Cycle.

transformedShare number No

The share of Products from the Cycle or the previous Transformation that enter the current Transformation. This field is useful when the physical quantities of Products being transformed are unknown, but the share transformed is known. For example, if Excreta, dairy cattle (kg mass) is a Product of a Cycle, transformedShare = 50, and Excreta, dairy cattle (kg mass) is an Input into this Transformation, 50% of the excreta is an Input to this Transformation. If there are more than one Product being transformed, transformedShare applies equally to all Products.

site Site No

If the Cycle occurred on multiple Sites, the Site where this Transformation occurred. Use transformedShare to apportion the transformed Product across each Site.

inputs List[Input] No

The Inputs into the Transformation.

inputs cannot be duplicated. The following fields determine whether an Input is unique: term.@id, dates, startDate, endDate, fromCycle, transport.@id, operation.@id, country.@id, impactAssessment.id

emissions List[Emission] No

The Emissions created from the Transformation.

emissions cannot be duplicated. The following fields determine whether an Emission is unique: term.@id, dates, startDate, endDate, depth, inputs.@id, transport.@id, operation.@id

products List[Product] No

The Products created from the Transformation.

products cannot be duplicated. The following fields determine whether a Product is unique: term.@id, dates, startDate, endDate, variety, fate

practices List[Practice] No

The Practices used during the Transformation.

practices cannot be duplicated. The following fields determine whether a Practice is unique: term.@id, key.@id, dates, startDate, endDate, area, ownershipStatus

Internal Properties

The following properties are automatically set when data are uploaded to the Hestia platform. If they are included in a file which is uploaded, they will be overwritten.

Field Type Definition
@type string Transformation
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.

Example 1

Download