[Tile-serving] Real time tile merging strategy

Paul Norman penorman at mac.com
Mon Apr 1 00:07:00 UTC 2013

> From: Kai Krueger [mailto:kakrueger at gmail.com]
> Sent: Sunday, March 31, 2013 1:45 PM
> Subject: Re: [Tile-serving] Real time tile merging strategy
> Coming to think of it, you can already get it working with the current
> system by using the http_proxy backend. You can use the http_proxy
> backend to retrieve the the tile data from your own server, thus going
> through the normal expiry and on the fly rendering stages. I.e.
> "composite:{ro_http_proxy://localhost/layer1}{ro_http_proxy://localhost/
> layer2}".
> Although it probably should work, it might be considered a little crazy
> though... ;-)

This is exactly what I do with mapproxy 1.4 and my imagery layer formed by
merging multiple layers. The composite layer could change but the underlying
source layers were fixed, and slow to generate a tile from the WMS that
backed them. It worked well, but you'd want all TMS sources involved to
interpret meta-tiles in the same way.

Mapproxy was patched to allow this kind of compositing to be done without
going through HTTP requests and it is definitely far easier to understand
configurations when they are not referring to other layers in the same
config in this manner. It also makes the configs more portable.

More information about the Tile-serving mailing list