On 6/14/2016 3:53 AM, Michal Seidl wrote:
With other operators ST_Distance,ST_Equal, = the spatial index is not
used (?) and query take about 500ms. 500 points x 500ms => 250s which
is quite a lot and I do not take into account time spent on python
side. That's the problem.
Do everything in
Hi Sandro,
mmh... I really would like to, but I am no programmer and wouldn't know
how to contribute and I am not in a position to decide about financing
somebody to add this functionality. I'm sorry.
But thank you anyway for clarifying the current functionality status!
Regards,
Birgit
Am
Index not used can have a lot of causes:
1. the way you write the sql query,
2. a problem with statistics (vacuum analyze concerned tables)
3. a wrong tuning of postgres server (less common)
...
Most likely in your case is 1., but you can vacuum analyze the tables
first, it could be an easy fix.
Hi Rémi,
thank you for sharing your function. In the meantime I seem to have
solved the problem by combining the st_split function with a function
from an old use case:
CREATE OR REPLACE FUNCTION ST_SplitPolygon(poly geometry, blade
geometry) RETURNS geometry AS
$$
declare
out_geom
On Wed, Jun 15, 2016 at 07:19:34PM +0200, Birgit Laggner, vTI wrote:
> Hi Sandro,
>
> yes, I read so, too. But, our database has PostGIS version:
> "POSTGIS="2.2.1 r14555" GEOS="3.5.0-CAPI-1.9.0 r4084" PROJ="Rel.
> 4.9.1, 04 March 2015" GDAL="GDAL 1.11.2, released 2015/02/10"
> LIBXML="2.9.2"
Hey,
I wrote a multi-friendly st_split a while ago.
Maybe it will help you:
https://github.com/Remi-C/_utilities/blob/master/postgis/rc_split_multi.sql
Cheers,
Rémi-C
2016-06-15 19:19 GMT+02:00 Birgit Laggner, vTI :
> Hi Sandro,
>
> yes, I read so, too. But, our