[ferret_users] Re: [Opendap-tech] Hyrax serving netCDF coordinate variables?

["McCann, Mike" <mccann@xxxxxxxxx>]

> 
> On 5/12/10 5:34 PM, McCann, Mike wrote:
>> Hello,
>> 
>> We have just set up a Hyrax server with the netCDF Handler and are
>> wondering why we don¹t see the coordinate variables from a netCDF data
>> file.  Here¹s the Hyrax served data:
>> 
>> http://elvis.shore.mbari.org/opendap/m1/200910/m1_asimetswr_20091022.nc.html
>> 
>> and the same file served by TDS:
>> 
>> http://elvis.shore.mbari.org/thredds/dodsC/m1/200910/m1_asimetswr_20091022.nc
>> .html
>> 
>> Why does the former not show the esecs, NominalDepth, Longitude, and
>> Latitude variables? (I¹m suspecting that this is the reason that Ferret
>> is not ³understanding² the time axis.)
> 
> Mike,
> 
> Short answer, bug fix. You can get the old behavior by setting an option
> in handler's config file. In the netcdf handler's conf file add
> 'NC.ShowSharedDimensions=true' at the bottom (or anywhere really).
> 
> Long story: Those top variables are actually an error that we introduced
> into the handler a long time ago because out netcdf client library
> didn't understand the Grid type very well. When Unidata designed the
> TDS, they copied that bug to make their code compatible.
> 
> James
> 

I set 'NC.ShowSharedDimensions=true' in the bes.conf file (there appears to
be no conf file for the handler) and I get the old behavior.  Ferret now
understands the axes.  Thanks!

Should Ferret understand the new behavior for the case when
'NC.ShowSharedDimensions=false'?

-Mike