[ncl-talk] Error reading h5 file.

[Marston Johnston]

Hi Dennis,

I suspected NCL 6.4 would work.
When is its release scheduled?
Yes, I would love to get access to a pre-release version for Linux. When can I get access?
For the project I’m working on, it is better to keep the data in h5 format rather than netcdf since netcdf doubles the datasize from 3 to ~7 Tb. I can get my admin to install 6.4. since this is the case.

Best
/M

On 17 Jan 2017, 19:22 +0100, Dennis Shea <shea at ucar.edu>, wrote:
NCL 6.3.0 fails
(beta) NVL 6.4.0 succeeds

%> ncl_filedump NSS.MHSX.NN.D07001.S2324.E0119.B0834142.WI.h5 >&! out.marston

see attached

I speculate a 6.4.0 version can be made available if you need it.

===

On Tue, Jan 17, 2017 at 10:54 AM, Marston Johnston <marston.johnston at gu.se<mailto:marston.johnston at gu.se>> wrote:

Hi,


I have a NOAA18 hdf5 file that NCL reads but does so incorrectly.

For example NCL reads the variable:


 integer btemps ( DIM_001, DIM_000, DIM_000 )

         Description : Brightness temperature

         FillValue : -999999

         Scale : 0.01

         Units : Krightness temperature


but h5dump gives:


GROUP "Data" {

      DATASET "btemps" {

         DATATYPE  H5T_STD_I32LE

         DATASPACE  SIMPLE { ( 2571, 90, 5 ) / ( 2571, 90, 5 ) }

         ATTRIBUTE "Description" {

            DATATYPE  H5T_STRING {

                  STRSIZE 22;

                  STRPAD H5T_STR_NULLTERM;

                  CSET H5T_CSET_ASCII;

                  CTYPE H5T_C_S1;

               }

            DATASPACE  SIMPLE { ( 1 ) / ( 1 ) }

         }

         ATTRIBUTE "FillValue" {

            DATATYPE  H5T_STD_I32LE

            DATASPACE  SIMPLE { ( 1 ) / ( 1 ) }

         }

         ATTRIBUTE "Scale" {

            DATATYPE  H5T_IEEE_F32LE

            DATASPACE  SIMPLE { ( 1 ) / ( 1 ) }

         }

         ATTRIBUTE "Units" {

            DATATYPE  H5T_STRING {

                  STRSIZE 1;

                  STRPAD H5T_STR_NULLTERM;

                  CSET H5T_CSET_ASCII;

                  CTYPE H5T_C_S1;

               }

            DATASPACE  SIMPLE { ( 1 ) / ( 1 ) }

         }

      }


As you can see the values of the dimensions are different and NCL reads them in erroneously.

Is there a way to read these files correctly?


Here’s a link to an example of the hdf5 file:


https://www.dropbox.com/s/nc0whngz7ajmx84/NSS.MHSX.NN.D07001.S2324.E0119.B0834142.WI.h5?dl=0


Appreciate your help with this matter,


/M


Marston S. Johnston, PhD

Department of Earth Sciences

University of Gothenburg, Sweden

Email: marston.johnston at gu.se<mailto:marston.johnston at gu.se>

SkypeID: marston.johnston

Phone: +46-31-7864901<tel:+46%2031%20786%2049%2001>

Only the fruitful thing is true!

_______________________________________________
ncl-talk mailing list
ncl-talk at ucar.edu<mailto:ncl-talk at ucar.edu>
List instructions, subscriber options, unsubscribe:
http://mailman.ucar.edu/mailman/listinfo/ncl-talk


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20170117/63849d0f/attachment.html