wiki:GSoC/2018/IntegrationInQGIS3

Version 1 (modified by radeknovotny94, 6 years ago) ( diff )

--

GSoC 2018 Improve GRASS GIS integration in QGIS 3

Title: Improve GRASS GIS integration in QGIS 3
Student Name: Radek Novotný, Czech Technical University in Prague
Organization: OSGeo - Open Source Geospatial Foundation
Mentor Name: Marin Landa, Vaclav Petras
GSoC proposal: view proposal

Abstract

Currently, GRASS integration in QGIS is hard to maintain. There are two QGIS plugins - Processing and GRASS Plugin, which differs each other. This proposal is focused on Processing plugin. Processing plugin is at this moment maintained by QGIS developers in core Git repository. This situation has been discussed in the QGIS and GRASS GIS mailing lists several times. GUI dialogues of the Processing plugin are generated from manually maintained text UI description files.

Goal

My goal is to design a Python library (and possibly also a GRASS module based on this library) which allows creating this text UI files automatically from generated GRASS XML description. This library also has to simplify and divide parameters for QGIS. This approach would be similar to the function of SAGA (or OTB) Processing plugin integration QGIS.

After this addition will be possible to generate text UI files for new GRASS modules (added to the core or even for add-ons) in an automated way. These generated UI files can be part of Git repository, but in future could be generated automatically during QGIS compilation, when a user installs GRASS Addon module using Processing plugin, or on the fly when the GUI is started.

Timeline

Time Period

Milestones

Tasks

Status

April 23 - May 14
Community Bonding

  • Prepare the wiki page about the project
  • Discuss the design of functions with mentors and on mailing lists (GRASS, QGIS)

May 14 - May 20
Week 1

  • Implement an initial version of Python library for generating UI files used by Processing plugin based on GRASS modules XML description.

May 21 - May 27
Week 2

  • Integration of generated description UI files from initial Python library to Processing plugin in order to generate GUI dialogue for GRASS modules.

May 28 - June 3
Week 3

  • Split GRASS module parameters in Processing plugin to basic and advanced tabs.

June 4 - June 10
Week 4

  • Customization of parameter descriptions in order to take care of differences in GRASS and QGIS terminology.

July 11 - July 15
Evaluation 1

  • Goal: Working Python library generating files which could be used in Processing plugin
  • Mentors evaluate me and I evaluate mentors of official coding period phase.

June 11 - June 17
Week 5

  • Solve how to split GRASS modules for Processing plugin and minimize user confusion.

June 18 - June 24
Week 6

  • Bugfixing, fix problems which appear after integration of Python library in Processing plugin.

June 25 - July 1
Week 7

  • Implement simplified run or --exec method logic in GRASS.

July 2 - July 8
Week 8

  • Research actual processing code and simplified it for using a run method.

July 9 - July 13
Evaluation 2

  • Goal: Release version of the library, implemented run method in GRASS
  • Mentors evaluate me and I evaluate mentors of official coding period phase.

July 9 - July 15
Week 9

  • Integrate GRASS run logic in Processing plugin

July 16 - July 22
Week 10

  • Create documentation related to GRASS Processing plugin integration (generating UI files, GRASS caller, …).
  • Testing implementation.

July 23 - July 29
Week 11

  • Fix bugs and documentation details.

July 30 - August 5
Week 12

  • Prepare for final delivery.

August 6 - August 14
Evaluation 3 (Final)

  • Wrap up my projects and submit the final evaluation of my mentors.

Weekly reports

Note: See TracWiki for help on using the wiki.