Closed jrhizor closed 1 year ago
Thanks for the details. It sounds like the point of confusion is the distinction between vector tiles and raster tiles.
Converting between vector and raster tile data is computationally very expensive and would require bringing in a rasterizer like Maplibre GL native, and is impossible to do in a general style-agnostic way.
Closing this issue as operations on tiles is outside the scope of this utility project, which is only operations on containers.
It'd be great to allow converting between any pair of supported tile types (mvt, png, jpeg, or webp).
Maybe this could be an option for
pmtiles convert --format png <a> <b>
?Here's what happened to me (and I imagine other users not super familiar with mapping tools can easily run into similar problems):
react-leaflet
, pointing aTileLayer
athttps://<mydomain>/<pmtiles name>/{z}/{x}/{y}.mvt
. This resulted in a CORB error due to the fact thatTileLayer
was creatingimg
objects withmvt
files that the Cloudflare server was serving withapplication/x-protobuf
.protomaps
npm library to create the layer frommvt
files.There are a few options that would make this easier for new users:
react-leaflet
(I created a separate issue for this)