| Table of Contents | ||
|---|---|---|
|
...
| Element | Example Value | Description |
|---|---|---|
| name | layer1 | The name of the layer that GWC should respond to. It is equivalent to the value of LAYERS= in WMS requests, and can contain commas. See wmsLayers |
| mimeFormats | <string>image/jpeg</string> | List of formats to be supported. These must be known to GeoWebCache. Legal values are image/png, image/png8, image/png24, image/gif, image/jpeg, image/tiff, gml, application/vnd.google-earth.kml+xml, application/vnd.google-earth.kmz+xml |
| wmsUrl | http://example.org/wms | A list of URLs to backend servers than can render tiles for this layer. They are used in a round robin fashion for load balancing and automatic failover. The only time you can ommit this element is if you expect the layer to be merged with that from another source. |
| wmsLayers | layer1,layer2 | The LAYERS parameter sent to the WMS backend. It may contain commas, to request composites of several layers from the backend, and be different from the name element. |
| wmsVersion | 1.1.1 | The VERSION parameter sent to the WMS backend. The default is 1.1.1 |
| tiled | false | The TILED parameter sent to the WMS backend. The default is FALSE, you should generally not change this. |
...
- documentation
- fix logging to use PAX Web logging (currently logging goes to std out)
- create admin UI plugin for
- service configurationconfiguration
- ability to add/modify/delete tile services
- seeding
- diskquota control (see http://geowebcache.org/docs/current/configuration/diskquotas.html)
- service configurationconfiguration
- verify HTTPS to external tile services - how do certs need to be configured?
- consider removal the use of the HTTP proxy in DDF for tile services (GWC is its own proxy)
...