Hi Hugues,
Congrats on the new family member.
I'd guess that the error is happening to the rasters being generated
within the function. Beyond that, I can't say more without being able
to recreate the situation.
-bborie
On Sun, Dec 2, 2012 at 2:17 PM, Francois Hugues
wrote:
> Hello,
>
> Hello
Hello,
Hello,
Thanks for your answer Bborie and, please, excuse me for the time it took me to
reply, but a new born girl arrived in my family on last Tuesday.
Your query returns no line and that's normal since I deleted all lines where
st_height = 0. I had already done that when I sent my firs
Hello,
You should directly use st_intersects with st_intersection :
SELECT ST_Intersection(table1.geom, table2.geom)
>From table1, table2
Where st_intersects(table1.geom, table2.geom)
St_intersection is slower than st_intersects.
Did you think to build spatial (gist) index on your tables to impr
Hello everyone,
I have quick questions please about ST_Intersects Vs. ST_Intersection:
1. Does the following SQL statement checks the intersection between each
geom in table1 Vs. each geom in table2?
SELECT ST_Intersection(table1.geom, table2.geom)
From table1, table2;
2. I have 3
Paul Ramsey wrote:
>Google knows,
>http://trac.osgeo.org/geos/wiki/PreparedGeometry
>http://blog.cleverelephant.ca/2008/10/postgis-performance-prepared-geometry.html
>
>p
I see
http://blog.cleverelephant.ca/2008/10/postgis-performance-prepared-geometry.html
Now I understand better.
As I understa