GRASS GIS | 6 Feb 14:26 2016

Re: [GRASS GIS] #2559: g.gui.metadata not functioning

#2559: g.gui.metadata not functioning
--------------------------+------------------------------
  Reporter:  pvanbosgeo   |      Owner:  grass-dev <at> …
      Type:  defect       |     Status:  closed
  Priority:  normal       |  Milestone:  7.1.0
 Component:  wxGUI        |    Version:  svn-trunk
Resolution:  fixed        |   Keywords:  addons, metadata
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+------------------------------
Changes (by krejcmat):

 * status:  new => closed
 * resolution:   => fixed

Comment:

 Fixed during GSOC2016.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2559#comment:2>
GRASS GIS <https://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
grass-dev <at> lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
GRASS GIS | 6 Feb 11:59 2016

Re: [GRASS GIS] #770: Close wxGUI on GRASS CLI exit

#770: Close wxGUI on GRASS CLI exit
--------------------------+-----------------------
  Reporter:  marisn       |      Owner:  martinl
      Type:  enhancement  |     Status:  assigned
  Priority:  minor        |  Milestone:  7.0.4
 Component:  wxGUI        |    Version:  6.4.0 RCs
Resolution:               |   Keywords:  init
       CPU:  Unspecified  |   Platform:  Linux
--------------------------+-----------------------
Changes (by martinl):

 * cc: martinl (removed)
 * cc: grass-dev <at> … (added)
 * status:  new => assigned
 * owner:  grass-dev <at> … => martinl

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/770#comment:16>
GRASS GIS <https://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
grass-dev <at> lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
GRASS GIS | 6 Feb 11:58 2016

Re: [GRASS GIS] #770: Close wxGUI on GRASS CLI exit

#770: Close wxGUI on GRASS CLI exit
--------------------------+-------------------------
  Reporter:  marisn       |      Owner:  grass-dev <at> …
      Type:  enhancement  |     Status:  new
  Priority:  minor        |  Milestone:  7.0.4
 Component:  wxGUI        |    Version:  6.4.0 RCs
Resolution:               |   Keywords:  init
       CPU:  Unspecified  |   Platform:  Linux
--------------------------+-------------------------

Comment (by martinl):

 Replying to [comment:13 martinl]:

 > attempt to solve this issue applied in r67306

 backported to relbr70 in r67731. Please test.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/770#comment:15>
GRASS GIS <https://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
grass-dev <at> lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
GRASS GIS | 5 Feb 23:08 2016

[GRASS GIS] #2898: GUI improvments for long list of mapsets or long mapset names (Location / Mapset selection)

#2898: GUI improvments for long list of mapsets or long mapset names (Location /
Mapset selection)
-------------------------+-------------------------
 Reporter:  sbl          |      Owner:  grass-dev <at> …
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  7.0.4
Component:  wxGUI        |    Version:  unspecified
 Keywords:               |        CPU:  Unspecified
 Platform:  All          |
-------------------------+-------------------------
 In order to be able handle a long list of mapsets or long mapset names
 better in the GUI startup (location / mapset selection) two enhancements
 might be useful:

 1) For long lists of mapsets in shared GRASS GIS DBs it would be nice if
 one could filter the list of mapsets to "mapsets owned by me" (e.g. using
 a tickbox), as these are the only ones the user technically can use for
 working anyway...

 2) If one has long mapset names it would be an advantage if the user was
 able to change the distribution of horizontal space used for the "mapset
 box" and the "locations box", meaning, that the user can make the mapset
 box wider if the location contains mapsets with longer names...

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2898>
GRASS GIS <https://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
(Continue reading)

GRASS GIS | 5 Feb 21:42 2016

[GRASS GIS] #2897: copy a Map Display to create a new identical one

#2897: copy a Map Display to create a new identical one
-------------------------+-------------------------
 Reporter:  ychemin      |      Owner:  grass-dev <at> …
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  7.1.0
Component:  Default      |    Version:  unspecified
 Keywords:               |        CPU:  Unspecified
 Platform:  Unspecified  |
-------------------------+-------------------------
 When making investigations with Map Display, it is often easier to
 duplicate actual map display and modify only an additional layer or two.

 If it was possible to duplicate the actual Map Display to create a new
 identical one, this would fasten exploratory workflow.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2897>
GRASS GIS <https://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
grass-dev <at> lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Yann | 5 Feb 14:15 2016
Picon

copying a Map Display to a new one

Hi,

is it possible to copy a Map Display to create a new identical one?

Thanks,
Yann

--

-- 
-----
Yann Chemin
Address: 3 Toul Melin, 56400 Plumergat
Mobile: +33 (0)7 83 85 52 34

_______________________________________________
grass-dev mailing list
grass-dev <at> lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
GRASS GIS | 5 Feb 11:30 2016

[GRASS GIS] #2896: Allow installation of specific versions of GRASS addons

#2896: Allow installation of specific versions of GRASS addons
-------------------------+-------------------------
 Reporter:  pmav99       |      Owner:  grass-dev <at> …
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:
Component:  Addons       |    Version:  unspecified
 Keywords:               |        CPU:  Unspecified
 Platform:  Unspecified  |
-------------------------+-------------------------
 At the moment, `g.extension` only supports the installation of the latest
 revision of the svn repository. As a result, any non-backward compatible
 change in the GRASS-addons repo, means that existing code may break.

 Being able to install specific versions of GRASS addons would mitigate a
 potential source of bugs and would make debugging of addon related code
 easier.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2896>
GRASS GIS <https://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
grass-dev <at> lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
GRASS GIS | 5 Feb 09:55 2016

[GRASS GIS] #2895: Define dependencies for GRASS addons

#2895: Define dependencies for GRASS addons
-------------------------+-------------------------
 Reporter:  pmav99       |      Owner:  grass-dev <at> …
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:
Component:  Addons       |    Version:  unspecified
 Keywords:  g.extension  |        CPU:  Unspecified
 Platform:  Unspecified  |
-------------------------+-------------------------
 Some addons depend on other addons. E.g. `r.lfp` depends on
 `r.stream.distance`.

 If you install `r.lfp` and you try to use it while `r.stream.distance` is
 not installed, you get the following traceback which is not particularly
 helpful; especially so if you are not familiar with Python.
 {{{
 Traceback (most recent call last):
   File "/home/grassuser/.grass7/addons/scripts/r.lfp", line 111, in
 <module>
     sys.exit(main())
   File "/home/grassuser/.grass7/addons/scripts/r.lfp", line 43, in main
     calculate_lfp(input, output, coords)
   File "/home/grassuser/.grass7/addons/scripts/r.lfp", line 67, in
 calculate_lfp
     distance=flds)
   File "/usr/lib/grass70/etc/python/grass/script/core.py", line 392, in
 run_command
     ps = start_command(*args, **kwargs)
   File "/usr/lib/grass70/etc/python/grass/script/core.py", line 361, in
 start_command
(Continue reading)

GRASS GIS | 5 Feb 08:38 2016

[GRASS GIS] #2894: wxGUI Histogramming Tool: small (cosmetic changes) in the gui of the plot statistics frame

#2894: wxGUI Histogramming Tool: small (cosmetic changes) in the gui of the plot
statistics frame
-------------------------------------------------+-------------------------
 Reporter:  tmsz                                 |      Owner:  grass-dev <at> …
     Type:  enhancement                          |     Status:  new
 Priority:  trivial                              |  Milestone:  7.0.4
Component:  wxGUI                                |    Version:  7.0.2
 Keywords:  wxGUI Histogramming tool, plot       |        CPU:  x86-64
  statistics frame                               |
 Platform:  MSWindows 7                          |
-------------------------------------------------+-------------------------
 I made some changes (small cosmetic improvements) in the source code of
 wxgGUI Histogramming Tool, specifically in the plot statistics frame
 (/gui/wxpython/wxplot/dialogs.py file, class PlotStatsFrame().[[BR]]

 * adding „background“ panel and frame icon

 Attached comparing picture with default and adjusted frame + patch file.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2894>
GRASS GIS <https://grass.osgeo.org>

_______________________________________________
grass-dev mailing list
grass-dev <at> lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Panagiotis Mavrogiorgos | 4 Feb 22:28 2016
Picon

GRASS addons dependencies

Hi everybody, 

Some addons depend on other addons. E.g. r.lfp depends on r.stream.distance.

If you try to use it while r.stream.distance is not installed, you get the following traceback which is not particularly helpful; especially so if you are not familiar with Python.

Traceback (most recent call last):
  File "/home/grassuser/.grass7/addons/scripts/r.lfp", line 111, in <module>
    sys.exit(main())
  File "/home/grassuser/.grass7/addons/scripts/r.lfp", line 43, in main
    calculate_lfp(input, output, coords)
  File "/home/grassuser/.grass7/addons/scripts/r.lfp", line 67, in calculate_lfp
    distance=flds)
  File "/usr/lib/grass70/etc/python/grass/script/core.py", line 392, in run_command
    ps = start_command(*args, **kwargs)
  File "/usr/lib/grass70/etc/python/grass/script/core.py", line 361, in start_command
    return Popen(args, **popts)
  File "/usr/lib/grass70/etc/python/grass/script/core.py", line 64, in __init__
    subprocess.Popen.__init__(self, args, **kwargs)
  File "/usr/lib/python2.7/subprocess.py", line 710, in __init__
    errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1335, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory

So my question is whether there is a way to define addon dependencies, and if there is not, what would be a sensible way to support something like this.

best regards,
Panos
_______________________________________________
grass-dev mailing list
grass-dev <at> lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Vaclav Petras | 3 Feb 20:51 2016
Picon
Gravatar

v.kriging: enable BLAS and LAPACK for Windows

Hi,

is it possible to enable BLAS and LAPACK for MS Windows build so that v.kriging and some other imagery modules compile as addons for Windows?

The compilation log says:

main.c:25:2: error: #error GRASS GIS is not configured with BLAS
 #error GRASS GIS is not configured with BLAS
main.c:29:2: error: #error GRASS GIS is not configured with LAPACK
 #error GRASS GIS is not configured with LAPACK

I don't see BALS and LAPACK in OSGeo4W but there is a Windows version [1].

Thanks,
Vaclav
_______________________________________________
grass-dev mailing list
grass-dev <at> lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Gmane