[gdal-dev] Reading GRIB2 with GDAL 1.6.3 leeds to Warning: Investigate Template 4.8 bytes 35-41

Eloi Ribeiro eloi.ribeiro at gmail.com
Mon May 24 08:05:21 EDT 2010


Thanks for the good news!
I will wait for the 1.7.3 release.
Best regards,
Eloi





On Mon, May 24, 2010 at 11:58 AM, Even Rouault <even.rouault at mines-paris.org
> wrote:

> Eloi,
>
> I've fixed an "obvious" coding error in the degrib library used by GDAL to
> read GRIB files that was the cause for the crash. It seems it is a bit
> related to the warning message about not being able to parse the date (that
> still persists), but not at the same place where the warning is emitted.
>
> Best regards,
>
> Even
>
> Le Monday 24 May 2010 10:30:25 Eloi Ribeiro, vous avez écrit :
> > On Fri, Apr 30, 2010 at 12:42 PM, Eloi Ribeiro
> <eloi.ribeiro at gmail.com>wrote:
> > > On Thu, Apr 29, 2010 at 3:35 PM, Frank Warmerdam
> <warmerdam at pobox.com>wrote:
> > >> Eloi Ribeiro wrote:
> > >>> Hi,
> > >>>
> > >>> I keep receiving this warning using GDAL (1.6.3 released 2009/11/19
> on
> > >>> Ubuntu desktop 9.10) whith GRIB2 files:
> > >>>
> > >>> "Warning: Investigate Template 4.8 bytes 35-41
> > >>> Warning: Investigate Template 4.8 bytes 35-41
> > >>> (...)
> > >>> Warning: Investigate Template 4.8 bytes 35-41
> > >>> Warning: Investigate Template 4.8 bytes 35-41
> > >>> Segmentation fault"
> > >>
> > >> Eloi,
> > >>
> > >> The message comes from this part of:
> > >>
> > >> gdal/frmts/grid/degrib18/degrib/inventory.cpp
> > >>
> > >>
> > >>         case GS4_STATISTIC: /* 4.8 */
> > >>            if (InventoryParseTime (*buffer + 35 - 5,
> &(inv->validTime))
> > >> != 0) {
> > >>               printf ("Warning: Investigate Template 4.8 bytes
> > >> 35-41\n"); inv->validTime = inv->refTime + inv->foreSec;
> > >>            }
> > >>
> > >> Basically, it appears that it means there was a problem parsing
> > >> a date in the grib file, and it is reported as a warning.
> > >>
> > >> There is no particular reason to believe it is related to the crash
> > >> you see with some files.
> > >>
> > >> You might want to file a ticket with one of the files resulting in a
> > >> crash for further investigation.
> > >>
> > >> Best regards,
> > >> --
> > >>
> > >>
> ---------------------------------------+--------------------------------
> > >>------ I set the clouds in motion - turn up   | Frank Warmerdam,
> > >> warmerdam at pobox.com
> > >> light and sound - activate the windows | http://pobox.com/~warmerdam
> > >> and watch the world go round - Rush    | Geospatial Programmer for
> Rent
> > >
> > > Thank's for the tip Frank.
> > > I just submitted a ticket[1].
> > > I hope this issue can be solved.
> > > Regards,
> > >
> > > [1] http://trac.osgeo.org/gdal/ticket/3555
> > >
> > > --
> > > Eloi Ribeiro
> > > GIS Analyst
> > > 39,45º -4,40º
> > > http://eloiribeiro.wordpress.com
> >
> > Hi,
> > Just to let Know that the bug [1] persist after update to the latest GDAL
> > version: GDAL 1.7.2, released 2010/04/23.
> > Best regards,
> >
> > [1] http://trac.osgeo.org/gdal/ticket/3555
>
>
>


-- 
Eloi Ribeiro
GIS Analyst
39,45º -4,40º
http://eloiribeiro.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/gdal-dev/attachments/20100524/ec3ce896/attachment-0001.html


More information about the gdal-dev mailing list