Message-ID: <1274397126.299606.1369001298638.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_299605_182280364.1369001298638" ------=_Part_299605_182280364.1369001298638 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Allows setting up a coverage store on top of a main folder containing se= veral datasets (which can also be organized in subfolders) such as simple i= mages, not georeferenced maps, ...
The GridCoverageReader will allow to provide access to a main folder con= taining several simple images (even organized in subfolders) without CRS. The input of the reader will be that main directory. Since that folder can = contain thousands of images, there isn't any preliminar "deep check&qu= ot;/"scan" when initializing the reader. Moreover, files could be= added/removed on that folder, even once the reader has been created.
Note that the Coverage reader will not provide any information (such as = metadata, properties) about the available images and/or image's properties= . The user should know in advance which image he needs to access as well as= the image's extent.
Reading an image will be achieved by specifying a "path" by me=
ans of a CQL Filter (such as, as an instance PATH=3D'subfolder1/draft3/imag=
The CQL_FILTER will be useful when propagating requests from GeoServer to t= he reader, as already happens for the ImageMosaic plugin.
Checks on the path should be performed in order to prevent requests to m= ove outside to the input folder.
The Coverage reader could cache image properties (width, height, URL, sp= i, ...) in a soft value hash map in order to know in advance (for repeated = requests) the BBOX of the image, the SPI to be used in order to instantiate= an ImageReader... and so on. When asked to take access to a specific image= , the reader can check if the image is still available or if it has been ch= anged. This could be achieved by taking note of the lastModified time as we= ll as the last check time.
The module lives in unsupported at this location.
It behaves like other plugins (geotiff, arcgrid, imagemosaic, ...). Therefo= re, in order to add it on GeoServer, you simply needs to add the gt-imageco= llectionXXX.jar into GeoServer/WEB-INF/lib.
If you need to include it in the GeoServer build (as an instance for debugg= ing purposes with eclipse), you should add the following entry to the paren= t's pom, within the
Then, edit the following poms:
by adding this dependecy:
In case you need to specify a minimal preliminar configuration before se=
tting up a new raster store, you can add a
ile into the folder you will use as root for the store.
In that properties file you can configure the following parameters:
By default, the plugin will use the folder name as coverage name.
coverageNameproperty allows you to specify a different= one to be used to configure the coverage.
defaultPathcan be used to specify a file to be used as= reference to setup basic coverage properties (envelope, size, ...)
expandis a boolean which allows to specify whether to = apply RGB expansion to paletted images. (DEFAULT is TRUE)
timeBetweenChecksis the time interval between two cons= ecutive checks on a file. Being the imageCollection a dynamic collection (f= iles can be modified, deleted, ...) there is a periodic check on file exist= ence and file "last modified time" flag. This property represents= the time between two checks, in seconds. (DEFAULT is 10 minutes =3D 600 se= conds)
maxHeightallow to specify re= ference values which will be used to represent the maximum extent of the co= nfigured coverage. (DEFAULT is 65536 for both values)
In order to configure a new store on top of a folder containing an image= collection, you simply needs to navigate to the GeoServer's gui "add = store" page and then select the ImageCollection raster data source. Th= en, select the folder you want to use as root of your image Collection and = continue configuring the store as a standard raster store.
Once you have configured your coverage, you can start sending WMS GetMap= requests to access an image available on the collection.
Suppose you have configured an imageCollection store on top of a
yCollection folder containing the following datasets.
In order to send a getMap request to access the E.TIF image contained on=
myCollection/folder2/subfolderB you simply need to append a CQL_FILTER to =
the getMap request, like this:
Make sure to always specify a
=3DPATH=3D'pathToRequestedImage' since geoserver actually h=
as no way to send a default path to the request (This will require some har=
Finally, if your image is 1000x1000 pixels and you want to get the area =
of the image contained within a rectangle (x0,y0 x1,y1) (As an instance, x0=
=3D400,y0=3D400 x1=3D700,y1=3D700), make sur to specify a BBOX parameter wh=
ere Yi are specified with negative coordinates. As instance, for the same e=
xample, you need to specify
BBOX=3D400,-700,700,-400. Make sur=
e to respect minX,minY,maxX,maxY syntax.
Moreover, the width and height getMap parameters allow to force the requ= ested image area to fit into the specified size.
IP Check: Need to be achieved.
Releasable: currently in beginning stages
Quality Assurance: currently in beginning stages
Stability: No planned API changes
Supported: currently in beginning stages
IP review is underway - known issue:http://svn.osgeo.org/geotools/trunk/m= odules/unsupported/imagecollection/src/site/apt/review.apt
Remember that the module maintainer is a volunteer, and if you can help = test this module please jump on the developers list and help out. Patches m= ay be attached to the above issues for review by the module maintainer.------=_Part_299605_182280364.1369001298638--