[SoC] Week 7 report: Creation of a new GRASS GIS startup mechanism
L.Kladivova at seznam.cz
Sun Jul 19 03:29:42 PDT 2020
I am sending my report for Week 7 (July 13-July 19). The report can also be
found in the project wiki: https://trac.osgeo.org/…dow
1) What did I complete this week?
I finalized the PR Add multiple GRASS databases (see https://github.com/
). I also made several smaller PRs related to several issues. As we would
like distinguish different layers according to lock and ownership in future,
it was necessary to distinguish the label and name of nodes (see https://
(https://github.com/OSGeo/grass/issues/780)). I also changed the order of
Layer Manager tabs and a label "Layers" to "Display" (see https://github.
). Simultaneously, I am working on bigger PRs related to new actions in Data
Catalog. The first one adds Create New Location and Download Location
actions to the database node in Data tab (see https://github.com/OSGeo/
second one allows the Delete action on multiple selected mapsets (see
2) What am I going to achieve next week?
As the paradigm has quite changed after the community video call on July 15
(startup screen will be probably removed), I will go ahead and add more
functions and actions to Data Catalog which is now becoming the center point
of the whole management in GRASS. First I am gonna focus on Adding new icons
to the data catalog for several actions whose list is still broadening. This
is related to the Issue https://github.com/OSGeo/grass/issues/800
(https://github.com/OSGeo/grass/issues/800). There are also other issues
related to the Data Catalog I am gonna address:
* Add functionality to load only data from the current mapset in the Data
tree (see https://github.com/OSGeo/grass/issues/749
* Startup screen: Distinguish mapsets by ownership and lock (see
* Check for gislock and other issues when deleting/renaming/editing
mapset and location in catalog (https://github.com/OSGeo/grass/issues/
3) Is there any blocking issue?
No, it is not.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SoC