Brandon Liu
Brandon Liu
Here's what it would look like for `#metadata=true` as a URL option https://github.com/protomaps/PMTiles/commit/8127188258fb93ee60b5cc2cb3fed316e2687c0c Adding a API surface to `addProtocol` seems worse than extending an "API"(URLs) that we're already using.
Also related to https://github.com/protomaps/PMTiles/issues/239
TODO: confirm that the above works with non-remote URL sources, like a local FileSource.
I changed my mind and will make it a protocol level option: https://github.com/protomaps/PMTiles/pull/461 This means you cannot control the loading of metadata/attribution per source. That required using a `#metadata=true` in...
Released in 3.2.0. See example: https://github.com/protomaps/PMTiles/blob/main/js/examples/maplibre.html#L23
I intentionally made it this way because a single page app makes the management of the URL parameters too complicated.
the PMTiles viewer is designed for client-side decoding, if you are running ` pmtiles serve` you can use any map renderer that supports ZXY urls like maputnik: http://maplibre.org/maputnik/ but I...
> I tried maputnik but I can't do much You need to add it as a TileJSON (vector) source > https://api.protomaps.com/tiles/v3.json?key=with_my_key did you allow the CORS origin https://maplibre.org ? >...
If you are using the lambda you do not need anything PMTiles related on the client side, just use normal {z}/{x}/{y} URLs in OpenLayers.
remove the olpmtiles.js file. https://openlayers.org/en/latest/examples/webgl-vector-tiles.html