[netCDF #EZQ-884585]: NetCDF: Unknown file format

Just to chime in; there should be a 'libnetcdf.settings' file that was created 
and installed in the same directory as the netcdf library.  Can you send that 
to us?

Thanks!

-Ward

> Hi,
> 
> ncdump version on my fedora27 x86-64
> 
> [bou@hp450-fed26 ~]$ ncdump
> netcdf library version 4.4.1.1 of Aug  4 2017 03:48:35 $
> 
> 
> I download again to make sure we have same file
> 
> 
> [bou@hp450-fed26 ~]$ wget
> https://github.com/Unidata/unidata-python-workshop/blob/master/data/rtofs_glo_3dz_f006_6hrly_reg3.nc
> 
> 2017-12-01 16:13:27 (57.3 KB/s) - ‘rtofs_glo_3dz_f006_6hrly_reg3.nc’ saved
> [40419]
> 
> [bou@hp450-fed26 ~]$ ncdump -h rtofs_glo_3dz_f006_6hrly_reg3.nc
> ncdump: rtofs_glo_3dz_f006_6hrly_reg3.nc.1: NetCDF: Unknown file format
> 
> so not sure why I am having problems.
> I can open other nc files from ECMWF reanalysis data just fine.
> 
> regards
> vin
> 
> address@hidden> wrote:
> 
> > So I got that file from here:
> > https://github.com/Unidata/unidata-python-workshop/blob/
> > master/data/rtofs_glo_3dz_f006_6hrly_reg3.nc
> > Using that and ndump version
> > netcdf library version 4.5.1-development of Nov 30 2017 13:39:21
> > I successfully opened the file.
> >
> > So, we need to check some things.
> > 1. is the file I am using the same as the one you have?
> > 2. what version of ncdump are you using. You can find out
> >    by justing typeing the command "ncdump" with no arguments.
> >    The version should be at the end of its usage output.
> >
> >
> >
> > > Just to confirm I get same error on both ver 4.4.1 and ver 4.5.0
> > > see screen dumps below
> > >
> > > regards
> > > vinorda
> > >
> > > I have netcdf version 4.4.1on Fedora23 64 bit linux
> > >
> > > $ rpm -qa netcdf
> > > netcdf-4.4.1.1-6.fc27.x86_64
> > >
> > > $ ncdump -h rtofs_glo_3dz_f006_6hrly_reg3.nc
> > > ncdump: rtofs_glo_3dz_f006_6hrly_reg3.nc: NetCDF: Unknown file format
> > >
> > > Opening data file with panoply gives this error
> > > "There was an error openeing the dataset:The file does not seem to be
> > valid
> > > CDM"
> > >
> > >
> > > On my Jupyter NOtebook I have netcdf ver 4.5.1, provided by Anaconda
> > > Distribution
> > > conda-forge channel and get same error
> > >
> > >
> > > netcdf library version 4.5.0 of Nov  8 2017 13:35:26
> > >
> > > $!ncdump -h ./rtofs_glo_3dz_f006_6hrly_reg3.nc
> > > ncdump: ./rtofs_glo_3dz_f006_6hrly_reg3.nc: NetCDF: Unknown file format
> > >
> > >
> > > address@hidden> wrote:
> > >
> > > >
> > > > vinorda .,
> > > >
> > > > Your Ticket has been received, and a Unidata staff member will review
> > it
> > > > and reply accordingly. Listed below are details of this new Ticket.
> > Please
> > > > make sure the Ticket ID remains in the Subject: line on all
> > correspondence
> > > > related to this Ticket.
> > > >
> > > > NOTE: All email exchanges with Unidata User Support are recorded in the
> > > > Unidata inquiry tracking system and then made publicly available
> > through
> > > > the web.  If you do not want to have your interactions made available
> > in
> > > > this way, you must let us know in each email you send to us.
> > > >
> > > >     Ticket ID: EZQ-884585
> > > >     Subject: NetCDF: Unknown file format
> > > >     Department: Support netCDF
> > > >     Priority: Normal
> > > >     Status: Open
> > > >
> > > >
> > > >
> > > > The NetCDF libraries are developed at the Unidata Program Center,
> > > > in Boulder, Colorado, funded primarily by the National Science
> > Foundation.
> > > >
> > > > All support requests are handled by the development team. No dedicated
> > > > support staff are funded at this time. For this reason we cannot
> > guarantee
> > > > response times, nor that we can resolve every support issue, although
> > we
> > > > do our best to respond within 72 hours.
> > > >
> > > > It is in the nature of support requests that the same question is asked
> > > > many
> > > > times. We urge you to search the support archives for material
> > relating to
> > > > your support request:
> > > >
> > > > http://www.unidata.ucar.edu/search.jsp?support&netcdf
> > > >
> > > > If you are having trouble building netCDF, please take a look at the
> > > > "Building NetCDF" page:
> > > >
> > > > http://www.unidata.ucar.edu/software/netcdf/docs/building.html
> > > >
> > > > or the (unfortunately somewhat out-of-date) NetCDF Build Troubleshooter
> > > > page:
> > > >
> > > > http://www.unidata.ucar.edu/software/netcdf/docs/troubleshoot.html
> > > >
> > > > Windows users should see the FAQ list:
> > > >
> > > > http://www.unidata.ucar.edu/software/netcdf/docs/faq.html#
> > > > windows_netcdf4_2
> > > >
> > > > Complete documentation (including a tutorial, and sample programs in C,
> > > > Fortran,
> > > > Java, and other programming languages) can be found on the netCDF
> > > > Documentation page:
> > > >
> > > > http://www.unidata.ucar.edu/software/netcdf/docs/
> > > > http://www.unidata.ucar.edu/software/netcdf/examples/programs/
> > > >
> > > > If you resolve your issue through one of these methods, please send a
> > > > reply to
> > > > this email, letting us know that you no longer need support. This will
> > help
> > > > us spend more time on netCDF development.
> > > >
> > > > Best regards,
> > > >
> > > > Unidata User Support
> > > >
> > > >
> > >
> > >
> >
> > =Dennis Heimbigner
> >   Unidata
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: EZQ-884585
> > Department: Support netCDF
> > Priority: Normal
> > Status: Open
> > ===================
> > NOTE: All email exchanges with Unidata User Support are recorded in the
> > Unidata inquiry tracking system and then made publicly available through
> > the web.  If you do not want to have your interactions made available in
> > this way, you must let us know in each email you send to us.
> >
> >
> >
> 
> 


Ticket Details
===================
Ticket ID: EZQ-884585
Department: Support netCDF
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.