Changes between Version 1 and Version 2 of MPLEMENTING_WPS_FOR_GEOPAPARAZZI_FIELD_DATA_COLLECTION_TOOL_USING_ZOO-PROJECT:SIMPLIFYING_INTEGRATION_OF_FIELD_DATA_AND_GIS
- Timestamp:
- Apr 29, 2016, 4:41:19 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MPLEMENTING_WPS_FOR_GEOPAPARAZZI_FIELD_DATA_COLLECTION_TOOL_USING_ZOO-PROJECT:SIMPLIFYING_INTEGRATION_OF_FIELD_DATA_AND_GIS
v1 v2 15 15 == Schedule == 16 16 Basically this project based on ZOOProject and the JGrasstools. Those two has many capabilities and functions. In order to focus this project, those functions and capabilities will be studied before start the GSoC. 17 {| class="wikitable"|- 18 ! Timeline !! TODO !! Status 17 19 18 |- 20 | 23 – 31 May 2016 || 21 * Starting with ZOO-Project and pyModis by learning how to write ZOO Service Configuration File (ZCFG) and Implementing the Python Service. 22 || --- 19 23 20 |- 24 | 1 – 25 June 2016 || 25 * Implementation of pyModis WPS services corresponding to an available script. 26 * Development made in the ZOO-Project (GRASS, OTB and SAGA processing support) by bringing MODIS data to the web. 27 || --- 21 | May 23 - June 04 2016 | || 22 * Identifying and analysing the different capabilities of JGrasstools Simultaneously starts the ZOOProjects and study and analyze about its capabilities by implementing example projects. 23 28 24 |- 29 | 26 June – 10 July 2016||30 * C reation of the first version of the template used by the web application to automatically generate the HTML form for accessing pyModis WPS services.31 || ---25 | 5 – 26 June 2016 ||| 26 * Configuration of ZOOProject and Implementing JGrasstools as a service in it. 27 || 32 28 |- 33 | 11 – 25 July 2016 || 34 * Testing template and design user interfaces of web mapping application. 35 || --- 29 | 27 June – 09 July 2016 ||| 30 * Development of the function to import and export Geopaparazzi project by using JGrasstools as a service. 31 * Analysing the converted project 32 || 36 33 |- 37 | 26 July – 2 August 2016||38 * Update the template for the web application to take into account potential new type of input.39 || ---34 | 09 – 16 July 2016 ||| 35 * Developing a simple template for web access to run the process. 36 || 40 37 |- 41 | 3 – 5 August 2016 || 42 * Usability testing template system and web mapping application. 43 || --- 38 | 17 - 30 July 2016 | || 39 * Testing other capabilities of JGrasstools and identify important capabilities ( based on different criterias). 40 * Testing the ports to them and develop an access to them 41 || 44 42 |- 45 | 6 – 9 August 2016||46 * Stringent testing and bug fixes full system.47 || ---43 | 31 July – 6 August 2016 ||| 44 * Integrate other capabilities to the template. 45 || 48 46 |- 49 | 10 – 17 August 2016 || 50 * Documenting the web application and publication on the ZOO-Project web site as an example application. 51 || --- 52 |} 53 On the last day of each week, I will write a blog post reporting all the work done during the past week. 47 | 7 – 9 August 2016 | || 48 * Testing the template and develop user interface for web access. 49 * Identifying the issues and problems regarding the template 50 || 51 |- 52 | 10 – 12 August 2016 | || 53 * Fix and updates the identified issues and potential changes. 54 || 55 |- 56 | 13 – 16 August 2016 | || 57 * Fully testing the whole system and validation. 58 * Identifying bugs. 59 * Fix all the bugs and errors 60 || 61 |- 62 | 16 – 17 August 2016||| 63 * Finalise the documentation, sources, project and the examples 64 65 66 While we are doing above steps, all the steps and action will be documented as a blog posts including all the errors and issues as a discussion. 54 67 55 68 == Reports ==