-
-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Artefacts on tiles when using apache module #291
Comments
This might be a good question for the mailing lists to start - more eyes. I've been running MapCache using the Apache module for years and have never seen anything like it. |
What kind of backend are you using? Do you pre-seed your tiles or are they cached on-the-fly? |
Tiles are stored on disk, and cached on-the-fly. |
Wonder if the MapCache 1.14.0 makes a difference? |
Sadly, it doesn't. |
Can you isolate the WMS call that creates the image that mapcache carves into tiles? Would be good to verify the artifacts aren't in the source material. |
If you are certain your WMTS source is OK, I would suggest to give LMDB a try. Although it will not shine any light on the root of problem, it is a workaround to try. |
@marisn : I tried LMDB as you suggested, and so far so good ! |
We are experiencing some strange artifacts on tiles when using the mapcache apache module, but not when using fcgi.
Sources are wmts services.
I have been testing in docker containers using the exact same versions of dependencies (including Gdal 3.5.1 - as it is used for wmts sources) and Mapcache (1.12.1).
Deleting the affected tiles and redownloading them or waiting for tile expiration fixes this issue.
We have been running mapcache in production through fcgi for quite some time now and I am 100% sure artifacts do not happen.
We switched to fcgi because of this issue.
Any idea what could be causing these artifacts, and why it only happens with apache module ?
The text was updated successfully, but these errors were encountered: