<html><body><p>Antonio, Francesco,</p><p><br></p>
<p>Thanks a lot for your input!</p>
<p>I’ve opened a new issue to describe the idea in more detail: <a href="https://github.com/geopython/pygeoapi/issues/2074" class rel="noopener">https://github.com/geopython/pygeoapi/issues/2074</a></p><p>I’d really appreciate it if you could take a look and let me know what you think.</p><br><p>Best regards,<br>Linda</p><p><br></p><aside>---------- Původní e-mail ----------<br>Od: Francesco Bartoli <xbartolone@gmail.com><br>Komu: pygeoapi@lists.osgeo.org, Linda Karlovská <linda.karlovska@seznam.cz><br>Datum: 3. 8. 2025 18:02:17<br>Předmět: Re: [pygeoapi] Externalizing tile matrix sets and supporting
custom TMS registration</aside><br><blockquote data-email="xbartolone@gmail.com">
<div>
<div>Hi Linda,</div>
<div> </div>
<div>my suggestions inline.</div>
</div>
<div><br>
<div>Regards,<br>
Francesco</div>
</div>
<div>
<div>On 1 Aug 2025 at 12:11 +0200, Linda Karlovská via pygeoapi <<a href="mailto:pygeoapi@lists.osgeo.org">pygeoapi@lists.osgeo.org</a>>, wrote:<br>
</div>
<blockquote style="margin:5px 5px;padding-left:10px;border-left-width:thin;border-left-style:solid;border-left-color:#1abc9c">
<div>Hi everyone,</div>
<div> </div>
<div>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).</div>
<div> </div>
<div>While exploring the pygeoapi code, I noticed that two standard tile matrix sets are currently hardcoded here:<br>
<a class href="https://github.com/geopython/pygeoapi/blob/master/pygeoapi/models/provider/base.py">https://github.com/geopython/pygeoapi/blob/master/pygeoapi/models/provider/base.py</a></div>
<div>As I understand it correctly, there's currently no built-in way in pygeoapi to register or load additional tile matrix sets dynamically.</div>
</blockquote>
<div><span class="-wm-spark-text-indent"> </span><span class="-wm-spark-text-indent"> </span>Can you open an issue for this feature? It would be useful as other OGC API - Tiles implementations support that</div>
<blockquote style="margin:5px 5px;padding-left:10px;border-left-width:thin;border-left-style:solid;border-left-color:#1abc9c">
<div>To improve flexibility, I'd like to propose a small refactor and extension:</div>
<ol type="1">
<li>Move the two hardcoded TMSs into separate JSON files (e.g., <code>WorldCRS84Quad.json</code>) in a new folder such as <code>pygeoapi/models/provider/tilematrixsets/</code>.</li>
<li>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, <code>S-JTSKQuad.json</code>).</li>
</ol>
<div>Does this direction make sense from the perspective of the current architecture?</div>
</blockquote>
<div><span class="-wm-spark-text-indent"> </span><span class="-wm-spark-text-indent"> </span> I'd rather follow the pygeoapi plugin pattern to support custom injected tile matrixes </div>
<blockquote style="margin:5px 5px;padding-left:10px;border-left-width:thin;border-left-style:solid;border-left-color:#1abc9c">
<div><br>
And are there any things I should keep in mind when implementing this change?</div>
</blockquote>
<div><span class="-wm-spark-text-indent"> </span><span class="-wm-spark-text-indent"> </span>I would use a pygeoapi plugin for your use case with a custom tile matrix</div>
<blockquote style="margin:5px 5px;padding-left:10px;border-left-width:thin;border-left-style:solid;border-left-color:#1abc9c">
<div>Thanks a lot for your time and feedback!</div>
<div> </div>
<div>Best regards,<br>
Linda Karlovska</div>
<div>_______________________________________________<br>
pygeoapi mailing list<br>
<a href="mailto:pygeoapi@lists.osgeo.org">pygeoapi@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/pygeoapi">https://lists.osgeo.org/mailman/listinfo/pygeoapi</a><br>
</div>
</blockquote>
</div>
</blockquote></body></html>