You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even though vtshaver is not designing for runtime style, we still want to make efforts to make things better.
Now we have two experimental ideas. This ticket is to track the process of support runtime style.
Style specific retain, we want to make some special marks in style specific, to mark which properties in a particular layer we want to use, then the vtshaver will keep the certain properties.
Query properties, vtshaver well accept a param to determine which properties the user want to use, then return the shaved tiles+the certain properties. For the client side, every time user wants to change the style, the client can access tile with the certain properties in query(like vector.pbf?styl=<path to style>&keep={"country_label" : ["name_ru", "name_de", "name_es"]}).
// style.json{"metadata": {"mapbox:retain": {"landuse": ["p6"],"water": ["all properties will already be kept so this value does not matter"],"test": [true]}}}
Support pass a param with properties to styleToFilters to determine with properties to keep
Even though
vtshaver
is not designing for runtime style, we still want to make efforts to make things better.Now we have two experimental ideas. This ticket is to track the process of support runtime style.
Style specific retain, we want to make some special marks in style specific, to mark which properties in a particular layer we want to use, then the vtshaver will keep the certain properties.
Query properties, vtshaver well accept a param to determine which properties the user want to use, then return the shaved tiles+the certain properties. For the client side, every time user wants to change the style, the client can access tile with the certain properties in query(like
vector.pbf?styl=<path to style>&keep={"country_label" : ["name_ru", "name_de", "name_es"]}
).cc w/ @springmeyer
The text was updated successfully, but these errors were encountered: