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

VPL merged tilesets behaviour at higher zoom levels #128

Open
sastcsgh opened this issue Dec 2, 2024 · 3 comments
Open

VPL merged tilesets behaviour at higher zoom levels #128

sastcsgh opened this issue Dec 2, 2024 · 3 comments

Comments

@sastcsgh
Copy link

sastcsgh commented Dec 2, 2024

Currently, in a tileset merged through from_vectortiles_merged, if a certain zoom level does not exist for a specific source, versatiles does not return it. It would be brilliant if there would be some way to configure it to behave like MapLibre does when a maximum zoom level for a source is specified, namely to re-use the highest existing zoom level for zoom levels above this.

@MichaelKreil
Copy link
Member

If I understand your issue correctly:

  • Consider a scenario with data source A covering zoom levels 1 to 3 and data source B covering zoom levels 2 to 4.
  • The expected behavior for from_vectortiles_merged is to provide merged vector tiles for zoom levels 1 through 4.

As far as I can tell, this should already work as described. Could you share a specific scenario where this isn’t the case?

@sastcsgh
Copy link
Author

sastcsgh commented Jan 7, 2025

Yes, it provides merged vector tiles for zoom levels 1 through 4, in the sense that it returns the tiles of data source B for zoom level 4. However, on zoom level 4, data source A is no longer included. What would be great (but probably not at all straightforward to implement) if the merged tileset would provide an overzoomed version of zoom level 3 of data source A, similar to the way that MapLibre does.

@MichaelKreil
Copy link
Member

I've fixed a lot of problems since version 0.14.x. Now I can't reproduce your issue.
Is it fixed in the latest version 0.15.1?

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

No branches or pull requests

2 participants