Hi
it seems that it has to do something with no-data areas. gdal_contour tries
to calculate all the contours from approx. 450m up to my no-data value
-3.4...e+38.
I use no gdal_fillnodata.py to fill the no data areas.
So I still think there is a slighly different behaviour of gdal since my
last
Another option is to use GMT grdcontour program
gmt grdcontour 6800_2480.tif -C1 -Dlixo.dat -V
it creates a ~8.3 Mb ascii file with a memory consuption of ~50 Mb (Task
manager info) that you can later convert to shp with ogr2ogr
Stefan,
I have problems creating contours with gdal_contour
Stefan,
> I have problems creating contours with gdal_contour and some tiff files.
> The following command
>
> gdal_contour -i 1.0 6800_2480.tif out.shp
>
> ends with "0Killed" after eating all memory and all swap. It happens with
> gdal 1.11 and gdal-master. It did work on a Ubuntu 10.04 machin
Hi
I have problems creating contours with gdal_contour and some tiff files.
The following command
gdal_contour -i 1.0 6800_2480.tif out.shp
ends with "0Killed" after eating all memory and all swap. It happens with
gdal 1.11 and gdal-master. It did work on a Ubuntu 10.04 machine (as far as
I reme
