On Tue, Oct 9, 2012 at 11:07 AM, Chris Barker wrote:
> On Sun, Oct 7, 2012 at 8:33 PM, Tim Keitt wrote:
>
>>> cool! though I"m a little confused as to how this fits with OGR.
>>
>> OGR is used for i/o.
>>
>
> I see -- so you've written something like the triangle command line
> utility, but with
On Sun, Oct 7, 2012 at 8:33 PM, Tim Keitt wrote:
>> cool! though I"m a little confused as to how this fits with OGR.
>
> OGR is used for i/o.
>
I see -- so you've written something like the triangle command line
utility, but with OGR for IO, so you don't need to use triangles
particular data fil
On Fri, Oct 5, 2012 at 11:11 AM, Chris Barker wrote:
> On Thu, Oct 4, 2012 at 6:31 PM, Tim Keitt wrote:
>> Just letting folks know that we've released an OGR wrapper for the
>> Triangle library. It would be great if folks could test it. I could
>> also use some help improving the OGR bits.
>
> co
> We've written a wrapper around triangle for Python (anyone feel free
> to send me a note if you're interested), and we ended up handling that
> by spawning another process to run triangle in -- but that has
> performance issues (copying data around) which would be nice to avoid.
>
> If only tri
On Thu, Oct 4, 2012 at 6:31 PM, Tim Keitt wrote:
> Just letting folks know that we've released an OGR wrapper for the
> Triangle library. It would be great if folks could test it. I could
> also use some help improving the OGR bits.
cool! though I"m a little confused as to how this fits with OGR.
Just letting folks know that we've released an OGR wrapper for the
Triangle library. It would be great if folks could test it. I could
also use some help improving the OGR bits.
Cheers,
THK
https://bitbucket.org/keittlab/meshpoly
--
Timothy H. Keitt
http://www.keittlab.org/
