Curve Thoughts

[Regina Obe]

I’d say unitary but I’m scared off by the major changes that would need to be done to collection handling and possible breaking change.

 

In the end consistency is most important.

 

ST_GeometryN(<>, 4)

 

Should return the 4th record that ST_Dump returns.

 

ST_DumpSegments should either bail with an error or return something for curves.

 

From: Paul Ramsey <pramsey at cleverelephant.ca> 
Sent: Friday, February 16, 2024 3:45 PM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
Subject: Curve Thoughts

 

The problem of how to deal with curve “decomposition” functions (ST_GeometryN, ST_Dump, ST_DumpRings) in the presence of the various Curve types, and our current inconsistent behaviour with them.

 

https://gist.github.com/pramsey/cbf6db1edb8762854925f6b6ad6d6b35

 

What it really comes down to is “are CompoundCurve and CurvePolygon collections or not”. If “not”, if they are unitary, then there are quite a few changes to be made in the behaviour of things like ST_Dump, and other functions that currently just stuff them through collection handling. 

 

So, your answer: unitary? or collection?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20240216/a5daecbf/attachment.htm>