<div dir="ltr"><div><div><div><div><div><div><div>Dear all,<br><br></div>It seems that with the latest release the <b>processing.alghelp('gladogr:cliprasterbymasklayer') </b>arguments have more than doubled from 7 to 16 arguments and the <a href="https://docs.qgis.org/2.6/en/docs/user_manual/processing_algs/gdalogr/gdal_extraction/cliprasterbymasklayer.html">documents</a> have not yet been updated to reflect this substantial increase in parameters.<br><br></div>The previous version that I was comfortable with was :<br>
<p class="MsoNormal"><font size="2"><span>ALGORITHM:
Clip raster by mask layer <span> </span></span></font></p><font size="2">
</font><p class="MsoNormal" style="text-indent:36pt"><font size="2"><span>INPUT <ParameterRaster> <span> </span></span></font></p><font size="2">
</font><p class="MsoNormal" style="text-indent:36pt"><font size="2"><span>MASK <ParameterVector> <span> <br></span></span></font></p><font size="2">
</font><p class="MsoNormal" style="text-indent:36pt"><font size="2"><span>NO_DATA <ParameterString> <span> <br></span></span></font></p><font size="2">
</font><p class="MsoNormal" style="text-indent:36pt"><font size="2"><span>ALPHA_BAND <ParameterBoolean> <span> </span></span></font></p><font size="2">
</font><p class="MsoNormal" style="text-indent:36pt"><font size="2"><span>KEEP_RESOLUTION <ParameterBoolean> <span> </span></span></font></p><font size="2">
</font><p class="MsoNormal" style="text-indent:36pt"><font size="2"><span>EXTRA <ParameterString> <span> <br></span></span></font></p><font size="2">
</font><p class="MsoNormal" style="text-indent:36pt"><font size="2"><span>OUTPUT <OutputRaster>(7)</span></font></p><font size="2">
</font><br></div>Which has now seemed to have increased to: <br>ALGORITHM: Clip raster by mask layer<br> INPUT <ParameterRaster> (1)<br>
MASK <ParameterVector> (2)<br>
NO_DATA <ParameterString> (3)<br>
ALPHA_BAND <ParameterBoolean> (4)<br>
CROP_TO_CUTLINE <ParameterBoolean> (5)
<br> KEEP_RESOLUTION <ParameterBoolean> (6)<br>
RTYPE <ParameterSelection>
(7)<br> COMPRESS <ParameterSelection> (8)<br>
JPEGCOMPRESSION <ParameterNumber> (9)
<br> ZLEVEL <ParameterNumber> (10)<br>
PREDICTOR <ParameterNumber> (11)<br>
TILED <ParameterBoolean> (12)<br>
BIGTIFF <ParameterSelection> (13)<br>
TFW <ParameterBoolean> (14)<br>
EXTRA <ParameterString> (15)<br>
OUTPUT <OutputRaster> (16)<br><br></div><div>Including:<br></div><div><br>RTYPE(Output raster type)<br> 0 - Byte<br> 1 - Int16<br> 2 - UInt16<br> 3 - UInt32<br> 4 - Int32<br> 5 - Float32<br> 6 - Float64<br>COMPRESS(GeoTIFF options. Compression type:)<br> 0 - NONE<br> 1 - JPEG<br> 2 - LZW<br> 3 - PACKBITS<br> 4 - DEFLATE<br>BIGTIFF(Control whether the created file is a BigTIFF or a classic TIFF)<br> 0 - <br> 1 - YES<br> 2 - NO<br> 3 - IF_NEEDED<br> 4 - IF_SAFER<br><br><br></div>If I run (without the [n]):<br><br> <b>>>> processing.runalg('gdalogr:cliprasterbymasklayer', </b>[1] <b>rstr, </b>[2]<b> shp, </b>[3] <b>"", </b>[4]<b> False, </b>[5] <b>True, </b>[6] <b>True, </b>[7]<b> 1, </b>[8]<b> 1, </b>[9]<b> 1, </b>[10] <b>1, </b>[11] <b>1, </b>[12] <b>True, </b>[13] <b>0, </b>[14] <b>True, </b>[15] <b>"", </b>[16]<b> rstrOutput+str(rstr))<br><br></b></div><div>that's ('gdalogr:cliprasterbymasklayer', <b>(1)</b> rstr input, <b>(2) </b>shp to clip, <b>(3)</b> no data = "", <b>(4) </b>alpha transparency band = false, <b>(5) </b>crop to cutline = true, <b>(6) </b>keep resolution = true, <b>(7) </b>RTYPE (0 is not allowed so I went with 1), <b>(8)</b> Compress =1 as 0 not allowed, <b>(9)</b> Jpegcompression = 1, <b>(10)</b>, Z level = 1, <b>(11)</b> Predictor = 1, <b>(12) </b>Tiled = True, <b>(13)</b> Bigtiff = 0, <b>(14) </b>'TFW' = True, <b>(15) </b>extra = "" and <b>(16)</b> I specify my output path....)<br></div><div><b><br></b></div><div>I can get an output but I can only create a binary mask.<br></div><div><br></div>Could anyone please offer some insights on where I'm going wrong and how I can take advantage of this powerful function once again please? <br><br></div><div>I would like to suggest too that 16 options seems like a bit much for clipping a raster and it makes debugging very difficult. Is there a simpler version that could be implemented? This is an incredibly useful function. It would great to see the documents updated too.<br><br></div><div>Is there anyone out there who can share some information of these very different options please?<br></div><div><br></div>Thank you,<br></div>Seán Lynch<br><div><div><div><div><div><div><div><div><div><div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div><div>M.Sc. Coastal & Marine Environments (NUIG, 2015)<br></div>M.Sc. GIS & Remote Sensing (UCC, 2014)<br></div>B.A. Geography & Economics (UCC, 2011)<br></div></div></div>
</div></div></div></div></div></div></div></div></div></div></div>