#3190 closed enhancement (duplicate)
Have ST_3DDWithin use the &&& operator
| Reported by: | strk | Owned by: | pramsey |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 2.2.0 |
| Component: | postgis | Version: | master |
| Keywords: | Cc: |
Description
See https://lists.osgeo.org/pipermail/postgis-users/2015-June/040615.html Continuing here: https://lists.osgeo.org/pipermail/postgis-users/2015-July/040617.html
Too late for 2.2.0 ?
Change History (3)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
This is a dupe of #1024 which you shot down when I brought it up over and over again because we've got M getting in the way,
Note:
See TracTickets
for help on using tickets.
There are actually many other 3D function currently using the && operator which may need to be updated. I guess "magic" would require to use both && and &&&, which may be even counter-productive, but I'll leave that evaluation to @robe2