Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
outlinetrue

...

  • local tile caching
    • automatic cache seeding based on user interaction with the mapĀ 
    • administrative seeding
  • tile service aggregation (1 DDF endpoint aggregates multiple external WMS services)
  • runs in the DDF container without extensive modificaitonmodification
  • includes administration services DDF can utilize
  • open source licensing

...

ElementExample ValueDescription
namelayer1The 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
wmsUrlhttp://example.org/wmsA 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.
wmsLayerslayer1,layer2The 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.
wmsVersion1.1.1The VERSION parameter sent to the WMS backend. The default is 1.1.1
tiledfalseThe TILED parameter sent to the WMS backend. The default is FALSE, you should generally not change this.

...