[postgis-devel] Inconsistencies in text output

[rmrodriguez at carto.com]

On Mon, Apr 20, 2020 at 6:10 PM Sandro Santilli <strk at kbt.io> wrote:

> Any decimal representation of a floating point number
> will have this problem, as not all numbers that can be
> represented by a floating point number can fit on a
> screen.

It has been demonstrated that you can guarantee round-trip conversion
with 17 significant digits. It's true that with decimal notation it
will require more characters, but with Postgis constraints this seems
to require at most 33 characters, which is way less than what a screen
fits.

I'd be more than happy to add examples of those big numbers to add
them to our unit tests and confirm round trip works for them.


-- 
Raúl Marín Rodríguez
carto.com