Hi Even,
I'm really appreciative of your help! And yes, gt[2] = gt[4] = 0 :) Here's
the code that I've written thus far (for those that are interested --
hopefully I'm not mistaken in my coding!):
def select(filename, x1, y1, x2, y2):
dataset = gdal.Open( filename, GA_ReadOnly )
colStart
Hi guys,
Working with GDAL 1.6.1, I got some strange result. It is not very
compromising, because the result is OK, but it shall be enhanced, or I shall
learn how to use it.
giving the following command :
gdalwarp -t_srs
Hi,
I had a similar problem with german umlauts not to long ago. I solved it
by specifing the client encodung in the postgresql connection string
example:
ogr2ogr -f PostgreSQL PG:dbname=mydb options='-c
client_encoding=latin1' .
hope it helps,
nico
Alexandre Dube schrieb:
Hi,
I need
If you use DATUM[GRS_1980 instead of DATUM[D_GRS_1980 it might work. See
http://spatialreference.org for
more info.
---Original Message---
From: Matthieu Rigal ri...@rapideye.de
Subject: [gdal-dev] non-fully conform output of gdalwarp
Sent: May 29 '09 05:11
Hi guys,
Hi Ivan,
I should have mentioned it, but I already tested it, by changing the DATUM,
the file is nicely projected, but the header still has this unknown and
unnamed fields...
Could it actually come from my GEOS or proj4 libraries ? Or can it only come
from GDAL ?
Best regards,
Matthieu
On
Hi list,
I'm trying to convert the attached virtual file into a regular geo-tiff.
Note that the dataset defines both a geo-transform and GCPs but
they have different projections.
After conversion if I call gdalinfo on the result file I get
$ gdalinfo out.tif
Driver: GTiff/GeoTIFF
Files:out.tif
Pooven,
We clearly miss a specific documentation for the GDAL Python bindings
(contributions welcome !). The OGR ones have docstring help generated from
C++ doxygen.
Generally, the Python API is close to the C++ one that is documented on the
website, but there are a few specific methods like
On May 29, 2009, at 12:59 PM, Even Rouault wrote:
* Someone brought my attention to the following site,
http://www.gis.usu.edu/~chrisg/python/, that has very interesting
slides and
exercices about how to use GDAL/OGR in Python.
That's awesome! We need to spread links to that everywhere
Antonio,
The behaviour you get is more or less expected. Generally in GDAL, either you
have a geotransform with its projection, either you have GCPs with their
associated projection. But having both at the same time isn't really
supported. The fact that the VRT seems to accept that is more an
Matthieu,
I can also reproduce it with GDAL 1.6.1, but no longer with GDAL 1.7.0dev.
Significatn changes have been done in trunk concerning preservation of
citations in the GeoTIFF driver. The most significant for your use case is
probably http://trac.osgeo.org/gdal/changeset/15993 that adds
Il giorno Fri, 29 May 2009 20:17:07 +0200
Even Rouault even.roua...@mines-paris.org ha scritto:
Antonio,
The behaviour you get is more or less expected. Generally in GDAL,
either you have a geotransform with its projection, either you have
GCPs with their associated projection. But having
11 matches
Mail list logo
