Generating Separated Tiles

[helloimalastair]

Hey y'all!

Is there a way to get planetiler to generate one file per tile, rather than a single file that contains all tiles? Currently working with a single .pmtiles file, but looks like Range requests aren't the most performant...

[msbarry]

Currently to do this you could generate an mbtiles archive then use a tool like tilelive-copy to extract it to files on disk.

Now that we have an easy way to plug in more archive types though it wouldn't be much work to add a "file" output type that would do this directly.

[helloimalastair]

Just took a look at what appears to be tilelive-copy, but it looks like it still copies from file to file. Or did you mean rewrite the code myself to manually create each individual tile?

On the topic of the custom archive type, is that a flag I can enable somewhere?

[msbarry]

Just took a look at what appears to be tilelive-copy, but it looks like it still copies from file to file. Or did you mean rewrite the code myself to manually create each individual tile?

In the past I've gotten tilelive-copy to work by doing npm install -g @mapbox/tilelive @mapbox/mbtiles @mapbox/tilelive-file then tilelive-copy input.mbtiles file://./tiles

On the topic of the custom archive type, is that a flag I can enable somewhere?

Not yet, I opened #536 to track this.

[bdon]

@helloimalastair have you experienced a difference between range request latency and non-range requests? From my experience the latency may be inherent to storage like Cloudflare R2 irrespective of whether the Range header is used.

[bdon]

See https://github.com/bdon/cloudflare-r2-latency/tree/main for test script on large vs small files and range vs non-range requests. It does seem that range requests for the end of large files are slower than non-range requests for small files, but not by any severe factor (2x, etc), though it is worth investigating more

(the test files were created in the US West region)

[bdon]

See protomaps/PMTiles#150 (comment) for updates on R2

[msbarry]

Nice! Do you have any stats on what the new performance looks like?

[bdon]

You can try https://github.com/bdon/cloudflare-r2-latency/tree/main - on my EC2 instance near the storage region the results are fairly comparable 180-220ms for all sizes of files now

[msbarry]

Ah nice, yeah I'm seeing 350-400ms
from Boston now.