WxGUI WMS service rendering GSoC 2011: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
Line 16: Line 16:


== Planned Timeline ==
== Planned Timeline ==
1 - 7 June : To introduce toy changes in the source code. To get familiar with the source file structuring and existing code. Learn WxPython and get Comfortable with it.
7-14 June  : To introduce meaningful changes in the WXGUI. Aim to write a module for statically updating the WXGUI without any back end support from WMS services.
14-21 June  :To hard code for dynamic updating of GUI without WMS support
21-28 June : To establish correctness of the code , testing of the modules.
29 June - 5 July: To understand the available WMS services. To extract the features available through get feature module.
6 July - 13 July: To hard code for the WMS layer supports available so as to update the front end GUI.
14 July - 21 July: To integrate the front end WXGUI new modules for updating the interface with the backend support from WMS GetCapabilites services.
22 July- 29 July: To introduce get layers service of the WMS services in the front end of WXGUI


== Weekly Reports, from SoC mailing list ==
== Weekly Reports, from SoC mailing list ==

Revision as of 10:14, 30 May 2011

Aim of the project

This project aims to introduce several features that make WXGUI more user-friendly. These include adding WMS layer support for WXGUI. The selection features will be displayed as per the based on service GetCapabilities response. The parameters and the layers are to be displayed are extracted out of the xml response.

State of the art

The project uses WMS service to fetch images of the maps. The Get Feature service of WMS services provides a GML based interface to access the information about various layers available. The WMS layer knowledge is used to update the GUI of the GRASS according to the available features for a particular layer. Thw WX-GUI is to be modified and to be integrated with the WMS services.

Bulletin Board

Documentation

The sequence diagram and use case diagram for the proposed Gsoc project are shown below

Planned Timeline

1 - 7 June : To introduce toy changes in the source code. To get familiar with the source file structuring and existing code. Learn WxPython and get Comfortable with it.

7-14 June  : To introduce meaningful changes in the WXGUI. Aim to write a module for statically updating the WXGUI without any back end support from WMS services.


14-21 June :To hard code for dynamic updating of GUI without WMS support

21-28 June : To establish correctness of the code , testing of the modules.

29 June - 5 July: To understand the available WMS services. To extract the features available through get feature module.

6 July - 13 July: To hard code for the WMS layer supports available so as to update the front end GUI.

14 July - 21 July: To integrate the front end WXGUI new modules for updating the interface with the backend support from WMS GetCapabilites services.

22 July- 29 July: To introduce get layers service of the WMS services in the front end of WXGUI

Weekly Reports, from SoC mailing list

May 29 , 2011 Report [0]

   Done
 

I have completed creating the uml diagrams (sequence and use case) for the planned architecture of the project.I have uploaded them to wiki. I have read GUI documentation from the programmer's manual [0]. I have gone through the source file structuring . I have setup the system, compiled the source and successfully installed it.


   Planned for next week 

I plan to introduce some toy changes in the source code, like print statements. I will try to familiarize myself with the wxPython.

   Bottleneck(s) 

No major bottlenecks till now.

[0] http://grass.osgeo.org/programming6/

References