Skip to content
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

Sparse storage for Geopackage caches #369

Open
brncsk opened this issue Jul 18, 2018 · 0 comments
Open

Sparse storage for Geopackage caches #369

brncsk opened this issue Jul 18, 2018 · 0 comments

Comments

@brncsk
Copy link

brncsk commented Jul 18, 2018

Context

As per the Geopackage specification, tile matrices can be sparsely populated: any tile can be omitted from the database. In fact, this is exactly what the OGR driver does (see section 'Creation issues') to save disk space by avoiding storing fully transparent tiles. MapProxy should probably do the same.

Expected Behavior

MapProxy should refrain from writing fully transparent tiles into Geopackage files.

Actual Behavior

MapProxy writes each and every tile into the Geopackage file even if they are fully transparent.

Possible Fix

This possibly overlaps with the functionality of link_single_color_images.

Your Environment

  • Version used: 1.11
  • Environment name and version (e.g. Python 2.7.5 with mod_wsgi 4.5.9): Python 3.4.5
  • Server type and version: N/A
  • Operating System and version: SLES 11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants