Yes, I was going to add another comment that the strategy of just using
the Envelope object probably doesn't apply in PostGIS, since its
functions are oriented towards using Geometrys.
So in the long term I think the answer is to have the envelope function
return a valid geometry modelling the envelope. In the short term
you'll have to create this yourself, I think.
Charlie Savage wrote:
In its defence I'll point out that in my experience working with JTS
it is *very* rare to need to obtain a Geometry as an envelope.
Usually when doing "Envelopey" kinds of things it is much faster,
simpler, and more robust to simply work with actual Envelope objects.
Right. Except with PostGIS its easier to store the Geometries so that
an SRID can be associated with them and you can use a GIST index. Or
can you index a bounds2D?
Charlie
------------------------------------------------------------------------
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
--
Martin Davis
Senior Technical Architect
Refractions Research, Inc.
(250) 383-3022
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
