<div dir="ltr"><div>Hi Linda,</div><div><br></div><div>Thanks for the suggestion. </div><div><br></div><div>Please note that some providers may support some tile matrix sets and others may not. Currently, these are the Tiles providers:<br><br><a href="https://github.com/search?q=repo%3Ageopython%2Fpygeoapi%20BaseTileProvider&type=code">https://github.com/search?q=repo%3Ageopython%2Fpygeoapi%20BaseTileProvider&type=code</a><br><br><a href="https://github.com/search?q=repo%3Ageopython%2Fpygeoapi%20BaseMVTProvider&type=code">https://github.com/search?q=repo%3Ageopython%2Fpygeoapi%20BaseMVTProvider&type=code</a><br><br>With the current system, it's pretty easy to acknowledge when a tile matrix set is supported or not in a specific provider.</div><div><br>Your suggestion would be a very nice improvement, but we still need a way to express this relation between providers and the tile matrix sets they support. Do you think there could be a way to address this with the changes you have in mind?</div><div><br></div><div>Thank you and Kind regards,</div><div>Antonio Cerciello</div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, Aug 1, 2025 at 9:00 PM <<a href="mailto:pygeoapi-request@lists.osgeo.org">pygeoapi-request@lists.osgeo.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send pygeoapi mailing list submissions to<br>
<a href="mailto:pygeoapi@lists.osgeo.org" target="_blank">pygeoapi@lists.osgeo.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.osgeo.org/mailman/listinfo/pygeoapi" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/pygeoapi</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:pygeoapi-request@lists.osgeo.org" target="_blank">pygeoapi-request@lists.osgeo.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:pygeoapi-owner@lists.osgeo.org" target="_blank">pygeoapi-owner@lists.osgeo.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of pygeoapi digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Externalizing tile matrix sets and supporting custom TMS<br>
registration (Linda Karlovsk?)<br>
2. next meeting 05 September 12h UTC (Tom Kralidis)<br>
3. Re: PSC vote: approve travel cost for FOSS4G 2025<br>
(Angelos Tzotsos)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 01 Aug 2025 11:49:31 +0200 (CEST)<br>
From: Linda Karlovsk? <<a href="mailto:linda.karlovska@seznam.cz" target="_blank">linda.karlovska@seznam.cz</a>><br>
To: <<a href="mailto:pygeoapi@lists.osgeo.org" target="_blank">pygeoapi@lists.osgeo.org</a>><br>
Subject: [pygeoapi] Externalizing tile matrix sets and supporting<br>
custom TMS registration<br>
Message-ID: <<a href="mailto:2Wt.9%7DqCv.2PCuinq4UP2.1eZ8sh@seznam.cz" target="_blank">2Wt.9}qCv.2PCuinq4UP2.1eZ8sh@seznam.cz</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
<br>
Hi everyone,<br>
<br>
<br>
<br>
<br>
I'm working with vector tiles on cadastral data using a custom tile matrix <br>
set (specifically one based on EPSG:5514 ? see <a href="https://github.com/OpenGeoLabs/tiles-cz/blob/main/03-tile-matrix-set.md" rel="noreferrer" target="_blank">https://github.com/<br>
OpenGeoLabs/tiles-cz/blob/main/03-tile-matrix-set.md</a>, it's the second TMS <br>
listed, though only in Czech).<br>
<br>
<br>
<br>
<br>
While exploring the pygeoapi code, I noticed that two standard tile matrix <br>
sets are currently hardcoded here:<br>
<a href="https://github.com/geopython/pygeoapi/blob/master/pygeoapi/models/provider/base.py" rel="noreferrer" target="_blank">https://github.com/geopython/pygeoapi/blob/master/pygeoapi/models/provider/<br>
base.py</a><br>
(<a href="https://github.com/geopython/pygeoapi/blob/master/pygeoapi/models/provider/base.py" rel="noreferrer" target="_blank">https://github.com/geopython/pygeoapi/blob/master/pygeoapi/models/provider/base.py</a>)<br>
<br>
As I understand it correctly, there's currently no built-in way in pygeoapi <br>
to register or load additional tile matrix sets dynamically.<br>
<br>
To improve flexibility, I'd like to propose a small refactor and extension:<br>
<br>
1. <br>
Move the two hardcoded TMSs into separate JSON files (e.g., WorldCRS84<br>
Quad.json) in a new folder such as pygeoapi/models/provider/<br>
tilematrixsets/.<br>
2. <br>
Add functionality to allow users to define their own custom tile matrix <br>
sets by simply adding a JSON file to that directory (e.g., for my use <br>
case, S-JTSKQuad.json).<br>
<br>
<br>
Does this direction make sense from the perspective of the current <br>
architecture?<br>
And are there any things I should keep in mind when implementing this <br>
change?<br>
<br>
<br>
<br>
<br>
Thanks a lot for your time and feedback!<br>
<br>
<br>
<br>
<br>
Best regards,<br>
Linda Karlovska<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.osgeo.org/pipermail/pygeoapi/attachments/20250801/84c43a50/attachment-0001.htm" rel="noreferrer" target="_blank">http://lists.osgeo.org/pipermail/pygeoapi/attachments/20250801/84c43a50/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 1 Aug 2025 10:36:28 -0400<br>
From: Tom Kralidis <<a href="mailto:tomkralidis@gmail.com" target="_blank">tomkralidis@gmail.com</a>><br>
To: Tom Kralidis via pygeoapi <<a href="mailto:pygeoapi@lists.osgeo.org" target="_blank">pygeoapi@lists.osgeo.org</a>><br>
Subject: [pygeoapi] next meeting 05 September 12h UTC<br>
Message-ID:<br>
<<a href="mailto:CAFWXLWU8crn2aaoHRWDAjkqjxyH73rRptJPKOvr-Pbicip%2Bi0w@mail.gmail.com" target="_blank">CAFWXLWU8crn2aaoHRWDAjkqjxyH73rRptJPKOvr-Pbicip+i0w@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi all: just a note that we will be resuming monthly meetings on 05<br>
September 2025 at 12h UTC. Please see [1] for more information and agenda.<br>
<br>
Thanks<br>
<br>
..Tom<br>
<br>
[1] <a href="https://github.com/geopython/pygeoapi/wiki/Meeting-2025-09-05" rel="noreferrer" target="_blank">https://github.com/geopython/pygeoapi/wiki/Meeting-2025-09-05</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.osgeo.org/pipermail/pygeoapi/attachments/20250801/9df68efa/attachment-0001.htm" rel="noreferrer" target="_blank">http://lists.osgeo.org/pipermail/pygeoapi/attachments/20250801/9df68efa/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Fri, 1 Aug 2025 17:51:24 +0300<br>
From: Angelos Tzotsos <<a href="mailto:gcpp.kalxas@gmail.com" target="_blank">gcpp.kalxas@gmail.com</a>><br>
To: <a href="mailto:pygeoapi@lists.osgeo.org" target="_blank">pygeoapi@lists.osgeo.org</a><br>
Subject: Re: [pygeoapi] PSC vote: approve travel cost for FOSS4G 2025<br>
Message-ID: <<a href="mailto:b86f510c-bb9c-4d56-8c7a-765b82c6e5cf@gmail.com" target="_blank">b86f510c-bb9c-4d56-8c7a-765b82c6e5cf@gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8; format=flowed<br>
<br>
+1<br>
Angelos<br>
<br>
On 7/29/25 16:00, Francesco Bartoli via pygeoapi wrote:<br>
> +1<br>
><br>
> Ciao<br>
> Francesco<br>
> On 29 Jul 2025 at 13:37 +0200, Just van den Broecke via pygeoapi <<a href="mailto:pygeoapi@lists.osgeo.org" target="_blank">pygeoapi@lists.osgeo.org</a>>, wrote:<br>
>> +1<br>
>><br>
>> Just<br>
>><br>
>> On 28/07/2025 21:54, Tom Kralidis via pygeoapi wrote:<br>
>>> Dear pygeoapi PSC:<br>
>>><br>
>>> This is a motion to approve up to 2 pygeoapi developers to travel to the<br>
>>> FOSS4G event on 17-23 November 2025 [1], to provide the Diving into<br>
>>> pygeoapi workshop [2] as well as the pygeoapi annual update presentation.<br>
>>><br>
>>> The budget to approve is $2000 USD and will help cover travel expenses.<br>
>>><br>
>>> Starting with my +1<br>
>>><br>
>>> ..Tom<br>
>>><br>
>>><br>
>>> [1]<a href="https://2025.foss4g.org" rel="noreferrer" target="_blank">https://2025.foss4g.org</a> <<a href="https://2025.foss4g.org" rel="noreferrer" target="_blank">https://2025.foss4g.org</a>><br>
>>> [2]<a href="https://dive.pygeoapi.io" rel="noreferrer" target="_blank">https://dive.pygeoapi.io</a> <<a href="https://dive.pygeoapi.io" rel="noreferrer" target="_blank">https://dive.pygeoapi.io</a>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> pygeoapi mailing list<br>
>>> <a href="mailto:pygeoapi@lists.osgeo.org" target="_blank">pygeoapi@lists.osgeo.org</a><br>
>>> <a href="https://lists.osgeo.org/mailman/listinfo/pygeoapi" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/pygeoapi</a><br>
>><br>
>> _______________________________________________<br>
>> pygeoapi mailing list<br>
>> <a href="mailto:pygeoapi@lists.osgeo.org" target="_blank">pygeoapi@lists.osgeo.org</a><br>
>> <a href="https://lists.osgeo.org/mailman/listinfo/pygeoapi" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/pygeoapi</a><br>
><br>
> _______________________________________________<br>
> pygeoapi mailing list<br>
> <a href="mailto:pygeoapi@lists.osgeo.org" target="_blank">pygeoapi@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/pygeoapi" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/pygeoapi</a><br>
<br>
<br>
-- <br>
Angelos Tzotsos, PhD<br>
President, Board of Directors<br>
Open Source Geospatial Foundation<br>
<a href="https://www.osgeo.org/member/angelos-tzotsos/" rel="noreferrer" target="_blank">https://www.osgeo.org/member/angelos-tzotsos/</a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
pygeoapi mailing list<br>
<a href="mailto:pygeoapi@lists.osgeo.org" target="_blank">pygeoapi@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/pygeoapi" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/pygeoapi</a><br>
<br>
<br>
------------------------------<br>
<br>
End of pygeoapi Digest, Vol 64, Issue 1<br>
***************************************<br>
</blockquote></div></div>