[Pywps-dev] Fwd: XXIII ISPRS Congress 2016 - Notification of Authors - Your paper was accepted for the Congress

[Jachym Cepicky]

Hi all,

this might mean, that PyWPS-4 could be presented at ISPRS in Prague this
year. Anybody else is going to come?

J

---------- Forwarded message ---------
From: XXIII ISPRS Congress <isprs2016 at conftool.net>
Date: po 22. 2. 2016 v 15:23
Subject: XXIII ISPRS Congress 2016 - Notification of Authors - Your paper
was accepted for the Congress
To: <jachym.cepicky at opengeolabs.cz>
Cc: <jachym.cepicky at opengeolabs.cz>, <luis.desousa at eawag.ch>


Dear Jachym Cepicky,

Congratulations, we would like to announce you that your submission was
accepted for the XXIII ISPRS Congress.

This contribution has been accepted for ISPRS Archives.

You will be notified about the paper location in the program (oral or
interactive session) until 10 March 2016.

You can now upload your final paper to Conftool.
Use the ISPRS template http://www.isprs2016-prague.com/download/)and native
speaker proofreading.

To be included in the Final program and in order to present your paper at
the
Congress, you must upload the final paper until 9 April 2016 and pay the
Early
Bird Fee until 14 April 2016.

Please consider the reviewers’ recommendation while preparing your final
paper.

If you have any questions, please contact us at program at isprs2016-prague.com

SUBMISSION DETAILS
------------------
ID: 2106
Title: ew implementation of OGC Web Processing Service in Python programming
language. PyWPS-4 and issues we are facing with processing of large raster
data using OGC WPS.


REVIEW RESULT OF THE PROGRAM COMMITTEE:
This contribution has been accepted for ISPRS Archives.




OVERVIEW OF REVIEWS
-------------------




Review 1
========

Contribution of the submission
------------------------------
The submission identifies main challenges for WPS for large raster data
sets.
It indicates that solutions proposed for pyWPS will be presented and no
specifics are given.


Evaluation of the Contribution
------------------------------
Quality of Content                                           (15%): 6
Please evaluate the originality and level of innovativeness. (15%): 6
Relevance                                                    (15%): 10
Quality of Presentation                                      (15%): 6
Overall Recommendation                                       (40%): 8
Total points (out of 100)                                         : 74


Comments for the authors
------------------------
I anticipate that this will be an excellent contribution, but lower ratings
were given because the abstract did not provide any description of results
or
solutions, so these should be included in the final abstract or paper.




-=-=-=-=-=-=-=-=-=-=-




Review 2
========

Contribution of the submission
------------------------------
Discusses the developmental and implementation challenges of PyWPS-4 in
consonance the OGC WPS Standard specifications.


Evaluation of the Contribution
------------------------------
Quality of Content                                           (15%): 10
Please evaluate the originality and level of innovativeness. (15%): 10
Relevance                                                    (15%): 10
Quality of Presentation                                      (15%): 8
Overall Recommendation                                       (40%): 10
Total points (out of 100)                                         : 97


Comments for the authors
------------------------
The work presents the technical challenges of implementation of PyWPS-4 and
describes the various steps in the processing chain.
It will be well appreciated if the paper can present suitable illustrations
that pose some of these challenges and how PyWPS can handle these.





-=-=-=-=-=-=-=-=-=-=-




--
XXIII ISPRS Congress 2016
http://conftool.pro/isprs2016/
http://isprs2016-prague.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pywps-dev/attachments/20160301/b79c7c67/attachment.html>