Closed jankovicgd closed 3 years ago
I found the issue to be this commit: https://github.com/MapServer/mapcache/commit/a118e919b8b2ceef00f0a92c5742a75a3dc888fd
In source_wms
for GetMap
the dimension value was changed from cached_value
(the time value of the actual tile) to requested_value
(the full timespan from the incoming request). I see that it makes sense to do that for GetFeatureInfo
, as I guess only a single request is sent to the source WMS, but for GetMap
this introduces the aforementioned bug.
Hey all, I have an issue where the same overlapping images gets stored as a tile for different time slices when time is provided as a dimension.
Example request:
The resulting image is expected and received, an assembly of two images:
The request sends two requests to the WMS and these two requests have the full intervals in the
time
parameter. Thetime
parameter is wrong in this case and it should be the timestamp, not the full interval:When looking in the cache db the image above gets stored for both dimensions.
I am able to get the proper images if I cache them manually one by one:
The
dimensions
config file is below. Tried tinkering with many values here but ultimately it doesn't change the result. Thestore_assemblies
is seemingly not enforced here.In the client consuming this, a single time slice is selected and shown but as you can see the other pieces from the other timeslice also render which is outside of the bbox.
Tested with
mapcache 1.10.0-1