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
I'm trying to use the Positron style in an offline map and therefore host fonts and style myself with a local http server.
Using a simple server like http-server to host the font files generated by this project seems to be limited to work with styles that contain only a single font family. With the Positron style, the url {fontstack}/{range}.pbf of the glyphs property gets replaced with Metropolis%20Regular,Noto%20Sans%20Regular/0-255.pbf and fails. And according to the Mapbox documentation {fontstack} is replaced with a comma-separated list.
The Maptiler seems to have this implemented: https://api.maptiler.com/fonts/Metropolis%20Regular,Noto%20Sans%20Regular/0-255.pbf?key={key}
Is there a solution available to this problem? How to translate the output folder of this project to such an API request? What is the expected result by the API?
Thanks.
The text was updated successfully, but these errors were encountered:
I'm trying to use the Positron style in an offline map and therefore host fonts and style myself with a local http server.
Using a simple server like http-server to host the font files generated by this project seems to be limited to work with styles that contain only a single font family. With the Positron style, the url
{fontstack}/{range}.pbf
of theglyphs
property gets replaced withMetropolis%20Regular,Noto%20Sans%20Regular/0-255.pbf
and fails. And according to the Mapbox documentation {fontstack} is replaced with a comma-separated list.The Maptiler seems to have this implemented:
https://api.maptiler.com/fonts/Metropolis%20Regular,Noto%20Sans%20Regular/0-255.pbf?key={key}
Is there a solution available to this problem? How to translate the output folder of this project to such an API request? What is the expected result by the API?
Thanks.
The text was updated successfully, but these errors were encountered: