You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
for configuration, we currently have this pattern:
pmtiles:
paths:
# scan this whole dir, matching all *.pmtiles files
- /dir-path# specific pmtiles file will be published as a pmt source (filename without extension)
- /path/to/pmt.pmtiles# A web server with a PMTiles file that supports range requests
- https://example.org/path/tiles.pmtilessources:
# named source matching source name to a single filepm-src1: /path/to/pmt.pmtiles# A named source to a web server with a PMTiles file that supports range requestspm-web2: https://example.org/path/tiles.pmtiles
We can add s3 support as either an s3 subsection under pmtiles, or by adding a new top level pmtiles-s3. I think the first option is better, but it might be trickier to implement.
files are auto-discovered (using s3 enumeration - requires additional permission)
multiple s3 buckets
So it seems the usage is similar to postgres configuration, where we can have one or more pg connection (i.e. s3 authentication), and each connection can have one or more table (i.e. pmtiles files), and the table name can be declared in the config (with the corresponding source name), or they can be auto-discovered, in which case the source name is auto-generated, e.g. {filename} or {bucket}_{filename}.
The protomaps/PMTiles supports specifying a bucket (and a path prefix), and allows fetching any pmtiles object by name, rather than having to specify them all ahead of time, or listing the objects. Would require some refactoring here, but it's a sensible way to avoid expensive reconfigurations.
pmtiles
crate will soon support s3 buckets directly. Martin needs to enable support for S3-hosted pmtilesTODO
PmtS3Source
similar toPmtHttpSource
Developers can already use by adding this at the end of the root Cargo.toml:
See also #1125
CC: @alexjball @lseelenbinder
The text was updated successfully, but these errors were encountered: