search

diarmuidw / pygrib2

Automatically exported from code.google.com/p/pygrib2
0 stars 2 forks source link

Error accessing grib2 data #2

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Dear Jeffrey,

I got some warnings during pygrib2 compilation process, but installation
ended quite normaly (I've attached my compilation log file). However, when
I try to access grib2 data from grib2Message object, I get the following
error :

>>> import grib2
>>> gb=grib2.Grib2Decode('gec00.t06z.pgrb2bf168')
>>> gb[0].data()
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/mnt/softs/PYTHON/lib/python2.4/site-packages/grib2/grib2.py", line
617, in data

fld1=g2lib.unpack7(gribmsg,gdtnum,gdtmpl,drtnum,drtmpl,ndpts,ipos,N.zeros,storag
eorder=storageorder)
  File "g2lib.pyx", line 463, in g2lib.unpack7
TypeError: 'order' is an invalid keyword argument for this function

Please keep this project alive, it would be extremely helpful for us.
Thanks for help.

Best regards,
Jul.

Original issue reported on code.google.com by j.vie...@gmail.com on 20 May 2008 at 3:31

Attachments:

GoogleCodeExporter commented 9 years ago 
Could you try deleting your current pygrib2 installation and re-installing?

I.e. /bin/rm -rf /mnt/softs/PYTHON/lib/python2.4/site-packages/grib2,

they 'python setup.py install' again.

And don't worry, the project is still alive.

Original comment by whitaker.jeffrey@gmail.com on 22 May 2008 at 11:45

GoogleCodeExporter commented 9 years ago 
I suppose you mean checking out an updated pygrib2-read-only CVS version and 
try again.
That's what I did, but compilation fails miserably without beeing completed.
Here is log file
++
Jul.

Original comment by j.vie...@gmail.com on 22 May 2008 at 4:51

Attachments:

GoogleCodeExporter commented 9 years ago 
Jul:  No, actually I meant re-installing the same package you had tried to 
install
initially, after deleting the pygrib2 site-packages directory.  I think you 
have some
leftover files in there there are messing things up.

As far as why compiling the svn version failed, it looks like it has something 
to do
with your png header.  Either it's not finding it, or it's corrupted somehow 
(sorry,
my French is not good enough to tell which).

-Jeff

Original comment by whitaker.jeffrey@gmail.com on 22 May 2008 at 4:56