Closed karlmsmith closed 6 years ago
Comment by @AnsleyManke on 28 Mar 2014 19:19 UTC This is done. The above dataset now looks like this after being opened.
yes? use "http://data1.gfdl.noaa.gov:8380/thredds3/dodsC/clivar_Fef_ensemble"
*** NOTE: Error in bounds "time_bnds" or bounds do not enclose point on axis time
*** NOTE: Substituting coordinate midpoints
*** NOTE: Units on axis "plev" are not recognized: Pa
*** NOTE: They will not be convertible:
*** NOTE: Axis coordinates are decreasing-ordered. Reversing ordering for axis plev
yes? sh dat
currently SET data sets:
1> http://data1.gfdl.noaa.gov:8380/thredds3/dodsC/clivar_Fef_ensemble (default)
name title I J K L M N
HEIGHT height ... ... ... ... ... ...
TIME_BNDS
1:2 ... ... 1:336 ... ...
(invalid axis bounds)
LABELS CLIVAR Fef ... ... ... ... 1:5 ...
RLS Net surface longwave 1:144 1:90 ... 1:336 ... ...
RLT Outgoing Longwave Radiation 1:144 1:90 ... 1:336 ... ...
...
yes? list time_bnds
VARIABLE : TIME_BNDS
invalid axis bounds
DATA SET : model output prepared for GFDL Seasonal-Interannual experimental forecasts - CM2.1U_CDAef_V1.0
FILENAME : clivar_Fef_ensemble
FILEPATH : http://data1.gfdl.noaa.gov:8380/thredds3/dodsC/
SUBSET : 2 by 336 points (X-TIME)
CALENDAR : JULIAN
1 2
1 2
16-FEB-1982 / 1: 0.0 28.0
18-MAR-1982 / 2: 28.0 59.0
18-APR-1982 / 3: 59.0 89.0
18-MAY-1982 / 4: 89.0 120.0
18-JUN-1982 / 5: 120.0 150.0
18-JUL-1982 / 6: 150.0 181.0
18-AUG-1982 / 7: 181.0 212.0
17-SEP-1982 / 8: 212.0 242.0
18-OCT-1982 / 9: 242.0 273.0
17-NOV-1982 / 10: 273.0 303.0
18-DEC-1982 / 11: 303.0 334.0
17-JAN-1983 / 12: 334.0 365.0
17-FEB-1983 / 13: 0.0 28.0
19-MAR-1983 / 14: 28.0 59.0
19-APR-1983 / 15: 59.0 89.0
19-MAY-1983 / 16: 89.0 120.0
19-JUN-1983 / 17: 120.0 150.0
19-JUL-1983 / 18: 150.0 181.0
19-AUG-1983 / 19: 181.0 212.0
...
Reported by steven.c.hankin on 28 Feb 2014 01:19 UTC When Ferret encounters a coordinate axis that is disordered (or whatever) it substitutes a simple index variable as the coordinate and makes the (disordered) coordinates visible as a dependent variable. That way the user can often assess the nature of the problem, correct it using Ferret definitions and fix it in a Ferret session.
However, when Ferret encounters erroneous coordinate bounds, it reports the problem, but fails to make the values visible. So there is no way for the Ferret user to compute on the values.
Erroneous bounds should be promoted to a dependent variable, much as the coordinates are.
An example of problem is illustrated in this script refering to '''time_bnds'''
As netCDF the dataset looks like this:
Some of the values of time and time_bounds are here
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/2146