[postgis-devel] BOX3D strange behaviour
remi.cura at gmail.com
Thu Feb 18 02:02:49 PST 2016
Using Even trick saves me about 25% time.
Now I'll always use the multipoints/line instead of box3D
2016-02-18 10:49 GMT+01:00 Sandro Santilli <strk at keybit.net>:
> On Thu, Feb 18, 2016 at 10:03:54AM +0100, Rémi Cura wrote:
> > Is there any way to perform &&& in all 3 dimensions?
> Our boxes are all broken.
> There should be somewhere a wiki page or ticker or something about
> options to improve the situation. IIRC it boiled down to:
> 1) Have a BOX geometry type (like LINESTRING/POINT/POLYGON)
> 2) Expose a GBOX postgresql type (like BOX2D, BOX3D)
> Recently, I've started using 2-vertices linestrings to simulate
> the equivalent of a "BOX geometry type". It is the value returned
> by http://postgis.net/docs/ST_BoundingDiagonal.html
> You can easily create such object via ST_MakeLine:
> It will support SRID and all supported dimensions.
> Changing the BOX3D->Geometry cast ? I'm all for it, and I'd have
> it return a "bounding diagonal" too...
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the postgis-devel