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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We play some tricks here with max zoom and tile sizes. For 256 tiles I recall the max zoom is 16, but for 512 tiles it's effectively 15, but when we build 256 tiles and 512 tiles we send the precut 256 zoom 16 tile for the 512 zoom 15 request. It's unclear to me what this
MAX_TILE_ZOOMis referring to and what it means in the context of a 512 px tile size only build. Do you know? Otherwise I'll do some reading...There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The variable defined here is for bbox build, it iterate all the zooms up to MAX_TILE_ZOOM to find tiles that touches the bounding box.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, LGTM