[MapProxy-dev] Contributing to MapProxy

Fri Nov 24 01:01:55 PST 2023

Hi,

So here are my first findings on the topic of OGC API and pygeoapi.

You can already publish cached WMS that come from MapProxy through 
pygeoapi via OGC API Map 
(https://docs.pygeoapi.io/en/stable/data-publishing/ogcapi-maps.html).

I think that is a bit inefficient, as OGC API Tiles could potentially 
access the tiles directly as they have been stored in the chosen 
MapProxy backend (mbtiles, files, ...).

So in order to avoid the image assembling and rescaling in mapproxy (and 
do it in the client instead, which may not perform better, maybe even 
worse), support for those tile backends need to be implemented in pygeoapi.

Currently the only provider for OGC API Tiles in pygeoapi seems to be 
the MVT-Provider, which obviously does not work with mapproxy. So a 
provider / reader like mbtiles, xyz structures or similar for non vector 
data needs to be implemented. Some things do exists in pygeoapi which 
should help to get on the train quickly.

I think that an implementation in pygeoapi would solve your needs most 
efficient.

Afterwards we could provide documentation and examples how to use 
MapProxy and pygeoapi together to be OGC-API comaptible.

My 2 cents,

Greetings,

Johannes

Am 22.11.23 um 16:18 schrieb Johannes Weskamm:
>
> Hi,
>
> This sounds very good in my opinion! Having OGC API Support in 
> MapProxy would be a really nice feature and enable MapProxy to catch 
> up with the future of OGC Standards.
>
> In general, Pull Request are always welcome and the features you 
> mentioned sound interesting, so i see no obvious reasons that would 
> block your contributions.
>
> Some bigger goals, like OGC API Support, would need some discussion 
> before starting with development. Before reinventing the wheel one 
> should examine what pygeoapi has to offer.
>
> The current documentation 
> (https://docs.pygeoapi.io/en/stable/data-publishing/ogcapi-tiles.html) 
> even mentions MapProxy as a possible data source, but the examples are 
> lacking, so i am not sure if support already exists or needs to be 
> done. But even if its still missing, i guess it would be the more 
> elegant way to use pygeoapi together with mapproxy or implement and 
> extend the relevant classes, as the main thing is already done in 
> pygeoapi and updated regularly.
>
>
> I may find some time in the upcoming weeks to shed some more light on 
> that.
>
> I am also interested what other people think about that.
>
>
> Greetings,
>
> Johannes
>
>
>
> Am 13.11.23 um 09:52 schrieb Alistair Everett via MapProxy-dev:
>>
>> Hi all,
>>
>> At the Norwegian Meteorological Institute we're considering using 
>> MapProxy to provide model and other map based data to some of our 
>> frontend services. I'm aware we've been somewhat involved with 
>> MapProxy before and used it for some of our services, unfortunately 
>> most of those involved aren't working here anymore so we're looking 
>> at building from scratch and modernising our services. First with a 
>> new WMS offering, but we would also like to be able to provide OGC 
>> API endpoints in the future.
>>
>> There are a couple of features which we would be interested in having 
>> in MapProxy, particularly related to dimensions - for example, other 
>> forms of caching (S3 and mbtiles), seeding, and potentially reading 
>> available dimensions from WMS sources. I know some of these features 
>> are available as standard but I believe they currently don't 
>> necessarily work with dimensions. As part of this project I'm hoping 
>> that we will have some developer time to put into this, so I'm 
>> interested in hearing what the community thinks of this, how it might 
>> fit in with any roadmap the MapProxy community might already have, 
>> and if you are open to us submitting our own MRs for these features?
>>
>> I'm also interested in what the community thinks of OGC-API 
>> endpoints, do you see this as something which MapProxy would like to 
>> offer, if the resources were available to develop it? Or do you see 
>> this as something which would rather be offered through other 
>> packages, for example pygeoapi with MapProxy providing a tile cache 
>> in the background?
>>
>> Interested to hear your thoughts,
>>
>> Kind regards,
>> Alistair
>>
>> --------------
>> *Dr Alistair Everett*
>> Senioringeniør / Senior Software Engineer
>> Avdeling for Geoutvikling
>>
>> *Phone:* +47 939 68 985
>> *Email:* alistair.everett at met.no <mailto:alistaire at met.no>
>>
>> *Meteorologisk Institutt*,
>> Henrik Mohns plass 1,
>> 0313 Oslo
>>
>>
>> _______________________________________________
>> MapProxy-dev mailing list
>> MapProxy-dev at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/mapproxy-dev

-- 
Dipl.-Geogr. Johannes Weskamm
   — Anwendungsentwickler —

   terrestris GmbH & Co. KG
   Kölnstraße 99
   53111 Bonn

   Tel: +49 (0)228 / 96 28 99 -51
   Fax: +49 (0)228 / 96 28 99 -57

   Email:weskamm at terrestris.de
   Web:https://www.terrestris.de

   Amtsgericht Bonn, HRA 6835
   Komplementärin: terrestris Verwaltungsgesellschaft mbH
   vertreten durch: Torsten Brassat, Marc Jansen

   Informationen über Ihre gespeicherten Daten finden Sie auf
   unserer Homepage unter folgendem Link:
   https://www.terrestris.de/datenschutzerklaerung/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapproxy-dev/attachments/20231124/66835f55/attachment.htm>