[gdal-dev] TRMM in GDAL?

[Yann Chemin]

On 25/01/2008, Frank Warmerdam <warmerdam at pobox.com> wrote:
> Yann Chemin wrote:
> > Hello I am trying to convert TRMM 2B31 from HDF into anything more
> > common for processing (Gtiff, HFA, ...)
> >
> > Basically gdalinfo returns this:
> >
> > yann at gis4400:~/TRMM$ gdalinfo 2B31.070101.52014.6.HDF
> > Driver: HDF4/Hierarchical Data Format Release 4
> > Size is 512, 512
> > Coordinate System is `'
> > Corner Coordinates:
> > Upper Left  (    0.0,    0.0)
> > Lower Left  (    0.0,  512.0)
> > Upper Right (  512.0,    0.0)
> > Lower Right (  512.0,  512.0)
> > Center      (  256.0,  256.0)
>
> Yann,
>
> The above sounds like the bogus parent dataset.  Were there
> subdatasets?  If so, do a gdalinfo on them and see if they have
> meaningful georeferencing.

This is all that gdalinfo returns. However, the c code provided by
TRMM website reads several subdatasets...
------------------------------------------------------------------------------------------------------------------
yann at gis4400:~/TRMM$ ./select_vNsds_linux 2B31.070101.52014.6.HDF

 Number of SDS arrays in file: 9

    1) geolocation                 dimensions =    9246     49      2
    2) dHat                        dimensions =    9246     49
    3) sigmaDHat                   dimensions =    9246     49
    4) rHat                        dimensions =    9246     49     80
    5) sigmaRHat                   dimensions =    9246     49     80
    6) rrSurf                      dimensions =    9246     49
    7) sigmaRRsurf                 dimensions =    9246     49
    8) latentHeatHH                dimensions =    9246     49     13
    9) spare                       dimensions =    9246     49      4
------------------------------------------------------------------------------------------------------------------
>
> If there are subdatsets but they lack georeferencing, you may
> find you can use "-a_ullr -180 40 180 40" on a gdal_translate line
> to assign the following bounds as part of a translation.

Thank you for this I will try this in any case.
Yann

>
> Best regards,
>
> > while in the  2B31.070101.52014.6.HDF.XML:
> > <SpatialDomainContainer>
> >     <HorizontalSpatialDomainContainer>
> >       <BoundingRectangle>
> >         <WestBoundingCoordinate>-180</WestBoundingCoordinate>
> >         <NorthBoundingCoordinate>40</NorthBoundingCoordinate>
> >         <EastBoundingCoordinate>180</EastBoundingCoordinate>
> >         <SouthBoundingCoordinate>-40</SouthBoundingCoordinate>
> >       </BoundingRectangle>
> >     </HorizontalSpatialDomainContainer>
> >   </SpatialDomainContainer>
> >
> > Any suggestion please?
> > Yann
> > _______________________________________________
> > gdal-dev mailing list
> > gdal-dev at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/gdal-dev
> >
>
>
> --
> ---------------------------------------+--------------------------------------
> 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    | President OSGeo, http://osgeo.org
>
>