Style Data for the Base Maps? Raster? about basemaps HOT 5 CLOSED

@prusswan in many cases it's easier to "assemble" a style JavaScript object (not JSON) by grabbing the layers from e.g. https://unpkg.com/[email protected]/dist/layers/light.json and providing your own sources key.

That doesn't address the case of Maputnik, etc though. What I may do is just spin up an editor interface with the right style.json preloaded? Is there another case for needing a style.json?

I have that as part of the hosted API with API keys too:

https://api.protomaps.com/styles/v2/dark.json?key=KEY

from basemaps.

Go to https://maps.protomaps.com/ and choose "get Style JSON" and inline that JSON into your application. This lets you customize it as well.

Because the JSON is static I don't see huge value in embedding the style into the Lambda API. The other option if you're using JS is to load the style object from NPM but I don't think that is relevant to Flutter.

PMTiles are static archives of tiles, vector or raster. If you want to store raster tiles you need to generate those raster tiles somewhere. Converting from vector to raster tiles requires a rasterizer like Mapnik or MapLibre GL Native which is computationally heavy and outside the scope of this project.

from basemaps.

It would be convenient if the style.json for the respective default styles is also provided as part of the API (would make it easier to use with https://maputnik.github.io). One workaround to get a hosted style json, is to use the daily builds https://maps.protomaps.com/builds/ -> Compare in Maperture -> something like https://build-metadata.protomaps.dev/[email protected]+theme@[email protected]

from basemaps.

I have that as part of the hosted API with API keys too:

That's neat and exactly what @coogle and I was looking for. Would be great to mention in the docs (e.g. https://protomaps.com/other), especially for users familiar with Mapbox/OpenMapTiles etc. Did not know about protomaps-themes-base as I only found this repo and thought users were expected to build the style.json themselves

Is there another case for needing a style.json?

Other than the online maputnik, I use it for working with other map clients and libraries where it is convenient to download/reference a style that already exists and just override the tile url or strip out the parts I don't need

from basemaps.

I listed out the hosted style endpoints at https://protomaps.com/other

The styles as part of the open source project have source code at https://github.com/protomaps/basemaps/tree/main/styles and also are compiled into layers objects like this: http://unpkg.com/[email protected]/dist/layers/dark.json - seems easiest to let you assemble your own Style object with the correct sources keys. Let me know if you find a better way!

from basemaps.