Hi Linda, my suggestions inline.
Regards, Francesco On 1 Aug 2025 at 12:11 +0200, Linda Karlovská via pygeoapi <[email protected]>, wrote: > Hi everyone, > > I'm working with vector tiles on cadastral data using a custom tile matrix > set (specifically one based on EPSG:5514 — see > https://github.com/OpenGeoLabs/tiles-cz/blob/main/03-tile-matrix-set.md, it's > the second TMS listed, though only in Czech). > > While exploring the pygeoapi code, I noticed that two standard tile matrix > sets are currently hardcoded here: > https://github.com/geopython/pygeoapi/blob/master/pygeoapi/models/provider/base.py > As I understand it correctly, there's currently no built-in way in pygeoapi > to register or load additional tile matrix sets dynamically. Can you open an issue for this feature? It would be useful as other OGC API - Tiles implementations support that > To improve flexibility, I'd like to propose a small refactor and extension: > > 1. Move the two hardcoded TMSs into separate JSON files (e.g., > WorldCRS84Quad.json) in a new folder such as > pygeoapi/models/provider/tilematrixsets/. > 2. Add functionality to allow users to define their own custom tile matrix > sets by simply adding a JSON file to that directory (e.g., for my use case, > S-JTSKQuad.json). > > Does this direction make sense from the perspective of the current > architecture? I'd rather follow the pygeoapi plugin pattern to support custom injected tile matrixes > > And are there any things I should keep in mind when implementing this change? I would use a pygeoapi plugin for your use case with a custom tile matrix > Thanks a lot for your time and feedback! > > Best regards, > Linda Karlovska > _______________________________________________ > pygeoapi mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/pygeoapi >
_______________________________________________ pygeoapi mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/pygeoapi
