Sample configs: use PostGIS to generate MVT's

This commit is contained in:
Rafa de la Torre 2018-10-09 18:48:44 +02:00
parent b75c1f7f08
commit 9cffc8781a
5 changed files with 5 additions and 4 deletions

View File

@ -5,6 +5,7 @@ Released 2018-mm-dd
New features
- Aggregation time dimensions
- Update sample configurations to use PostGIS to generate MVT's by default (as in production)
- Upgrades Windshaft to [4.11.2](https://github.com/CartoDB/Windshaft/blob/4.11.2/NEWS.md#version-4112)
- `pg-mvt`: Use `query-rewriter` to compose the query to render a MVT tile. If not defined, it will use a Default Query Rewriter.
- `pg-mvt`: Fix bug while building query and there is no columns defined for the layer.

View File

@ -130,7 +130,7 @@ var config = {
//If enabled, MVTs will be generated with PostGIS directly, instead of using Mapnik,
//PostGIS 2.4 is required for this to work
//If disabled it will use Mapnik MVT generation
usePostGIS: false
usePostGIS: true
},
mapnik: {
// The size of the pool of internal mapnik backend

View File

@ -130,7 +130,7 @@ var config = {
//If enabled, MVTs will be generated with PostGIS directly, instead of using Mapnik,
//PostGIS 2.4 is required for this to work
//If disabled it will use Mapnik MVT generation
usePostGIS: false
usePostGIS: true
},
mapnik: {
// The size of the pool of internal mapnik backend

View File

@ -130,7 +130,7 @@ var config = {
//If enabled, MVTs will be generated with PostGIS directly, instead of using Mapnik,
//PostGIS 2.4 is required for this to work
//If disabled it will use Mapnik MVT generation
usePostGIS: false
usePostGIS: true
},
mapnik: {
// The size of the pool of internal mapnik backend

View File

@ -130,7 +130,7 @@ var config = {
//If enabled, MVTs will be generated with PostGIS directly, instead of using Mapnik,
//PostGIS 2.4 is required for this to work
//If disabled it will use Mapnik MVT generation
usePostGIS: false
usePostGIS: true
},
mapnik: {
// The size of the pool of internal mapnik backend