原始连接：
http://docs.codehaus.org/display/GEOSDEV/WCS+Branch
Introduction
The branch is located at:
http://svn.codehaus.org/geoserver/branches/1.4.x_merge_wcs, you can also find a release available from: GEOS:GeoServer 1.4-M2-WCS.
It is worthwhile noting that the WCS experiment is implemented using GeoTools trunk (2.3-SNAPSHOT version), JAI and ImageIO libraries. A lot of improvements on the Renderers and plugins have been done in the last monts in order enanche the capabilities and the performances of GeoTools/GeoServer with respect to raster support.
Configuration
The WCS and WMS raster support is fully configurable from the web admin tool. If you've learned how to use the web admin tool, then go to it and look for coverage stuff. Configure your layers as you do for the non-coverage stuff, but they will be available as WCS coverages as well as WMS layers.
First of all you have to configure your Server capabilities. In the Config > Server section you can find several fields that allow you to optimize the JAI memory configuration:
JAI mem capacity expressed in bytes represents the amount of available memory for JAI operations. We suggest to use the default amount, more advices will come later.
JAI mem threshold is the percentage at which the Tile cache starts flushing tiles.
JAI cache recycling if checked allows JAI to re-use alredy loaded tiles (vital capabilty for perfomances).
At this point the WCS can be configured and feed with your data.
In the Config > Data > CoveragePlugins you can find the list of installed plugins. A plugin represents the raster format that GeoServer is able to read/write. With the default distribution the supported file formats are:
GRIB edition 1
GeoTiff
WorldImages: PNG, JPG, TIFF, GIF with a world file attached
ArcGrid: ASCII files
GTOPO 30: DEM files
ImageMosaic: a mosaic of several images with world file or geotiff files. It is still quite experimental but it is showing good perfomances.
CoverageStore
Before creating a new Coverage you have to add a new CoverageStore. The CoverageStore represents the phisical location of the raster file and the default reading parameters for it. From a CoverageStore you can derive as Coverages you want. For every new Coverage the read parameters can be modified so you can obtain different Coverages from the same CoverageStore.
To create/modify a CoverageStore you have to go in the Config > Data > CoverageStore section.
Coverage
Once the CoverageStore is configured, a new Coverage can be created. This can be done from the Config > Data > Coverage section. Here you can configre all the stuff related to the Coverage included its reading parameters.
Attention: in order to correctly render a Coverage in the WMS you have to assign to it a Style with a RasterSymbolizer inside.
WMSPath
Notice: in the GeoServer WCS Experiment there are few improvements in the Feature section too. One is for instance the WMSPath parameter. With this parameter you can tell to the WMS how to format the GetCapabilities response. For example if you have a Feature/Coverage called Test and you write in the WMSPath field the string /today/tests/01/ then in the WMS GetCapabilites response you will have a layer tree like this:
|-today
|---tests
|---01
|---Test
