[Gdal-dev] ASTER DEM and HDF and PROJ problem

[Markus Neteler]

On Tue, May 20, 2003 at 09:25:32AM -0400, Frank Warmerdam wrote:
> Markus Neteler wrote:
> > Dear GDAL developers,
> > 
> > I am facing a problem with gdal/hdf/asterdem/proj4 (GDAL and PROJ4 from
> > yesterday's CVS):
> > 
> > gdalinfo ASTER_DEM20020827134235.hdf | more
> > ERROR 6: Failed to initialize PROJ.4 with +proj=longlat +ellps=WGS84
> > +datum=WGS84 +no_defs '.
> > unknown projection id
> > ERROR 6: Failed to initialize PROJ.4 with +proj=longlat +ellps=WGS84
> > +datum=WGS84 +no_defs '.
> > unknown projection id
> > ERROR 6: Failed to initialize PROJ.4 with +proj=longlat +ellps=WGS84
> > +datum=WGS84 +no_defs '.
> > unknown projection id
> > ERROR 6: Failed to initialize PROJ.4 with +proj=longlat +ellps=WGS84
> > +datum=WGS84 +no_defs '.
> > unknown projection id
> > 
> > I don't know where the error occurs (GDAL or PROJ4).
> 
> 
> Markus,
> 
> Offhand, my guess would be that somehow the wrong PROJ.4 has been picked
> up at runtime (a very old one) and it doesn't know about latlong.  However,
> it might also be that PROJ.4 isn't being picked up at all.  Does gdalinfo
> report lat/long corners for other images such as a GeoTIFF file?

Frank,

now I understand...
this sounds reasonable due to my last experiments with OGDI:

ldd /usr/local/bin/gdalinfo
        libgdal.1.1.so => /usr/local/lib/libgdal.1.1.so (0x40017000)
        libogdi31.so => /usr/local/lib/libogdi31.so (0x4039d000)
        libungif.so.4 => /usr/lib/libungif.so.4 (0x403dc000)
        libpng12.so.0 => /usr/lib/libpng12.so.0 (0x403e4000)
        libdl.so.2 => /lib/libdl.so.2 (0x4041d000)
        libm.so.6 => /lib/libm.so.6 (0x40422000)
        libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x40444000)
        libc.so.6 => /lib/libc.so.6 (0x40487000)
        libzlib_ogdi31.so => /usr/local/lib/libzlib_ogdi31.so (0x405bd000)
        libexpat_ogdi31.so => /usr/local/lib/libexpat_ogdi31.so (0x405ca000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x405e6000)
        libz.so.1 => /usr/lib/libz.so.1 (0x406dd000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

(My) OGDI uses it's internal proj which is old. So far I didn't manage to
configure OGDI to use an external PROJ4 (the new one) but I'll try harder.

Since I don't get OGR/OGDI to work with VMAP0 I'll disable it again.

Thanks for the hint,

 Markus