-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
.setFilter() triggers vector tile requests #2198
Comments
Could be related to #2174. |
Or it this expected behavior? I'm interested because we're trying to implement this functionality for a client, and it's a bit of a "make or break" to get this working. Would it be possible to used cached vector tiles instead of requesting new tiles, for example? |
Thanks for the bug report! This is not expected behavior. We'll take a look soon. |
Don't mean to rush anyone, but do you have an ETA for a fix? |
Is your browser cache disabled when your console is open? The current implementation makes new xhr request whenever it needs to reparse a tile. This should hit the browser cache pretty much always. Whenever a change to any layer definition or layout property the entire tile is reparsed. We plan to improve this by recreating only what changed, but there is no current eta for that. |
Can confirm this has to do with cache. I was serving vector tiles with Thanks a lot for the tip! Closing. |
Problem
When using .setFilter(), vector tiles that are already loaded get re-requested from server.
Requesting vector tiles when setting filter seems unnecessary and is a bit of a performance killer?
jsbin
See this jsbin for a working example.
Screen dump
Version
Mapbox-gl.js version:
0.14.3
Relevant code:
The text was updated successfully, but these errors were encountered: