Open kyleredilla opened 2 years ago
With inclusion of the ALFRESCO endpoints PR #94 we have a shared method of extracting encodings from a rasdaman coverage via a DescribeCoverage request, instead of only with a netcdf WCS request. Ensure that all endpoints use this to generate the lookup tables for dimension coordinate encodings at startup so that the API is adaptable to changes in the rasdaman coverages provided the encodings metadata is updated in accordance with the changes.
OWSLib may have better ways of parsing XML metadata encodings
Currently some (or all) of the endpoints rely on hard-coded encoding values for rasdaman coverages. I think that a more robust approach would be to ensure that encodings are present in the coverage metadata, and to programmatically query that metadata via DescribeCoverage request to construct the encoding lookup dicts in the API.