Hi Andrea:
You came up with exactly the same suggestion I was going to make (extending
ResourceInfo or ServiceInfo as appropriate since this is metadata).
On the GeoServer importer side Torbien and I have experiemnted with storing
the files associated with an "import" as part of the GeoServer metadata map
(allowing us to clean up the files when a service is removed). I like the
idea of making an API at the GeoTools level much better.
I would prefer a FileServiceInfo and FileResourceInfo (rather than a
mixing) - since it is an optional interface you still would not be looking
at any breakage preventing back porting.
I had a question about coverage readers and getSource() - for a moasic the
source probably points to the directory rather than listing all the files
... is that sufficient for your needs?
--
Jody Garnett
On 13 May 2015 at 10:15, Andrea Aime <[email protected]> wrote:
> Hi,
> in the importer module in GeoServer I have a need to determine which files
> compose a certain store or reader.
>
> This is needed because I need to perform some work on the files I'm given
> (transformations) and only if they succeed, decide to move the files to
> a final place (their stable location in the data dir).
>
> For data stores, maybe we could have a sub-interface of ResourceInfo?
> FileResourceInfo, that would have an extra method such as
>
> /**
> * Returns all files making up this resource
> */
> List<File> getFiles();
>
> For coverage readers there is already a getSource() method, which
> for file based readers returns a File object, or a String/URL that
> can be turned into a File.
> In AbstractGridCoverage2DReader there is also getInfo, which returns a
> ServiceInfo...
> maybe we could have a FileServiceInfo there, with the same extension
> as ResourceInfo, or a mixin interface FileInfo that can be applied to
> both.
>
> I guess I like best the mixin one, seems like something that's also
> easy to backport to the stable series (as a pure addition, with no breakage
> of existing interfaces)
>
> Opinions?
>
>
> Cheers
> Andrea
>
> --
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/NWWaa2 for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39 339 8844549
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
>
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
> darcene notizia via e-mail e di procedere alla distruzione del messaggio
> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
> principi dettati dal D.Lgs. 196/2003.
>
>
>
> The information in this message and/or attachments, is intended solely for
> the attention and use of the named addressee(s) and may be confidential or
> proprietary in nature or covered by the provisions of privacy act
> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
> Code).Any use not in accord with its purpose, any disclosure, reproduction,
> copying, distribution, or either dissemination, either whole or partial, is
> strictly forbidden except previous formal approval of the named
> addressee(s). If you are not the intended recipient, please contact
> immediately the sender by telephone, fax or e-mail and delete the
> information in this message that has been received in error. The sender
> does not give any warranty or accept liability as the content, accuracy or
> completeness of sent messages and accepts no responsibility for changes
> made after they were sent or for other risks which arise as a result of
> e-mail transmission, viruses, etc.
>
> -------------------------------------------------------
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> GeoTools-Devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
>
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
