The minimum setup required for a WMS map engine is the capabilities URL for the service.
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<wms:mapengine id="test">
<url>http://server/wms/test</url>
<tokens>
<token name="VIEWPARAMS" value="${user.filter.status}" prefix="STATUS:" infix=","/>
<token name="VIEWPARAMS" value="USER:${user.id}"/>
<token name="BACKFILL" value="falsetrue" legendOnly="true" layer="ward,busroutes"/> <!-- BACKFILL will be true for ward and busroutes -->
<token name="BACKFILL" value="truefalse" layerlegendOnly="ward,busroutes"/true"/> <!-- BACKFILL will be false for any other layers -->
</tokens>
</wms:mapengine> |
...
| Note |
|---|
As of version 1.3.7 of the WMS bundle, the password can be encrypted using the OSGi encrypt command. |
WMS 1.3.0
Don't "upgrade" to WMS 1.3.0 unless you really have to.
Version 2.15.16 of the com.cohga.server.map.wms bundle (released as part of Weave 2.5.21) improves support for WMS 1.3.0 by supporting map services that require their axis order to be swapped.
...