Hi all,
I'm looking into adding this (http://jira.codehaus.org/browse/GEOT-4597)
feature to the geotools/geoserver.
The intention is to add to geotools the capability to create an
ImageMosaicReader using hints without the need to add or modify properties
files somewhere.
The idea is:
Starting from an existing schema (or Datastore), we can navigate into its
structure (validating granules) to create an imagemosaic CatalogGranule.
Essentially no accessory files are needed (*.properties) but still some
configuration (those located into the datastore.properties) should be
passed via Hints I believe.
The Hints.MOSAIC_LOCATION_ATTRIBUTE is still needed and will be used to
store generated accessory files such as the Imagemosaic.properties file and
the sample_image and is also considered the default parent dir of relative
paths for granules.
The entry point will be the ImageMosaicReader constructor:
-------------------------------------------------------
//
// Check source
//
if (source instanceof ImageMosaicDescriptor) {
initReaderFromDescriptor((ImageMosaicDescriptor) source,
uHints);
} else if (checkForDatastore(uHints)){
// if Hints contains all the needed params to configure a
Mosaic (datastore connection, etc)
initReaderFromDescriptor(createGranuleDescriptorFromHints(uHints), uHints);
} else {
...
// normal filesystem scan
initReaderFromURL(source, localHints);
}
--------------------
Essentially the condition to distinguish from the classic folder based scan
and the new DataStore based scan is in the content of Hints.
If we can locate all the needed information to start the navigation we
assume to use the DataStore scan mode (which essentially reads from
existing datastore) otherwise, normal filesystem scan is performed (which
writes creating a new datastore).
A better option can be adding a new Hint option to select between the modes
f.e.:
- fs
[the ImageMosaic create the datastore scanning the passed folder as
usually]
- datastore
[the imagemosaic scan the datastore schema for coverages (typeNames) and
recursively coverages (typeNames) for granules. Empty tables creates an
empty coverage see http://jira.codehaus.org/browse/GEOT-4597]
- auto
[ use 'source' and old method to create the mosaic reader. This should be
the default to preserve old workflow ]
Once the 'datastore' mode is selected the DataStore is created and the
typeNames will be queried for granules as the ImageMosaicWalker does for
the folders. Note that the ImageMosaic base dir
(Hints.MOSAIC_LOCATION_ATTRIBUTE) will contain a list of folder
representing typenames.
Other options can be added to recalculate the bbox for each granule.
Feedback are really appreciated
Cheers,
Carlo
--
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.
==
Dott. Carlo Cancellieri
@cancellieric
Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
mobile: +39 3371094494
fax: +39 0584 1660272
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
