This PR provides a set of bootstrap configuration values for coverages. The main objectives of this PR are to ensure that:
All coverage configurations have localized display names and descriptions
All coverage configurations have sufficient meta information by means of possible values so that the frontend is able to find them by searching for this meta info.
These bootstrap configs are meant to allow to replicate the configuration of the system very fast, by simply typing the CLI command:
arpav-ppcv bootstrap coverage-configurations
The above command creates the configurations for all coverages.
As an example, the bootstrap config for tas_seasonal_anomaly_model_ensemble now includes the following information
name: tas_seasonal_anomaly_model_ensemble
display_name_english: Mean temperature
display_name_italian: Temperatura media
description_english: Average daily air temperature near the ground
description_italian: Temperatura media giornaliera dell'aria vicino al suolo
In order to get the relevant coverage identifier, which is used to request WMS layers, time series and downloads, the frontend can query the API - for example for retrieving the TAS value for the summer month, scenario RCP26 for the configuration mentioned above, the frontend can perform a request like:
This PR also includes the existing values in the response, so that the frontend may further filter the returned items into the one it wants to use. The reponse to the above request:
In the example above, the response include three items:
the main coverage
the lower uncertainty coverage
the upper uncertainty coverage
Upon receiving the response, the frontend is able to distinguish between them by inspecting the properties of each. Those that represent uncertainty will have a configuration_parameter_name: uncertainty_type property
This PR provides a set of bootstrap configuration values for coverages. The main objectives of this PR are to ensure that:
possible values
so that the frontend is able to find them by searching for this meta info.These bootstrap configs are meant to allow to replicate the configuration of the system very fast, by simply typing the CLI command:
The above command creates the configurations for all coverages.
As an example, the bootstrap config for
tas_seasonal_anomaly_model_ensemble
now includes the following informationtas_seasonal_anomaly_model_ensemble
Mean temperature
Temperatura media
Average daily air temperature near the ground
Temperatura media giornaliera dell'aria vicino al suolo
tas
tas
ens5ym/clipped/tas_anom_pp_ts_{scenario}_{year_period}_VFVGTAA.nc
ºC
default/seq-YlOrRd
0
6
tas
annual
anomaly
model_ensemble
rcp26
rcp45
rcp85
DJF
MAM
JJA
SON
In order to get the relevant coverage identifier, which is used to request WMS layers, time series and downloads, the frontend can query the API - for example for retrieving the TAS value for the summer month, scenario RCP26 for the configuration mentioned above, the frontend can perform a request like:
This PR also includes the existing values in the response, so that the frontend may further filter the returned items into the one it wants to use. The reponse to the above request:
In the example above, the response include three items:
Upon receiving the response, the frontend is able to distinguish between them by inspecting the properties of each. Those that represent uncertainty will have a
configuration_parameter_name: uncertainty_type
property