@@ -30,7 +30,68 @@ Below is a minimum example of VIPS result data.
This is the 10-character unique id for the specific model
## configParameters
Here are the input data, which are free-form, but by convention weather data are to be found in the `observations` property, and they must follow the [VIPS weather data format](./weather_data.md). Here, we also have a `sowingDate` that this specific model requires.
Here are the input data, which are free-form. The first one is the `sowingDate` that this specific model requires.
### Weather data
By convention weather data are to be found in the `observations` property, and they must follow the [VIPS weather data format](./weather_data.md). With observations, we actually mean **all weather data that the model uses; past, present and future**. A typical model expects all weather data to be in one continuous list of observations combining measured data and forecasts.
### PestObservation: Observations/registrations of pests and diseases in the field
The weather observations follow a standard pattern, and so do the field observations:
* timeOfObservation - timestamp when the obervation was made [REQUIRED]
* geoinfo: GeoJson describing the location. May or may not be required by the model
* name: Title of the observation (not important in models)
* observationData: Json formatted data quantifying the observation. **The properties vary greatly between the pests**. For each pest observation based models, there is a Json schema for this.
Pest observations may be only one or a series, depending on the model. If no observations available, the model should handle NULL.