You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to integrate observations data from the third-party meteo fvg API.
Integration shall follow a similar strategy as done for the ARPAV-PPCV observations data.
The intention is to ultimately show this data alongside the ARPA Veneto observation data on the climate projections section (but not on the historical data section).
Therefore, we will need to:
Store ARPA FVG observation data locally, in a similar manner to what is done with the ARPAV observations data - this includes the periodic refresh of existing data. Note that the schema of the remote API is not exactly equal, with the most relevant difference being the existence of a statid property, which we will need to store
Enrich current schema for stations such that it becomes possible to distinguish ARPAV and ARPA-FVG stations
Produce vector tile layers for stations to show in climate projections section (which must include both stations from ARPAV and ARPA FVG) and for the historical data section (which must only show stations from ARPAV)
The text was updated successfully, but these errors were encountered:
We need to integrate observations data from the third-party meteo fvg API.
Integration shall follow a similar strategy as done for the ARPAV-PPCV observations data.
The intention is to ultimately show this data alongside the ARPA Veneto observation data on the climate projections section (but not on the historical data section).
Therefore, we will need to:
statid
property, which we will need to storeThe text was updated successfully, but these errors were encountered: