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 would like to transition from the heatmax_median_multivariate endpoint to the heatmax_median_multivariate_historical_annual endpoint in the EIC app, but there are discrepancies in the data, particularly missing StdTime values after 2014 (the historical cut off date), and differences in the returned values between the two endpoints.
Key points:
Endpoint:
We intend to switch to the heatmax_median_multivariate_historical_annual endpoint as monthly data is no longer needed
However, after 2014, the StdTime values are missing from the returned data for future years (until 2100)
Discrepancies in returned values:
The two endpoints return different values for the same time period and location
Example: For Phoenix, AZ in 2013, the two endpoints return different values:
Annual endpoint returns a heatmax_ssp585 value of 102.53°F for 2013 (with the StdTime showing December as the chosen month)
Multivariate endpoint returns monthly values for 2013, where no values exceed 100°F, with the December value being 64.23°F
Detailed example:
1. Heatmax Median Multivariate Annual Endpoint (heatmax_median_multivariate_historical_annual):
Filtered response for the whole year 2013, with December being the last sample in the blob (also no values throughout the year go above 100°F so it's unclear what the data serves or represents)
Clarify what to show: tasmax (daily maximum near-surface air temperature; aggregated into annual max?) + precipitation (aggregated how?)
Create data services that have accurate names and ideally also short descriptions of what they are showing, so we are never in doubt and can ideally surface those descriptions in the app
Make sure the services behave as expected - e.g. that they consistently return stdTime, which is currently not the case (see above)
Validate the values against known / expected ranges
The production server and services have been deployed/published on the minimum recommend AWS instance size. These can be incorporated into the app now. We will continue load testing this week and provide considerations for increasing AWS instance RAM. We would also like to propose restricting access to EIC app and Worldview.
Aggregated annual tasmax and annual pr
Replicated NEX naming schema; added basic description and variable units not intended to be public - welcome guidance to change
Won’t have the inconsistent stdTime issue – these services have historical data appended to each scenario; will explain the issue in a dev sync
Validated the service results match the source data… assuming EIC/Alex will validate the source data
We would like to transition from the
heatmax_median_multivariate
endpoint to theheatmax_median_multivariate_historical_annual
endpoint in the EIC app, but there are discrepancies in the data, particularly missingStdTime
values after 2014 (the historical cut off date), and differences in the returned values between the two endpoints.Key points:
heatmax_median_multivariate_historical_annual
endpoint as monthly data is no longer neededStdTime
values are missing from the returned data for future years (until 2100)heatmax_ssp585
value of 102.53°F for 2013 (with theStdTime
showing December as the chosen month)Detailed example:
1. Heatmax Median Multivariate Annual Endpoint (
heatmax_median_multivariate_historical_annual
):2. Heatmax Median Multivariate (heatmax_median_multivariate):
Action items
StdTime
values after 2014 in theheatmax_median_multivariate_historical_annual
endpointThe text was updated successfully, but these errors were encountered: