Changes between Version 1 and Version 2 of Ticket #4603


Ignore:
Timestamp:
Apr 5, 2012, 8:32:43 PM (12 years ago)
Author:
warmerdam
Comment:

Hi, can you provide the file in question?

I suspect the fix is to declare "chData" as "unsigned char" but it would be easier to confirm with a file demonstrating the issue.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #4603

    • Property Keywords grib added; grb files removed
    • Property Status new → assigned
    • Property Component default → GDAL_Raster

  • Ticket #4603 – Description

    v1 v2  
    22A character is read from the grib file apparently to test whether it is at the end of the file. EOF is returned if there is an error in reading a character. But if the character read in the file is equal to EOF, the reading of valid data stops.  I have a NLDAP grib file with 37 data sets in it. It stop after 9 because a character read with this routine happens to be -1. I did a check of chData to see if it was equal to EOF and set chData to 0 instead. The grib file was read correctly. I was able to access all 37 data sets. Is there a reason for chData at this point to indicate a badly formed grib file if the value return here is -1?
    33
     4{{{
    45int FileDataSource::DataSourceFgetc()
    56{
    … …  
    1112        return EOF;
    1213}
     14}}}