Caroline Lewis
Sent: Tuesday, August 23, 2011 1:31 PM
To: PostGIS Users
Subject: [postgis-users] Array Size Error
Thanks for you previous help and quick responses. I'm only getting to look
at your suggestions now, however I noticed in PostGIS 2.0 the
ST_ConcaveHull() which is closer to our fun
Thanks for you previous help and quick responses. I'm only getting to look at
your suggestions now, however I noticed in PostGIS 2.0 the ST_ConcaveHull()
which is closer to our functionality needs so have started to try and work with
this instead of the convexhull option. Maybe another to-d
Hi All, Thanks again to Leo, Regina and Paul for your help and
suggestions. I will pursue this snap-to-grid approach for my next test set.As
you may have guessed the amount of points we are working with are sourced from
LiDAR.Mobile terrestrial in our case with a very high resolution.
om: postgis-users-boun...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis.refractions.net] On Behalf Of Paragon
Corporation
Sent: Wednesday, July 27, 2011 6:38 AM
To: 'PostGIS Users Discussion'
Subject: Re: [postgis-users] Array Size Error
Paul,
I think it's a was
-users-boun...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis.refractions.net] On Behalf Of Paul &
Caroline Lewis
Sent: Wednesday, July 27, 2011 5:32 AM
To: PostGIS Users
Subject: [postgis-users] Array Size Error
Thanks for the responses. Have changed the original query from this:
SELECT ST_Convex
Thanks for the responses. Have changed the original query from this: SELECT
ST_ConvexHull(ST_Collect(ST_Force_2D(geom))) FROM table001 to this: SELECT
ST_ConvexHull(ST_MemUnion(geom)) FROM table001 and its still running; over 12
hours now.Is this a waste of time.I'm trying it this way as I g
<http://www.postgis.us/>
_
From: postgis-users-boun...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis.refractions.net] On Behalf Of Paul
Ramsey
Sent: Tuesday, July 26, 2011 1:44 PM
To: PostGIS Users Discussion
Cc: PostGIS Users
Subject: Re: [postgis-users] Arra
The problem is you are collecting the whole table into memory before running
the hull operation. There is just an upper limit to the size of tables you can
use that trick on. The solution, says the software developer, is smarter
software, like a convex hull aggregate that builds the hull progres
Hi All,
The following error has me lost as to finding the solution:
*
ERROR: array size exceeds the maximum allowed (1073741823)
-- Error
ERROR: array size exceeds the maximum
