Replies: 3 comments 6 replies
-
(Moved to discussion) I get the motivation, but I think Styles themselves would be a better candidate for combining with a tileset, since fonts/sprites are only associated with a tileset through a style. You can as-is store a JSON Style within the arbitrary JSON section of PMTiles. You could even hack in a way to store fonts and sprites as base64 encoded values in there, but that's pretty ugly. One thing I have thought about is doing a range-request like thing with |
Beta Was this translation helpful? Give feedback.
-
I am looping back to this idea because I think it would be so much easier for users of MapLibre if they just had to have a single file on their server, the
The problem at the moment is that new users do not have a concept of styles, tiles, fonts, and sprites. They just want to get a map on their website. For that, they would probably expect to put some library (MapLibre GL JS and the pmtiles plugin) into their website and host the maps file on their server. PMTiles simplified the tiles aspect of storing the map so much already. If we could also put the other stuff into the PMTiles file it would basically be perfect. You are right @bdon that sprites and fonts can be reused between maps, but often a user just has a single map. |
Beta Was this translation helpful? Give feedback.
-
Esri has a vector tile package |
Beta Was this translation helpful? Give feedback.
-
I think it would be super convenient if we could store fonts and sprites in
.pmtiles
files. Like that, all the stuff needed to make a MapLibre GL JS map would be in one place...Beta Was this translation helpful? Give feedback.
All reactions