-
Notifications
You must be signed in to change notification settings - Fork 0
Description
I think something must be amiss with the ingest for this coverage, as no matter what variable is requested the variable metadata in the returned netCDF describes the clt
variable:
Requesting tas
variable (encoded as 13
):
https://zeus.snap.uaf.edu/rasdaman/ows?&SERVICE=WCS&VERSION=2.0.1&REQUEST=GetCoverage&COVERAGEID=cmip6_monthly&SUBSET=varname(13)&SUBSET=ansi(%221950-01-15T12:00:00.000Z%22)&SUBSET=lat(61.5)&SUBSET=lon(-147)&FORMAT=application/netcdf
Requesting pr
variable (encoded as 4
):
https://zeus.snap.uaf.edu/rasdaman/ows?&SERVICE=WCS&VERSION=2.0.1&REQUEST=GetCoverage&COVERAGEID=cmip6_monthly&SUBSET=varname(4)&SUBSET=ansi(%221950-01-15T12:00:00.000Z%22)&SUBSET=lat(61.5)&SUBSET=lon(-147)&FORMAT=application/netcdf
both result in a dataset that has the clt
metadata, though the values are clearly not for clt
:
In the Rasdaman UI, I see this clt
info under the <covMetadata>/<bands>/<data>
tags, and it seems to be the only variable listed here. How do we get the right metadata to appear in the xarray.Dataset
when requesting the data as netCDF?