The current "optimization" avoids to call reading at all if the requested envelope is outside the reader original envelope. Some readers like mosaic can have a time varying envelope that might be very expensive to recompute (especially if used to decide if we want to call read, which would require a very precise result, not an approximate one) and not easy to keep up to date over a distributed environment. Just attempt a read instead, like common OGC clients do in face of the capabilities envelopes (for the same reason). For RenderedImageMapOutputFormat this happens only on the direct raster path and if a rendering transformation is present
td>
|