[MapProxy-dev] Contributing to MapProxy

[Alistair Everett]

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 <alistaire at met.no>

*Meteorologisk Institutt*,
Henrik Mohns plass 1,
0313 Oslo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapproxy-dev/attachments/20231113/fa22b025/attachment.htm>