For ensuring there are no cloud occurences in a given roi I used
except at first then realised having combined with count/groupby was
the key.
Having 0 occurence or in our case having maximum pixels clear - same
either way.
These queries get thorny - sqlalchemy orm made things alot
Try making a copy of your wastac.t_tile_geometry_old table but with
a geography instead of geometry column for border, and you should
see an improvement.
That's precisely what I showed in the original post - geography
intersecting geography column. See the table def. I was outlining in
Drop the opts from the parentheses for geog I think.
On 14/05/2010, at 5:14 PM, rakesh modi rakesh.modi1...@gmail.com
wrote:
Hi All,
I am newer to use postgres.
I get an error using this query :- operator class
gist_geometry_ops does not accept data type geography
when i run query :-
Thanks but not according to the doc I think?
1) Abstract superclass is mentioned in API, not point,
2) the SQL example uses circles
3) the blog link specifically uses polygons in it's discussion of OGC
coverage behaviour.
The docs are a bit rough in this area imo but I think it is assuming
postgis 1.5 is installed (to libdir/postgis-1.5).
Btw my experience is that it will also assume postgis 1.4 is installed
to libdir/postgis. Confusingly when I ran 1.3 to 1.5 I found this and
that I needed to have both
Yes geography - migrated data from a geometry column (as per
suggestion in other thread).
I'll work on getting a dump for you to reproduce over the w/e.
On 16/04/2010, at 12:32 AM, Paul Ramsey pram...@cleverelephant.ca
wrote:
Nicholas,
Could you confirm that the crash is building an
? Thanks, Nick.
--
Nick Bower
[EMAIL PROTECTED]
___
postgis-users mailing list
postgis-users@postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
