Hi,
Mapserver is not clever at all when it finds many overlapping images. It
renders them all one by one. If the list of images is sorted correctly then the
end result is what was desired, but with all too much work. See
https://github.com/MapServer/MapServer/issues/5899.
We use two tricks:
1)
Hello Jukka,
Yup I guess that's the case, I assumed that WCS has the same capabilities as
WMS when it comes to handling time dimension and it would use the default time
from mapfile while requesting the data.
This is my mapserv log file from one getCoverage request (very small, that's
why It
Hi,
Does the tileindex query " DATA 'geometry from (select * from plua order by
"maxCC" desc) " return several images from the requested BBOX?
I know that MapServer WCS can be fast and we have also a demo at
Hi Seth,
as you suggested, I've added the Extent parameter to all of my layers, and it
resulted in decreasing time to 5m33.534s. But still, it's quite a lot of time
for generating 1.5 MiB file.
Any other suggestions?
Maybe there is something wrong with projection so beyond just serving data
Hi Marcin,
As a first test I'd recommend adding in EXTENTs to all your layers (and
ensuring they are correct):
EXTENT 1334552.857598 5342648.587634 4715044.821842 7547620.486088
If these are missing MapServer will often try and calculate these from the
datasource automatically. Depending on
