Multiple layers of the same type

[pnorman]

There is an example of a water layer, but it might not be what everyone needs. It's not clear how to add two layers to the repo which cover the same content and have the same most-obvious name.

[lukasmartinelli]

There is an example of a water layer, but it might not be what everyone needs. It's not clear how to add two layers to the repo which cover the same content and have the same most-obvious name.

Yes - we hadn't had that case yet but water is a good example where different implementations are desirable.

If one is choosing two layers that have the same layer id (e.g. water) only the last one would take effect.

So for this tileset referencing both layers.

tileset:
  layers:
    - layers/water/water.yaml
    - layers/water_different/water.yaml

The later one water_different/water.yaml would have effect.

layers/water
├── mapping.yaml
├── water.sql
└── water.yaml (id of layer is `water`)

layers/water_different
└── water.yaml (id of layer is `water` as well)

One would switch it out in the tileset definition for a different layer.
Happy for feedback on the layer structure, very glad for the feedback and these questions posed by you.

[lukasmartinelli]

We have internally agreed that OpenMapTiles should be more schema than layer catalog (since essentially it is always bound to a certain backend e.g. imposm3).

What helps to solve the use case of alternative layers is that we will make the ids configurable in the tileset rather in tile definition #43 Then you can use the approach I described above and explicitly give them an ID.