[postgis-devel] Precision Reduction?

[Martin Davis]

I am neutral about encoding precision in the data or in the schema.  As
Darafei points out it raises a raft of tricky questions about what should
be made precise, the semantics of spatial predicates, and what to do about
mixed precision. It's a far bigger change than what Paul is asking about,
since it requires many operations to be enhanced to support precise output.

Providing ST_PrecisionReduce may or may not be a small step in that
direction.  But it lets users and the development team get some experience
with how and when to enforce precision.

On Wed, Nov 11, 2020 at 2:06 AM Sandro Santilli <strk at kbt.io> wrote:

> I think we should add a precision field to the Geometry type
> so that once precision is set on a geometry it sticks and can
> be passed around, in particular to GEOS functions for retaining
> the precision in output (basically using fixed precision all
> the way).
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20201111/d8cd1f5f/attachment.html>