RE: [gdal-dev] Difference in output using gdal_translate from FWTools shell and cmd window

2011-12-01 Thread Anne Brookes
ecember 2011 11:00 To: gdal-dev@lists.osgeo.org Subject: Re: [gdal-dev] Difference in output using gdal_translate from FWTools shell and cmd window Hi, are you sure that the same libraries (proj, epsg et. al.) are available under both cirumstances? Do you have access to proj and epsg codes in pl

Re: [gdal-dev] Difference in output using gdal_translate from FWTools shell and cmd window

2011-12-01 Thread Frank Broniewski
Hi, are you sure that the same libraries (proj, epsg et. al.) are available under both cirumstances? Do you have access to proj and epsg codes in plain cmd? That's where I would start to investigate ... btw. I think the osgeo4w package is more recent than the fwtools build, so might also hav

[gdal-dev] Difference in output using gdal_translate from FWTools shell and cmd window

2011-12-01 Thread Anne Brookes
Hello, When I run gdalinfo and gdal_translate commands from the FWTools Shell (on Windows) the output is different to when I run the same commands from an ordinary cmd window (or from a python script). The difference is in the PROJCS, DATUM and SPHEROID metadata. Here is the (correct) output fr