martin/tests/expected/auto/fnc.json

{
  "name": "public.function_zxy_query",
  "tilejson": "3.0.0",
  "tiles": [
    "http://localhost:3111/function_zxy_query/{z}/{x}/{y}"
  ]
}
Refactorings, content-type/enc, cli parsing, tests, minor fixes (#548) * introduce a new Connections object to track all positional strings passed as the CLI arguments * each tile provider can now indicate if it can take a positional CLI arg, and if the value can be shared between multiple providers, i.e. if its a directory that could contain files for multiple providers * make xyz use better types - u8 for zoom, u32 for x&y. Postgres casts those to INT2 and INT8 * minor bug in pre-push git hook to abort in case of a testingerror * added GIF detection/type * combine MVT and compression concepts into one enum more explicitly. It is not ideal (technically they are separate concerns), but it keeps it a bit simpler for now for multiple providers. * set content encoding and content type on HTTP responses if known, and also include them in the `/catalog` response (json) * raise an error if the user attempts to merge non-concatenatable tiles from multiple sources. We may want to implement it in the future, e.g. combine multiple semi-transparent PNGs. Or even combine GIF & PNG & JPEG * do not set content-type on empty responses (http 204) * add tilejson outputs to testing 2023-01-08 17:31:58 +03:00			`{`
			`"name": "public.function_zxy_query",`
Add .mbtiles support (#549) Adds a new [.mbtiles](https://github.com/mapbox/mbtiles-spec/blob/master/1.3/spec.md) backend, without the grid support. Uses extensive tile content detection, i.e. if the content is gzipped, png, jpeg, gif, webp. From CLI, can be as easy as adding a path to a directory that contains a .mbtiles file (works just like pmtiles support) ```bash # All .mbtiles files in this dir will be published. # The filename will be used as the source ID martin ./tests/fixtures ``` From configuration file, the path can be specified in a number of ways (same as pmtiles) ```yaml mbtiles: paths: # scan this whole dir, matching all .mbtiles files - /dir-path # specific mbtiles file will be published as mbtiles2 source - /path/to/mbtiles2.mbtiles sources: # named source matching source name to a single file pm-src1: /tmp/mbtiles.mbtiles # named source, where the filename is explicitly set. This way we will be able to add more options later pm-src2: path: /tmp/mbtiles.mbtiles ``` Fixes #494 2023-01-09 08:10:23 +03:00			`"tilejson": "3.0.0",`
Refactorings, content-type/enc, cli parsing, tests, minor fixes (#548) * introduce a new Connections object to track all positional strings passed as the CLI arguments * each tile provider can now indicate if it can take a positional CLI arg, and if the value can be shared between multiple providers, i.e. if its a directory that could contain files for multiple providers * make xyz use better types - u8 for zoom, u32 for x&y. Postgres casts those to INT2 and INT8 * minor bug in pre-push git hook to abort in case of a testingerror * added GIF detection/type * combine MVT and compression concepts into one enum more explicitly. It is not ideal (technically they are separate concerns), but it keeps it a bit simpler for now for multiple providers. * set content encoding and content type on HTTP responses if known, and also include them in the `/catalog` response (json) * raise an error if the user attempts to merge non-concatenatable tiles from multiple sources. We may want to implement it in the future, e.g. combine multiple semi-transparent PNGs. Or even combine GIF & PNG & JPEG * do not set content-type on empty responses (http 204) * add tilejson outputs to testing 2023-01-08 17:31:58 +03:00			`"tiles": [`
			`"http://localhost:3111/function_zxy_query/{z}/{x}/{y}"`
Add .mbtiles support (#549) Adds a new [.mbtiles](https://github.com/mapbox/mbtiles-spec/blob/master/1.3/spec.md) backend, without the grid support. Uses extensive tile content detection, i.e. if the content is gzipped, png, jpeg, gif, webp. From CLI, can be as easy as adding a path to a directory that contains a .mbtiles file (works just like pmtiles support) ```bash # All .mbtiles files in this dir will be published. # The filename will be used as the source ID martin ./tests/fixtures ``` From configuration file, the path can be specified in a number of ways (same as pmtiles) ```yaml mbtiles: paths: # scan this whole dir, matching all .mbtiles files - /dir-path # specific mbtiles file will be published as mbtiles2 source - /path/to/mbtiles2.mbtiles sources: # named source matching source name to a single file pm-src1: /tmp/mbtiles.mbtiles # named source, where the filename is explicitly set. This way we will be able to add more options later pm-src2: path: /tmp/mbtiles.mbtiles ``` Fixes #494 2023-01-09 08:10:23 +03:00			`]`
Refactorings, content-type/enc, cli parsing, tests, minor fixes (#548) * introduce a new Connections object to track all positional strings passed as the CLI arguments * each tile provider can now indicate if it can take a positional CLI arg, and if the value can be shared between multiple providers, i.e. if its a directory that could contain files for multiple providers * make xyz use better types - u8 for zoom, u32 for x&y. Postgres casts those to INT2 and INT8 * minor bug in pre-push git hook to abort in case of a testingerror * added GIF detection/type * combine MVT and compression concepts into one enum more explicitly. It is not ideal (technically they are separate concerns), but it keeps it a bit simpler for now for multiple providers. * set content encoding and content type on HTTP responses if known, and also include them in the `/catalog` response (json) * raise an error if the user attempts to merge non-concatenatable tiles from multiple sources. We may want to implement it in the future, e.g. combine multiple semi-transparent PNGs. Or even combine GIF & PNG & JPEG * do not set content-type on empty responses (http 204) * add tilejson outputs to testing 2023-01-08 17:31:58 +03:00			`}`