Elliptical Curve, NURBS, Clothoid, Spiral Curve

Daniel Baston dbaston at gmail.com
Thu Oct 29 18:09:22 PDT 2026


Jeroen,

Perhaps the need has been evident to you for a long time, but I'm not aware
that it's ever been communicated to the project, so you may have to educate
us a bit. What software are these users working with that interfaces with
GEOS, and what operations do they expect GEOS to perform?

Dan

On Thu, Oct 29, 2026 at 3:06 AM Jeroen Bloemscheer <
jeroen.bloemscheer at merkator.com> wrote:

> Dan,
>
> The impetus is simple. Engineers in rail, road design and flight-path
> planning work with transition curves every day, and for about ten years
> they've had to linearise them before GEOS could touch them. The need has
> been evident for a long time. What was missing was someone to write the
> code. GEOS is an OSGeo project, and OSGeo works as a do-ocracy. So I wrote
> it.
>
> ISO 13249-3 already defines these types, so GEOS doesn't have to invent a
> model, only implement the standard. #1566 deliberately keeps the scope
> small: I/O, length, envelope and linearisation for the clothoid.
> Unsupported operations throw rather than guess, so nothing silently
> produces the wrong answer.
>
> On architecture, that's exactly why I raised the segment hierarchy
> question before going further. I'd rather we agree the design now than bolt
> types on later.
>
> On maintenance, I'm not handing this over and walking away. I'll maintain
> the curve code and respond to issues with it.
>
> The three fixes (fix/arc-segment-distance, fix/arc-arc-distance,
> fix/envelope-touching-distance) affect the existing CircularString code,
> and I'll submit those as separate PRs regardless.
>
> So I don't think the open question is whether there's a need. The need
> predates the implementation by years. The useful question is what stands
> between #1566 and acceptance: the design, the scope, or maintenance. If one
> of those is the blocker, tell me which and I'll address it.
>
> Thanks,
> Jeroen
>
>
> ------------------------------
> *Jeroen Bloemscheer*
> Geo-IT Consultant
> Zaltbommel
>
> *[image: Merkator] *
>
> m: +31 (0)6 478 728 18
> e:  jeroen.bloemscheer at merkator.com
>
>
> Merkator BV
> Hogeweg 137a
> 5301 LL Zaltbommel(NL)
> www.merkator.com [image: LinkedIn]
> <https://www.linkedin.com/company/2400587>
> ------------------------------
>
> 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geos-devel/attachments/20261029/ce2ac400/attachment-0001.htm>


More information about the geos-devel mailing list