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

separate Tile's style zoom level from it's data zoom level #1912

Closed
ansis opened this issue Jan 8, 2016 · 2 comments
Closed

separate Tile's style zoom level from it's data zoom level #1912

ansis opened this issue Jan 8, 2016 · 2 comments

Comments

@ansis
Copy link
Contributor

ansis commented Jan 8, 2016

The current implementation of overscaled tile reparsing abuses the z coordinate to store the zoom level that needs to be used for style parsing. The real z is recovered using sourceMaxZoom. It's really hard to follow how this works or if it works.

A TileCoord should have two separate z's. One for the style and one for the actual vectortile.

@lucaswoj
Copy link
Contributor

lucaswoj commented Jan 8, 2016

ref #1909

ansis added a commit that referenced this issue Jan 27, 2016
fixes #1912

TileCoord's constructor now requires `sourceMaxZoom`, which is used to
calculate the TileCoord's data zoom level and for calculating child and
parent TileCoords.

The goal is to contain all the weird logic for representing overscaled
tiles within TileCoord.
@ansis ansis self-assigned this Jan 27, 2016
@ansis ansis removed their assignment Mar 17, 2016
@lucaswoj
Copy link
Contributor

Closing in favor of #2868 which highlights user-facing behaviour and doesn't specify an implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants