[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[THREDDS #NCT-216206]: TDS report incorrect attribute data type

Hi Tim,

I grabbed your dataset and I'm seeing this here as well. All "valid_min" 
attributes of type byte are being converted by OPeNDAP to Int16 instead of 
Byte. None of the other byte attributes are affected. E.g., all the 
corresponding "valid_max" byte attributes are Byte in OPeNDAP.

We'll look into this further and see about a fix.

Thanks,

Ethan

Tim Pugh wrote:
> Package Version: TDS 4.2.8 - 20110727.2340
> Operating System: Linux 2.6.18-274.el, Apache Tomcat/6.0.26, JVM 1.6.0_26-b03
> Hardware: Intel x86_64
>
> I've attached two ncdump files, one file is the ncdump of a local netCDF 
> file's
> meta-data, and the other is the ncdump of a remote netCDF file's meta-data 
> from a
> Unidata THREDDS server (v4.2.8).  The difference between the files is the 
> valid_min
> attribute which has been changed seven times from "-127b" to "-127s".
> 
> sses_bias:valid_min = -127s ;
> sses_standard_deviation:valid_min = -127s ;
> dt_analysis:valid_min = -127s ;
> wind_speed:valid_min = -127s ;
> wind_speed_dtime_from_sst:valid_min = -127s ;
> sea_ice_fraction_dtime_from_sst:valid_min = -127s ;
> satellite_zenith_angle:valid_min = -90s ;
> 
> To test this, ask our THREDDS data server for the das or ddx response, and
> you'll see the incorrect response, the valid_min will appear as Int16.  Then
> download the file and inspect the metadata.
> 
> http://opendap.bom.gov.au:8080/thredds/dodsC/ghrsst_l3s/ABOM-L3S_GHRSST-SSTs
> kin-AVHRR_D/2011/20111121180229-ABOM-L3S_GHRSST-SSTskin-AVHRR_D-1d_night-v02.0-fv01.0.nc.gz.das
> 
> I've confirmed that the attribute for valid_min in the file is written as 
> "-127b".
> 
> Regards,
> 
> - Tim -
> 
> 
> 


Ticket Details
===================
Ticket ID: NCT-216206
Department: Support THREDDS
Priority: Urgent
Status: Open