Brandon Liu
Brandon Liu
The python writer isn't particularly optimized for large use cases, but ideally it should work - that seems like too much ram consumption. What is the total # of tiles...
OK, thanks for the report. So it sounds like this isn't a hang. The progress bar might be nice but I don't think there's a clean way to add it...
[Go-pmtiles](https://github.com/protomaps/go-pmtiles) is now the preferred way to convert from mbtiles, which should be much more memory-efficient and shows a progress bar.
@migurski OK, I think I've wrapped my head around the design here: wondering if there's a need for: `0/0/0.pbf?attributes=L1:a1,L1:a2` - select multiple attributes in a single layer? In the case...
first pass of tile filtering implemented as a separate TS module in https://github.com/protomaps/PMTiles/compare/master...vtfilter but this isn't hooked up to any query string API yet.
did you set the `paint_rules` to match the layers in your file? do you know what the layers are named in the tiles?
@DavidDvpt what tool are you using going geojson > mbtiles?
add tile type as a required metadata field (png, jpg, mvt, etc)
Flaws in current design: * 512000 fixed-size header is wasteful * Index performs poorly for certain cases (panning at leaf level and leaf+level 1, especially) * Waste of ID space...
target metric: (total # of tiles in archive / size of index in bytes) = average number of bytes per tile entry Currently this is 17, 3-5 bytes per entry...