Changes between Version 41 and Version 42 of GSoC/2018

Timestamp:

Mar 10, 2018, 2:54:19 PM (6 years ago)

Author:

wenzeslaus

Comment:

more examples, test tasks, link tickets

GSoC/2018

@@ -294 +294 @@
 
  * TL;DR: Make running of GRASS GIS modules as easy as it is to run GDAL commands.
+  * `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
+  * CLI like GDAL has.
   * No GRASS Database, Location, Mapset to deal with.
   * No import, export from user perspective.
@@ -324 +326 @@
   * Ideally this should work also with PostGIS and databases provided through GDAL/OGR.
  * Proposal should discuss and address how advanced things such raster algebra, multi-map inputs and outputs, temporal framework, cartography and visualization tools will work.
+ * Use should be able to always specify the details manually:
+
+{{{
+grass run --mapset=/some/directory/grassdata/ncspm/practice1 r.lake elevation=some/file.tiff ...
+grass run --region="s=55600 n=60500..." --mask=some/mask.tiff r.lake elevation=some/file.tiff ...
+grass run --crs=EPSG:3358 --mask=some/mask.tiff r.lake elevation=some/file.tiff ...
+}}}
+
  * The system behind the interface will be inherently fragile, so it is necessary to write large amount of tests which would check different combinations of data types and projections.
  * All the underlying code is expected to be in Python, so the project should involve also creation of Python API on the way.
@@ -334 +344 @@
   * source:grass/trunk/lib/init/grass.py (full GRASS GIS standard startup "script")
  * See also:
-  * #2579 Specify command to be executed as parameter of grass command (patch) and other suggestion for CLI
-  * [http://lists.osgeo.org/pipermail/grass-dev/2015-January/072979.html grass-dev QGIS Processing & GRASS (January 2015)]
-  * #2424 PyGRASS does not work when GRASS is invoked from outside because it is not possible to change path to dynamic libraries in running process
-  * [http://grasswiki.osgeo.org/wiki/Working_with_GRASS_without_starting_it_explicitly Working with GRASS without starting it explicitly]
-  * wiki:Grass7/VectorLib/OGRInterface
-  * wiki:Grass7/VectorLib/PostGISInterface
-  * [https://github.com/qgis/QGIS/blob/0a1382a0be36d408aebd227fb0066f68c513e41e/python/plugins/processing/algs/grass7/Grass7Algorithm.py QGIS Processing Grass7Algorithm.py] source code
-  * [https://github.com/moovida/jgrasstools/blob/530c87f26d220f3eeff9d2fb9d21abd8821c00c3/grass/src/main/java/org/jgrasstools/grass/utils/ModuleSupporter.java uDig's JGrasstools] source code
-  * [http://sextante.googlecode.com/svn/trunk/soft/sextante_lib/sextante_gui/src/es/unex/sextante/gui/grass/ SEXTANTE grass] source code (broken link)
-  * [https://github.com/geopython/PyWPS/blob/425f0eb160f60714a6705a24ba926e03690ab371/pywps/Grass.py PyWPS source code] and [http://pywps.wald.intevation.org/documentation/process.html PyWPS documentation] (broken link)
-  * [https://code.google.com/p/wps-grass-bridge/source/browse/trunk/?r=97 wps-grass-bridge] source code (broken link)
-  * Related discussions on mailing list:
-   * [http://lists.osgeo.org/pipermail/grass-dev/2015-February/073867.html On GSoC Proposal New easy-to-use...]
-   * [http://lists.osgeo.org/pipermail/grass-dev/2015-March/074433.html GSOC project proposal]
+  * Tickets:
+   * #2579 Specify command to be executed as parameter of grass command (patch) and other suggestion for CLI
+   * #2678 GRASS starts even when Mapset is locked 
+   * #2679 Drop or fix setting of Location and Mapset using environmental variables
+   * #2681 Remove legacy meaning of LOCATION variable 
+   * #2424 PyGRASS does not work when GRASS is invoked from outside because it is not possible to change path to dynamic libraries in running process
+  * Mailing list and wikis:
+   * [http://lists.osgeo.org/pipermail/grass-dev/2015-January/072979.html grass-dev QGIS Processing & GRASS (January 2015)]
+   * [http://grasswiki.osgeo.org/wiki/Working_with_GRASS_without_starting_it_explicitly Working with GRASS without starting it explicitly]
+   * wiki:Grass7/VectorLib/OGRInterface
+   * wiki:Grass7/VectorLib/PostGISInterface
+  * Other projects (see also the ones linked in the text):
+   * [https://github.com/qgis/QGIS/blob/0a1382a0be36d408aebd227fb0066f68c513e41e/python/plugins/processing/algs/grass7/Grass7Algorithm.py QGIS Processing Grass7Algorithm.py] source code
+   * [https://github.com/moovida/jgrasstools/blob/530c87f26d220f3eeff9d2fb9d21abd8821c00c3/grass/src/main/java/org/jgrasstools/grass/utils/ModuleSupporter.java uDig's JGrasstools] source code
+   * [http://sextante.googlecode.com/svn/trunk/soft/sextante_lib/sextante_gui/src/es/unex/sextante/gui/grass/ SEXTANTE grass] source code (broken link)
+   * [https://github.com/geopython/PyWPS/blob/425f0eb160f60714a6705a24ba926e03690ab371/pywps/Grass.py PyWPS source code] and [http://pywps.wald.intevation.org/documentation/process.html PyWPS documentation] (broken link)
+   * [https://code.google.com/p/wps-grass-bridge/source/browse/trunk/?r=97 wps-grass-bridge] source code (broken link)
+   * Related discussions on mailing list:
+    * [http://lists.osgeo.org/pipermail/grass-dev/2015-February/073867.html On GSoC Proposal New easy-to-use...]
+    * [http://lists.osgeo.org/pipermail/grass-dev/2015-March/074433.html GSOC project proposal]
+   * Similar complex command line interfaces to learn from: !GeoGig, !ImageMagic (compare new and old CLI), Git, Docker
+ * Test and training tasks:
+  * Tests and extent `--exec` functionality:
+   * Add `--tmp-location` which runs `--exec` in a database/location/mapset which are created at the beginning and deleted at the end.
+   * Add `-c XY` and `-c LL` for simple unprojected and latitude-longitude Locations (compare options in the current CLI to wxGUI Location Wizard).
+   * Add `--clean` (current default) and `--no-clean` which say if `--exec` should clean the `.tmp` directory in the Mapset (for parallel execution).
+   * Add `--lock` (current default) and `--no-lock` which say if `--exec` should lock the Mapset (for parallel execution).
+   * Add `--region` to set a temporary computational region for the execution.
+   * Add `--import-raster=some/file.tiff` which imports (r.in.gdal or r.import) a raster file (same for vector).
+   * Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector).
+   * Add `--export-raster=some/file.tiff` which exports (e.g. r.out.gdal) a raster file (same for vector).
+   * Add `--link-output-raster=some/file.tiff` which creates (r.external.out) a new (output) raster file (same for vector).
  * Language requirements: Python
- * Mentor for the GRASS GIS part: Vaclav Petras
- * Mentor for the QGIS part: ?
- * Mentor for the <insert other OSGeo project> part: ?
- * Co-mentors (e.g. PostGIS connection part): ?
+ * Mentors: Vaclav Petras
+ * Co-mentors: ?
 == Tips for students ==