Hi all,
I apologize if this specific issue has been addressed before. I've checked the
listserve and didn't see anything right off. I'm sure I'm doing something
stupid ...
Previously, I had been compiling GDAL from trunk using VS2005 (VC8) and Python
2.5. I've recently gone to Python 2.6 (3
On 27/10/2010 11:42, Jean-Claude Repetto wrote:
Le 27/10/2010 11:18, Jean-Claude Repetto a écrit :
Le 27/10/2010 10:32, Paul Meems a écrit :
I'm now on the gdal_warp track again. But I can't produce a PNG file.
When I use -ot PNG I get this list of supported file formats
Because the syntax i
Le 27/10/2010 11:18, Jean-Claude Repetto a écrit :
Le 27/10/2010 10:32, Paul Meems a écrit :
I'm now on the gdal_warp track again. But I can't produce a PNG file.
When I use -ot PNG I get this list of supported file formats
Because the syntax is "-of ONG", not "-ot PNG".
"-of PNG" , of cou
Le 27/10/2010 10:32, Paul Meems a écrit :
I'm now on the gdal_warp track again. But I can't produce a PNG file.
When I use -ot PNG I get this list of supported file formats
Because the syntax is "-of ONG", not "-ot PNG".
Jean-Claude
___
gdal-dev mai
Hermann,
You're right the size difference is because of PNG8 or PNG24.
I'm now on the gdal_warp track again. But I can't produce a PNG file. When I
use -ot PNG I get this list of supported file formats:
VRT: Virtual Raster
GTiff: GeoTIFF
NITF: National Imagery Transmission Format
HFA: Erd
Ivan,
in my experience it is often enough to keep a ref to the dataset to
avoid these segfaults. However, my experience is more with gdal (raster)
than with ogr (vector), so ymmv, and some experimenting might be
required. Just start with keeping a ds reference, if that doesn't work,
go furthe