error when accessing the time series api endpoint

[ricardogsilva]

as resported by @sirmmo

A request like:

https://arpav.geobeyond.dev/api/v2/coverages/time-series/tas_annual_absolute_model_ensemble-absolute-media_ensemble-annual-rcp26?coords=POINT(12.1014%2046.0847)&datetime=..%2F..&include_coverage_data=true&include_observation_data=false&coverage_data_smoothing=LOESS_SMOOTHING&coverage_data_smoothing=MOVING_AVERAGE_11_YEARS&observation_data_smoothing=MOVING_AVERAGE_5_YEARS&include_coverage_uncertainty=true&include_coverage_related_data=true

and the response is 500...

After investigation, it seems a db function got renamed and not all places that call it were updated.

[francbartoli]

@ricardogsilva the above request is still not working

[ricardogsilva]

Turns out there were several issues which were causing multiple errors. These were actually regressions that were caused by the merge of #168

Issues found:

• rename of function not propagated to all the places that used it
• incorrect generation of coverage identifiers for related and uncertainty datasets
• missing translations for static strings

[francbartoli]

Reopening since after few requests to time series endpoint, i.e. https://arpav.geobeyond.dev/api/v2/coverages/time-series/tas_annual_absolute_model_ensemble-annual-model_ensemble-tas-absolute-rcp26-year?coords=POINT(12.1447%2045.8148)&datetime=..%2F..&include_coverage_data=true&coverage_data_smoothing=NO_SMOOTHING&coverage_data_smoothing=MOVING_AVERAGE_11_YEARS&coverage_data_smoothing=LOESS_SMOOTHING&include_coverage_uncertainty=true&include_coverage_related_data=true&inclied_observation_data=false the server becomes unresponsive. Checking its status it give CPU consumption beyond the available resources.
LOESS calculation is part of the scenario and might cause this behavior