[postgis-devel] BOX3D strange behaviour
me at komzpa.net
Fri Feb 26 06:45:57 PST 2016
When performong ST_3DIntersection(geom, box3d), will approach with line do
the thing that's awaited from it clipping geometry by the box, or make
strange multipoint/multilinestring/EMPTY intersection? :)
пт, 26 февр. 2016 г. в 17:34, Paul Ramsey <pramsey at cleverelephant.ca>:
> Codacil to this: a linestring involves an lwline and a pointarray, a
> multipoint involves a multipoint, 2 x point, 2 x pointarray, so
> there's a minor efficiency in sticking w/ the line.
> On Thu, Feb 18, 2016 at 1:27 PM, Rémi Cura <remi.cura at gmail.com> wrote:
> > Exactly,
> > in the end it's just 2 points.
> > I personally would prefer to keep it as 2 points,
> > because I feel a line is semantically more different,
> > but it amounts to the same thing in the end.
> > Cheers,
> > Rémi-C
> > 2016-02-18 11:36 GMT+01:00 Sandro Santilli <strk at keybit.net>:
> >> On Thu, Feb 18, 2016 at 11:02:49AM +0100, Rémi Cura wrote:
> >> > Using Even trick saves me about 25% time.
> >> > Good !
> >> Right, it's the same approach of the "BoundingDiagonal",
> >> only he does it with a 2-members multipoint rather than
> >> with a 2-vertices linestring.
> >> --strk;
> >> _______________________________________________
> >> postgis-devel mailing list
> >> postgis-devel at lists.osgeo.org
> >> http://lists.osgeo.org/mailman/listinfo/postgis-devel
> > _______________________________________________
> > postgis-devel mailing list
> > postgis-devel at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/postgis-devel
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the postgis-devel