#1673 closed defect (fixed)
[raster] Add a note on ST_Union(raster) slowness
Reported by: | pracine | Owned by: | robe |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 2.0.0 |
Component: | documentation | Version: | master |
Keywords: | Cc: |
Description
So we receive a bit less complains
And give some promises that WWDBIANR (we will do better in a next release) or WWDBITNR…
Change History (6)
comment:1 by , 13 years ago
Summary: | Add a note on ST_Union slowness → Add a note on ST_Union(raster) slowness |
---|
comment:2 by , 13 years ago
Summary: | Add a note on ST_Union(raster) slowness → [raster] Add a note on ST_Union(raster) slowness |
---|
comment:3 by , 13 years ago
comment:4 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
done at r9508. I also put in a note to use ST_Clip first and then union.
I discovered when creating my report images that if I clip the rasters to my polygon area of interest and then union the raster shards, it's way faster than trying to union the intersecting rasters and then clipping to my geometry of interest.
For example for my o_2 the difference was 3.5 seconds vs. 8 seconds if you (clip + union) vs. (union + clip).
For the hi-res, the timing was more starkling — something like 9 seconds vs. 30 seconds.