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
With client side layers proposed as featured layers, we need to figure out how to serve the styles to the client.
Description
We have a couple of proposed featured layers that are Maplibre GL styles. These styles consist of a style json, spritesheet, and fonts. The MapLibre style contains the URL of the spritesheet and fonts.
The style, spritesheet, and fonts are all built by various processes. Some of them (particularly fonts) may not be easily automated and they don't need to be regenerated frequently.
Some options come to mind are
referencing an external style URL,
including files in the repo, or
trying to generate them at build time.
The last probably isn't an option for fonts.
I would like to avoid the situation we ended up with OpenLayers where we're compelled to keep an ancient version of software or a resource available forever.
Screenshots
No response
The text was updated successfully, but these errors were encountered:
Problem
With client side layers proposed as featured layers, we need to figure out how to serve the styles to the client.
Description
We have a couple of proposed featured layers that are Maplibre GL styles. These styles consist of a style json, spritesheet, and fonts. The MapLibre style contains the URL of the spritesheet and fonts.
The style, spritesheet, and fonts are all built by various processes. Some of them (particularly fonts) may not be easily automated and they don't need to be regenerated frequently.
Some options come to mind are
The last probably isn't an option for fonts.
I would like to avoid the situation we ended up with OpenLayers where we're compelled to keep an ancient version of software or a resource available forever.
Screenshots
No response
The text was updated successfully, but these errors were encountered: