<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>More nagging questions about GEOS Capi</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>I apologize for being a bit long-winded here.<BR>
<BR>
Recall I mentioned that Geometry.Union() does some short-circuit stuff<BR>
and then does the standard Overlay op stuff.<BR>
<BR>
However GEOS Capi GeomUnion doesn't appear to use Geometry.Union() at all and<BR>
goes straight for the Overlay operation.<BR>
<BR>
On closer inspection of Capi, I see there must have been a time when Geometry.Union() was done instead and that piece of code is now remarked out<BR>
So now looks like this<BR>
GeomAutoPtr g3 = BinaryOp(g1, g2, overlayOp(OverlayOp::opUNION));<BR>
return g3.release();<BR>
//Geometry *g3 = g1->Union(g2);<BR>
//return g3;<BR>
<BR>
Same deal with intersection, but the intersection one is not quite as big<BR>
of a concern since Geometry.intersection doesn't do much more than the BinaryOp call.<BR>
<BR>
Is there a performance reason why this was done? It seems to me slightly undesirable<BR>
to have CAPI do something differently than what one would be necessarily doing with the Core C++ api and I can only imagine most people using the GEOS C++ api would be hitting the Geometry.Union method (maybe not though).<BR>
<BR>
Thanks,<BR>
Regina<BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
The substance of this message, including any attachments, may be confidential, legally privileged and/or exempt from disclosure pursuant to Massachusetts law. It is intended solely for the addressee. If you received this in error, please contact the sender and delete the material from any computer.
</STRONG></P></BODY></HTML>
<P><hr size=1></P>
<P><STRONG><font size="2" color="339900"> Help make the earth a greener place. If at all possible resist printing this email and join us in saving paper. </p> <p> </font></STRONG></P>