search

landam / grass-gis-git-migration-test

0 stars 0 forks source link

Allow wildcards in multiple map input and evaluate to map lists accordingly #173

Open landam opened 5 years ago

landam commented 5 years ago

Reported by sbl on 10 Sep 2015 17:49 UTC For GRASS beginners and people who stick to the GUI the ability to use wildcards in multiple map input might be handy.

People who are not afraid of the command line can of course easily pipe g.list output to modules with multiple input or re-use the latter from file like e.g. in temporal modules.

An idea would be to allow something like this:

# Example: calculate average temperature for Norway`s national day
r.series input=temperature_*_05_17 output=norway_national_day_temperature_avg method=average

in the GUI or command line, where wildcards are evaluated to a list of available maps following that pattern. Since the asterisk is not allowed in map names, it might used to trigger a respective g.list operation whenever it appears in a multiple map input

One suggestion would be to reuse a dialog for selecting multiple maps using regular expressions (accessible from layer manager) and have a small button near the map entry in the autogenerated dialogs which would open this dialog and transfer the resulting map series back in the map entry field. So this would be implemented on the GUI level.

Another suggestion would be to implement this on parser level. Both have some pluses and minuses.

Anyway, a potential risk is that result might be - especially for beginners - difficult to anticipate. That may result in unexpected behavior, esp when several mapsets are in the search path ...

See also: https://lists.osgeo.org/pipermail/grass-dev/2015-September/076222.html

Migrated-From: https://trac.osgeo.org/grass/ticket/2739

landam commented 5 years ago

Modified by sbl on 4 Jan 2016 13:31 UTC

landam commented 5 years ago

Comment by neteler on 5 May 2016 14:08 UTC Milestone renamed

landam commented 5 years ago

Comment by neteler on 28 Dec 2016 15:04 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Modified by @landam on 5 May 2017 20:40 UTC

landam commented 5 years ago

Comment by @landam on 1 Sep 2017 20:28 UTC All enhancement tickets should be assigned to 7.4 milestone.

landam commented 5 years ago

Comment by neteler on 26 Jan 2018 11:40 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Modified by neteler on 12 Jun 2018 20:48 UTC

landam commented 5 years ago

Comment by @landam on 25 Sep 2018 16:52 UTC All enhancement tickets should be assigned to 7.6 milestone.

landam commented 5 years ago

Comment by @landam on 25 Jan 2019 21:07 UTC Ticket retargeted after milestone closed