Optionally disable 1024px tile #309
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
November 21, 2017 16:46
This means that the coordinate has to be included explicitly, and is a stepping stone to being able to exclude the "top" coordinate if we don't want it for 1024px tiles.
rmarianski
approved these changes
Nov 21, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a configurable option to lop the top off the metatile pyramid. E.g: if we're using
metatile.size: 4to generate 4x4 metatiles, thenmetatile.start-zoom: 1should mean we don't generate the "1024px" tile.Note that this changes the meaning of
process_coord- it used to generate a tile forcoordand each ofcut_coords, but now only generates a tile for each ofcut_coords. This change in meaning (and the same forformat_tile) requires a corresponding change intileserver.