Here is the list of validations running on a Impact Assessment.
Adding an Impact Assessment without a Cycle, and no emissionsResourceUse or impacts or endpoints, is not allowed. You must set at least one of these fields, as otherwise the Impact Assessment will remain empty.
When linking an Impact Assessment with a Cycle, the product must refer to a Product of the Cycle. Plase make sure to set the exact same field on both the Impact Assessment and Cycle product.
This validation will ensure the Impact Assessment endDate is the same as the linked Cycle, when provided.
This validation ensures two things:
endDate must be later than startDate;endDate must be the same as startDate.This validation is to ensure that the startDate and endDate formats match, for any blank node.
This validation ensures that the number of items in value and dates are identical.
For any blank node, if the value is not between the min and max fields, an error will be given.
For any blank node, if the max is not greater than the min field, an error will be given.
For some Terms, HESTIA has defined some minimum and maximum value. If the specified value does not fall within these, an error is raised.
This validation checks if the property value provided is consistent with the value stored in a lookup table. For example, we can use the lookup region-liveAnimal-liveweightPerHead.csv file to determine if the liveweightPerHead value provided is within 75% of the high value contained in the lookup, for the country.
This validation gives a warning when 2 identical nodes, with different id value`, are detected.
For all Terms that are in percentages, the value must be between 0 and 100.
Some Terms are part of a group from the lookup sumIs100Group, meaning when summed up, their total value must be exactly 100% (with a 5% tolerance).
For all Terms that are set as percentages, the value must be provided.
Using the lookup "valueType", this validation will make sure the provided value is of the correct type. Example: a Term that should be either True or False will only accept True/False value.
Using the lookup recommendedPropertyTermIds on a blank node term, this validation will suggest the user to add any missing Property. These properties are necessary to run the models, and should be specified to prevent HESTIA from using default properties.
When using the region field, it must point to GADM Terms that are not countries. This can be identified with the gadmLevel field: it must be > 0 to be a region.
When using both country and region, the region must be within the country specified.
When using the country field, it must point to GADM Terms that are countries. This can be identified with the gadmLevel field: it must be == 0 to be a country.
When providing longitude and latitude, the coordinates must fall within the region or country provided.
HESTIA will calculate the boundary area during upload, and this validation will show a warning when the area does not match. Please verify that the area provided is correct and in the correct unit.
HESTIA will only gap-fill data from Geospatial datasets when the site area is less than 5000km2. If you see this warning, it means the calculation will be incomplete, and the measurements will need to be manually provided. Please provide a smaller polygon instead.
HESTIA will only gap-fill data from Geospatial datasets when the site area is less than 5000km2. If you see this warning, it means the calculation will be incomplete, and the measurements will need to be manually provided. Please provide a smaller region/country instead.
This validation returns warnings when fields are added without a value (or using 'no data' for example).
When adding a Source to a Cycle or an ImpactAssessment, this validation ensures that the same level of privacy is used on both.
Example:
dataPrivate=true, the Source it is linked to must also be dataPrivate=true;dataPrivate=false, the Source it is linked to must also be dataPrivate=false.It is recommended to always link a Cycle, Site, or ImpactAssessment, to a Source, even when private.
This validation will use the models library to recalculate the value of a blank node, and will give an error when the value too different from the models value. Note: the default tolerance is 5%, but we use the lookup valueToleranceToHestiaRecalculatedValue when available.
Some of the terms in the Glossary have been added with different units, e.g., kg / kg N / kg VS. This validation returns a warning when those terms have been used together in the same Node.
The "Other model" Term has been added in the eventuality that HESTIA has not added the required model yet. However, to use this Term, the methodModelDescription must be set.
When uploading Cycle, Site, etc., the referenced nodes must also be uploaded. Example:
The model emissionNotRelevant is reserved for the model emissionNotRelevant. This validation will therefore raise a warning when it is being used, and the methodModel should be replaced.
The methodTier not relevant is reserved for the model emissionNotRelevant. This validation will therefore raise a warning when it is being used, and the methodTier should be replaced.
Only specific emissions can use the methodTier=background. For all emissions that are not allowed to use it, this validation will throw an error, and another methodTier must be used instead. Example of emission that can use it: CO2, to air, inputs production.
Certain emissions are depth dependent, and depthUpper and depthLower fields should be provided. This validation will show a warning if the depthUpper and depthLower fields are missing for these emissions.
Some characterisedIndicator Terms can only be used with specific model. This validation uses the lookup characterisedIndicator-model-mapping.csv to verify if it is valid.
Land transformation (i.e. the amount of land you cleared to make space for that crop / some amortization period) should be less than land occupation (i.e. the area that crop is using this year).
This validation enforces using a waste Input as key for "Inonising compounds" emissions.
This validation checks if landCover or previousLandCover is required based on the term lookup.