Sorry that was my assumption:
- sometimes an import applies to more than one file (say in a directory)
- The result of processing may result in multiple files out of a single
raster (say if tiling was used match the block size of the distributed file
system).
I was more interested in the async workflow in case processing takes some
time (regardless of where it is importing from).
--
Jody Garnett
On 13 May 2015 at 11:13, Andrea Aime <[email protected]> wrote:
> On Wed, May 13, 2015 at 8:06 PM, Jody Garnett <[email protected]>
> wrote:
>
>> 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.
>>
>
> Confused by your sentence here, where is multiple images coming into the
> picture here (at least, it was not part of my original mail, maybe you're
> extending the scope in a way I don't understand).
>
>
>>
>> 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'm aware of it, but don't think it has anything to do with the use case
> I'm trying to discuss?
>
>
>>
>> I would hope the processing of the file would provide similar feedback?
>>
>
> As stated in my first mail (see the other thread), we cannot go for an
> HTTP upload, the server has to grab the files on its own,
> the files are too big and the speed difference between a HTTP transfer and
> a simple shared filesystem copy is (rather) significant.
>
> Also, if by VFS I can also get support for FTP (as said, out of scope, but
> trying to leave the door open for it),
> we could have a light js client point to the importer heavy files available
> on a FTP, instead of making it grab them from FTP (which I don't know if
> feasible to start with) and then HTTP upload
> them to GeoServer.
>
> 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
