Elliptical Curve, NURBS, Clothoid, Spiral Curve
Daniel Baston
dbaston at gmail.com
Fri Oct 30 06:28:44 PDT 2026
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
>
>
>
> <https://outlook.office.com/bookwithme/user/23c7633d14994a4bbdc50bf6aec0b485@merkator.com?anonymous&ep=bwmEmailSignature>
> Book time to meet with me
> <https://outlook.office.com/bookwithme/user/23c7633d14994a4bbdc50bf6aec0b485@merkator.com?anonymous&ep=bwmEmailSignature>
>
>
> ------------------------------
> *From:* Nyall Dawson <nyall.dawson at gmail.com>
> *Sent:* Friday, October 30, 2026 3:30 AM
> *To:* Daniel Baston <dbaston at gmail.com>
> *Cc:* Jeroen Bloemscheer <jeroen.bloemscheer at merkator.com>;
> geos-devel at lists.osgeo.org <geos-devel at lists.osgeo.org>
> *Subject:* Re: Elliptical Curve, NURBS, Clothoid, Spiral Curve
>
> [U ontvang niet vaak e-mail van nyall.dawson at gmail.com. Meer informatie
> over waarom dit belangrijk is, vindt u op
> https://aka.ms/LearnAboutSenderIdentification]
>
> It's probably worth at least having some discussion about an LLM /
> agent usage policy for GEOS too, as merging these PRs would basically
> equate to GEOS becoming a "vibe coded" project.
>
> Nyall
>
> On Fri, 30 Oct 2026 at 11:25, Daniel Baston <dbaston at gmail.com> wrote:
> >
> > 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
> >>
> >>
> >> m: +31 (0)6 478 728 18
> >> e: jeroen.bloemscheer at merkator.com
> >>
> >>
> >> Merkator BV
> >> Hogeweg 137a
> >> 5301 LL Zaltbommel(NL)
> >>
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.merkator.com%2F&data=05%7C02%7Cjeroen.bloemscheer%40merkator.com%7Ca0427a027eba4756003708df362dccbb%7Ca17ec843af694e17a6fc3e803a903e14%7C0%7C0%7C639289242475755515%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=2tmmT%2FBIi%2Fo29xcYQ65y7Qtve9vXeIA5hyfoCNh9UcQ%3D&reserved=0
> <http://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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geos-devel/attachments/20261030/67ec3117/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 528 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/geos-devel/attachments/20261030/67ec3117/attachment-0001.png>
More information about the geos-devel
mailing list