Opened 10 years ago
Closed 7 years ago
#2904 closed defect (wontfix)
documentation on ST_3DIntersects is misleading
| Reported by: | robe | Owned by: | robe |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 2.4.0 |
| Component: | documentation | Version: | master |
| Keywords: | Cc: |
Description (last modified by )
http://postgis.net/docs/manual-dev/ST_3DIntersects.htmlI t's also wrong. It says it only support linestrings but supports others with caveats.
It also doesn't reflect what happens when sfcgal is enabled as backend. I suspect for sfcgal for closed surfaces it treats them as volumes, but then again not absolutely sure.
See stackoverflow user comment http://gis.stackexchange.com/questions/111420/sdo-inside-equivalent-in-postgis-for-3d-objects/111502
Change History (5)
comment:1 by , 10 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 10 years ago
| Milestone: | PostGIS 2.1.4 → PostGIS 2.2.0 |
|---|
comment:3 by , 9 years ago
| Milestone: | PostGIS 2.2.0 → PostGIS 2.3.0 |
|---|
comment:4 by , 8 years ago
| Milestone: | PostGIS 2.3.0 → PostGIS 2.4.0 |
|---|
comment:5 by , 7 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I think this requires a bit more investigation as how best to explain and where the real gotchas are. I unfortunately probably won't have time before we need to release 2.1.4