The Inputs, Emissions, Products, and Practices created or used during a period. A Cycle also includes a Completeness assessment, describing how complete the Inputs and Products data are, and Transformations, which allow Products to be transformed into new Products in the same Cycle. For animal production Cycles, the types of Animal present can also be specified. A Cycle occurs on a Site.
A description of the Cycle, including information that cannot be captured with other fields.
A description of the treatment administered by researchers to the experimental unit. E.g., a Site is divided into four and each part is 'treated' with a different fertiliser type to see which produces the most maize (Easton & McColl (1997)). Use the
Whether this treatment is representative of typical commercial practice. Required if
The start date of the Cycle in ISO 8601 format (YYYY-MM-DD, YYYY-MM, or YYYY). Use the
A definition of what the start date is. This is a required field if
Possible values are: harvest of previous crop, sowing date, transplanting date, soil preparation date, orchard or vineyard establishment date, first bearing year, stocking date, start of year
A reference to the Site describing the primary location where this Cycle occurred.
If the Cycle occurred on multiple Sites, a list of the other Sites.
The units that the
Possible values are: 1 ha, relative
Further information on the functional unit (e.g., 'one batch').
If data on multiple Cycles are aggregated and represented as a single Cycle, the number of Cycles. For example, Cycles occurred on the same site in multiple growing seasons might be represented as a single Cycle with standard deviations across Cycles.
In experimental studies, the number of replicates for the
In surveys, the sample weight for this Cycle relative to all other Cycles included in the Source.
For crops, the area harvested in hectares. Area harvested is the same as area under cultivation if the entire cultivated area is harvested, but less if crops fail or are not harvested for economic or other reasons.
The default classification of the method used to acquire or estimate all Input, Product, Practice, and Transport data in the Cycle. It can be overridden by specifying a
Possible values are: physical measurement, verified survey data, non-verified survey data, modelled, estimated with assumptions, consistent external sources, inconsistent external sources, expert opinion, unsourced assumption
A justification of the
The Practices used.
practices cannot be duplicated. The following fields determine whether a Practice is unique: term.@id, key.@id, dates, startDate, endDate, areaPercent, ownershipStatus
The types of Animal present.
animals cannot be duplicated. The following fields determine whether an Animal is unique: term.@id, properties.term.@id, properties.value
The Inputs used.
inputs cannot be duplicated. The following fields determine whether an Input is unique: term.@id, dates, startDate, endDate, isAnimalFeed, transport.@id, operation.@id, country.@id, impactAssessment.id, properties.term.@id, properties.value
The Products created.
products cannot be duplicated. The following fields determine whether a Product is unique: term.@id, dates, startDate, endDate, variety, fate
The Transformations applied to
transformations cannot be duplicated. The following fields determine whether a Transformation is unique: transformationId
The Emissions created.
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, transformation.@id
If these data are private. Private means that Hestia administrators can access these data and you can grant access to other platform users, but these data will not be made available to any other users of the platform or distributed to third parties.
Defaults to: False
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.
|@context||string||The location of the JSON-LD context file.|
|@id||string||The unique ID assigned to the Node by Hestia.|
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).
The version of the schema when these data were created.
A list of fields that have been added to the original dataset.
A list of versions of the model used to add these fields.
A list of fields that have been updated on the original dataset.
A list of versions of the model used to update these fields.
If this Cycle has been 'aggregated' using data from multiple Cycles.
A version of the aggregation engine corresponding to this Cycle.
A data quality score for aggregated data. Multiple points can be awarded for: no Emissions are missing from the system boundary; the aggregation is based on data from over fifty Cycles; the difference between FAOSTAT yield and the aggregated yield for the
The maximum value for the aggregated quality score.
Cycles used to aggregated this Cycle.
Sources used to aggregated this Cycle.
Date created on Hestia in ISO 8601 format (YYYY-MM-DD).
Last update date on Hestia in ISO 8601 format (YYYY-MM-DD).