Acceptance criteria
- Tegola is configured to use beta PostGIS as a data provider
- Tegola is configured to serve vectors with layers that can be used with OSM bright
- Tegola is configured to use beta Redis as a cache
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Add example config for tegola deployment | maps/spikes | master | +384 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | ssastry | T263854 [Maps] Modernize Vector Tile Infrastructure | |||
| Resolved | MSantos | T269690 View an Example Map (using Tegola vector tile server) | |||
| Resolved | MSantos | T270169 Bootstrap Tegola vector-tile server with baseline MVT schema from OSM bright | |||
| Resolved | Jgiannelos | T270177 Configure tegola to serve tiles |
Regarding tegola config, I captured all the work done so far here: https://github.com/johngian/openmaptiles-tegola
It involves patches:
@MSantos OpenMapTiles by default uses some data as described here:
https://github.com/openmaptiles/openmaptiles-tools/tree/master/docker/import-data
Do you see this as a blocker for now?
All the data sources are freely licensed and doesn't block us to move forward. From that list we currently use water polygons as well but just sync this data in a different pace (once a month), in summary here are my two observations:
Some updates from our beta environment:
Endpoints:
Change 658239 had a related patch set uploaded (by Jgiannelos; owner: Jgiannelos):
[maps/spikes@master] Add example config for tegola deployment
Change 658239 merged by MSantos:
[maps/spikes@master] Add example config for tegola deployment