maplibre/martin
1
1
Fork 0
mirror of https://github.com/maplibre/martin.git synced 2024-12-19 21:01:45 +03:00
Code Issues Actions 5 Packages Projects Releases Wiki Activity
3e2dceb4bf
martin/tests/expected/given_config.yaml

164 lines
3.2 KiB
YAML
Raw Normal View History

Fix legacy DB, add CI tests (#547) * fixed SQL to work on older PG versions * re-enable CI to test expected `test.sh` output against the one stored in the `tests/expected` * add postgres in docker tests on linux - one for the oldest supported DB, and another using the more recent version * minor justfile cleanup * ensure config files are sorted alphabetically
2023-01-01 08:03:21 +03:00
keep_alive: 75
listen_addresses: localhost:3111
worker_processes: 1
postgres:
default_srid: 4326
Feat: max_feature_count query limit (#576) Implements #384 - ability to limit the number of features included in a tile from a Postgres table/view. This allows zoomed-out view of a table with a reasonable speed because each tile could be limited in size, rather than include millions of features. If set on a CLI, overrides whatever is set in the config file (if given). Any naming suggestions?
2023-02-17 19:11:16 +03:00
max_feature_count: 1000
Fix legacy DB, add CI tests (#547) * fixed SQL to work on older PG versions * re-enable CI to test expected `test.sh` output against the one stored in the `tests/expected` * add postgres in docker tests on linux - one for the oldest supported DB, and another using the more recent version * minor justfile cleanup * ensure config files are sorted alphabetically
2023-01-01 08:03:21 +03:00
pool_size: 20
Improve auto-publish usability (#795) * on `--save-config`, only save configured `auto_publish` settings * alias `from_schemas` as `from_schema` * add integration testing for `auto_publish` * if integration test DB preloading fails, try to clean up the test DB * A few more info traces This change should benefit testing of the #790 cc: @Binabh
2023-08-04 00:51:10 +03:00
auto_publish:
tables:
from_schemas: autodetect
adds support for id_column in tables for auto_publish (#790) Resolves #682 - [x] Get id_column string from config.yaml and use for id column - [x] Support for list of strings - [x] Add info/warnings if column is not there or is of wrong type - [x] if column for the feature ID is found, remove it from properties (see inline comment) - [x] cleanup logging messages - [x] need more tests to catch other edge cases --------- Co-authored-by: Yuri Astrakhan <YuriAstrakhan@gmail.com>
2023-08-13 05:06:23 +03:00
id_columns:
- feat_id
- big_feat_id
Fix legacy DB, add CI tests (#547) * fixed SQL to work on older PG versions * re-enable CI to test expected `test.sh` output against the one stored in the `tests/expected` * add postgres in docker tests on linux - one for the oldest supported DB, and another using the more recent version * minor justfile cleanup * ensure config files are sorted alphabetically
2023-01-01 08:03:21 +03:00
tables:
MixPoints:
schema: MixedCase
table: MixPoints
srid: 4326
geometry_column: Geom
id_column: giD
bounds:
- -170.94984639004662
- -84.20025580733805
- 167.70892858284475
- 74.23573284753762
geometry_type: POINT
properties:
taBLe: text
Improve auto-publish usability (#795) * on `--save-config`, only save configured `auto_publish` settings * alias `from_schemas` as `from_schema` * add integration testing for `auto_publish` * if integration test DB preloading fails, try to clean up the test DB * A few more info traces This change should benefit testing of the #790 cc: @Binabh
2023-08-04 00:51:10 +03:00
auto_table:
schema: autodetect
table: auto_table
srid: 4326
geometry_column: geom
adds support for id_column in tables for auto_publish (#790) Resolves #682 - [x] Get id_column string from config.yaml and use for id column - [x] Support for list of strings - [x] Add info/warnings if column is not there or is of wrong type - [x] if column for the feature ID is found, remove it from properties (see inline comment) - [x] cleanup logging messages - [x] need more tests to catch other edge cases --------- Co-authored-by: Yuri Astrakhan <YuriAstrakhan@gmail.com>
2023-08-13 05:06:23 +03:00
id_column: feat_id
Improve auto-publish usability (#795) * on `--save-config`, only save configured `auto_publish` settings * alias `from_schemas` as `from_schema` * add integration testing for `auto_publish` * if integration test DB preloading fails, try to clean up the test DB * A few more info traces This change should benefit testing of the #790 cc: @Binabh
2023-08-04 00:51:10 +03:00
bounds:
- -166.87107126230424
- -53.44747249115674
- 168.14061220360549
- 84.22411861475385
extent: 4096
buffer: 64
clip_geom: true
geometry_type: POINT
properties:
gid: int4
adds support for id_column in tables for auto_publish (#790) Resolves #682 - [x] Get id_column string from config.yaml and use for id column - [x] Support for list of strings - [x] Add info/warnings if column is not there or is of wrong type - [x] if column for the feature ID is found, remove it from properties (see inline comment) - [x] cleanup logging messages - [x] need more tests to catch other edge cases --------- Co-authored-by: Yuri Astrakhan <YuriAstrakhan@gmail.com>
2023-08-13 05:06:23 +03:00
bigint_table:
schema: autodetect
table: bigint_table
srid: 4326
geometry_column: geom
id_column: big_feat_id
bounds:
- -174.89475564568033
- -77.2579745396886
- 174.72753224514435
- 73.80785950599903
extent: 4096
buffer: 64
clip_geom: true
geometry_type: POINT
properties:
id: int4
Fix legacy DB, add CI tests (#547) * fixed SQL to work on older PG versions * re-enable CI to test expected `test.sh` output against the one stored in the `tests/expected` * add postgres in docker tests on linux - one for the oldest supported DB, and another using the more recent version * minor justfile cleanup * ensure config files are sorted alphabetically
2023-01-01 08:03:21 +03:00
points1:
[breaking] Use table name as the layer ID for PG tables (#598) * [BREAKING] Use source ID (table name) as the default layer ID, instead of `schema.table.column` * Add support for the optional `layer_id` table config parameter Fix #595
2023-03-13 14:41:25 +03:00
layer_id: abc
Fix legacy DB, add CI tests (#547) * fixed SQL to work on older PG versions * re-enable CI to test expected `test.sh` output against the one stored in the `tests/expected` * add postgres in docker tests on linux - one for the oldest supported DB, and another using the more recent version * minor justfile cleanup * ensure config files are sorted alphabetically
2023-01-01 08:03:21 +03:00
schema: public
table: points1
srid: 4326
geometry_column: geom
minzoom: 0
maxzoom: 30
bounds:
- -180.0
- -90.0
- 180.0
- 90.0
extent: 4096
buffer: 64
clip_geom: true
geometry_type: POINT
properties:
gid: int4
points2:
schema: public
table: points2
srid: 4326
geometry_column: geom
minzoom: 0
maxzoom: 30
bounds:
- -180.0
- -90.0
- 180.0
- 90.0
extent: 4096
buffer: 64
clip_geom: true
geometry_type: POINT
properties:
gid: int4
points3857:
schema: public
table: points3857
srid: 3857
geometry_column: geom
minzoom: 0
maxzoom: 30
bounds:
- -180.0
- -90.0
- 180.0
- 90.0
extent: 4096
buffer: 64
clip_geom: true
geometry_type: POINT
properties:
gid: int4
table_source:
schema: public
table: table_source
srid: 4326
geometry_column: geom
minzoom: 0
maxzoom: 30
bounds:
- -180.0
- -90.0
- 180.0
- 90.0
extent: 4096
buffer: 64
clip_geom: true
geometry_type: GEOMETRY
properties:
gid: int4
functions:
function_zxy_query:
schema: public
function: function_zxy_query
minzoom: 0
maxzoom: 30
bounds:
- -180.0
- -90.0
- 180.0
- 90.0
function_zxy_query_test:
schema: public
function: function_zxy_query_test
minzoom: 0
maxzoom: 30
bounds:
- -180.0
- -90.0
- 180.0
- 90.0
Add .pmtiles file support (#517) Merge after #548 Adds a new [.pmtiles](https://protomaps.com/docs/pmtiles/) backend. Supports all formats like png, vector, etc. From CLI, can be as easy as adding a path to a directory that contains a .pmtiles file: ```bash # All *.pmtiles 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: ```yaml pmtiles: paths: # scan this whole dir, matching all *.pmtiles files - /dir-path # specific pmtiles file will be published as pmtiles2 source - /path/to/pmtiles2.pmtiles sources: # named source matching source name to a single file pm-src1: /tmp/pmtiles.pmtiles # named source, where the filename is explicitly set. This way we will be able to add more options later pm-src2: path: /tmp/pmtiles.pmtiles ``` Fixes #508
2023-01-08 22:19:11 +03:00
pmtiles:
sources:
fix (re-)compression of images (#579) Compression middleware turned out to be hard to use for image cases - it simply looks at the content-encoding, and if not set, tries to compress if accepted by the client. Instead, now individual routes are configured with either that middleware, or for tiles, I decompress and optionally recompress if applicable. Now encoding is tracked separately from the tile content, making it cleaner too. Plus lots of tests for mbtiles & pmtiles. Fixes #577
2023-02-20 18:44:22 +03:00
pmt: tests/fixtures/files/stamen_toner__raster_CC-BY+ODbL_z3.pmtiles
Add dynamic sprites support (#715) Dynamically create image sprites for MapLibre rendering, given a directory with images. ### TODO * [x] Work with @flother to merge these PRs * [x] https://github.com/flother/spreet/pull/59 (must have) * [x] https://github.com/flother/spreet/pull/57 * [x] https://github.com/flother/spreet/pull/56 * [ ] https://github.com/flother/spreet/pull/62 (not required but nice to have, can upgrade later without any code changes) * [x] Add docs to the book * [x] Add CLI param, e.g. `--sprite <dir_path>` * [x] Don't output `.sprites` in auto-genned config when not in use ### API Per [MapLibre sprites API](https://maplibre.org/maplibre-style-spec/sprite/), we need to support the following: * `/sprite/<sprite_id>.json` metadata about the sprite file - all coming from a single directory * `/sprite/<sprite_id>.png` all images combined into a single PNG * `/sprite/<sprite_id>@2x.json` same but for high DPI devices * `/sprite/<sprite_id>@2x.png` Multiple sprite_id values can be combined into one sprite with the same pattern as for tile joining: `/sprite/<sprite_id1>,<sprite_id2>,...,<sprite_idN>[.json|.png|@2x.json|@2x.png]`. No ID renaming is done, so identical names will override one another. ### Configuration [Config file](https://maplibre.org/martin/config-file.html) and possibly CLI should have a simple option to serve sprites. The configuration may look similar to how mbtiles and pmtiles are configured: ```yaml # Publish sprite images sprites: paths: # scan this whole dir, matching all image files, and publishing it as "my_images" sprite source - /path/to/my_images sources: # named source matching source name to a directory my_sprites: /path/to/some_dir ``` Implement #705
2023-06-16 15:19:47 +03:00
sprites:
paths: tests/fixtures/sprites/src1
sources:
mysrc: tests/fixtures/sprites/src2
Reference in New Issue Copy Permalink