Skip to content
This repository was archived by the owner on Aug 8, 2023. It is now read-only.

Don't treat empty raster tiles as valid#8164

Merged
kkaefer merged 1 commit into
masterfrom
overzoom-raster-tiles
Feb 22, 2017
Merged

Don't treat empty raster tiles as valid#8164
kkaefer merged 1 commit into
masterfrom
overzoom-raster-tiles

Conversation

@kkaefer
Copy link
Copy Markdown
Member

@kkaefer kkaefer commented Feb 22, 2017

We're currently treating raster tiles that are "empty" or not found as valid by setting DataAvailability::All. Tiles that can't be found on the server and that return a 404 code are treated as valid responses with no content ("empty").

While the concept of an "empty" tile makes sense for vector sources (denoting no features within that tile), it doesn't make sense for raster sources. Instead, we should fall back to lower zoom level tiles. Our updateRenderables algorithm takes care of loading these lower zoom level tiles iff the loaded tile can't be rendered.

Fixes #8151

@mention-bot
Copy link
Copy Markdown

@kkaefer, thanks for your PR! By analyzing this pull request, we identified @jfirebaugh to be potential reviewers.

@kkaefer kkaefer force-pushed the overzoom-raster-tiles branch from 6ec6f52 to 8f267f9 Compare February 22, 2017 15:28
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

bug Core The cross-platform C++ core, aka mbgl

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants