Ok, this is the script made up yesterday:
http://paste.pocoo.org/show/336317/
and an example script which is using it:
http://paste.pocoo.org/show/336318/
The convert_datasource funtion can convert an input datasource from one
format to another, and in an optional step do a coordinate
transfor
On 11-02-10 01:43 PM, Hailey Eckstrand wrote:
But the stays the same:
ERROR 1: Too many points (440 out of 441) failed to transform,
unable to compute output bounds.
Hailey,
I tried with your file and with debugging on and saw the following message:
WARP: Recompute out extent with CHECK_WIT
Le jeudi 10 février 2011 09:09:45, Frank Broniewski a écrit :
> Even,
>
> thank you for your verbose and helpful answer!
>
> Am 09.02.2011 20:24, schrieb Even Rouault:
> > Several points :
> >
> > 1) The implementation of Layer.GetFeature() is only efficient for just a
> > few drivers (shapefile
My GDAL package version:
GDAL 1.9dev, released 2011/01/18
My input file is a NETCDF file which contains global average temperatures.
This is the gdalinfo spew:
Driver: netCDF/Network Common Data Format
Files: gfdl_cm2_1-sresa2-tas-run1-2041-2070.nc
Size is 144, 88
Coordinate System is `'
Origin =
Hi GDAL/OGR Devs,
This is a reminder that the Montreal Code Sprint will be taking place on
March 15-18, 2011. We've already got a few participants for GDAL/OGR and
there is still room for more.
If you plan on participating then please, please, please add your name
to the list in the wiki to
On 02/10/2011 10:28 AM, Frank Broniewski wrote:
Hi Ari,
thanks for your answer. I am not sure what you mean with return a
geometry in scalar context, and I don't have a sound understanding of
perl, SWIG and the impacts of it on the objects created by the bindings.
A very quick google search
Hi Ari,
thanks for your answer. I am not sure what you mean with return a
geometry in scalar context, and I don't have a sound understanding of
perl, SWIG and the impacts of it on the objects created by the bindings.
A very quick google search didn't reveal a good explanation of what a
scala
Even,
thank you for your verbose and helpful answer!
Am 09.02.2011 20:24, schrieb Even Rouault:
Several points :
1) The implementation of Layer.GetFeature() is only efficient for just a few
drivers (shapefile). Other drivers will need to sequentially read from the first
feature ... So use GetN
