Hello Devon,
Directory walking is part of the harvesting process, which is at the
moment implemented inside the ImageMosaicReader (see the inner class
HarvestedResource).
In the API, there is a separate MosaicHarvester interface, as well as a
very light ImageMosaicReader with all the logic inside the ImageMosaic
class.
With this API, we can either do one of these two thing to customise
harvesting:
1. Write our own reader and use all the mosaic functionality through the
ImageMosaic class.
2. Write our own implementation of MosaicHarvester for a customised
harvesting process and plug it into the ImageMosaicReader.
Does that make any sense?
Kind Regards
Niels
On 06-04-16 01:48, Devon Tucker wrote:
For my own part, Niels maybe you could throw in some small examples of
how these API changes would be used in practice to accomplish some of
the items in the description? For example, how could I customize the
directory walking with the new API?
Thanks,
Devon
On Tue, Apr 5, 2016 at 4:44 PM, Devon Tucker <devonrtuc...@gmail.com
<mailto:devonrtuc...@gmail.com>> wrote:
Hi all,
Just noticed that there wasn't a dedicated email thread for this
proposal and figured I'd kick one off since I've also been
involved in it.
https://github.com/geotools/geotools/wiki/Refactor-ImageMosaic-for-extensibility
I think the description gives a pretty good rationale for what we
want to accomplish with this proposal and I'd like to solicit any
discussion, advice, feedback, etc. from everyone.
Cheers,
Devon
------------------------------------------------------------------------------
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
------------------------------------------------------------------------------
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
