<div dir="ltr"><div><div>Respected Sir,<br><br></div>Followings are the points which needed to be answer regarding the proposal according to OSGeo Guideline.<br><br>1. Introduction --<br>2. Background -- <br>3. The idea --<br>
4. Project plan [ Detailed Time-line (Probably <b>13-week</b> ) ] --<br>5. Future ideas / How can your idea be expanded ? <br><br></div>I think we should consider these points on tonight hangout<br><br><br><div class="gmail_extra">
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">>> > 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]<a href="http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140313T20&ah=1" target="_blank">http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140313T20&ah=1</a><br>
>> > ><br>
>> > > we are still aranging, how to define timeslots<br>
>> > ><br>
>> > > J<br>
>> > ><br>
>> > >> [1] -<br>
>> > >><br>
>> [2][4]<a href="http://netmar.nersc.no/sites/netmar.nersc.no/files/D7.7_WPS_Cookbook_r1_20111229.pdf" target="_blank">http://netmar.nersc.no/sites/netmar.nersc.no/files/D7.7_WPS_Cookbook_r1_20111229.pdf</a><br>
>> > >><br>
>> > >> On Mon, Mar 10, 2014 at 2:33 AM, Jachym Cepicky<br>
>> > >> <[3][5]<a href="mailto:jachym.cepicky@gmail.com">jachym.cepicky@gmail.com</a>> 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]<a href="https://github.com/jachym/pywps-4/blob/master/pywps/inout.py#L227" target="_blank">https://github.com/jachym/pywps-4/blob/master/pywps/inout.py#L227</a><br>
>> > >> (will be moved to separate file soon, or maybe package)<br>
>> > >> J<br>
>> > >><br>
>> > >> ><br>
>> > >> ><br>
>> > >> > [1] [5][7]<a href="http://www.opengeospatial.org/standards/wps" target="_blank">http://www.opengeospatial.org/standards/wps</a><br>
>> > >> > [2] [6][8]<a href="http://wiki.rsg.pml.ac.uk/pywps/Main_Page" target="_blank">http://wiki.rsg.pml.ac.uk/pywps/Main_Page</a><br>
>> > >> > [3] [7][9]<a href="http://pywps.wald.intevation.org/documentation/" target="_blank">http://pywps.wald.intevation.org/documentation/</a><br>
>> > >> > [4] [8][10]<a href="http://pywps.readthedocs.or" target="_blank">http://pywps.readthedocs.or</a><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]<a href="mailto:panwarn09@gmail.com">panwarn09@gmail.com</a>]<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]<a href="http://lsi.iiit.ac.in/naveen.panwar" target="_blank">http://lsi.iiit.ac.in/naveen.panwar</a><br>
>> > >> ><br>
>> > >><br>
>> > >> --<br>
>> > >> Jachym Cepicky<br>
>> > >> URL: [11][13]<a href="http://les-ejk.cz" target="_blank">http://les-ejk.cz</a><br>
>> > >> e-mail: jachym.cepicky at gmail com<br>
>> > >> PGP: [12][14]<a href="http://les-ejk.cz/pgp/JachymCepicky.pgp" target="_blank">http://les-ejk.cz/pgp/JachymCepicky.pgp</a><br>
>> > >> @jachymc<br>
>> > >><br>
>> > >> --<br>
>> > >> Regards,<br>
>> > >> Naveen Panwar<br>
>> > >> Senior Undergraduate Student<br>
>> > >> IIIT-Hyderabad, India.<br>
>> > >> [13][15]<a href="http://lsi.iiit.ac.in/naveen.panwar" target="_blank">http://lsi.iiit.ac.in/naveen.panwar</a><br>
>> > >><br>
>> > >> References<br>
>> > >><br>
>> > >> Visible links<br>
>> > >> 1.<br>
>> [16]<a href="http://netmar.nersc.no/sites/netmar.nersc.no/files/D7.7_WPS_Cookbook_r1_20111229.pdf" target="_blank">http://netmar.nersc.no/sites/netmar.nersc.no/files/D7.7_WPS_Cookbook_r1_20111229.pdf</a><br>
>> > >> 2.<br>
>> [17]<a href="http://netmar.nersc.no/sites/netmar.nersc.no/files/D7.7_WPS_Cookbook_r1_20111229.pdf" target="_blank">http://netmar.nersc.no/sites/netmar.nersc.no/files/D7.7_WPS_Cookbook_r1_20111229.pdf</a><br>
>> > >> 3. mailto:[18]<a href="mailto:jachym.cepicky@gmail.com">jachym.cepicky@gmail.com</a><br>
>> > >> 4.<br>
>> [19]<a href="https://github.com/jachym/pywps-4/blob/master/pywps/inout.py#L227" target="_blank">https://github.com/jachym/pywps-4/blob/master/pywps/inout.py#L227</a><br>
>> > >> 5. [20]<a href="http://www.opengeospatial.org/standards/wps" target="_blank">http://www.opengeospatial.org/standards/wps</a><br>
>> > >> 6. [21]<a href="http://wiki.rsg.pml.ac.uk/pywps/Main_Page" target="_blank">http://wiki.rsg.pml.ac.uk/pywps/Main_Page</a><br>
>> > >> 7. [22]<a href="http://pywps.wald.intevation.org/documentation/" target="_blank">http://pywps.wald.intevation.org/documentation/</a><br>
>> > >> 8. [23]<a href="http://pywps.readthedocs.or/" target="_blank">http://pywps.readthedocs.or/</a><br>
>> > >> 9. mailto:[24]<a href="mailto:panwarn09@gmail.com">panwarn09@gmail.com</a><br>
>> > >> 10. [25]<a href="http://lsi.iiit.ac.in/naveen.panwar" target="_blank">http://lsi.iiit.ac.in/naveen.panwar</a><br>
>> > >> 11. [26]<a href="http://les-ejk.cz/" target="_blank">http://les-ejk.cz/</a><br>
>> > >> 12. [27]<a href="http://les-ejk.cz/pgp/JachymCepicky.pgp" target="_blank">http://les-ejk.cz/pgp/JachymCepicky.pgp</a><br>
>> > >> 13. [28]<a href="http://lsi.iiit.ac.in/naveen.panwar" target="_blank">http://lsi.iiit.ac.in/naveen.panwar</a><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]<a href="http://les-ejk.cz" target="_blank">http://les-ejk.cz</a><br>
>> e-mail: jachym.cepicky at gmail com<br>
>> PGP: [30]<a href="http://les-ejk.cz/pgp/JachymCepicky.pgp" target="_blank">http://les-ejk.cz/pgp/JachymCepicky.pgp</a><br>
>> @jachymc<br>
>> _______________________________________________<br>
>> pywps-dev mailing list<br>
>> [31]<a href="mailto:pywps-dev@lists.osgeo.org">pywps-dev@lists.osgeo.org</a><br>
>> [32]<a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev</a><br>
>><br>
>> --<br>
>> Regards,<br>
>> Naveen Panwar<br>
>> Senior Undergraduate Student<br>
>> IIIT-Hyderabad, India.<br>
>> [33]<a href="http://lsi.iiit.ac.in/naveen.panwar" target="_blank">http://lsi.iiit.ac.in/naveen.panwar</a><br>
>><br>
>> References<br>
>><br>
>> Visible links<br>
>> 1. mailto:<a href="mailto:jachym.cepicky@gmail.com">jachym.cepicky@gmail.com</a><br>
>> 2. <a href="http://istgeo.ist.supsi.ch/software/istsos/" target="_blank">http://istgeo.ist.supsi.ch/software/istsos/</a><br>
>> 3. <a href="http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140313T20&ah=1" target="_blank">http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140313T20&ah=1</a><br>
>> 4. <a href="http://netmar.nersc.no/sites/netmar.nersc.no/files/D7.7_WPS_Cookbook_r1_20111229.pdf" target="_blank">http://netmar.nersc.no/sites/netmar.nersc.no/files/D7.7_WPS_Cookbook_r1_20111229.pdf</a><br>
>> 5. mailto:<a href="mailto:jachym.cepicky@gmail.com">jachym.cepicky@gmail.com</a><br>
>> 6. <a href="https://github.com/jachym/pywps-4/blob/master/pywps/inout.py#L227" target="_blank">https://github.com/jachym/pywps-4/blob/master/pywps/inout.py#L227</a><br>
>> 7. <a href="http://www.opengeospatial.org/standards/wps" target="_blank">http://www.opengeospatial.org/standards/wps</a><br>
>> 8. <a href="http://wiki.rsg.pml.ac.uk/pywps/Main_Page" target="_blank">http://wiki.rsg.pml.ac.uk/pywps/Main_Page</a><br>
>> 9. <a href="http://pywps.wald.intevation.org/documentation/" target="_blank">http://pywps.wald.intevation.org/documentation/</a><br>
>> 10. <a href="http://pywps.readthedocs.or/" target="_blank">http://pywps.readthedocs.or/</a><br>
>> 11. mailto:<a href="mailto:panwarn09@gmail.com">panwarn09@gmail.com</a><br>
>> 12. <a href="http://lsi.iiit.ac.in/naveen.panwar" target="_blank">http://lsi.iiit.ac.in/naveen.panwar</a><br>
>> 13. <a href="http://les-ejk.cz/" target="_blank">http://les-ejk.cz/</a><br>
>> 14. <a href="http://les-ejk.cz/pgp/JachymCepicky.pgp" target="_blank">http://les-ejk.cz/pgp/JachymCepicky.pgp</a><br>
>> 15. <a href="http://lsi.iiit.ac.in/naveen.panwar" target="_blank">http://lsi.iiit.ac.in/naveen.panwar</a><br>
>> 16. <a href="http://netmar.nersc.no/sites/netmar.nersc.no/files/D7.7_WPS_Cookbook_r1_20111229.pdf" target="_blank">http://netmar.nersc.no/sites/netmar.nersc.no/files/D7.7_WPS_Cookbook_r1_20111229.pdf</a><br>
>> 17. <a href="http://netmar.nersc.no/sites/netmar.nersc.no/files/D7.7_WPS_Cookbook_r1_20111229.pdf" target="_blank">http://netmar.nersc.no/sites/netmar.nersc.no/files/D7.7_WPS_Cookbook_r1_20111229.pdf</a><br>
>> 18. mailto:<a href="mailto:jachym.cepicky@gmail.com">jachym.cepicky@gmail.com</a><br>
>> 19. <a href="https://github.com/jachym/pywps-4/blob/master/pywps/inout.py#L227" target="_blank">https://github.com/jachym/pywps-4/blob/master/pywps/inout.py#L227</a><br>
>> 20. <a href="http://www.opengeospatial.org/standards/wps" target="_blank">http://www.opengeospatial.org/standards/wps</a><br>
>> 21. <a href="http://wiki.rsg.pml.ac.uk/pywps/Main_Page" target="_blank">http://wiki.rsg.pml.ac.uk/pywps/Main_Page</a><br>
>> 22. <a href="http://pywps.wald.intevation.org/documentation/" target="_blank">http://pywps.wald.intevation.org/documentation/</a><br>
>> 23. <a href="http://pywps.readthedocs.or/" target="_blank">http://pywps.readthedocs.or/</a><br>
>> 24. mailto:<a href="mailto:panwarn09@gmail.com">panwarn09@gmail.com</a><br>
>> 25. <a href="http://lsi.iiit.ac.in/naveen.panwar" target="_blank">http://lsi.iiit.ac.in/naveen.panwar</a><br>
>> 26. <a href="http://les-ejk.cz/" target="_blank">http://les-ejk.cz/</a><br>
>> 27. <a href="http://les-ejk.cz/pgp/JachymCepicky.pgp" target="_blank">http://les-ejk.cz/pgp/JachymCepicky.pgp</a><br>
>> 28. <a href="http://lsi.iiit.ac.in/naveen.panwar" target="_blank">http://lsi.iiit.ac.in/naveen.panwar</a><br>
>> 29. <a href="http://les-ejk.cz/" target="_blank">http://les-ejk.cz/</a><br>
>> 30. <a href="http://les-ejk.cz/pgp/JachymCepicky.pgp" target="_blank">http://les-ejk.cz/pgp/JachymCepicky.pgp</a><br>
>> 31. mailto:<a href="mailto:pywps-dev@lists.osgeo.org">pywps-dev@lists.osgeo.org</a><br>
>> 32. <a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev</a><br>
>> 33. <a href="http://lsi.iiit.ac.in/naveen.panwar" target="_blank">http://lsi.iiit.ac.in/naveen.panwar</a><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>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr"><br><div dir="ltr"><div><font face="arial, helvetica, sans-serif">Regards,</font></div><div><font face="arial, helvetica, sans-serif">Naveen Panwar</font></div>
<div><font face="arial, helvetica, sans-serif"><span style="text-align:-webkit-auto">Senior</span><span style="text-align:-webkit-auto"> </span><span style="text-align:-webkit-auto">Undergraduate Student</span><br></font></div>
<div><span style="text-align:-webkit-auto"><font face="arial, helvetica, sans-serif">IIIT-Hyderabad, India.</font></span></div><div><span style="text-align:-webkit-auto"><font face="arial, helvetica, sans-serif"><br></font></span></div>
<div><div style="font-family:arial;font-size:small"><a href="http://lsi.iiit.ac.in/naveen.panwar" style="font-family:arial,helvetica,sans-serif;color:rgb(17,85,204)" target="_blank">http://lsi.iiit.ac.in/naveen.panwar</a><br>
</div><div style="font-family:arial;font-size:small"><br></div></div></div></div>
</div></div>