[MapProxy] Heads up - Implementing TIME support in MapProxy

Ariel Nunez ingenieroariel at gmail.com
Wed Mar 4 10:34:31 PST 2020

Dear Trond,

Thanks a lot for the PR you created and the offer to help.

I have started working locally on some modifications to it but I am
still in time to adjust the approach.

Since this will need to go into production relatively soon I would be
very interested in learning more about your preseeding strategy and
how you and the rest of the community consider this should ultimately

I'll follow up with you off list and then post an update here once we
have a design document.




That's great to hear. I'm the author of the pull request you mention,
and I'd be happy to assist in getting it to work. Since I made this
pull request, I have added dimension support to mbtiles caches, too.

I work at the Norwegian Meteorological Institute, and we have a
project coming up (in cooperation with two other Meteorological
Institutes) where we'll probably use Mapproxy, so we are also eager to
expand the support for dimensions.

We are currently using mbtiles for our air quality forecast. Five
layers, 50 timesteps. The entire cache is preseeded (not by mapproxy)
every six hours.

Anyway - this works pretty well, but I've not made any effort to
support preseeding or cache expiry.

If I were to start over, I think I'd rather subclass the Tile class,
and add a dimension attribute to it. That would probably be a lot more
elegant than my current patch.

Trond Michelsen

On Thu, Feb 27, 2020 at 10:42:29AM -0500, Daniel Morissette wrote:
>* Hello MapProxy devs and community,
*> >* This email is a heads up that we have started to work on the
*>* implementation of WMS TIME dimension support in MapProxy, including
*>* caching and seeding of time-enabled WMS sources, and support for
*>* assembling WMS requests from a time-enabled tile cache.
*> >* This work is funded by the Meteorological Service of Canada and will
*>* be used to serve hundreds or time-enabled weather layers, A RFC
*>* (Request For Comments) document is underway and will be shared via
*>* this list soon, so that other devs and contributors can comment on
*>* the proposed approach to ensure that the implementation will meet
*>* the expectations of the project to be included in future releases.
*>* (We are also aware of
*>* and will actually try to build on it)
*> >* A parallel goal of our initiative will be to set the bases to make
*>* it easier for new devs to join the project as contributors and to
*>* assist Oliver to maintain the project in the long run, inspired by
*>* the way other OSGeo projects work. (We had some exchanges with
*>* Oliver on this offlist already)
*> >* Finally, I am only the project lead here, the guys doing the bulk of
*>* the coding work are:
*> >* - Ariel Nunez (https://github.com/ingenieroariel
*>* - Denis Rykov (https://github.com/drnextgis <https://github.com/drnextgis>)
*>* - Tom Kralidis (https://github.com/tomkralidis
<https://github.com/tomkralidis>) - Tom is also the
*>* end client who will be testing/validating the final results.
*> >* We should hear from them soon.
*> >* Cheers all
*> >* Daniel
*>* --
*>* Daniel Morissette
*>* Mapgears Inc
*> >* _______________________________________________
*>* MapProxy mailing list
*>* MapProxy at lists.osgeo.org
*>* https://lists.osgeo.org/mailman/listinfo/mapproxy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapproxy/attachments/20200304/9ec9aa33/attachment.html>

More information about the MapProxy mailing list