Skip to content

WKT: name SQL/MM §4.2.1 curve types and refuse - #21

Merged
grootstebozewolf merged 1 commit into
developfrom
cursor/sqlmm-type-honesty-ccfa
Sep 2, 2026
Merged

grootstebozewolf merged 1 commit into
developfrom
cursor/sqlmm-type-honesty-ccfa

Conversation

@grootstebozewolf

Copy link
Copy Markdown
Owner

Prerequisites

  • I have written a descriptive pull-request title
  • I have verified that there are no overlapping pull-requests open
  • I have verified that I am following the existing coding patterns and practice as demonstrated in the repository.
  • I have provided test coverage for my change (where applicable)

Description

ST_Clothoid, ST_Circle, ST_GeodesicString, ST_NURBSCurve, ST_SpiralCurve, and ST_EllipticalCurve are instantiable ST_Curve subtypes in ISO/IEC 13249-3 §4.2.1. They are not optional extras. This reader used to call them Unknown type. That is a lie.

Named refuse, matching GEOS: the message cites §4.2.1 and does not say Unknown type. A genuine unknown token (NOTATYPE) still does. COMPOUNDCURVE (CLOTHOID …) hits the same refuse, not Unexpected token. CIRCLE does not steal CIRCULARSTRING (dim-suffix match, not IsTypeName).

No carrier. No flatten to LINESTRING. Do not remint 508. Type-9/10/11/12 reader PRs stay out.

Pins: CurveWktTest.SqlMmSection421TypesAreNamedRefusesNotUnknown (31 CurveWktTest passed locally).

Companion Proofs letter: grootstebozewolf/NetTopologySuite.Proofs#660 (ticket 38).

Open in Web Open in Cursor 

CLOTHOID, CIRCLE, GEODESICSTRING, NURBSCURVE, SPIRALCURVE, and
ELLIPTICALCURVE are instantiable ST_Curve subtypes, not unknown
extras. No carrier. CIRCLE does not steal CIRCULARSTRING.

Co-authored-by: jbloemscheer <jbloemscheer@gmail.com>
@grootstebozewolf
grootstebozewolf marked this pull request as ready for review September 2, 2026 01:06
@grootstebozewolf
grootstebozewolf merged commit ae99071 into develop Sep 2, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants