You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When printing a WMTS layer where the layer bounds is smaller than the printing view, mapfish make HTTP requests to non existing tiles (negative row/column or row/column out of the layer bounds).
This is especially an issue when using the flag FailOnError on the layer.
From what I've seen and understand in the code, mapfish don't check if the tile is in the bound provided by the matrixSize of the payload. It would be good that it does the check and avoid calling tile outside of the matrixSize provided in the payload.
Context
Describe the bug
When printing a WMTS layer where the layer bounds is smaller than the printing view, mapfish make HTTP requests to non existing tiles (negative row/column or row/column out of the layer bounds).
This is especially an issue when using the flag FailOnError on the layer.
How to reproduce
Actual results
Although the tile matrix for zoom 14 specifies that the service has max 3 column and 2 rows, it seems to try to get the tile col 3, see log below
Logs
mapfishprint-log.txt
Expected results
From what I've seen and understand in the code, mapfish don't check if the tile is in the bound provided by the matrixSize of the payload. It would be good that it does the check and avoid calling tile outside of the matrixSize provided in the payload.
NOTE: This issue has been found while integrating mapfish with the new web mapviewer for map.geo.admin.ch (see https://github.com/geoadmin/web-mapviewer)
The text was updated successfully, but these errors were encountered: