No, my mistake. I think there might be an issue with the processing wrapper for gdal:warp. It takes the argument TARGET_EXTENT, and uses that for the GDAL arg "-te". However, it then tries to add in extent details, and I think there might be an incorrect variable name. In warp.py from line 190:
arguments.append(rasterExtent.xMinimum()) arguments.append(rasterExtent.yMinimum()) arguments.append(rasterExtent.xMaximum()) arguments.append(rasterExtent.yMaximum()) I'm not sure "rasterExtents" is defined, but substituting the more plausible "extent" gets no extent value out. Is this an issue, or are the Python bindings for Processing's gdal:warpreproject working for others? Thanks Tom ----- Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon -- Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html _______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
