maplibre/martin
1
1
Fork 0
mirror of https://github.com/maplibre/martin.git synced 2024-12-19 12:51:37 +03:00
Code Issues Actions 5 Packages Projects Releases Wiki Activity
dbf25f041c
martin/tests/expected/generated_config.yaml

215 lines
5.5 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
listen_addresses: localhost:3111
postgres:
default_srid: 900913
[BREAKING] New bounds calculation methods (#958) * Remove `--disable-bounds` flag and `disable_bounds` config parameters. * Add `--auto-bounds` / `-b` CLI parameter and `auto_bounds` config value: * `quick`: Compute table geometry bounds, but abort if it takes longer than 5 seconds (default) * `calc`: Compute table geometry bounds. The startup time may be significant. Make sure all GEO columns have indexes * `skip`: Skip bounds calculation. The bounds will be set to the whole world * `-b` is now mapped to `--auto-bounds` param, but it will fail if used by itself because it now requires a value. Fixes #955
2023-10-22 10:30:18 +03:00
auto_bounds: calc
Implement postgres auto-publish (#546) * NEW: support for #512 - pg table/function auto-discovery * can filter schemas * can use patterns like `{schema}.{table}.{column}` and `{schema}.{function}` * NEW: add `disable_bounds` bool flag to allow disabling of the bounds computation * reworked integration tests to use yaml
2023-01-03 19:09:41 +03:00
auto_publish: true
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
[BREAKING] New bounds calculation methods (#958) * Remove `--disable-bounds` flag and `disable_bounds` config parameters. * Add `--auto-bounds` / `-b` CLI parameter and `auto_bounds` config value: * `quick`: Compute table geometry bounds, but abort if it takes longer than 5 seconds (default) * `calc`: Compute table geometry bounds. The startup time may be significant. Make sure all GEO columns have indexes * `skip`: Skip bounds calculation. The bounds will be set to the whole world * `-b` is now mapped to `--auto-bounds` param, but it will fail if used by itself because it now requires a value. Fixes #955
2023-10-22 10:30:18 +03:00
bounds:
- -170.94984639004662
- -84.20025580733805
- 167.70892858284475
- 74.23573284753762
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
geometry_type: POINT
properties:
Gid: int4
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
[BREAKING] New bounds calculation methods (#958) * Remove `--disable-bounds` flag and `disable_bounds` config parameters. * Add `--auto-bounds` / `-b` CLI parameter and `auto_bounds` config value: * `quick`: Compute table geometry bounds, but abort if it takes longer than 5 seconds (default) * `calc`: Compute table geometry bounds. The startup time may be significant. Make sure all GEO columns have indexes * `skip`: Skip bounds calculation. The bounds will be set to the whole world * `-b` is now mapped to `--auto-bounds` param, but it will fail if used by itself because it now requires a value. Fixes #955
2023-10-22 10:30:18 +03:00
bounds:
- -166.87107126230424
- -53.44747249115674
- 168.14061220360549
- 84.22411861475385
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
geometry_type: POINT
properties:
feat_id: int4
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
[BREAKING] New bounds calculation methods (#958) * Remove `--disable-bounds` flag and `disable_bounds` config parameters. * Add `--auto-bounds` / `-b` CLI parameter and `auto_bounds` config value: * `quick`: Compute table geometry bounds, but abort if it takes longer than 5 seconds (default) * `calc`: Compute table geometry bounds. The startup time may be significant. Make sure all GEO columns have indexes * `skip`: Skip bounds calculation. The bounds will be set to the whole world * `-b` is now mapped to `--auto-bounds` param, but it will fail if used by itself because it now requires a value. Fixes #955
2023-10-22 10:30:18 +03:00
bounds:
- -174.89475564568033
- -77.2579745396886
- 174.72753224514435
- 73.80785950599903
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
geometry_type: POINT
properties:
big_feat_id: int8
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:
schema: public
table: points1
srid: 4326
geometry_column: geom
[BREAKING] New bounds calculation methods (#958) * Remove `--disable-bounds` flag and `disable_bounds` config parameters. * Add `--auto-bounds` / `-b` CLI parameter and `auto_bounds` config value: * `quick`: Compute table geometry bounds, but abort if it takes longer than 5 seconds (default) * `calc`: Compute table geometry bounds. The startup time may be significant. Make sure all GEO columns have indexes * `skip`: Skip bounds calculation. The bounds will be set to the whole world * `-b` is now mapped to `--auto-bounds` param, but it will fail if used by itself because it now requires a value. Fixes #955
2023-10-22 10:30:18 +03:00
bounds:
- -179.27313970132585
- -67.52518563265659
- 162.60117193735186
- 84.93092095128937
Views handling (#571) * Adds a view to `points1.sql` fixture * Replaces `table` with `view` in log statements relating to views --------- Co-authored-by: Chris Thiange <cthiange@gmail.com>
2023-02-08 04:45:01 +03:00
geometry_type: POINT
properties:
gid: int4
points1_vw:
schema: public
table: points1_vw
srid: 4326
geometry_column: geom
[BREAKING] New bounds calculation methods (#958) * Remove `--disable-bounds` flag and `disable_bounds` config parameters. * Add `--auto-bounds` / `-b` CLI parameter and `auto_bounds` config value: * `quick`: Compute table geometry bounds, but abort if it takes longer than 5 seconds (default) * `calc`: Compute table geometry bounds. The startup time may be significant. Make sure all GEO columns have indexes * `skip`: Skip bounds calculation. The bounds will be set to the whole world * `-b` is now mapped to `--auto-bounds` param, but it will fail if used by itself because it now requires a value. Fixes #955
2023-10-22 10:30:18 +03:00
bounds:
- -179.27313970132585
- -67.52518563265659
- 162.60117193735186
- 84.93092095128937
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
geometry_type: POINT
properties:
gid: int4
points2:
schema: public
table: points2
srid: 4326
geometry_column: geom
[BREAKING] New bounds calculation methods (#958) * Remove `--disable-bounds` flag and `disable_bounds` config parameters. * Add `--auto-bounds` / `-b` CLI parameter and `auto_bounds` config value: * `quick`: Compute table geometry bounds, but abort if it takes longer than 5 seconds (default) * `calc`: Compute table geometry bounds. The startup time may be significant. Make sure all GEO columns have indexes * `skip`: Skip bounds calculation. The bounds will be set to the whole world * `-b` is now mapped to `--auto-bounds` param, but it will fail if used by itself because it now requires a value. Fixes #955
2023-10-22 10:30:18 +03:00
bounds:
- -174.050750735362
- -80.46177157848345
- 179.11187181086706
- 81.13068764165727
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
geometry_type: POINT
properties:
gid: int4
points3857:
schema: public
table: points3857
srid: 3857
geometry_column: geom
[BREAKING] New bounds calculation methods (#958) * Remove `--disable-bounds` flag and `disable_bounds` config parameters. * Add `--auto-bounds` / `-b` CLI parameter and `auto_bounds` config value: * `quick`: Compute table geometry bounds, but abort if it takes longer than 5 seconds (default) * `calc`: Compute table geometry bounds. The startup time may be significant. Make sure all GEO columns have indexes * `skip`: Skip bounds calculation. The bounds will be set to the whole world * `-b` is now mapped to `--auto-bounds` param, but it will fail if used by itself because it now requires a value. Fixes #955
2023-10-22 10:30:18 +03:00
bounds:
- -161.40590777554058
- -81.50727021609012
- 172.51549126768532
- 84.2440187164111
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
geometry_type: POINT
properties:
gid: int4
points_empty_srid:
schema: public
table: points_empty_srid
srid: 900913
geometry_column: geom
[BREAKING] New bounds calculation methods (#958) * Remove `--disable-bounds` flag and `disable_bounds` config parameters. * Add `--auto-bounds` / `-b` CLI parameter and `auto_bounds` config value: * `quick`: Compute table geometry bounds, but abort if it takes longer than 5 seconds (default) * `calc`: Compute table geometry bounds. The startup time may be significant. Make sure all GEO columns have indexes * `skip`: Skip bounds calculation. The bounds will be set to the whole world * `-b` is now mapped to `--auto-bounds` param, but it will fail if used by itself because it now requires a value. Fixes #955
2023-10-22 10:30:18 +03:00
bounds:
- -162.35196679784573
- -84.49919770031491
- 178.47294677445652
- 82.7000012450467
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
geometry_type: GEOMETRY
properties:
gid: int4
table_source:
schema: public
table: table_source
srid: 4326
geometry_column: geom
[BREAKING] New bounds calculation methods (#958) * Remove `--disable-bounds` flag and `disable_bounds` config parameters. * Add `--auto-bounds` / `-b` CLI parameter and `auto_bounds` config value: * `quick`: Compute table geometry bounds, but abort if it takes longer than 5 seconds (default) * `calc`: Compute table geometry bounds. The startup time may be significant. Make sure all GEO columns have indexes * `skip`: Skip bounds calculation. The bounds will be set to the whole world * `-b` is now mapped to `--auto-bounds` param, but it will fail if used by itself because it now requires a value. Fixes #955
2023-10-22 10:30:18 +03:00
bounds:
- -2.0
- -1.0
- 142.84131509869133
- 45.0
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
geometry_type: GEOMETRY
properties:
gid: int4
table_source_multiple_geom:
schema: public
table: table_source_multiple_geom
srid: 4326
geometry_column: geom1
[BREAKING] New bounds calculation methods (#958) * Remove `--disable-bounds` flag and `disable_bounds` config parameters. * Add `--auto-bounds` / `-b` CLI parameter and `auto_bounds` config value: * `quick`: Compute table geometry bounds, but abort if it takes longer than 5 seconds (default) * `calc`: Compute table geometry bounds. The startup time may be significant. Make sure all GEO columns have indexes * `skip`: Skip bounds calculation. The bounds will be set to the whole world * `-b` is now mapped to `--auto-bounds` param, but it will fail if used by itself because it now requires a value. Fixes #955
2023-10-22 10:30:18 +03:00
bounds:
- -136.62076049706184
- -78.3350299285405
- 176.56297743499888
- 75.78731065954437
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
geometry_type: POINT
properties:
gid: int4
table_source_multiple_geom.1:
schema: public
table: table_source_multiple_geom
srid: 4326
geometry_column: geom2
[BREAKING] New bounds calculation methods (#958) * Remove `--disable-bounds` flag and `disable_bounds` config parameters. * Add `--auto-bounds` / `-b` CLI parameter and `auto_bounds` config value: * `quick`: Compute table geometry bounds, but abort if it takes longer than 5 seconds (default) * `calc`: Compute table geometry bounds. The startup time may be significant. Make sure all GEO columns have indexes * `skip`: Skip bounds calculation. The bounds will be set to the whole world * `-b` is now mapped to `--auto-bounds` param, but it will fail if used by itself because it now requires a value. Fixes #955
2023-10-22 10:30:18 +03:00
bounds:
- -136.62076049706184
- -78.3350299285405
- 176.56297743499888
- 75.78731065954437
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
geometry_type: POINT
properties:
gid: int4
functions:
function_Mixed_Name:
schema: MixedCase
function: function_Mixed_Name
function_null:
schema: public
function: function_null
function_null_row:
schema: public
function: function_null_row
function_null_row2:
schema: public
function: function_null_row2
function_zoom_xy:
schema: public
function: function_zoom_xy
function_zxy:
schema: public
function: function_zxy
function_zxy2:
schema: public
function: function_zxy2
function_zxy_query:
schema: public
function: function_zxy_query
function_zxy_query_jsonb:
schema: public
function: function_zxy_query_jsonb
function_zxy_query_test:
schema: public
function: function_zxy_query_test
function_zxy_row:
schema: public
function: function_zxy_row
function_zxy_row_key:
schema: public
function: function_zxy_row_key
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:
Fix mbtiles validation, CI, and logging (#903)
2023-09-29 21:37:18 +03:00
paths:
- tests/fixtures/mbtiles
- tests/fixtures/pmtiles
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
sources:
Fix mbtiles validation, CI, and logging (#903)
2023-09-29 21:37:18 +03:00
png: tests/fixtures/pmtiles/png.pmtiles
stamen_toner__raster_CC-BY-ODbL_z3: tests/fixtures/pmtiles/stamen_toner__raster_CC-BY+ODbL_z3.pmtiles
webp2: tests/fixtures/pmtiles/webp2.pmtiles
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
mbtiles:
Fix mbtiles validation, CI, and logging (#903)
2023-09-29 21:37:18 +03:00
paths:
- tests/fixtures/mbtiles
- tests/fixtures/pmtiles
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
sources:
Fix mbtiles validation, CI, and logging (#903)
2023-09-29 21:37:18 +03:00
geography-class-jpg: tests/fixtures/mbtiles/geography-class-jpg.mbtiles
geography-class-jpg-diff: tests/fixtures/mbtiles/geography-class-jpg-diff.mbtiles
geography-class-jpg-modified: tests/fixtures/mbtiles/geography-class-jpg-modified.mbtiles
geography-class-png: tests/fixtures/mbtiles/geography-class-png.mbtiles
geography-class-png-no-bounds: tests/fixtures/mbtiles/geography-class-png-no-bounds.mbtiles
json: tests/fixtures/mbtiles/json.mbtiles
uncompressed_mvt: tests/fixtures/mbtiles/uncompressed_mvt.mbtiles
webp: tests/fixtures/mbtiles/webp.mbtiles
world_cities: tests/fixtures/mbtiles/world_cities.mbtiles
world_cities_diff: tests/fixtures/mbtiles/world_cities_diff.mbtiles
world_cities_modified: tests/fixtures/mbtiles/world_cities_modified.mbtiles
zoomed_world_cities: tests/fixtures/mbtiles/zoomed_world_cities.mbtiles
Reference in New Issue Copy Permalink