[MapProxy] Define multiple services of the same type

[Richard Law]

Hi, apologies if a similar question has been asked before; I can't find a
way to search the archives for this list.

I create a MapProxy configuration YAML programmatically, for a single WMS
service that is a proxy to a tile service. The output tends to be very
large (hundreds to thousands of layers), and we manage this for consumers
of the WMS by filtering layers based on what they are authorised to see.
However even with filtering, occasionally it is possible that a WMS
consumer is authorised to see such a volume of layers that the initial WMS
GetCapabilities document is very large, leading to a timeout, or at best a
very long response time and a huge download.

I was wondering if instead it would be possible to define multiple services
of the same type in the MapProxy service configuration. For example, we
could have three WMS services defined in the configuration that are
accessed at

domain/service/wms-a
domain/service/wms-b
domain/service/wms-c

I would expect that different clients would be interested in different
services, because they would each be distinct in terms of theme. Each WMS
service would include a reference to the layers that they provide. This
way, pointing to service/wms-a implies a much smaller download for the
GetCapabilities than the full list of layers that are provided.

I could run multiple instances of MapProxy located at different endpoints
(domain/a/service, domain/b/service, etc.), but this feels a little
superfluous when it is already possible to have MapProxy run multiple
services (as long as they are of different types).

So, is it possible/planned to run multiple services of the same type (in
this case WMS services)?

Thanks,
Richard


-- 

[image: MetOcean Solutions Ltd] <http://www.metocean.co.nz>

Richard Law
Geographic Information Systems (GIS) Developer
t: +64 7 825 0540 ext.123
m: +64 27 6355 328
www.metocean.co.nz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapproxy/attachments/20180124/3f4e3f47/attachment.html>