Jean-Claude I guess it's not only a problem of gdalinfo but of some parts of GDAL in general dealing with the ECW.
I made some more tests and when I add the options -co DATUM=WGS84 -co PROJ=NUTM32 to the gdal_translate call then gdalinfo identifies the coordinates correctly afterwards, but then of course the whole projection is set to UTM... It seems that the default value entered for DATUM is "RAW" and that seems to cause some of the problems afterwards for GDAL. The problem for me is that I need to insert the correct datum and projection using the syntax of ECW, and I don't know if all available datums/projections used e.g. in Europe are supported, and which syntax to use for the available ones. I found on my Windows installation a file "PcskeyProjDatum.dat" with a few definitions of projection and datum used but this was very limited and covered mainly UTM and NAD. Most European projections and datums were missing in this file. Armin -------- Original-Nachricht -------- > Datum: Wed, 08 Jun 2011 16:27:22 +0200 > Von: Jean-Claude Repetto <[email protected]> > An: Armin Burger <[email protected]> > CC: [email protected] > Betreff: Re: [gdal-dev] gdal_translate - ECW format and non-UTM projections > Hi, > > I think there is a bug in gdalinfo, I already noticed this kind of > problem, for example > <http://osgeo-org.1803224.n2.nabble.com/gdal-dev-corner-coords-in-tif-vs-ecw-td5608144.html> > > You should file a bug at <http://trac.osgeo.org/gdal/> . > > Jean-Claude -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
