Re: [geos-devel] Writing a wrapper around LibGEOS

2023-03-08 Thread Regina Obe
Graham, Please do keep us posted on this with your trials and share your code. As a fellow member of the “not one of us” crowd, I am interested in pushing GEOS beyond the very confined geography domain. Thanks, Regina From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On

Re: [geos-devel] Writing a wrapper around LibGEOS

2023-03-08 Thread Graham Toal
On Wed, Mar 8, 2023 at 1:12 PM Martin Davis wrote: > As others have said on this thread, adding curve support to GEOS is likely > to be a big effort. > > My opinion is that to consider an extension of this magnitude, there needs > to be evidence that this initiative is feasible and sustainable

Re: [geos-devel] Writing a wrapper around LibGEOS

2023-03-08 Thread Martin Davis
Over the 20 year lifetime of GEOS there have been at least 6 developers involved at a deep algorithmic level (fixing bugs and design issues and contributing new and improved algorithms). And now that GEOS is so mature and widely used, I'd say the bar is higher. Anyway, the key point is: let's

Re: [geos-devel] Writing a wrapper around LibGEOS

2023-03-08 Thread Daniel Baston
> > My opinion is that to consider an extension of this magnitude, there needs > to be evidence that this initiative is feasible and sustainable over the > long term (at least 10 years). A good way to demonstrate this is a separate > project that extends GEOS with support for representing curves,

Re: [geos-devel] Writing a wrapper around LibGEOS

2023-03-08 Thread Martin Davis
As others have said on this thread, adding curve support to GEOS is likely to be a big effort. My opinion is that to consider an extension of this magnitude, there needs to be evidence that this initiative is feasible and sustainable over the long term (at least 10 years). A good way to