Discussion
Subject: Re: [postgis-users] 2.1.6 Released
Hum you can do a simple test,
for the table you are using,
look at the pgpoint column type number (called pcid)
You can know this like this
SELECT pc_astext(pt)
FROM xyz_patches, pc_explode(pa) as pt
LIMIT 1
Know look
] On Behalf Of Paul Ramsey
Sent: Friday, March 20, 2015 5:45 PM
To: PostGIS Users Discussion
Subject: [postgis-users] 2.1.6 Released
The 2.1.6 release of PostGIS is now
availablehttp://download.osgeo.org/postgis/source/postgis-2.1.6.tar.gz.
The PostGIS development team is happy to release patch
Of *Rémi Cura
*Sent:* Thursday, March 26, 2015 5:33 PM
*To:* PostGIS Users Discussion
*Subject:* Re: [postgis-users] 2.1.6 Released
Hey,
if you use the compression of patch and sensible xml schema,
you should already have a 1:2 to 1:4 compression of the point size.
(compared to binary ply in my
actually uses it.
Cheers,
Jonathan
From: postgis-users-boun...@lists.osgeo.org
[mailto:postgis-users-boun...@lists.osgeo.org] On Behalf Of Rémi Cura
Sent: Thursday, March 26, 2015 5:33 PM
To: PostGIS Users Discussion
Subject: Re: [postgis-users] 2.1.6 Released
Hey,
if you use the compression
The 2.1.6 release of PostGIS is now available.
The PostGIS development team is happy to release patch for PostGIS 2.1, the
2.1.6 release. As befits a patch release, the focus is on bugs, breakages, and
performance issues. Users with large tables of points will want to priorize
this patch, for
