On Fri, 29 May 2015 13:37:24 -0500
David Haynes II wrote:
>
> Let me explain this a bit more clearly. The dataset (table) that we are
> using in this analysis is produced from a satellite image (tif) called
> MODIS. This image can be placed into PostgreSQL using the raster2pgsql
> command (http:/
Hello,
Let me explain this a bit more clearly. The dataset (table) that we are
using in this analysis is produced from a satellite image (tif) called
MODIS. This image can be placed into PostgreSQL using the raster2pgsql
command (http://postgis.net/docs/using_raster_dataman.html). The
raster2pgsql
On Thu, 28 May 2015 10:06:24 -0500
David Haynes II wrote:
>
> The query run times are significantly slower on outdb as that using indb
> here are the run times on 2 queries.
>
> ST_Count/ST_Clip(select single band here)/Inner Join/ST_Transform (US
> Counties)
> OutDB: 873.564s (14 minutes 33s)
Sorry,
The query run times are significantly slower on outdb as that using indb
here are the run times on 2 queries.
ST_Count/ST_Clip(select single band here)/Inner Join/ST_Transform (US
Counties)
OutDB: 873.564s (14 minutes 33s) InDB: 127.36s (2 minutes 7s)
ST_Count(select single band here
On Tue, 26 May 2015 12:52:24 -0500
David Haynes II wrote:
> Hello,
>
> I have a question about the query optimizer and its performance on spatial
> datasets, specifically rasters. My use case is rather unique, the
> application that I am developing allows users to request summarizations of
> var
Hello,
I have a question about the query optimizer and its performance on spatial
datasets, specifically rasters. My use case is rather unique, the
application that I am developing allows users to request summarizations of
various geographic boundaries around the world. Therefore our raster
datase
