Opened 14 years ago
Last modified 7 years ago
#502 closed enhancement
[wktraster] Optimize ST_Intersection — at Version 3
| Reported by: | pracine | Owned by: | jorgearevalo |
|---|---|---|---|
| Priority: | low | Milestone: | PostGIS Fund Me |
| Component: | raster | Version: | master |
| Keywords: | Cc: |
Description (last modified by )
It might be much quicker to provide the value associated with a pixel intersecting with a point geometry when using ST_Intersection() by accessing the pixel value with ST_Value instead of vectorizing the whole tile. We have first to fix st_value(rast, geom) so it behave exactly as st_intersect on edge of raster and pixels.
This, obviously, do not work when the intersecting geometry is a line or a polygon. In this case we should try to vectorize only the intersecting part of the raster tile.
Change History (3)
comment:1 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 14 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
Actually no. it was not adressed. To do…
comment:3 by , 14 years ago
| Description: | modified (diff) |
|---|---|
| Summary: | [wktraster] Optimize ST_Intersection when the geometry is a point → [wktraster] Optimize ST_Intersection |
Note:
See TracTickets
for help on using tickets.
Adressed in r5687