>Martin Davis:
>There's some new code on the way in GEOS and PostGIS which will improve
>the performance of this case.
Martin, do you have some specifics about that?
___
postgis-users mailing list
postgis-users@postgis.refractions.net
http://postgis.refra
Hi Kis,
I don't think the GiST index has anything to do with this, i'm only
processing one record.
thx,
WBL
On Thu, Feb 21, 2008 at 7:47 AM, Kis János Tamás <[EMAIL PROTECTED]> wrote:
> csütörtök 14 február 2008 15.11 dátummal Willy-Bas Loos ezt írta:
> >
> > select 'yes' as foo
> > from table1 a
that is, i'm not saying GEOS should work in the way that i describe, i just
mean it should know that it has a hit when one of the vertices intersects
with the other polygon.
Probably i'm seeing things too simple, but i guess never asking is the best
way to not get things improved, so i just ask stu
csütörtök 14 február 2008 15.11 dátummal Willy-Bas Loos ezt írta:
>
> select 'yes' as foo
> from table1 a, table1 b
> where a.gid=4
> and b.gid=4
> and intersects(a.the_geom, b.the_geom)
>
Did you try the next procedure?
create index i_a on table1 usng gist the_geom;
create index i_b on table2
Right, this:
select 'yes' as foo
from table1 a, table1 b
where a.gid=4
and b.gid=4
and st_intersects(a.the_geom, b.the_geom)
seems likely to a LOT less common than
select 'yes' as foo
from table1 a, table1 b
where a.gid=4
and st_intersects(a.the_geom, b.the_geom)
and the latte
There's some new code on the way in GEOS and PostGIS which will improve
the performance of this case. Bu it won't be anywhere near as fast as
your proposed check for an identical start point.
The "identical start point" check is great for the particular case of
comparing identical polygons.
Hi,
I´ve noticed that intersect(a,b) is slow when i compare a (nice and large)
geometry with itself.
so the syntax is:
select 'yes' as foo
from table1 a, table1 b
where a.gid=4
and b.gid=4
and intersects(a.the_geom, b.the_geom)
This particular polygon has about 10 000 points, and the query runs
