[MapProxy] MapProxy passing parameters to wms source
jukka.rahkonen at mmmtike.fi
Wed Nov 27 04:44:40 PST 2013
Feels like something that could be handled by filtering the requests before MapProxy and redirecting them if needed with something like Apache mod_rewrite http://httpd.apache.org/docs/current/mod/mod_rewrite.html
Filtering might get easier if you would set up Mapserver with default values for the variables http://mapserver.org/cgi/runsub.html#runsub
Then in normal case your WMS client would not need to send vendor parameters at all and if any of them exists in the GetMap request the request would be redirected to the WMS. MapProxy could be totally unaware about what is happening.
Lars Lingner wrote:
> Hello MapProxy Community,
> I'm trying to find a solution for the following scenario:
> MapServer is publishing a WMS with filter configuration. The client is forced to
> send a set of vendor parameters. The WMS ist configured with a default
> parameter set, so it is for sure that there isn't a request made without these
> I'm trying to setup MapProxy to cache the default parameter request, as these
> set is used most of the time.
> All request with different parameter set could be rendered on demand.
> For this to work, MapProxy needs to know the default vendor parameter.
> If there are variant parameter passed, MapProxy should pass these to the wms
> I doubt that it is possible, it would be a mix of a cached and a direct layer. But
> maybe I just don't see the simplest solution.
> Btw: it is not practical to publish a unique wms for each parameter combination.
> Have a nice day
> MapProxy mailing list
> MapProxy at lists.osgeo.org
More information about the MapProxy