<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 7, 2015 at 4:32 AM, Moritz Lennert <span dir="ltr"><<a href="mailto:mlennert@club.worldonline.be" target="_blank">mlennert@club.worldonline.be</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Of course<br>
<a href="https://trac.osgeo.org/grass/ticket/2734" rel="noreferrer" target="_blank">https://trac.osgeo.org/grass/ticket/2734</a><br>
remains - will you submit that change?<br>
</blockquote>
<br></span>
I have the feeling that the second proposed solution, i.e. "introduce a 2D version of the Vect_point_in_box function which checks x and y only" is the better long-run solution.</blockquote></div><br></div><div class="gmail_extra">Continuing discussion in Trac.<br></div><div class="gmail_extra"><br><a href="https://trac.osgeo.org/grass/ticket/2734#comment:1">https://trac.osgeo.org/grass/ticket/2734#comment:1</a></div></div>