knudby,
According to http://gdal.org/formats_list.html and
http://gdal.org/frmt_various.html#Envisat you cannot get the projection
information but will be able to read GCPs with GDALDataset::GetGCPs().
On Mon, Feb 22, 2010 at 5:40 AM, knudby wrote:
>
> Hi, I'm trying to read AATSR data in ESA's
Hi, I'm trying to read AATSR data in ESA's N1 format. Supposedly gdal can do
this, but when I open my files I get no projection or geotransform
information. Is this a known issue, or am I doing something wrong. If I'm
doing something wrong, can someone give me a quick tip on how to get the
informa
Hi, did you ever get a response to this? I'm having a problem reading L1
AATSR data (.N1 format), I get no projection or geotransform information at
all.
Anders
--
View this message in context:
http://n2.nabble.com/gdal-does-not-read-ENVISAT-N1-files-correctly-tp3641025p4609398.html
Sent from t
Hum, I think you have regenerated swig/python/extensions/gdal_wrap.cpp with
your own swig version (which is probably too old), as the official version of
gdal_wrap.cpp in 1.7.1 has lines that don't match with your error message.
Try restoring the official files in swig/python/extensions and
s
Sounds logical, I already had a weired feeling copying the files just like this.
OK, I tried your advice, but I got a long list of errors. Doing the same with
2.6 works fine.
$ sudo /usr/bin/python3.1 setup.py install
running install
running build
running build_py
running build_ext
building 'os
Thomas,
you can't use the python package compiled with a python version with another
python version.
So try the following :
cd /path/to/gdal_source_tree/swig/python
sudo /path/to/your/python3.1/bin/python setup.py install
Le Sunday 21 February 2010 23:00:24 Thomas Maschler, vous avez écrit :
>
Hi,
I am trying to get Gdal 1.7.1 running with Python3.1 since I was reading that
this is possible now, but somehow it does not work.
I am using Ubuntu 9.10 having, python2.6 and python3.1 installed.
I compiled gdal from source. The packages were placed in the 2.6 folder and
gdal runs fine in
Jukka Rahkonen wrote:
Frank wrote:
Also the extents reported by gdalinfo are the widest possible extents
and if
those are to be used only UL coordinated can be used as it. For
other three
corners there is a need to minus one pixel size in one or both axis
directions.
The lower right co
Frank wrote:
>> Also the extents reported by gdalinfo are the widest possible extents
and if
>> those are to be used only UL coordinated can be used as it. For
other three
>> corners there is a need to minus one pixel size in one or both axis
directions.
> The lower right corner reported by
