[geos-devel] Writing a wrapper around LibGEOS

[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 see some real code for GEOS curves, and
then the cost/benefit tradeoff will be clearer.


On Wed, Mar 8, 2023 at 11:36 AM Daniel Baston <dbaston at gmail.com> wrote:

> 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, and
>> implementing a *significant* set of *native* operations on curves.  That
>> project should have at least two developers contributing algorithmic code
>> to it, to show that there is ability and desire to maintain such complex
>> code over the long term.
>>
>
> This seems a bit excessive. How much of GEOS has two developers involved
> in algorithmic development and committing to maintenance for > 10 years?
>
> Dan
> _______________________________________________
> geos-devel mailing list
> geos-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geos-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geos-devel/attachments/20230308/937fcd4a/attachment.htm>