The historical and current management of a Site. Used to represent land use and land cover history, crop rotations, aquaculture rotations, and historical and future production practices. Each Management blank node must be unique, and the fields which determine uniqueness are defined in the management field of the Site.
| Field | Type | Required | Definition |
|---|---|---|---|
term | Term | Yes | A reference to the Term describing the Site Management. This field has additional validation rules when set:
|
description | string | No | A description of the Management. |
value | number|boolean | No | The value associated with the Management Term. |
distribution | array[number] | No | An array of up to 1000 random samples from the posterior distribution of |
sd | number | No | The standard deviation of |
min | number | No | The minimum of |
max | number | No | The maximum of |
statsDefinition | string | No | What the descriptive statistics ( Possible values are: |
observations | integer | No | The number of observations the descriptive statistics are calculated over. |
startDate | string | No | The start date of this Site Management in ISO 8601 format (YYYY-MM-DD, YYYY-MM, or YYYY). |
endDate | string | Yes | The end date of this Site Management in ISO 8601 format (YYYY-MM-DD, YYYY-MM, or YYYY). |
methodClassification | string | No | A classification of the method used to acquire or estimate the
Possible values are: This field has additional validation rules when set:
|
methodClassificationDescription | string | No | A justification of the |
model | Term | No | |
modelDescription | string | No | A free text field, describing the model used to estimate these data. |
source | Source | No | |
otherSources | List[Source] | No | A list of references to any other sources of these data. |
properties | List[Property] | No | A list of Properties which can be assigned to the Management Term.
properties
cannot be duplicated.
The following fields determine whether a
Property is unique:
|
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 |
|---|---|---|
@context | The location of the JSON-LD context file. | |
@id | The unique ID assigned to the Node by HESTIA. | |
@type | Management | |
percentile10th | number | The 10th percentile of |
percentile90th | number | The 90th percentile of |
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 | array[string] | A list of fields that have been 'aggregated' using data from multiple Sites. |
aggregatedVersion | array[string] | A list of versions of the aggregation engine corresponding to each aggregated field. |
Example 1
{
"@type": "Management",
"term": {
"@id": "animalManureUsed",
"@type": "Term",
"name": "Animal manure used",
"units": "boolean",
"termType": "landUseManagement"
},
"value": true,
"startDate": "2015",
"endDate": "2022"
}Example 2
{
"@type": "Management",
"term": {
"@id": "forest",
"@type": "Term",
"name": "Forest",
"termType": "landCover"
},
"value": 5.9,
"startDate": "1990-01-01",
"endDate": "1990-12-31"
}Example 3
{
"@type": "Management",
"term": {
"@id": "fullTillage",
"@type": "Term",
"name": "Full tillage",
"units": "% area",
"termType": "tillage"
},
"value": 42,
"startDate": "1990",
"endDate": "2005"
}