Feature request #15746

Processing: enable GDALWARP_IGNORE_BAD_CUTLINE YES by default

Added by Paolo Cavallini almost 4 years ago. Updated almost 4 years ago.

Status:Closed
Priority:Normal
Assignee:Victor Olaya
Category:Processing/GDAL
Pull Request or Patch supplied:No Resolution:
Easy fix?:No Copied to github as #:23668

Description

Currently gdalwarp fails in Processing and elsewhere:

gdalwarp -ot Float32 -q -of GTiff -cutline watersheds.shp -co
COMPRESS=DEFLATE -co PREDICTOR=1 -co ZLEVEL=6 -wo OPTIMIZE_SIZE=TRUE
dem25.tif OUTPUT.tif

and I get

GDAL command output:
Warning 1: Self-intersection at or near point 583.00000000000182 326
ERROR 1: Cutline is not valid after transformation

A reasonable solution is to add GDALWARP_IGNORE_BAD_CUTLINE YES by default, and perhaps an extra
option to disable it.

See https://lists.osgeo.org/pipermail/gdal-dev/2016-October/045341.html for a detailed explanation.

Associated revisions

Revision 323c6582
Added by Alexander Bruy almost 4 years ago

[processing] add workaround for GDAL regression with cutlines (fix #15746)

History

#1 Updated by Even Rouault almost 4 years ago

The above mentionned GDAL 2.1.0 regression will be fixed in the upcomping GDAL 2.1.2 per https://trac.osgeo.org/gdal/ticket/6694

#2 Updated by Alexander Bruy almost 4 years ago

Fix pushed to master. Please test

#3 Updated by Alexander Bruy almost 4 years ago

  • Status changed from Open to Closed

Also available in: Atom PDF