<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>At the time I created the ticket I had created a workaround that uses gdal_translate to clip a rectangular window and gdal_rasterize to burn an inverse image of the vector. Interested folks can email me for the script (does the list take attachments?). The script makes some assumptions about your data type (e.g. 0 is assigned as nodata) but you can change those assumptions to suit your needs.<div><br></div><div>I plan to make the feature request I mentioned in #3947.</div><div><br></div><div>-marius</div><div><br><div><div id="SkyDrivePlaceholder"></div>> To: gdal-dev@lists.osgeo.org<br>> From: jukka.rahkonen@mmmtike.fi<br>> Date: Fri, 26 Oct 2012 09:05:06 +0000<br>> Subject: Re: [gdal-dev] Question about using crop_to_cutline<br>> <br>> Even Rouault <even.rouault <at> mines-paris.org> writes:<br>> <br>> <br>> > This is the very same topic that is discussed in <br>> > http://trac.osgeo.org/gdal/ticket/3947 . There's no solution to your problem, <br>> > but some background discussion that explains the current behaviour.<br>> <br>> This is close to a problem I had once with creating mosaics from individually<br>> warped orthophotos. Accurately calculated extents make pixels to slide a bit and<br>> individually warped images do not share any common canvas for their pixels. I<br>> sketched a plan for forcing the warped image to use a common canvas and found a<br>> python guy to make a program. I have been satisfied with the result.<br>> <br>> I believe that the same solution will work for you. You must widen the -te<br>> parameters that is calculated by crop_to_cutline to each direction so that they<br>> match exactly with some pixel row and line of the original image. See figures 3,<br>> 4, and 5 in http://www.scangis.org/scangis2007/papers/r3_rahkonen.pdf. The<br>> python code is there too. Without understanding anything about programming I<br>> suppose that the job is done with this:<br>> <br>> minmax = get_minmax(tm32_coords)<br>> minmax_wider = [<br>> (int(math.floor(minmax[0][0])), int(math.floor(minmax[0][1]))),<br>> (int(math.ceil (minmax[1][0])), int(math.ceil (minmax[1][1]))),<br>> ]<br>> <br>> log("Extents (min,max): " + str(minmax), outfilename)<br>> log("Widened extents (min,max): " + str(minmax_wider), outfilename)<br>> <br>> -Jukka Rahkonen-<br>> <br>> _______________________________________________<br>> gdal-dev mailing list<br>> gdal-dev@lists.osgeo.org<br>> http://lists.osgeo.org/mailman/listinfo/gdal-dev<br></div></div> </div></body>
</html>