[gdal-dev] GDAL/OGR 1.8.1 Advance Warning

[Anton Korosov]

Hi Frank!

There is a bug in the current Envisat driver which could be fixed in 1.8.1.
Not all bands (MDS) are read properly from the MERIS Level 2 imagery. 
Below are last lines of the output of
gdalinfo MER_RR__2PNPDK20110502_144833_000024913102_00097_47956_7579.N1

MDSs are numbered from 1 to 13, then 16 and 19. And in the file MDSs 
14-15 and 17-18 also exist.
I'm not sure if that's the proper place to report this bug but I just 
follow your invitation.

All the best!
Anton

Band 1 Block=1121x1 Type=UInt16, ColorInterp=Undefined
   Description = Norm. rho_surf - MDS(1)
Band 2 Block=1121x1 Type=UInt16, ColorInterp=Undefined
   Description = Norm. rho_surf - MDS(2)
Band 3 Block=1121x1 Type=UInt16, ColorInterp=Undefined
   Description = Norm. rho_surf - MDS(3)
Band 4 Block=1121x1 Type=UInt16, ColorInterp=Undefined
   Description = Norm. rho_surf - MDS(4)
Band 5 Block=1121x1 Type=UInt16, ColorInterp=Undefined
   Description = Norm. rho_surf - MDS(5)
Band 6 Block=1121x1 Type=UInt16, ColorInterp=Undefined
   Description = Norm. rho_surf - MDS(6)
Band 7 Block=1121x1 Type=UInt16, ColorInterp=Undefined
   Description = Norm. rho_surf - MDS(7)
Band 8 Block=1121x1 Type=UInt16, ColorInterp=Undefined
   Description = Norm. rho_surf - MDS(8)
Band 9 Block=1121x1 Type=UInt16, ColorInterp=Undefined
   Description = Norm. rho_surf - MDS(9)
Band 10 Block=1121x1 Type=UInt16, ColorInterp=Undefined
   Description = Norm. rho_surf - MDS(10)
Band 11 Block=1121x1 Type=UInt16, ColorInterp=Undefined
   Description = Norm. rho_surf - MDS(11)
Band 12 Block=1121x1 Type=UInt16, ColorInterp=Undefined
   Description = Norm. rho_surf - MDS(12)
Band 13 Block=1121x1 Type=UInt16, ColorInterp=Undefined
   Description = Norm. rho_surf - MDS(13)
Band 14 Block=1121x1 Type=UInt16, ColorInterp=Undefined
   Description = YS, SPM, Rect. Rho- MDS(16)
Band 15 Block=1121x1 Type=UInt16, ColorInterp=Undefined
   Description = Alpha, OPT     - MDS(19)

On 27/06/2011 14:31, Frank Warmerdam wrote:
> Folks,
>
> I would like to prepare a 1.8.1 release candidate in the next couple
> days.
> Developers are encouraged to address any bug fixes they would like
> promptly.
> Is there anything folks feel strongly needs to be addressed in 1.8.1 that
> has not yet made it into the 1.8 branch?
>
> Best regards,