The update is intended to expose Weave map engines as a WMS service, but the bundle can also be used to create URL's that can be called from external application to create custom map images, this is because the bundle supports additional parameters beyond those required by WMS which allows for more customised map output.
This functionality is included in Weave 2.5, and for Weave 2.4 requires at least release 2.4.25.12 and an additional two bundles, com.cohga.server.wms and com.cohga.server.acetate.highlight, which can be downloaded below.
| Info |
|---|
com.cohga.server.wms_1.0.0.jar - Provide a WMS interface into Weave to generate maps |
The bundle must be installed and started (by editing the platform\configuration\config.ini file and restarting Weave) and a new configuration created to describe the WMS services that Weave will expose.
To add the new bundles to the config.ini file the following 2 lines should be added to the list of bundles to be started as startup
...
.
...
A new configuration describes a map context that is similar to that which is setup for a map view in a client configuration, and is generated in a similar way to the maps that are included in a BIRT report.
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<?xml version="1.0" encoding="UTF-8"?> <config xmlns="urn:com.cohga.server.config#1.0" xmlns:wmsserver="urn:com.cohga.server.wms#1.0"> <wmsserver:context id="test"> <mapengine id="mapengine.raster"> <layer>satellite</layer> </mapengine> <mapengine id="mapengine.vector"> <layer>property</layer> <layer>road</layer> <layer>suburb</layer> <layer>mccbound</layer> </mapengine> <mapengine id="mapengine.parks" opacity="0.75"> <layer>Reserve Images</layer> </mapengine> </wmsserver:context> </config> |
The above example will expose a new WMS service at /weave/wms/test that will contain the layers listed (and only those layers).
And, when the WMS client tries to draw the map Weave will use the three map engines to generate the individual images and combine them into a single map image to return to the client.
This service should be supported in any WMS compliant client.
Complete option list
Name | Description | WMS Compliant |
|---|---|---|
srs | Coordinate reference system of the coordinates specified in the URL | X |
width | Width of generated image in pixels | X |
height | Height of generated image in pixels | X |
format | Output format of the generated image | X |
bgcolor | Background colour | X |
transparent | true if transparent images should be created, false if opaque images should be generated | X |
bbox | Comma separated minx, miny, maxx and maxy of the generated image | X |
layers | List of layers to draw, all layers will be drawn if not set at all, |
and no layers drawn if layers is set to no value | X | |
exceptions | Method used to return errors to the caller | X |
size | Comma separated width and height of generated image in pixels |
dpi | DPI of generated image, to ensure scale |
dependencies are calculated correctly |
minx | Left X coordinate |
miny | Bottom Y coordinate |
maxx | Right X Coordinate |
maxy | Top Y coordinate |
x |
Centre X coordinate |
y |
Centre Y coordinate |
centre |
center
Comma separated X and Y coordinate |
. Both | |
scale | Scale to generate map at |
entity | Entity to use to determine map extent and draw highlight |
ids | Identifiers of entities to zoom to and highlight |
filter | Filters to be applied to 'ids' before calculating the extent. For use if external system uses different id's for the underlying GIS data |
buffer | Amount to scale entity extent by to calculate extent, e.g. 1.2 to place a 20% buffer around the entity bounds |
minscale | Minimum scale to zoom to when zooming to an entity |
highlight | false if the entity highlight should not be drawn, true if it should be drawn |
hlcolor | Vector highlight colour |
| mcolor | Marker highlight colour. Should be blue, brown, dark, green, orange, purple, red, silver or yellow. The default is green. The mcolor 'dark' is a dark grey. |
| Note |
|---|
When specifying the map extent bounding box setting minx, miny, maxx and maxy is the same as specifying just bbox, and bbox will take precedence if both are persent. |
The above settings will generally be supplied by the WMS client, and defaults can be set in the context.
Generally these will all be set by the WMS client when sending WMS requests to the Weave server and do not need to be specified in the configuration, however, you may want to set these values in the configuration if you're intending on constructing and using the URL's from another application and you want to simplify the URL that the other application needs to use.
For example, if you have an application that you want to always generate an 800x800 PNG image with a light blue background then you could use the URL:
/weave/wms/test?width=800&height=800&bgcolor=0x7f7fff&format=png&bbox=...140,-36,141,-35
or you could set width, height, format and bgcolor in the context and use the following URL instead
/weave/wms/test?bbox=...140,-36,141,-35
This allows you to provide a simplified URL to the application provider while specifying the fixed settings yourself, it all depends upon the requirements of the other application and how much of it can be pre-set.
...
.
Basic Context Example Requests
...