Elliptical Curve, NURBS, Clothoid, Spiral Curve
Daniel Baston
dbaston at gmail.com
Fri Oct 30 10:21:31 PDT 2026
It would be great if we could go back in time and have a common
geometry representation that's used by everyone, but that's not how
the ecosystem developed. The downstream projects I'm familiar with
have their own geometry representations that are converted to GEOS to
perform a particular spatial operation. In the absence of support for
spatial operations on these types, a GEOS in-memory representation
provides no real value. You say that "the usual answer is to linearise
them before GEOS sees them" but you're not saying what software wants
to use GEOS to work with these types, or what operations it wants to
perform that currently require linearization.
Dan
On Fri, Oct 30, 2026 at 1:03 PM Jeroen Bloemscheer
<jeroen.bloemscheer at merkator.com> wrote:
>
> Hi Dan,
>
> Thanks, that's a fair question.
>
> I think the question is less whether these curves are "GIS" in the traditional sense, and more whether GEOS should be able to represent and operate on geometry that already exists in the systems built on top of it. PostGIS, Shapely, and QGIS all sit on GEOS, while rail, road, and similar engineering workflows already use these transition geometries. Today the usual answer is to linearise them before GEOS sees them.
>
> That seems like the wrong boundary to me. SQL/MM already defines the geometry model, so GEOS does not need to invent one. If GEOS implements that model once, downstream projects can share the same representation and behaviour instead of each adding its own approximation or adapter.
>
> I'm not proposing that every operation has to arrive at once. #1566 is deliberately small: representation, I/O, length, envelope, and linearisation, with unsupported operations throwing rather than guessing. That gives downstream projects something they can build on without pretending GEOS already supports more than it does.
>
> And on maintenance, I'm not proposing to drop this on the existing maintainers. I'll maintain the curve code and respond to issues with it.
>
> So for me the useful question is: is representing these standardized curve types, and providing a path for downstream projects to use them without first destroying the curve information, within GEOS's scope? I think it is.
>
> ________________________________
>
> From: Daniel Baston <dbaston at gmail.com>
> Sent: Friday, October 30, 2026 2:28 PM
> To: Jeroen Bloemscheer <jeroen.bloemscheer at merkator.com>
> Cc: Nyall Dawson <nyall.dawson at gmail.com>; geos-devel at lists.osgeo.org <geos-devel at lists.osgeo.org>
> Subject: Re: Elliptical Curve, NURBS, Clothoid, Spiral Curve
>
> The primary question for me is not about the quality or provenance of the PRs, but whether it makes sense for GEOS to handle these types at all.
>
> I'd rather not derail that discussion with an AI debate, although I can see that it will be probably be necessary under a separate thread.
>
> Dan
>
> On Fri, Oct 30, 2026 at 7:15 AM Jeroen Bloemscheer <jeroen.bloemscheer at merkator.com> wrote:
>
> I think there are two separate discussions here: whether GEOS should have a policy around LLM-assisted development, and whether this particular contribution meets GEOS quality standards.
>
> For the latter, the code is not being submitted on faith. The implementation has been validated using proofs and working ArcGIS Pro notebooks, and the results are reproducible and independently verifiable.
>
> If there are concerns about the algorithm, implementation details, performance, or maintainability, I'm happy to discuss those. But I don't think "vibe coded" is an accurate characterization of the work.
>
> Jeroen
>
> ________________________________
> Jeroen Bloemscheer
> Geo-IT Consultant
> Zaltbommel
>
>
> m: +31 (0)6 478 728 18
> e: jeroen.bloemscheer at merkator.com
>
>
> Merkator BV
> Hogeweg 137a
> 5301 LL Zaltbommel(NL)
> www.merkator.com
> ________________________________
>
> This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing.
More information about the geos-devel
mailing list