Sorry Andrea, I was away ... and do not have much to say about the importer
REST API for fear of making it more complicated. I will check with Torben
who has more recently looked at the importer internals and get back to you
for any specific feedback.
In general I like the workflow of uploading the single original file and
then processing it in place. It sounds much more sensible/efficient to do
it this way then to take on the overhead of uploading multiple processed
images.
The importer REST api already has a async workflow:
- Allowing vector data to be processed into a database (think it even lets
you poll status).
- Allowing the SRS to be defined after the initial file(s) are uploaded.
I would hope the processing of the file would provide similar feedback?
--
Jody Garnett
On 13 May 2015 at 10:46, Andrea Aime <[email protected]> wrote:
> Hi,
> some time ago I asked feedback on this question, related to importing
> (eventually
> big) rasters:
>
> 1) The client indicates that one or more "golden" images need to be
> importer
> into GeoServer for WMS/WCS usage. The original files are big, and must
> not be touched, so ideally the client would just tell GeoServer where
> the
> files are (disk shares) and GeoServer should copy them autonomously
>
> I proposed a few options, but got no feedback.
>
> In the spirit of collaboration, here is what I'm going to do. The REST api
> will recognize a new bit in "data" called "source", which can be either
> a plain string, or an array of strings, something like this:
>
> "data": {
> "type": "directory",
> "source": "/mnt/share/myImage.tif",
> }
>
> When this tag is found, the file (or files) pointed by source will be
> treated
> as data that needs to be copied over to GeoServer, and the importer
> will act just like as is it was an upload, it will grab those files, copy
> them locally into a random subdirectory of $DATA_DIR/uploads,
> and then move from there as if the file had gotten uploaded.
>
> I am planning to use commons VFS just like it's already done with
> compressed files to perform the copy, in the hopes to support
> more sources (like FTP), although I see we are depending on
> an old version (1.0 instead of the current 2.0), and I'm not sure
> what 1.0 supports, or how hard an upgrade to 2.0 would be.
>
> The goal/scope for this set of changes is just to copy over from a share
> to local file system, but I don't want to corner the module on it.
>
> 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
> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-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
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
