[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gdal-dev
Subject:    [gdal-dev] Re: OGR Select Features by Location...
From:       estrada.adam () gmail ! com (estrada ! adam () gmail ! com)
Date:       2008-01-30 15:27:16
Message-ID: 2256ddfb-7283-4faa-a427-3815abc1af30 () s19g2000prg ! googlegroups ! com
[Download RAW message or body]

Joe,
    I am actually using ogr2ogr to get the data in and out of the
database so this is not totally off topic!  Thanks for the update
though...it appears to be working wonderfully.

Adam

On Jan 29, 6:55?pm, Joe Healy <j...@omc-international.com.au> wrote:
> We're probably getting a little off topic, but
>
> estrada.a...@gmail.com wrote:
> > All,
> > ? ? How important is it to create the index for the intersection
> > function I am trying to perform.
>
> It depends on how many of your points are within the bounding box of
> each polygon.
> If the bounding box will reduce the number of point in polygon
> comparisons significantly then it is essential, otherwise a linear scan
> may be quicker if they are all inside.> ?We are talking over 15 million LIDAR
> > points already loaded in to my PostgreSQL DB for a single dataset. ?I
> > read something that said that each set of 1 million points takes an
> > hour to process when creating the index.
>
> For sets with approx 8 million points someone here ran yesterday, the
> complete loading, indexing and querying took approximately 40 minutes
> per set.
> Make sure you are using copy to insert the data. Email either the
> posgresql performance list or postgis list for other performance hints
> if it is still not quick enough.
>
> Hope that helps,
>
> Joe
> _______________________________________________
> gdal-dev mailing list
> gdal-...@lists.osgeo.orghttp://lists.osgeo.org/mailman/listinfo/gdal-dev

[prev in list] [next in list] [prev in thread] [next in thread]