Jo
@tomkralidis I think it is working! :-) https://noc.social/@pygeoapi
I think the issue may be here: https://github.com/geopython/pygeoapi/blame/1e424174f5c5d73391abad4e46ca378d544d489d/pygeoapi/api.py#L1246-L1248 It will only read one tile provider. One possible approach could be to create a vector-tile and raster-tile providers.
@PascalLike @francbartoli please take a look at this https://github.com/geopython/pygeoapi/issues/987
@francbartoli @PascalLike I guess this is solved now.
@pa5cal thank you for reporting this. Does the issue still persist in the latest version?
@ghobona @cportele could you have a look at this?
@skyNacho @francbartoli what is the status of this plugin? I recogn this could be important enough to be in the core?
@PascalLike @KoalaGeo As the metadata backend and the support to pg_tileserv was completely refactored, could you check if this issue was solved? If not, feel free to reopen it. https://docs.pygeoapi.io/en/stable/data-publishing/ogcapi-tiles.html#mvt-proxy
@KoalaGeo there is a [3D tiles candidate standard](https://portal.ogc.org/files/102132).
@landryb pygeoapi does support now generic tiles providers in the formats `{z}/{x}/{y}` or `{z}/{y}/{x}`. [Tiles rendered using Pg_tileserv or Elastisearch, can be published as OGC API Tiles](https://docs.pygeoapi.io/en/latest/data-publishing/ogcapi-tiles.html#connection-examples).