Thx for your tip Ben.<br>I have replied to myself a minute ago with the solution of my problem :)<br>1.4.4 looks for a .dat file while 1.5.0 looks for a .wkt file and I'm linking GDAL_DATA to the bad one... <br><br>Regards,<br>
Daniele<br><br><div class="gmail_quote">On Feb 12, 2008 3:27 PM, Collins, Benjamin <<a href="mailto:collinsb@mitre.org">collinsb@mitre.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">>-----Original Message-----<br>>From: Daniele Romagnoli<br>>As an instance I used gdalinfo from fwtools 2.0.4 on a ECW<br>>file and I obtained this Coordinate System (partial copy and paste).<br>
</div><div class="Ih2E3d">....<br>>Using "my" gdalinfo I obtain the classic empty string.<br><br></div>Daniele,<br><br>Recently I got bit with a similar problem: fwtools (v2.0.x) reported a<br>projection that my in-house compiled version was not seeing (on a<br>
JP2KAK-driven dataset). In my case there was an ".aux.xml" for the<br>file. FWTools is compiled with PAM overrides turned on by default,<br>where the default build from ./configure is not (v1.5.0). One way to<br>
turn this on at runtime for the default build (at least for JP2 w/<br>Kakadu) is to set the environment variable GDAL_PAM_ENABLED (or<br>--config option) to YES.<br><br>Of course, I have no idea if this is applicable for ECW datasets.<br>
<br>Good luck!<br><font color="#888888">--<br>Ben<br></font></blockquote></div><br><br clear="all"><br>-- <br>-------------------------------------------------------<br>Eng. Daniele Romagnoli <br>Software Engineer<br><br>
GeoSolutions S.A.S.<br>Via Carignoni 51<br>55041 Camaiore (LU)<br>Italy<br><br>phone: +39 0584983027<br>fax: +39 0584983027<br>mob: +39 328 0559267<br><br><br><a href="http://www.geo-solutions.it">http://www.geo-solutions.it</a><br>
<br>-------------------------------------------------------<br>