-
Notifications
You must be signed in to change notification settings - Fork 250
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
Mixed image formats doesn't work with s3/local directories tiles cache #605
Comments
@weskamm @simonseyock Could you please reopen this issue? The PR was reverted. |
I had asked to revert the PR on this ticket. The background is that our services with the .mixed cache format only displayed white tiles. Here is my config - it may help to understand the problem: dop20.zip I will also ask Mr Weskamm again to reopen this ticket. |
Thank you very much! |
We would prefer to maintain backwards compatibility. That means we would want to be able to read |
Both good ideas. We also have caches that cannot be refetched. |
I understand, I'll try to keep the fix backwards compatible for fetching the |
Context
Mapproxy has the ability to use mixed image formats (https://mapproxy.org/docs/nightly/configuration.html#format).
It works fine when the tiles stored in a geopackage file, but doesn't work when using s3/local directory hierarchy.
Expected Behavior
Tiles should be rendered to the client.
Actual Behavior
Nothing is rendered. All tiles are empty.
Possible Fix
S3:
When making a request (as shown here) the file's extension is
.mixed
. Since the original file extension isn't known, we need to consider checking for the correct extension and use it.Worst case scenario is making two requests per tile in order to find out the extension.
FS:
It's the same for FS - this line.
Steps to Reproduce
Create a directory with mixed tiles in it, upload to it S3 / use it locally and try to configure Mapproxy to use it.
Your Environment
The text was updated successfully, but these errors were encountered: