date:20150326

[postgis-users] Does ST_SimplifyPreserveTopology preserve "contains" property

2015-03-26 Thread Igor Stassiy

Hello,

does any postgis implementation of ST_SimplifyPreserveTopology preserve
"contains" property for polygons and multilines, that is, if I have a
(Multi)Polygon Parent and a (Multi)Linestring/(Multi)Polygon Child s.t.
ST_Contains(Parent, Child) holds, will
ST_Contains(ST_SimplifyPreserveTopology(Parent),
ST_SimplifyPreserveTopology(Child)) also hold?

Here I assume that the threshold for simplifying is the same for both Child
and Parent.

Thank you,
Igor
___
postgis-users mailing list
postgis-users@lists.osgeo.org
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users

Re: [postgis-users] 2.1.6 Released

2015-03-26 Thread Jonathan Moules

Hi Paul,
I suspect I know the answer to this (“no”), but to confirm, is the disk saving 
for points going to apply to points stored using the pointcloud extension in a 
postgis database?

Thanks,
Jonathan

From: postgis-users-boun...@lists.osgeo.org 
[mailto:postgis-users-boun...@lists.osgeo.org] 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 
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 substantial (~50%) disk space savings.

http://download.osgeo.org/postgis/source/postgis-2.1.6.tar.gz

Enhancements
· #3000, Ensure edge splitting and healing algorithms use indexes
· #3048, Speed up geometry simplification (J.Santana @ CartoDB)
· #3050, Speep up geometry type reading (J.Santana @ CartoDB)

Bug Fixes
· #2941, allow geography columns with SRID other than 4326
· #3069, small objects getting inappropriately fluffed up w/ boxes
· #3068, Have postgis_typmod_dims return NULL for unconstrained dims
· #3061, Allow duplicate points in JSON, GML, GML ST_GeomFrom* functions
· #3058, Fix ND-GiST picksplit method to split on the best plane
· #3052, Make operators <-> and <#> available for PostgreSQL < 9.1
· #3045, Fix dimensionality confusion in &&& operator
· #3016, Allow unregistering layers of corrupted topologies
· #3015, Avoid exceptions from TopologySummary
· #3020, ST_AddBand out-db bug where height using width value
· #3031, Allow restore of Geometry(Point) tables dumped with empties in 
them

View all closed 
tickets.


--
Paul Ramsey
http://cleverelephant.ca
http://postgis.net


This message has been scanned for viruses by 
MailControl, a service from BlackSpider Technology

Click 
here
 to report this email as spam.





HR Wallingford and its subsidiaries uses faxes and emails for confidential and 
legally privileged business communications. They do not of themselves create 
legal commitments. Disclosure to parties other than addressees requires our 
specific consent. We are not liable for unauthorised disclosures nor reliance 
upon them.
If you have received this message in error please advise us immediately and 
destroy all copies of it.

HR Wallingford Limited
Howbery Park, Wallingford, Oxfordshire, OX10 8BA, United Kingdom
Registered in England No. 02562099


___
postgis-users mailing list
postgis-users@lists.osgeo.org
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users

Re: [postgis-users] 2.1.6 Released

2015-03-26 Thread Rémi Cura

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 case)

Cheers,
Rémi-C

2015-03-26 18:05 GMT+01:00 Jonathan Moules :

>  Hi Paul,
>
> I suspect I know the answer to this (“no”), but to confirm, is the disk
> saving for points going to apply to points stored using the pointcloud
> extension in a postgis database?
>
>
>
> Thanks,
>
> Jonathan
>
>
>
> *From:* postgis-users-boun...@lists.osgeo.org [mailto:
> postgis-users-boun...@lists.osgeo.org] *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 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 substantial (~50%) disk space savings.
>
> http://download.osgeo.org/postgis/source/postgis-2.1.6.tar.gz
>
> *Enhancements*
>
> · #3000, Ensure edge splitting and healing algorithms use indexes
>
> · #3048, Speed up geometry simplification (J.Santana @ CartoDB)
>
> · #3050, Speep up geometry type reading (J.Santana @ CartoDB)
>
> *Bug Fixes*
>
> · #2941, allow geography columns with SRID other than 4326
>
> · #3069, small objects getting inappropriately fluffed up w/ boxes
>
> · #3068, Have postgis_typmod_dims return NULL for unconstrained
> dims
>
> · #3061, Allow duplicate points in JSON, GML, GML ST_GeomFrom*
> functions
>
> · #3058, Fix ND-GiST picksplit method to split on the best plane
>
> · #3052, Make operators <-> and <#> available for PostgreSQL < 9.1
>
> · #3045, Fix dimensionality confusion in &&& operator
>
> · #3016, Allow unregistering layers of corrupted topologies
>
> · #3015, Avoid exceptions from TopologySummary
>
> · #3020, ST_AddBand out-db bug where height using width value
>
> · #3031, Allow restore of Geometry(Point) tables dumped with
> empties in them
>
> View all closed tickets
> 
> .
>
>
>
>
>
> --
> Paul Ramsey
> http://cleverelephant.ca
>
> http://postgis.net
>
>
>
> This message has been scanned for viruses by MailControl
> , a service from BlackSpider Technology
>
> Click here
> 
> to report this email as spam.
>
>
>
> --
>
> *HR Wallingford and its subsidiaries* uses faxes and emails for
> confidential and legally privileged business communications. They do not of
> themselves create legal commitments. Disclosure to parties other than
> addressees requires our specific consent. We are not liable for
> unauthorised disclosures nor reliance upon them.
> If you have received this message in error please advise us immediately
> and destroy all copies of it.
>
> HR Wallingford Limited
> Howbery Park, Wallingford, Oxfordshire, OX10 8BA, United Kingdom
> Registered in England No. 02562099
>
> --
>
>
> ___
> postgis-users mailing list
> postgis-users@lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
>
___
postgis-users mailing list
postgis-users@lists.osgeo.org
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users

Re: [postgis-users] 2.1.6 Released

2015-03-26 Thread Paul Ramsey

"no", a different kind of issue entirely

On Thu, Mar 26, 2015 at 10:05 AM, Jonathan Moules
 wrote:
> Hi Paul,
>
> I suspect I know the answer to this (“no”), but to confirm, is the disk
> saving for points going to apply to points stored using the pointcloud
> extension in a postgis database?
>
>
>
> Thanks,
>
> Jonathan
>
>
>
> From: postgis-users-boun...@lists.osgeo.org
> [mailto:postgis-users-boun...@lists.osgeo.org] 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 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 substantial (~50%) disk space savings.
>
> http://download.osgeo.org/postgis/source/postgis-2.1.6.tar.gz
>
> Enhancements
>
> · #3000, Ensure edge splitting and healing algorithms use indexes
>
> · #3048, Speed up geometry simplification (J.Santana @ CartoDB)
>
> · #3050, Speep up geometry type reading (J.Santana @ CartoDB)
>
> Bug Fixes
>
> · #2941, allow geography columns with SRID other than 4326
>
> · #3069, small objects getting inappropriately fluffed up w/ boxes
>
> · #3068, Have postgis_typmod_dims return NULL for unconstrained dims
>
> · #3061, Allow duplicate points in JSON, GML, GML ST_GeomFrom*
> functions
>
> · #3058, Fix ND-GiST picksplit method to split on the best plane
>
> · #3052, Make operators <-> and <#> available for PostgreSQL < 9.1
>
> · #3045, Fix dimensionality confusion in &&& operator
>
> · #3016, Allow unregistering layers of corrupted topologies
>
> · #3015, Avoid exceptions from TopologySummary
>
> · #3020, ST_AddBand out-db bug where height using width value
>
> · #3031, Allow restore of Geometry(Point) tables dumped with empties
> in them
>
> View all closed tickets.
>
>
>
>
>
> --
> Paul Ramsey
> http://cleverelephant.ca
>
> http://postgis.net
>
>
>
> This message has been scanned for viruses by MailControl, a service from
> BlackSpider Technology
>
> Click here to report this email as spam.
>
>
>
>
> 
>
> HR Wallingford and its subsidiaries uses faxes and emails for confidential
> and legally privileged business communications. They do not of themselves
> create legal commitments. Disclosure to parties other than addressees
> requires our specific consent. We are not liable for unauthorised
> disclosures nor reliance upon them.
> If you have received this message in error please advise us immediately and
> destroy all copies of it.
>
> HR Wallingford Limited
> Howbery Park, Wallingford, Oxfordshire, OX10 8BA, United Kingdom
> Registered in England No. 02562099
>
> 
>
>
> ___
> postgis-users mailing list
> postgis-users@lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
___
postgis-users mailing list
postgis-users@lists.osgeo.org
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users

Re: [postgis-users] 2.1.6 Released

2015-03-26 Thread Jonathan Moules

Hi Rémi,
Thanks for the reply and information.

I’m afraid I inherited this database and don’t know much about it (or 
pointcloud).

Looking into though, I doubt it’s compressed, we extract the data with:
select block_id , pc_get(pc_explode(pa), 'X') as x, pc_get(pc_explode(pa), 'Y') 
as y, pc_get(pc_explode(pa), 'Z') as z from xyz_patches

so using pc_get rather than pc_uncompress.

On the other hand, there are 6 entries in pointcloud_formats which all have the 
“dimensional” line set. But I can’t 
decipher the documentation well enough to know if the data 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 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 case)
Cheers,
Rémi-C

2015-03-26 18:05 GMT+01:00 Jonathan Moules 
mailto:j.mou...@hrwallingford.com>>:
Hi Paul,
I suspect I know the answer to this (“no”), but to confirm, is the disk saving 
for points going to apply to points stored using the pointcloud extension in a 
postgis database?

Thanks,
Jonathan

From: 
postgis-users-boun...@lists.osgeo.org
 
[mailto:postgis-users-boun...@lists.osgeo.org]
 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 
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 substantial (~50%) disk space savings.

http://download.osgeo.org/postgis/source/postgis-2.1.6.tar.gz

Enhancements
• #3000, Ensure edge splitting and healing algorithms use indexes
• #3048, Speed up geometry simplification (J.Santana @ CartoDB)
• #3050, Speep up geometry type reading (J.Santana @ CartoDB)

Bug Fixes
• #2941, allow geography columns with SRID other than 4326
• #3069, small objects getting inappropriately fluffed up w/ boxes
• #3068, Have postgis_typmod_dims return NULL for unconstrained dims
• #3061, Allow duplicate points in JSON, GML, GML ST_GeomFrom* functions
• #3058, Fix ND-GiST picksplit method to split on the best plane
• #3052, Make operators <-> and <#> available for PostgreSQL < 9.1
• #3045, Fix dimensionality confusion in &&& operator
• #3016, Allow unregistering layers of corrupted topologies
• #3015, Avoid exceptions from TopologySummary
• #3020, ST_AddBand out-db bug where height using width value
• #3031, Allow restore of Geometry(Point) tables dumped with empties in 
them

View all closed 
tickets.


--
Paul Ramsey
http://cleverelephant.ca
http://postgis.net


This message has been scanned for viruses by 
MailControl, a service from BlackSpider Technology

Click here to report 
this email as spam.





HR Wallingford and its subsidiaries uses faxes and emails for confidential and 
legally privileged business communications. They do not of themselves create 
legal commitments. Disclosure to parties other than addressees requires our 
specific consent. We are not liable for unauthorised disclosures nor reliance 
upon them.
If you have received this message in error please advise us immediately and 
destroy all copies of it.

HR Wallingford Limited
Howbery Park, Wallingford, Oxfordshire, OX10 8BA, United Kingdom
Registered in England No. 02562099



___
postgis-users mailing list
postgis-users@lists.osgeo.org
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users




HR Wallingford and its subsidiaries uses faxes and emails for confidential and 
legally privileged business communications. They do not of themselves create 
legal commitments. Disclosure to parties other than addressees requires our 
specific consent. We are not liable for unauthorised disclosures nor reliance 
upon them.
If you have received this message in error please advise us immediately and 
destroy all copies of it.

HR Wallingford Limited
Howbery Park, Wallingford, Oxfordshire, OX10 8BA, United Kingdom
Registered in England No. 02562099

___

Re: [postgis-users] 2.1.6 Released

2015-03-26 Thread Rémi Cura

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 into public.pointcloud_formats, the xml schema corresponding to
the pcid you found.
You should see if it is compressed.

Another method is to take a patch and compare it with the uncompressed
version.

SELECT block_id, pa, pc_uncompress(pa)
FROM patches
LIMIT 1


Here is the correct way to write your querry anyway, you should see a great
speed up.

--recent postgres
SELECT block_id , pc_get(pt, 'X') as x, pc_get(pt, 'Y') as y, pc_get(pt,
'Z') as z
FROM xyz_patches, pc_explode(pa) as pt

--old postgres
WITH points AS (
SELECT block_id, pc_explode(pa) as pt
FROM xyz_patches, pc_explode(pa) as pt
)
SELECT block_id , pc_get(pt, 'X') as x, pc_get(pt, 'Y') as y, pc_get(pt,
'Z') as z
FROM points

Cheers,
Rémi-C


2015-03-26 19:09 GMT+01:00 Jonathan Moules :

>  Hi Rémi,
>
> Thanks for the reply and information.
>
>
>
> I’m afraid I inherited this database and don’t know much about it (or
> pointcloud).
>
>
>
> Looking into though, I doubt it’s compressed, we extract the data with:
>
> select block_id , pc_get(pc_explode(pa), 'X') as x, pc_get(pc_explode(pa),
> 'Y') as y, pc_get(pc_explode(pa), 'Z') as z from xyz_patches
>
>
>
> so using pc_get rather than pc_uncompress.
>
>
>
> On the other hand, there are 6 entries in pointcloud_formats which all
> have the “dimensional” line set.
> But I can’t decipher the documentation well enough to know if the data
> 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 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 case)
>
> Cheers,
>
> Rémi-C
>
>
>
> 2015-03-26 18:05 GMT+01:00 Jonathan Moules :
>
> Hi Paul,
>
> I suspect I know the answer to this (“no”), but to confirm, is the disk
> saving for points going to apply to points stored using the pointcloud
> extension in a postgis database?
>
>
>
> Thanks,
>
> Jonathan
>
>
>
> *From:* postgis-users-boun...@lists.osgeo.org [mailto:
> postgis-users-boun...@lists.osgeo.org] *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 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 substantial (~50%) disk space savings.
>
> http://download.osgeo.org/postgis/source/postgis-2.1.6.tar.gz
>
> *Enhancements*
>
> · #3000, Ensure edge splitting and healing algorithms use indexes
>
> · #3048, Speed up geometry simplification (J.Santana @ CartoDB)
>
> · #3050, Speep up geometry type reading (J.Santana @ CartoDB)
>
> *Bug Fixes*
>
> · #2941, allow geography columns with SRID other than 4326
>
> · #3069, small objects getting inappropriately fluffed up w/ boxes
>
> · #3068, Have postgis_typmod_dims return NULL for unconstrained
> dims
>
> · #3061, Allow duplicate points in JSON, GML, GML ST_GeomFrom*
> functions
>
> · #3058, Fix ND-GiST picksplit method to split on the best plane
>
> · #3052, Make operators <-> and <#> available for PostgreSQL < 9.1
>
> · #3045, Fix dimensionality confusion in &&& operator
>
> · #3016, Allow unregistering layers of corrupted topologies
>
> · #3015, Avoid exceptions from TopologySummary
>
> · #3020, ST_AddBand out-db bug where height using width value
>
> · #3031, Allow restore of Geometry(Point) tables dumped with
> empties in them
>
> View all closed tickets
> 
> .
>
>
>
>
>
> --
> Paul Ramsey
> http://cleverelephant.ca
>
> http://postgis.net
>
>
>
> This message has been scanned for viruses by MailControl
> , a service from BlackSpider Technology
>
> Click here  to
> report this email as spam.
>
>
>
>
>  --
>
> *HR Wallingford and its subsidiaries* uses faxes and emails for
> confidential and legally privileged business communications. They do not of
> themselves create legal commitments. Disclosure to parties other than
> addressees requires our specific c

Re: [postgis-users] Does ST_SimplifyPreserveTopology preserve "contains" property

2015-03-26 Thread Paul Ramsey

No, it preserves internal topology, not relative topology.

On Thu, Mar 26, 2015 at 9:59 AM, Igor Stassiy  wrote:
> Hello,
>
> does any postgis implementation of ST_SimplifyPreserveTopology preserve
> "contains" property for polygons and multilines, that is, if I have a
> (Multi)Polygon Parent and a (Multi)Linestring/(Multi)Polygon Child s.t.
> ST_Contains(Parent, Child) holds, will
> ST_Contains(ST_SimplifyPreserveTopology(Parent),
> ST_SimplifyPreserveTopology(Child)) also hold?
>
> Here I assume that the threshold for simplifying is the same for both Child
> and Parent.
>
> Thank you,
> Igor
>
> ___
> postgis-users mailing list
> postgis-users@lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
___
postgis-users mailing list
postgis-users@lists.osgeo.org
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users

[postgis-users] Does ST_SimplifyPreserveTopology preserve "contains" property

Re: [postgis-users] 2.1.6 Released

Re: [postgis-users] 2.1.6 Released

Re: [postgis-users] 2.1.6 Released

Re: [postgis-users] 2.1.6 Released

Re: [postgis-users] 2.1.6 Released

Re: [postgis-users] Does ST_SimplifyPreserveTopology preserve "contains" property

7 matches

Site Navigation

Mail list logo

Footer information