Re: [GRASS-dev] gsoc preferred source location
2014-05-26 9:05 GMT+02:00 Luca Delucchi lucadel...@gmail.com: On 23 May 2014 19:02, Vaclav Petras wenzesl...@gmail.com wrote: I don't think that grass-addons are appropriate. I consider grass-addons as extension/addon/plugin repository, so thinks which you can install into GRASS make sense there. r3.flow definitely does. I'm not so sure about testing framework or metadata. sandbox make seems like more appropriate in this case (no structure required or expected). sandbox/gsoc sandbox/gsoc/2014/ sandbox/gsoc/2014/metadata +1 for use sandbox... agreed, Martin ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] gsoc preferred source location
On 23 May 2014 19:02, Vaclav Petras wenzesl...@gmail.com wrote: I don't think that grass-addons are appropriate. I consider grass-addons as extension/addon/plugin repository, so thinks which you can install into GRASS make sense there. r3.flow definitely does. I'm not so sure about testing framework or metadata. sandbox make seems like more appropriate in this case (no structure required or expected). sandbox/gsoc sandbox/gsoc/2014/ sandbox/gsoc/2014/metadata +1 for use sandbox... -- ciao Luca http://gis.cri.fmach.it/delucchi/ www.lucadelu.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2253: WinGRASS doesn't allow to close console window
#2253: WinGRASS doesn't allow to close console window --+- Reporter: martinl | Owner: grass-dev@… Type: defect | Status: closed Priority: blocker | Milestone: 7.0.0 Component: wxGUI| Version: svn-trunk Resolution: fixed|Keywords: wingrass, terminal window Platform: All | Cpu: Unspecified --+- Changes (by martinl): * status: new = closed * resolution: = fixed Comment: Replying to [comment:7 annakrat]: Backported in r60489. Confirmed, closing the ticket. Thanks. -- Ticket URL: http://trac.osgeo.org/grass/ticket/2253#comment:9 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2312: browse button in import vector/raster wrapper for v.in.ogr and r.in.gdal crashes entire GUI
#2312: browse button in import vector/raster wrapper for v.in.ogr and r.in.gdal crashes entire GUI --+- Reporter: cmbarton | Owner: grass-dev@… Type: defect | Status: closed Priority: blocker | Milestone: 7.1.0 Component: wxGUI| Version: svn-trunk Resolution: fixed|Keywords: Platform: Unspecified | Cpu: Unspecified --+- Comment(by cmbarton): Thanks. Too bad this wasn't caught before I did the binaries as I won't be able to compile again until mid-July. Oh well. -- Ticket URL: http://trac.osgeo.org/grass/ticket/2312#comment:4 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 7.0beta3 planning
On 25 May 2014 23:23, Markus Neteler nete...@osgeo.org wrote: Hi, Hi, as Martin stated in a recent ticket comment, beta3 should be released asap. I would like to get first the pygrass changes backported (not difficult including the manual improvements). Today and tomorrow I would like to improve a little bit more the pygrass manual, could you wait few days before backport these changes? A few more things are potentially missing, too. Opinions? Markus -- ciao Luca http://gis.cri.fmach.it/delucchi/ www.lucadelu.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] g.mlist: output (to ASCII file) parameter wish
Hi, since backticks are somewhat complicated to manage on some systems and since the wxGUI command line actually eats them, it would be good to have the possibility to output the result of g.mlist into an ASCII file. E.g. r.series accepts map lists from a file, so in a two-pass also Windows users could easily process map series. g.mlist rast pattern=precip*1951_1980_monthly_sums* output=maplist.txt r.series file=maplist.txt output=precip_0_25deg.1951.1980.sum method=sum Makes sense? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
On 25/05/14 09:32, Markus Neteler wrote: On Fri, May 16, 2014 at 2:38 PM, Moritz Lennert mlenn...@club.worldonline.be wrote: On 15/05/14 23:14, Markus Neteler wrote: ... Draft announcement to be updated: http://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News Important bugs concerning the next release https://trac.osgeo.org/grass/report/13 Here the full list of issues but none is a blocker: https://trac.osgeo.org/grass/query?status=assignedstatus=newstatus=reopenedgroup=statusmilestone=6.4.4 To test on Windows: g.remove cannot remove vector map because of space in DB layer name https://trac.osgeo.org/grass/ticket/1438 You note that this should be wontfix. What do you want to be tested ? Right, nothing to be tested I guess. To be closed? Yes. - r.walk backport https://trac.osgeo.org/grass/ticket/1628 ... not sure what to backport. Markus Metz may have an idea. v.kcv backport https://trac.osgeo.org/grass/ticket/2035 See my comment in the ticket. The vector overwrite issue in other mapsets seems to be a general problem, see ticket. Yes, and I think this is serious enough to solve this before release, even if people seem to have lived with it for a long time... And/or I can tag RC1 now and we do these issues later. I think that except for the r.walk segfault, none are really showstoppers. And even that only seems to be reproducible in a very specific situation. Given the recent discussion elsewhere I am stuck here. Do you want me to tag RC1 or wait ...? I think that we should try to structure the entire release process a bit more as we are currently dealing with two release processes in parallel (6 and 7) and I have the feeling that this is a bit overwhelming for our little team and that the lack of clear structure of the process leads to the frustrations seen on the list lately. I would, therefore, propose to focus on 6.4.4 for now, getting that out of the door before we work on 7.0 (especially since there seem to be some fundamental issues to be solved before releasing anything). I also think that we should work out a clear calendar for that release with official announcements of freeze policy. I think we are not far at all from releasing, so maybe something like this: - Real freeze of grass64_release at the end of this week. This means that any backports from grass6_devel should happen before that moment. But only non-invasive and well-tested elements should be backported. - RC1 beginning of next week - Bug squashing effort during the two weeks that follow. - RC2 around June 15th. - Another week of bug squashing, if necessary. - Release of 6.4.4 by end of June, the latest. That sound ok ? Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.4 planning
Hi, 2014-05-26 12:58 GMT+02:00 Moritz Lennert mlenn...@club.worldonline.be: I think we are not far at all from releasing, so maybe something like this: - Real freeze of grass64_release at the end of this week. This means that any backports from grass6_devel should happen before that moment. But only non-invasive and well-tested elements should be backported. - RC1 beginning of next week - Bug squashing effort during the two weeks that follow. - RC2 around June 15th. - Another week of bug squashing, if necessary. - Release of 6.4.4 by end of June, the latest. That sound ok ? sounds good to me... Martin -- Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] g.mlist: output (to ASCII file) parameter wish
Hi,
2014-05-26 11:33 GMT+02:00 Markus Neteler nete...@osgeo.org:
g.mlist rast pattern=precip*1951_1980_monthly_sums* output=maplist.txt
r.series file=maplist.txt output=precip_0_25deg.1951.1980.sum method=sum
Makes sense?
yes, make sense, see patch in the attachment (it's not complete, -p/-f
ignores output option).
Martin
--
Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa
Index: general/g.mlist/main.c
===
--- general/g.mlist/main.c (revision 60489)
+++ general/g.mlist/main.c (working copy)
@@ -9,7 +9,7 @@
* PURPOSE: Lists available GRASS data base files of the
* user-specified data type to standard output
*
- * COPYRIGHT:(C) 1999-2011 by the GRASS Development Team
+ * COPYRIGHT:(C) 1999-2014 by the GRASS Development Team
*
* This program is free software under the GNU General Public
* License (=v2). Read the file COPYING that comes with GRASS
@@ -27,7 +27,7 @@
static int any = 0;
-static void make_list(const struct list *,
+static void make_list(FILE *, const struct list *,
const char *, const char *,
int, int, int, int);
@@ -41,6 +41,7 @@
struct Option *exclude;
struct Option *separator;
struct Option *mapset;
+struct Option *output;
} opt;
struct
{
@@ -53,6 +54,7 @@
} flag;
int i, n, all, num_types, nlist;
void *filter = NULL, *exclude = NULL;
+FILE *fd;
const char *mapset;
char separator[2];
@@ -96,6 +98,9 @@
opt.separator = G_define_standard_option(G_OPT_F_SEP);
opt.separator-answer = newline;
+opt.output = G_define_standard_option(G_OPT_F_OUTPUT);
+opt.output-required = NO;
+
flag.regex = G_define_flag();
flag.regex-key = 'r';
flag.regex-description =
@@ -134,6 +139,13 @@
if (flag.regex-answer flag.extended-answer)
G_fatal_error(_(-r and -e are mutually exclusive));
+if (!opt.output-answer || strcmp(opt.output-answer, -) == 0) {
+fd = stdout;
+}
+else {
+fd = fopen(opt.output-answer, w);
+}
+
if (opt.pattern-answer) {
if (flag.regex-answer || flag.extended-answer)
filter = G_ls_regex_filter(opt.pattern-answer, 0, (int)
flag.extended-answer);
@@ -181,6 +193,9 @@
num_types = i;
}
+if (fd != stdout)
+G_set_verbose(0);
+
for (i = 0; i num_types; i++) {
n = all ? i : M_get_element(opt.type-answers[i]);
@@ -198,14 +213,17 @@
}
}
else
- make_list(M_get_list(n), mapset, separator,
+ make_list(fd, M_get_list(n), mapset, separator,
flag.pretty-answer, flag.type-answer,
flag.mapset-answer, mapset *mapset);
}
if (!flag.pretty-answer any)
- fprintf(stdout, \n);
+ fprintf(fd, \n);
+if (fd != stdout)
+ fclose(fd);
+
if (filter)
G_free_ls_filter(filter);
@@ -215,10 +233,10 @@
exit(EXIT_SUCCESS);
}
-static void make_list(
-const struct list *elem,
-const char *mapset, const char *separator,
-int pretty, int add_type, int add_mapset, int single_mapset)
+static void make_list(FILE *fd,
+ const struct list *elem,
+ const char *mapset, const char *separator,
+ int pretty, int add_type, int add_mapset, int
single_mapset)
{
char path[GPATH_MAX];
const char *element = elem-element[0];
@@ -235,7 +253,7 @@
if (!mapset || !*mapset) {
int n;
for (n = 0; mapset = G__mapset_name(n), mapset; n++)
- make_list(elem, mapset, separator,
+ make_list(fd, elem, mapset, separator,
pretty, add_type, add_mapset, n == 0);
return;
}
@@ -251,9 +269,9 @@
if (count 0) {
if (any) {
if (pretty)
- fprintf(stdout, \n);
+ fprintf(fd, \n);
else
- fprintf(stdout, %s, separator);
+ fprintf(fd, %s, separator);
}
G_message(_(%s available in mapset %s:),
elem-text, mapset);
@@ -267,12 +285,12 @@
int need_mapset = 0;
if (any i != 0)
- fprintf(stdout, %s, separator);
+ fprintf(fd, %s, separator);
if (add_type)
- fprintf(stdout, %s/, alias);
+ fprintf(fd, %s/, alias);
- fprintf(stdout, %s, name);
+ fprintf(fd, %s, name);
if (!add_mapset !single_mapset) {
const char *mapset2 = G_find_file2(element, name, );
@@ -280,7 +298,7 @@
need_mapset = strcmp(mapset, mapset2) != 0;
}
if (add_mapset || need_mapset)
- fprintf(stdout, @%s, mapset);
+ fprintf(fd, @%s, mapset);
G_free(name);
@@ -288,8 +306,9 @@
}
[GRASS-dev] [GRASS GIS] #2313: display commands: add copy button to GUI
#2313: display commands: add copy button to GUI -+-- Reporter: mlennert | Owner: grass-dev@… Type: enhancement | Status: new Priority: normal | Milestone: 7.0.0 Component: wxGUI| Version: svn-trunk Keywords: |Platform: Unspecified Cpu: Unspecified | -+-- I have a vague notion that this has been discussed before, but cannot find the discussion, so noting it here: All GRASS command GUI windows in the wxgui have a Copy button allowing to copy the command line created by the GUI. The display commands do not have such a button. Why is this so ? I think a Copy button would also be helpful in the display command GUI windows. Moritz -- Ticket URL: https://trac.osgeo.org/grass/ticket/2313 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] g.mlist: output (to ASCII file) parameter wish
On Mon, May 26, 2014 at 5:33 AM, Markus Neteler nete...@osgeo.org wrote: g.mlist rast pattern=precip*1951_1980_monthly_sums* output=maplist.txt r.series file=maplist.txt output=precip_0_25deg.1951.1980.sum method=sum Makes sense? It is a very good idea. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2243: wxGUI: raster importer single file GdalImportDialog crash after import
#2243: wxGUI: raster importer single file GdalImportDialog crash after import --+- Reporter: neteler | Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: 7.0.0 Component: wxGUI| Version: svn-releasebranch70 Resolution: fixed|Keywords: Platform: Unspecified | Cpu: Unspecified --+- Comment(by annakrat): Replying to [comment:4 neteler]: Replying to [comment:3 annakrat]: Please try r59571. Thanks, it works now. Closing. Backported in r60492. -- Ticket URL: http://trac.osgeo.org/grass/ticket/2243#comment:5 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2313: display commands: add copy button to GUI
#2313: display commands: add copy button to GUI ---+ Reporter: mlennert | Owner: grass-dev@… Type: enhancement| Status: new Priority: normal | Milestone: 7.0.0 Component: wxGUI | Version: svn-trunk Keywords: display, d.* commands |Platform: Unspecified Cpu: Unspecified| ---+ Changes (by wenzeslaus): * keywords: = display, d.* commands Comment: I agree. I think the idea behind ''not'' having the Copy button there is that you are not expected to use `d.*` commands in GUI and that novice users might be confused by seeing command behind adding of the layer. However, `d.*` commands works in GUI (at least the ones available from GUI), i.e. are usable in GUI command line, so Copy could be quite advantageous for advanced users and also for saving (and sharing) commands and perhaps even writing scripts. -- Ticket URL: https://trac.osgeo.org/grass/ticket/2313#comment:1 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] g.mlist: output (to ASCII file) parameter wish
What about the standard output redirection ()? g.mlist ... file.txt.. Hmm... We can overwrite existing files.. -p and -f flags redirect outputs to a pager, so it won't make sense for them to output to a file. Why don't we make output=file and -p/-f mutually exclusive? See the attached patch. On Mon, May 26, 2014 at 9:53 AM, Vaclav Petras wenzesl...@gmail.com wrote: On Mon, May 26, 2014 at 5:33 AM, Markus Neteler nete...@osgeo.org wrote: g.mlist rast pattern=precip*1951_1980_monthly_sums* output=maplist.txt r.series file=maplist.txt output=precip_0_25deg.1951.1980.sum method=sum Makes sense? It is a very good idea. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev main.c.patch Description: Binary data ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] g.mlist: output (to ASCII file) parameter wish
On Mon, May 26, 2014 at 10:39 AM, Huidae Cho gras...@gmail.com wrote: What about the standard output redirection ()? g.mlist ... file.txt.. Hmm... We can overwrite existing files.. This does not work from GUI and in terminal, it requires additional knowledge. I'm not sure how if this works on MS Windows but even some Linux now don't know this. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] g.mlist: output (to ASCII file) parameter wish
On Mon, May 26, 2014 at 5:27 PM, Vaclav Petras wenzesl...@gmail.com wrote: On Mon, May 26, 2014 at 10:39 AM, Huidae Cho gras...@gmail.com wrote: What about the standard output redirection ()? g.mlist ... file.txt.. Hmm... We can overwrite existing files.. This does not work from GUI and in terminal, it requires additional knowledge. I'm not sure how if this works on MS Windows It doesn't, we tried. Perhaps under some conditions but not known to me. but even some Linux now don't know this. The younger people perhaps not :-) So it would be great and clear (and perhaps even natural given the nature of a list generator) to have such an output. Best Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] g.mlist: output (to ASCII file) parameter wish
Makes sense. If no objections, I'll apply the two patches in this discussion. BTW, does r.series take input from stdin? In terminal, g.mlist ¦ r.series would be great. On May 26, 2014 5:44 PM, Markus Neteler nete...@osgeo.org wrote: On Mon, May 26, 2014 at 5:27 PM, Vaclav Petras wenzesl...@gmail.com wrote: On Mon, May 26, 2014 at 10:39 AM, Huidae Cho gras...@gmail.com wrote: What about the standard output redirection ()? g.mlist ... file.txt.. Hmm... We can overwrite existing files.. This does not work from GUI and in terminal, it requires additional knowledge. I'm not sure how if this works on MS Windows It doesn't, we tried. Perhaps under some conditions but not known to me. but even some Linux now don't know this. The younger people perhaps not :-) So it would be great and clear (and perhaps even natural given the nature of a list generator) to have such an output. Best Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] g.mlist: output (to ASCII file) parameter wish
Huidae Cho wrote: BTW, does r.series take input from stdin? In terminal, g.mlist ¦ r.series would be great. It doesn't understand file=- as referring to stdin (although that would be a simple change), but on Unix you can typically use e.g. g.mlist | r.series file=/dev/stdin. -- Glynn Clements gl...@gclements.plus.com ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] problems building grass7_trunk on debian wheezy
Hi, trying to upgrade my grass7 installation i got errors for the following modules : v.kernel, v.net.path, v.to.db, m.measure Attached as gist the full build log for each module : https://gist.github.com/anonymous/cc53f782312fb347ee26 for both v.to.db and m.measure the erros seems to be related to an undefined “G_units_to_meters_*” while v.kernel, v.net.path are pointing to problems in vect.h have you any clue ? Thanks for help. Massimo. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] problems building grass7_trunk on debian wheezy
On Mon, May 26, 2014 at 7:46 PM, epi massimodisa...@gmail.com wrote: Hi, trying to upgrade my grass7 installation i got errors for the following modules : v.kernel, v.net.path, v.to.db, m.measure Attached as gist the full build log for each module : https://gist.github.com/anonymous/cc53f782312fb347ee26 for both v.to.db and m.measure the erros seems to be related to an undefined “G_units_to_meters_*” while v.kernel, v.net.path are pointing to problems in vect.h have you any clue ? Try to do make distclean. There were some changes in library. This usually requires distclean. Thanks for help. Massimo. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] problems building grass7_trunk on debian wheezy
i already did a make distclean then i posted the log On May 26, 2014, at 8:37 PM, Vaclav Petras wenzesl...@gmail.com wrote: On Mon, May 26, 2014 at 7:46 PM, epi massimodisa...@gmail.com wrote: Hi, trying to upgrade my grass7 installation i got errors for the following modules : v.kernel, v.net.path, v.to.db, m.measure Attached as gist the full build log for each module : https://gist.github.com/anonymous/cc53f782312fb347ee26 for both v.to.db and m.measure the erros seems to be related to an undefined “G_units_to_meters_*” while v.kernel, v.net.path are pointing to problems in vect.h have you any clue ? Try to do make distclean. There were some changes in library. This usually requires distclean. Thanks for help. Massimo. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] problems building grass7_trunk on debian wheezy
there was a problem with svn up” the trunk was not fully upgraded, because svn found the r.stream.* add ons inside the grass_trunk src directory their presence was generating an svn conflict and aborting the upgrade. I manually removed the add ons from trunk and did a complete svn up. Now the build goes ahead without errors. On May 26, 2014, at 8:41 PM, epi massimodisa...@gmail.com wrote: i already did a make distclean then i posted the log On May 26, 2014, at 8:37 PM, Vaclav Petras wenzesl...@gmail.com wrote: On Mon, May 26, 2014 at 7:46 PM, epi massimodisa...@gmail.com wrote: Hi, trying to upgrade my grass7 installation i got errors for the following modules : v.kernel, v.net.path, v.to.db, m.measure Attached as gist the full build log for each module : https://gist.github.com/anonymous/cc53f782312fb347ee26 for both v.to.db and m.measure the erros seems to be related to an undefined “G_units_to_meters_*” while v.kernel, v.net.path are pointing to problems in vect.h have you any clue ? Try to do make distclean. There were some changes in library. This usually requires distclean. Thanks for help. Massimo. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] g.mlist: output (to ASCII file) parameter wish
On Tue, May 27, 2014 at 12:57 AM, Glynn Clements gl...@gclements.plus.com wrote: Huidae Cho wrote: BTW, does r.series take input from stdin? In terminal, g.mlist ¦ r.series would be great. It doesn't understand file=- as referring to stdin (although that would be a simple change) For consistency with other commands that would be a good change in r.series. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
