The minimum setup required for a WMS map engine is the capabilities URL for the service.
...
| 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.
...
Note that setting swapAxis to false will force x, y ordering of the axis regardless of what the projection information says.
Metromap
If you're using Metromap as a WMS map engine it uses two different methods to provide the API key in the URL you have to configure for the map engine, one format sets the key as a parameter and the other method embeds the key within the URL path, see this page for more info.
The format with the key set as a query parameter will not work with Weave, you have to use the format where the API key is provided as part of the URL path.
| Code Block | ||
|---|---|---|
| ||
https://api.metromap.com.au/api-link/{YOUR_API_KEY}/wms |