I am posting this again without test files attached due the 50K size limit. Anyone who wants to see them, please contact me directly.
--
We have observed interesting anomaly with gdal_contour when one of the fixed
levels is zero.
If the zero contour is expressed as 0.0 (or indeed 0.0000) gdal_contour replies
with the standard Usage message (see below). If the zero contour is expressed
as the integer 0 (or 0.00000001) it works and produces the expected contours.
FAILURE WITH FIXED LEVEL == 0.0
nie...@shiva:~$ gdal_contour -fl -0.5 0.0 0.5 test_file.tif test_file.shp
Usage: gdal_contour [-b <band>] [-a <attribute_name>] [-3d] [-inodata]
[-snodata n] [-f <formatname>] [-i <interval>]
[-off <offset>] [-fl <level> <level>...]
[-nln <outlayername>]
<src_filename> <dst_filename>
SUCCESS WITH FIXED LEVEL == 0
nie...@shiva:~$ gdal_contour -fl -0.5 0 0.5 test_file.tif test_file.shp
0...10...20...30...40...50...60...70...80...90...100 - done.
Has anyone else seen this problem?
Cheers
Ole
Dr Ole Nielsen
Numerical Modeller
Australia-Indonesia Facility for Disaster Reduction
Mobile: +62 811 820 4637 | Phone: +62 21 398 30088 x1007 | Fax: +62 21 398 30068
[cid:[email protected]]
<<inline: image001.jpg>>
_______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
