[postgis-devel] BOX3D strange behaviour

[Komяpa]

I'd call it a bug too.
Bumped into it storing timestamp in z coordinate of linestring and willing
to cut it by timestamp interpolating endpoints, calculating
ST_3DIntersection(geom, box3d). It failed, so I had to give up and go back
to ST_Dump + WHERE ST_Z(pt) BETWEEN :(

чт, 18 февр. 2016 г. в 11:37, Sandro Santilli <strk at keybit.net>:

> On Wed, Feb 17, 2016 at 11:33:12AM -0800, Paul Ramsey wrote:
> > > On Feb 17, 2016, at 10:46 AM, Rémi Cura <remi.cura at gmail.com> wrote:
> > >
> > > SELECT 'BOX3D( 0 0 0, 10 10 10)'::box3D::geometry &&&
> ST_Makepoint(5,5,-1)
> >
> > select st_astext('BOX3D( 0 0 0, 10 10 10)'::box3D::geometry);
>
> Horrible. box3d::geometry drops the Z ?
> Was it always like that ? I'd call it a bug ...
>
> --strk;
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/postgis-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20160218/35fc8eec/attachment.html>