<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">Right, it would need some kung-fu across QGIS-GEOS python bindings. It</div>
was never really a top priority for me since QgsGeometry exposes the<br>
most important GEOS geometry algorithms.</blockquote><div><br></div>I would like to extend it, to include the linearref methods exposed by the C API:<br> - GEOSInterpolate<br>(- GEOSInterpolateNormalized)<br> - GEOSProject<br>
(- GEOSProjectNormalized)</div><div class="gmail_quote"><br></div><div class="gmail_quote">and other buffer methods like GEOSSingleSidedBuffer<div><span style="background-color:rgb(255,255,255);color:rgb(51,51,51);font-family:'Bitstream Vera Sans Mono','Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"><br>
</span></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">That's probably the easiest thing right now. Internally, QgsGeometry</div>
is by default stored in WKB anyway.<br></blockquote><div><br></div><div>For now I will use the geos_c lib throug ctypes, but supporting some more GEOS C/API methods directly from C++ would remove a lot of overhead and would speed up performance, obviously.</div>
<div><br></div><div>giovanni</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
Martin<br>
</font></span></blockquote></div><br>