As it stands now invalid dimensions where the data is 100% null (e.g., "rcp85 scenario + "CRU-TS") are handled on an ad hoc basis in the API. If we continue the pattern of combining historical and future data in a single coverage, we'll continue to have the need to handle invalid dimensions. We should perhaps add the invalid dimensional combinations to the metadata in the ingest.json files so that the API can either drop them from the packaged data dictionary without much hassle (traversing a nested dictionary, checking for key combinations, etc.). They could probably even be dropped immediately after the response.
Something in like
invalid_dims = {
[0, 1, 1]...
}
But maybe encode with the actual names to make it clear.
As it stands now invalid dimensions where the data is 100% null (e.g., "rcp85 scenario + "CRU-TS") are handled on an ad hoc basis in the API. If we continue the pattern of combining historical and future data in a single coverage, we'll continue to have the need to handle invalid dimensions. We should perhaps add the invalid dimensional combinations to the metadata in the
ingest.jsonfiles so that the API can either drop them from the packaged data dictionary without much hassle (traversing a nested dictionary, checking for key combinations, etc.). They could probably even be dropped immediately after the response.Something in like
But maybe encode with the actual names to make it clear.