gt; suggestion would get me closer to what I wanted in the final output.
>
>
>
> Best,
>
> Trang
>
>
>
> *From:* postgis-users-boun...@lists.osgeo.org [mailto:
> postgis-users-boun...@lists.osgeo.org] *On Behalf Of *Birgit Laggner
> *Sent:* Wednesday, February
t.
Best,
Trang
From: postgis-users-boun...@lists.osgeo.org
[mailto:postgis-users-boun...@lists.osgeo.org] On Behalf Of Birgit Laggner
Sent: Wednesday, February 11, 2015 12:20 AM
To: postgis-users@lists.osgeo.org
Subject: Re: [postgis-users] Question on optimizing slow geospatial query
Hi Tran
Hi Trang,
I think, it could help to create btree indices on "startts" and "uuid",
too, since you are using them in your where clause as a filter (a
probably unnecessary question regarding your date filter: I would expect
the result of "t.startts > '2015-01-16' and t.startts < '2015-01-17'" to
Hi,
I am a newbie to Postgres/PostGIS and have a long running query that I would
like to optimize.
There are two tables (trip and zone) that I am joining in the query, one which
has "startloc" and "endloc" columns with type Geometry(Point) and other which
contains a Geometry(MultiPolygon). Ther
