Frank, Howard and Schuyler and all,<br>
<br>
<div><span class="gmail_quote">On 9/18/05, <b class="gmail_sendername">Frank Warmerdam</b> <<a href="mailto:warmerdam@pobox.com">warmerdam@pobox.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>I'm afraid the Distance method didn't make it into the OGR Python bindings<br>
</blockquote></div>
<br>
Thanks for your all your suggestions. I added the Distance
function to ogr.py as Frank suggested. The try/except block suggested
by Howard is a really good idea since it will ensure backwards
compatibility.<br>
<br>
So as I was going through the methods of the Geometry class, I
noticed that there were a bunch of them (GetPointCount, GetX, GetY,
GetZ, SetPoint, AddPoint, more?) that aren't documented in the official
OGRGeometry docs. Are the python bindings that significantly
different than the C++ methods? If so, It might be worth considering
using a tool like epydoc to create GDAL/OGR documentation specifically
for python. I'd be willing to head this up if there were significant
interest in doing so.<br>
<br>
-- <br>Matt Perry<br><a href="mailto:perrygeo@gmail.com">perrygeo@gmail.com</a><br><a href="http://www.perrygeo.net">http://www.perrygeo.net</a>