[pygeoapi] Externalizing tile matrix sets and supporting custom TMS registration

Fri Aug 1 13:44:40 PDT 2025

Hi Linda,

Thanks for the suggestion.

Please note that some providers may support some tile matrix sets and
others may not. Currently, these are the Tiles providers:

https://github.com/search?q=repo%3Ageopython%2Fpygeoapi%20BaseTileProvider&type=code

https://github.com/search?q=repo%3Ageopython%2Fpygeoapi%20BaseMVTProvider&type=code

With the current system, it's pretty easy to acknowledge when a tile matrix
set is supported or not in a specific provider.

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?

Thank you and Kind regards,
Antonio Cerciello

On Fri, Aug 1, 2025 at 9:00 PM <pygeoapi-request at lists.osgeo.org> wrote:

> Send pygeoapi mailing list submissions to
>         pygeoapi at lists.osgeo.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.osgeo.org/mailman/listinfo/pygeoapi
> or, via email, send a message with subject or body 'help' to
>         pygeoapi-request at lists.osgeo.org
>
> You can reach the person managing the list at
>         pygeoapi-owner at lists.osgeo.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of pygeoapi digest..."
>
>
> Today's Topics:
>
>    1. Externalizing tile matrix sets and supporting custom TMS
>       registration (Linda Karlovsk?)
>    2. next meeting 05 September 12h UTC (Tom Kralidis)
>    3. Re: PSC vote: approve travel cost for FOSS4G 2025
>       (Angelos Tzotsos)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 01 Aug 2025 11:49:31 +0200 (CEST)
> From: Linda Karlovsk? <linda.karlovska at seznam.cz>
> To: <pygeoapi at lists.osgeo.org>
> Subject: [pygeoapi] Externalizing tile matrix sets and supporting
>         custom TMS registration
> Message-ID: <2Wt.9}qCv.2PCuinq4UP2.1eZ8sh at seznam.cz>
> Content-Type: text/plain; charset="utf-8"
>
>
> 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
> <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
> <https://github.com/geopython/pygeoapi/blob/master/pygeoapi/models/provider/base.py>
> (
> 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.
>
> 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., WorldCRS84
>    Quad.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?
> And are there any things I should keep in mind when implementing this
> change?
>
>
>
>
> Thanks a lot for your time and feedback!
>
>
>
>
> Best regards,
> Linda Karlovska
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.osgeo.org/pipermail/pygeoapi/attachments/20250801/84c43a50/attachment-0001.htm
> >
>
> ------------------------------
>
> Message: 2
> Date: Fri, 1 Aug 2025 10:36:28 -0400
> From: Tom Kralidis <tomkralidis at gmail.com>
> To: Tom Kralidis via pygeoapi <pygeoapi at lists.osgeo.org>
> Subject: [pygeoapi] next meeting 05 September 12h UTC
> Message-ID:
>         <
> CAFWXLWU8crn2aaoHRWDAjkqjxyH73rRptJPKOvr-Pbicip+i0w at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi all: just a note that we will be resuming monthly meetings on 05
> September 2025 at 12h UTC.  Please see [1] for more information and agenda.
>
> Thanks
>
> ..Tom
>
> [1] https://github.com/geopython/pygeoapi/wiki/Meeting-2025-09-05
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.osgeo.org/pipermail/pygeoapi/attachments/20250801/9df68efa/attachment-0001.htm
> >
>
> ------------------------------
>
> Message: 3
> Date: Fri, 1 Aug 2025 17:51:24 +0300
> From: Angelos Tzotsos <gcpp.kalxas at gmail.com>
> To: pygeoapi at lists.osgeo.org
> Subject: Re: [pygeoapi] PSC vote: approve travel cost for FOSS4G 2025
> Message-ID: <b86f510c-bb9c-4d56-8c7a-765b82c6e5cf at gmail.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> +1
> Angelos
>
> On 7/29/25 16:00, Francesco Bartoli via pygeoapi wrote:
> > +1
> >
> > Ciao
> > Francesco
> > On 29 Jul 2025 at 13:37 +0200, Just van den Broecke via pygeoapi <
> pygeoapi at lists.osgeo.org>, wrote:
> >> +1
> >>
> >> Just
> >>
> >> On 28/07/2025 21:54, Tom Kralidis via pygeoapi wrote:
> >>> Dear pygeoapi PSC:
> >>>
> >>> This is a motion to approve up to 2 pygeoapi developers to travel to
> the
> >>> FOSS4G event on 17-23 November 2025 [1], to provide the Diving into
> >>> pygeoapi workshop [2] as well as the pygeoapi annual update
> presentation.
> >>>
> >>> The budget to approve is $2000 USD and will help cover travel expenses.
> >>>
> >>> Starting with my +1
> >>>
> >>> ..Tom
> >>>
> >>>
> >>> [1]https://2025.foss4g.org <https://2025.foss4g.org>
> >>> [2]https://dive.pygeoapi.io <https://dive.pygeoapi.io>
> >>>
> >>>
> >>> _______________________________________________
> >>> pygeoapi mailing list
> >>> pygeoapi at lists.osgeo.org
> >>> https://lists.osgeo.org/mailman/listinfo/pygeoapi
> >>
> >> _______________________________________________
> >> pygeoapi mailing list
> >> pygeoapi at lists.osgeo.org
> >> https://lists.osgeo.org/mailman/listinfo/pygeoapi
> >
> > _______________________________________________
> > pygeoapi mailing list
> > pygeoapi at lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/pygeoapi
>
>
> --
> Angelos Tzotsos, PhD
> President, Board of Directors
> Open Source Geospatial Foundation
> https://www.osgeo.org/member/angelos-tzotsos/
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> pygeoapi mailing list
> pygeoapi at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/pygeoapi
>
>
> ------------------------------
>
> End of pygeoapi Digest, Vol 64, Issue 1
> ***************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pygeoapi/attachments/20250801/6a556239/attachment.htm>