It's linked with netCDF 4.4.1.1 which is prior to the problems we
saw with these thredds aggregation datasets. The issues with these
files have been reported to Unidata so we will watch their
upcoming releases as well.
A more major Ferret/PyFerret release isn't too far off, and at
that point we'll do a more complete release.
Dear Ajay Krishnan,
yes, I have seen something similar related to recent
netcdf-versions. I do not remember in the error code, guess it
was -68, but the error showed up when accessing a huge data set
on a thredds.
Lets check your data set:
with ferret 7.42, linked to netcdf 4.4.1.1:
yes? use
https://data.nodc.noaa.gov/thredds/dodsC/las/id-a074156616/data_https___data.nodc.noaa.gov_thredds_dodsC_ncml_ghrsst_ncml_fullAgg_aggregate__ghrsst_L4_GLOB_UKMO_OSTIA_20170605.ncml.jnl
*** NOTE: Ignored modulo length less than axis
length: LON
*** NOTE: netCDF bounds variable definition error
*** NOTE: Bounds definition "time_bnds" points to no
existing axis
*** NOTE: Ignoring BOUNDS attribute
So, there is something with the data set, but I can access the
data. I think this is not the problem.
The following works without any error
message. Using ferret linked with netcdf 4.4.1.1:
yes? shade/l=100 ANALYSED_SST
On my machine
gives "wrong argument" with netcdf
4.5.0 and works with netcdf 4.4.1.1
But:
yes? use
https://data.nodc.noaa.gov/thredds/dodsC/ncml/ghrsst_ncml/fullAgg/aggregate__ghrsst_L4_GLOB_UKMO_OSTIA_20170605.ncml
yes? shade/x=-15 ANALYSED_SST
CURL Error: Transferred a partial file
**netCDF error
NetCDF: DAP failure (OPeNDAP/netCDF Error code -66)
Data set:
https://data.nodc.noaa.gov/thredds/dodsC/ncml/ghrsst_ncml/fullAgg/aggregate__ghrsst_L4_GLOB_UKMO_OSTIA_20170605.ncml
Sorry for beeing not very specific, but I can confirm errors
with the data set and different behaviour with different
netcdf-versions.
Best,
Martin
On 11/19/18 5:53 PM, Ajay Krishnan -
NOAA Affiliate wrote:
Ever since we upgraded our LAS to 8.6.3, some of
our large aggregations which ran perfectly fine on the old
instance (v7.2) keep breaking with very generic OPeNDAP
errors.
For e.g.: