Open cpaulik opened 8 years ago
@cpaulik @lesserwhirls Did you ever resolve this issue? I'm seeing the same issue with the empty
Greetings! I finally had a chance to investigate this one, and it looks like there are two issues at hand here.
The metadata for longitude
specifies the valid_range
as:
lon:valid_range = -180.f, 180.f ;
except the actual longitude
values used in the file are from 0 - 360. When netCDF-Java opens this file, it interprets half of the longitude values and invalid. This can be fixed by using NcML to change the valid_range
attribute.
The latitude variable does not appear to be "regular" (i.e. regularly spaced), or at least it's not passing our check for being regular (which is needed to use WCS). We do the following to check if the grid spacing is regular:
0.005
The 0.005
tolerance is supposed to help account for errors in floating point math. For the example dataset attached to this ticket, the computed spacing is 0.701669188773156
, but the range of individual deltas is from 8.38639E-05
to 0.00579897303795818
, which is just outside of the tolerance level of 0.005
. This threshold is only reached for the delta between the first and second values, and the delta between the second-to-last and last values.
I think this issue really comes down to how the latitude variable was computed, and how it was written to the netCDF file. I noticed that while lat
and lon
are of type double
, their valid_range
attributes are of type float
, which makes me think something wasn't quite right when it was generated. Thankfully, this too can be addressed using NcML.
Here is what I did with the example file to make things happy:
<netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2"
location="./39.128_RD_OPER_gbg4_AN_N128_19840102_1800_0-regular-avg-removed_depth.nc">
<variable name="lon">
<attribute name="valid_range" type="double" value="0 360" />
</variable>
<variable name="lat">
<values start="-89.296875" increment="0.703125" />
</variable>
</netcdf>
Just update the location
attribute in the netcdf
element and you should be good to go.
Hi,
I have a dataset (ERA-LAND modelled data). It was converted from a grib file using CDO and NCO. Putting it into Thredds it works fine with WMS and OpenDAP. When I try to access it via WCS I get the Backtrace at the bottom. It also does not have any
<ContentMetadata/>
in the WCSGetCapabilities
.I've tried adding some metadata fields that thredds might expect but it did not change anything. Could you please point me to documentation about which metadata attributes thredds expects for a dataset to work with WCS? According to the CF checker it is conform with the conventions.
The file can also be found here in a zip file.
Dataset details
Output of WCS GetCapabilities
Backtrace