Schema

Cycle

Type: Node


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. A Cycle occurs on a Site.


Field Type Required Definition
description string No

A description of the Cycle, including information that cannot be captured with other fields.

treatment string No

The treatment.

site Site Yes

A reference to the Site describing the primary location where this Cycle occurred.

otherSites List[Site] No

If the Cycle occurred on multiple Sites, a list of the other Sites.

siteDuration number No

The duration on the primary site in days. For a single Site, this is equal to cycleDuration.

otherSitesDuration array[number] No

If a Cycle occurs on multiple Sites, a corresponding array to otherSites representing the number of days on each Site.

defaultSource Source Yes

The default Source for all data in the Cycle.

endDate string Yes

The end date or year of the Cycle in ISO 8601 format (YYYY-MM-DD, YYYY-MM, or YYYY). If startDate is specified to month or day precision, endDate should be too. For crops, endDate is always the harvest date. For continually harvested crops, it should be the end of the year.

startDate string No

The start date of the Cycle in ISO 8601 format (YYYY-MM-DD, YYYY-MM, or YYYY). Use the startDateDefinition field to define what this represents. For consistency with FAOSTAT, this should ideally be the date of harvest of the previous crop (a fallow period of greater than a year but less than five years is counted as a crop). However other start dates can be specified, such as the sowing date or soil preparation date. For continually harvested crops it should be the start of the year.

startDateDefinition string No

A definition of what the start date is. This is a required field if startDate is provided.

Possible values are: harvest of previous crop,sowing date,soil preparation date,stocking date,start of year

cycleDuration number No

The duration of the Cycle in days. Calculated from startDate and endDate if provided.

Defaults to: 365

functionalUnit string Yes

The units that the inputs, emissions, products, and transformations are expressed 'per'. Can either be: '1 ha' (one hectare) or 'relative' (meaning that the quantities of Inputs and Emissions correspond to the quantities of Products). For cropland or permanent pasture, the functional unit can only be '1 ha'.

Possible values are: 1 ha,relative

functionalUnitDetails string No

Further information on the functional unit (e.g. 'one batch').

numberOfCycles integer No

If data on multiple Cycles are aggregated and represented as a single Cycle, the number of Cycles. For example, multiple treatments might be represented as a single Cycle with standard deviations across treatments.

dataCompleteness Completeness Yes

A specification of how complete the Inputs and Products data are. If an area of activity data is marked as complete, then the associated Inputs and Products represent a complete description of the Cycle.

inputs List[Input] No

The Inputs used.

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

emissions List[Emission] No

The Emissions created.

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

products List[Product] No

The Products created.

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

practices List[Practice] No

The Practices used.

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

transformations List[Transformation] No

The Transformations applied to products generated from this Cycle.

dataPrivate boolean Yes

If these data 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 Cycle
name string

An automatically generated name for the Cycle composed of: primary product name, "-", site.region "," site.country, "-", endDate, "-", treatment and/or description.

dataDescription string

An automatically generated description of the data in the Cycle and Site, based on Emissions, Inputs, Products, and Site Measurements.

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