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
{{ message }}
This repository has been archived by the owner on Sep 1, 2022. It is now read-only.
I have a netCDF resource with no coverage metadata (no longitude, latitude) because it contains integrated quantities (global or regional means for example).
In this case, the NCSS complains with err=Could not open as Coverage
Hi @cofinoa,
thank you for your interest in this issue.
In the concerned project, the resource does not include spatial description unfortunately. But in another project, I have indeed be carefull to include a false lon, lat to get rid off this "limitations" and it works.
So my purpose would be to change NCSS to be able to handle those cases where describing a longitude, latitude is not relevant. Because spatial integrations are often made on regions defined by shapefiles, define a longitude and a latitude is not very adapted (even if possible by taking the center of the shapefile).
I have a netCDF resource with no coverage metadata (no longitude, latitude) because it contains integrated quantities (global or regional means for example).
In this case, the NCSS complains with
err=Could not open as Coverage
https://vesg.ipsl.upmc.fr/thredds/ncss/point/work_thredds/p86pasb/IPSLCM6/PROD/lig127k/CM61LIG127k00/MONITORING/files/ATM_precip_land_ave.nc?var=T2M_GLOBAL_PRIOtemporal=all&accept=csv
returns a zero size file.
The OPeNDAP service is available from:
https://vesg.ipsl.upmc.fr/thredds/dodsC/work_thredds/p86pasb/IPSLCM6/PROD/lig127k/CM61LIG127k00/MONITORING/files/ATM_precip_land_ave.nc.html
and the header of this file is:
The text was updated successfully, but these errors were encountered: