Opened 12 years ago
Closed 12 years ago
#1357 closed task (fixed)
Use gbox_overlap where appropriate
| Reported by: | strk | Owned by: | strk |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 2.0.0 |
| Component: | postgis | Version: | master |
| Keywords: | Cc: |
Description
In r8323 a manually crafted "box overlap" is implemented. It would be less error prone to use the existing gbox_overlaps instead. Paul mentioned there are more such cases. Worth cleaning them up. And making sure the cunit tests are in place for that.
Change History (2)
comment:1 by , 12 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
As of r8331 I added a gbox_overlaps_2d and used that within lwgeom_geos.c where appropriate.
I noticed there's a need for gbox_contains_2d as well but isn't available for gbox, only for box2df inside gserialized_gist_2d. May be worth exporting to higher levels.