[postgis-users] Different hex POINT representation but the same coordinates?

[Martin Davis]

PostGIS WKT output does overly-aggressive rounding, IMO.

In JTS you get:

01010000000ad7a3f0735727c13e0ad7a3ae0c30c1 = POINT (-764857.97
-1051822.6400000001)

01010000000ad7a3f0735727c13d0ad7a3ae0c30c1 = POINT (-764857.97 -1051822.64)


On Mon, Oct 5, 2020 at 8:21 AM Michal Seidl <michal.seidl at gmail.com> wrote:

> Hello I have two points with different HEX representation but the same
> WKT representation? I do not know the binary representation in detail.
>
> The difference in HEX is somewhere in th middle "d" versus "e" value
>
> SELECT
> ST_AsEWKT(ST_GeomFromWKB('\x01010000000ad7a3f0735727c13e0ad7a3ae0c30c1'));
>
> SELECT
> ST_AsEWKT(ST_GeomFromWKB('\x01010000000ad7a3f0735727c13d0ad7a3ae0c30c1'));
>
> SELECT ST_GeomFromWKB('\x01010000000ad7a3f0735727c13e0ad7a3ae0c30c1') =
> ST_GeomFromWKB('\x01010000000ad7a3f0735727c13d0ad7a3ae0c30c1');
>
> So what is different?
>
> Michal
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20201005/fedf167a/attachment.html>