<html><body><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt; color: #000000"><div>Jachym, submitting ourselves as a mentor is needed if we want that people work on the provided GSoC ideas. See following link: </div><div><a href="http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2014_Administrative#How_to_register_as_a_mentor">http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2014_Administrative#How_to_register_as_a_mentor</a></div><div><br></div><div>Furthermore, Anna Ghisla posted a mail in the OSGeo Summer of Code mailinglist: </div><div><a href="http://lists.osgeo.org/pipermail/soc/2014-March/002508.html">http://lists.osgeo.org/pipermail/soc/2014-March/002508.html</a></div><div><br></div><div>Jonas</div><div><br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;">Ok, go ahead.<br><div><br></div>Is there anything you need from us right now? Shall we submit ourselves as<br>mentors to the task as well? Just say, what you need, we will try to help<br><div><br></div>Jachym<br><div><br></div>P.S. Sorry, this is first GSoC for PyWPS people, the things are still new to us.<br><div><br></div>On Wed, Mar 12, 2014 at 10:06:07PM +0530, Naveen Panwar wrote:<br>> Respected Sir,<br>> <br>> Here is the summary of our last conversations<br>> <br>> 1. We have to enable users to configure their own database connectivity,<br>> by providing appropriate information in the config file.<br>> 2. They will be using PostgreSQL, and SQLite according to their need.<br>> 3. In later phase of project we can provide support for NoSql(pycass).<br>> 4. Schema for the data we have to generate on the fly based on user<br>> demand.<br>> Also Google has started application for the Students and Mentors for<br>> GSOC-2014. I think, we should put a draft of our proposal on melange, So<br>> that other people/mentors in OSGeo can get to know about idea. <br>> <br>> On Tue, Mar 11, 2014 at 1:01 PM, Jachym Cepicky<br>> <[1]jachym.cepicky@gmail.com> wrote:<br>> <br>> OK<br>> <br>> On Tue, Mar 11, 2014 at 08:18:19AM +0100, Jorge de Jesus wrote:<br>> > Hi Jachym lets discuss the topic on the hangout then I can take some<br>> > notes and prepare things for Naveen<br>> ><br>> > I'm not so certain how the schema in DB will be done, I was thinking a<br>> > sort of pre-defined schema/relations like the one in the istSOS<br>> > ([2]http://istgeo.ist.supsi.ch/software/istsos/)<br>> ><br>> > Cheers<br>> ><br>> ><br>> ><br>> > On 03/11/2014 12:31 AM, Jachym Cepicky wrote:<br>> > > Hi,<br>> > ><br>> > ><br>> > > On Tue, Mar 11, 2014 at 01:02:08AM +0530, Naveen Panwar wrote:<br>> > >> Respected Sir,<br>> > >><br>> > >> As you suggested in previous mail I have gone through Pywps<br>> [1]Cookbook<br>> > >> Documentation[1]. As there are three types of inputs and<br>> outputs are<br>> > >> defined in the OGC standard: LiteralData, ComplexData,<br>> BoundingBox data.<br>> > >> But as you mentioned we have to take care of ComplexData.<br>> > ><br>> > > Not true: also literal and bbox data can be stored in database (but<br>> they are<br>> > > much simplier task to be done thought).<br>> > ><br>> > >><br>> > >> Currently ComplexData data store in two manner, One with xml as<br>> GML<br>> > >> format, Second with binary raster data encoded in base64.<br>> > >> these data stored as a file in system. Now we need database for<br>> the better<br>> > >> access and availability.<br>> > >><br>> > >> I following questions in my mind.<br>> > >><br>> > >> 1. Do we have write database module so that user can configure<br>> there own<br>> > >> database server by providing db URL and user credential, like<br>> standard db<br>> > >> connectivity ?<br>> > ><br>> > > This case<br>> > ><br>> > >><br>> > >> 2. Or we have to design our own database and provide db<br>> connection object<br>> > >> to user, so that they can write to the DB ?<br>> > ><br>> > > User should be able to setup everything using configuration file.<br>> > ><br>> > >><br>> > >> 3. How are we supposed to store the data in DB as both vector<br>> and raster<br>> > >> data present in different format ?<br>> > ><br>> > > PostGIS should do this. SQLite has support for some raster formats<br>> as well<br>> > ><br>> > >> 4. What kind of database support do we need ? Relational<br>> DB(PostgreSQL,<br>> > >> MySQL) or NOSql DB (as we have Cassandra by pycassa ) ?<br>> > ><br>> > > PostgreSQL/PostGIS, SQLite for the first steps. NOSql you nemntioned<br>> at the<br>> > > second.<br>> > ><br>> > >><br>> > >> 5. What should be the schema of the database ? is it predefine<br>> or define<br>> > >> by the user ?<br>> > ><br>> > > User should define, which schema schould be used.<br>> > ><br>> > >><br>> > >> and last but not the least when will be next hangout 13 march or<br>> 26 march<br>> > >> ? sorry bit confuse.<br>> > ><br>> > > sorry for the mess<br>> > ><br>> > ><br>> [3]http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140313T20&ah=1<br>> > ><br>> > > we are still aranging, how to define timeslots<br>> > ><br>> > > J<br>> > ><br>> > >> [1] -<br>> > >> <br>> [2][4]http://netmar.nersc.no/sites/netmar.nersc.no/files/D7.7_WPS_Cookbook_r1_20111229.pdf<br>> > >><br>> > >> On Mon, Mar 10, 2014 at 2:33 AM, Jachym Cepicky<br>> > >> <[3][5]jachym.cepicky@gmail.com> wrote:<br>> > >><br>> > >> Hi,<br>> > >><br>> > >> On Sun, Mar 09, 2014 at 05:46:09PM +0000, Mendes de Jesus,<br>> Jorge wrote:<br>> > >> > Hi to all<br>> > >> ><br>> > >> > @Naveen, first give a look at the WPS standard 1.0.0[1] and<br>> we have a<br>> > >> wiki [2]and doc online [3] (all document refer to the old 3.2<br>> version<br>> > >> but still a good source of information and technical know-how<br>> > >> > @Jachym, correct me when wrong<br>> > >> ><br>> > >> > WPS defines one output as ComplexData, meaning a raster<br>> images,<br>> > >> vetorial data etc etc can be contained between the element<br>> tags<br>> > >> <ComplexData /> The output data can be stored in the server<br>> when the<br>> > >> user requests an async result, the data stored is then fetch<br>> by an URL<br>> > >> location indicates by a status response.<br>> > >> ><br>> > >> > So,<br>> > >> > 1) The data stored in the server is currently saved on the<br>> filesystem<br>> > >> and we need it in a DB<br>> > >><br>> > >> better say: we would like to offer option, that all generated<br>> output<br>> > >> data could<br>> > >> be stored in some database, instead of file system<br>> > >> > 2) URLs will have to point to some<br>> function/service/DBrequest that<br>> > >> will fetch the results to the user<br>> > >><br>> > >> so service will have to be written/configured (using<br>> > >> mapserver/geoserver/custom<br>> > >> something), which will do the serving<br>> > >> > 3) DB structure should contain metadata on the request,<br>> datatype etc<br>> > >> etc etc<br>> > >><br>> > >> > 4) We are currently working on new code and things are not<br>> 100%<br>> > >> stable, nor I have a clear knowledge of the code therefore I<br>> can't give<br>> > >> you a direct answer to were in the code this has to be<br>> hookedup (Maybe<br>> > >> during the next hangout 13-March I/we will check it<br>> out).Please give a<br>> > >> look at the pywps4.0 documentation [4]<br>> > >><br>> > >> currently, first version of file storage is implemented - just<br>> storing,<br>> > >> no data<br>> > >> exporting<br>> > >> <br>> [4][6]https://github.com/jachym/pywps-4/blob/master/pywps/inout.py#L227<br>> > >> (will be moved to separate file soon, or maybe package)<br>> > >> J<br>> > >><br>> > >> ><br>> > >> ><br>> > >> > [1] [5][7]http://www.opengeospatial.org/standards/wps<br>> > >> > [2] [6][8]http://wiki.rsg.pml.ac.uk/pywps/Main_Page<br>> > >> > [3] [7][9]http://pywps.wald.intevation.org/documentation/<br>> > >> > [4] [8][10]http://pywps.readthedocs.or<br>> > >> ><br>> > >> > I will try to give you more information on the following<br>> days<br>> > >> ><br>> > >> > Jorge<br>> > >> ><br>> > >> ><br>> > >> ><br>> > >> > ________________________________________<br>> > >> > From: Naveen Panwar [[9][11]panwarn09@gmail.com]<br>> > >> > Sent: 07 March 2014 10:00<br>> > >> > To: Mendes de Jesus, Jorge; Jáchym Čepický<br>> > >> > Subject: [ GSOC 2014 ] Database output storage idea.<br>> > >> ><br>> > >> > Hello Sir,<br>> > >> ><br>> > >> > As we know students application starts on March 10th.<br>> > >> > For that I have to write proposal for the idea "Database<br>> output<br>> > >> storage - PostGIS and SQLite".<br>> > >> > So could you suggest anything in this direction. What should<br>> be in the<br>> > >> IDEA related to Pywps.<br>> > >> ><br>> > >> > Also could you suggest on which modules we have to add<br>> database<br>> > >> interaction<br>> > >> > in Pywps code base.<br>> > >> ><br>> > >> > --<br>> > >> ><br>> > >> > Regards,<br>> > >> > Naveen Panwar<br>> > >> > Senior Undergraduate Student<br>> > >> > IIIT-Hyderabad, India.<br>> > >> ><br>> > >> > [10][12]http://lsi.iiit.ac.in/naveen.panwar<br>> > >> ><br>> > >><br>> > >> --<br>> > >> Jachym Cepicky<br>> > >> URL: [11][13]http://les-ejk.cz<br>> > >> e-mail: jachym.cepicky at gmail com<br>> > >> PGP: [12][14]http://les-ejk.cz/pgp/JachymCepicky.pgp<br>> > >> @jachymc<br>> > >><br>> > >> --<br>> > >> Regards,<br>> > >> Naveen Panwar<br>> > >> Senior Undergraduate Student<br>> > >> IIIT-Hyderabad, India.<br>> > >> [13][15]http://lsi.iiit.ac.in/naveen.panwar<br>> > >><br>> > >> References<br>> > >><br>> > >> Visible links<br>> > >> 1.<br>> [16]http://netmar.nersc.no/sites/netmar.nersc.no/files/D7.7_WPS_Cookbook_r1_20111229.pdf<br>> > >> 2.<br>> [17]http://netmar.nersc.no/sites/netmar.nersc.no/files/D7.7_WPS_Cookbook_r1_20111229.pdf<br>> > >> 3. mailto:[18]jachym.cepicky@gmail.com<br>> > >> 4.<br>> [19]https://github.com/jachym/pywps-4/blob/master/pywps/inout.py#L227<br>> > >> 5. [20]http://www.opengeospatial.org/standards/wps<br>> > >> 6. [21]http://wiki.rsg.pml.ac.uk/pywps/Main_Page<br>> > >> 7. [22]http://pywps.wald.intevation.org/documentation/<br>> > >> 8. [23]http://pywps.readthedocs.or/<br>> > >> 9. mailto:[24]panwarn09@gmail.com<br>> > >> 10. [25]http://lsi.iiit.ac.in/naveen.panwar<br>> > >> 11. [26]http://les-ejk.cz/<br>> > >> 12. [27]http://les-ejk.cz/pgp/JachymCepicky.pgp<br>> > >> 13. [28]http://lsi.iiit.ac.in/naveen.panwar<br>> > ><br>> ><br>> ><br>> > --<br>> > ISRIC - World Soil Information Post: PO box 353, 6700 AJ, Wageningen,<br>> > The Netherlands Visiting Address: Droevendaalsesteeg 3, 6708 PB<br>> > Wageningen (Bdg. 101), Office: C.013 Office Phone: +31 (0) 317 4 83715<br>> > Mobile Phone: +31 (0) 613 9 06950 OpenPGPKey: 0xA3D0065A<br>> ><br>> <br>> --<br>> Jachym Cepicky<br>> URL: [29]http://les-ejk.cz<br>> e-mail: jachym.cepicky at gmail com<br>> PGP: [30]http://les-ejk.cz/pgp/JachymCepicky.pgp<br>> @jachymc<br>> _______________________________________________<br>> pywps-dev mailing list<br>> [31]pywps-dev@lists.osgeo.org<br>> [32]http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev<br>> <br>> --<br>> Regards,<br>> Naveen Panwar<br>> Senior Undergraduate Student<br>> IIIT-Hyderabad, India.<br>> [33]http://lsi.iiit.ac.in/naveen.panwar<br>> <br>> References<br>> <br>> Visible links<br>> 1. mailto:jachym.cepicky@gmail.com<br>> 2. http://istgeo.ist.supsi.ch/software/istsos/<br>> 3. http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140313T20&ah=1<br>> 4. http://netmar.nersc.no/sites/netmar.nersc.no/files/D7.7_WPS_Cookbook_r1_20111229.pdf<br>> 5. mailto:jachym.cepicky@gmail.com<br>> 6. https://github.com/jachym/pywps-4/blob/master/pywps/inout.py#L227<br>> 7. http://www.opengeospatial.org/standards/wps<br>> 8. http://wiki.rsg.pml.ac.uk/pywps/Main_Page<br>> 9. http://pywps.wald.intevation.org/documentation/<br>> 10. http://pywps.readthedocs.or/<br>> 11. mailto:panwarn09@gmail.com<br>> 12. http://lsi.iiit.ac.in/naveen.panwar<br>> 13. http://les-ejk.cz/<br>> 14. http://les-ejk.cz/pgp/JachymCepicky.pgp<br>> 15. http://lsi.iiit.ac.in/naveen.panwar<br>> 16. http://netmar.nersc.no/sites/netmar.nersc.no/files/D7.7_WPS_Cookbook_r1_20111229.pdf<br>> 17. http://netmar.nersc.no/sites/netmar.nersc.no/files/D7.7_WPS_Cookbook_r1_20111229.pdf<br>> 18. mailto:jachym.cepicky@gmail.com<br>> 19. https://github.com/jachym/pywps-4/blob/master/pywps/inout.py#L227<br>> 20. http://www.opengeospatial.org/standards/wps<br>> 21. http://wiki.rsg.pml.ac.uk/pywps/Main_Page<br>> 22. http://pywps.wald.intevation.org/documentation/<br>> 23. http://pywps.readthedocs.or/<br>> 24. mailto:panwarn09@gmail.com<br>> 25. http://lsi.iiit.ac.in/naveen.panwar<br>> 26. http://les-ejk.cz/<br>> 27. http://les-ejk.cz/pgp/JachymCepicky.pgp<br>> 28. http://lsi.iiit.ac.in/naveen.panwar<br>> 29. http://les-ejk.cz/<br>> 30. http://les-ejk.cz/pgp/JachymCepicky.pgp<br>> 31. mailto:pywps-dev@lists.osgeo.org<br>> 32. http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev<br>> 33. http://lsi.iiit.ac.in/naveen.panwar<br><div><br></div>-- <br>Jachym Cepicky<br>URL: http://les-ejk.cz<br>e-mail: jachym.cepicky at gmail com<br>PGP: http://les-ejk.cz/pgp/JachymCepicky.pgp<br>@jachymc<br>_______________________________________________<br>pywps-dev mailing list<br>pywps-dev@lists.osgeo.org<br>http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev</blockquote><div><br></div></div></body></html>