[GRASS-dev] Re: [GRASS GIS] #763: r.statistics method=distribution: no percentages for negative basemap values

[GRASS GIS]

#763: r.statistics method=distribution: no percentages for negative basemap
values
--+-
 Reporter:  peifer|   Owner:  grass-...@…  
 Type:  defect|  Status:  new  
 Priority:  normal|   Milestone:  6.4.0
Component:  Raster| Version:  6.4.0 RCs
 Keywords:  r.statistics  |Platform:  Unspecified  
  Cpu:  x86-32|  
--+-

Comment(by peifer):

 Replying to [comment:4 glynn]:
 > ...but some code still follows the old zero-is-null convention.
 >
 [[BR]]
 This is what I observed, from a simple end-user perspective. But actually,
 I didn't want to believe it and I never dared to create a ticket whenever
 I came across such an observation.

 As stated: my current practice is to reclassify my maps so that all
 legitimate 0's (and negative values) are replaced by some more or less
 meaningful positive integer. Can you confirm that this continues to make
 sense, if one wants to be on the safe side?

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [Qgis-developer] new GRASS 6.4 modules

[Paolo Cavallini]

Il 10/09/2010 20:02, MORREALE Jean Roc ha scritto:

> Paolo, if it is not of a too high level, could it be possible to write a
> wiki page explaining how to wrote and update the grass modules in qgis ?
> I would like to help on this point but I don't know how.

Simple:
http://www.qgis.org/wiki/Adding_New_Tools_to_the_GRASS_Toolbox
See also:
http://www.qgis.org/wiki/Adding_New_Tools_to_the_GRASS_Toolbox#Modules_which_can_be_added
and following.
(and yes, Markus, this replies to your other suggestion too; see and below).
All the best.
-- 
Paolo Cavallini: http://www.faunalia.it/pc
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #991: v.out.gpsbabel export fails with layer=2

[GRASS GIS]

#991: v.out.gpsbabel export fails with layer=2
---+
  Reporter:  needelsd  |   Owner:  hamish
  Type:  defect|  Status:  reopened  
  Priority:  normal|   Milestone:  6.4.1 
 Component:  Vector| Version:  6.4.0 RCs 
Resolution:|Keywords:  GPS GPX export, v.out.gpsbabel, m.proj
  Platform:  MacOSX| Cpu:  Unspecified   
---+
Changes (by hamish):

  * status:  closed => reopened
  * resolution:  fixed =>
  * milestone:  6.4.0 => 6.4.1


Comment:

 is the change to the first sed expression just a simplification, or does
 it contribute to the bug?

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS-user] wx.class

[Mohammed Rashad]

Fixed for grass6.4.0RC6
please update svn
http://svn.osgeo.org/grass/grass-addons/gui/wxpython/wx.class/wx.class.py
and download wx.class again
and try it

If any problem persists Please feel free to mail me.

On Fri, Sep 10, 2010 at 10:44 AM, Mohammed Rashad <
mohammedrasha...@gmail.com> wrote:

> Fixed for grass6.4.0RC6
> please update svn
> http://svn.osgeo.org/grass/grass-addons/gui/wxpython/wx.class/wx.class.py
> and download wx.class again
> and try it
>
> If any problem persists Please feel free to mail me. I have no disturbances
> and happy to help you.
> I tested the wx.class on Ubunbtu 10.04 LTS and grass6.4.9RC6
>
> ThankYou
>
>
> On Thu, Sep 9, 2010 at 9:40 PM, Leonardo Hardtke wrote:
>
>>  Hi,
>> Ok, it was my fault. I was runing it with ./wx.class instead of python
>> wx.class
>> but now...
>>
>> (nc_spm_08):~ > python wx.class.py
>> Traceback (most recent call last):
>>   File "wx.class.py", line 60, in 
>> from mapdisp_window import BufferedWindow
>> ImportError: No module named mapdisp_window
>>
>> Am I missing something again?
>> I'm running an Ubuntu 10.04 with grass 6.4.rc6
>>
>> Bests,
>> Leonardo
>>
>>
>>
>>
>> On 09/09/2010 12:42 AM, Mohammed Rashad wrote:
>>
>> Leonardo Hardtk,
>> Plesase see the README.txt included with wx.class
>>
>> http://trac.osgeo.org/grass/browser/grass-addons/gui/wxpython/wx.class/README.txt
>>
>> On Thu, Sep 9, 2010 at 3:48 AM, Leonardo Hardtke wrote:
>>
>>> Hi,
>>> I tried to use it, but
>>>
>>> GRASS 6.4.0RC6 (Spearfish):~ > ./wx.class.py
>>> ./wx.class.py: line 19: !
>>> @package wx.class.py
>>>
>>> @brief Interface implementation of i.class module without Xterm.
>>> Many thanks to Markus Neteler for his help which allowed me to
>>> know about i.class and its usage.
>>> Classes:
>>> - IClass
>>> - BufferedWindow2
>>> - IClassApp
>>>
>>>
>>> (C) 2006-2010 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
>>> for details.
>>>
>>> @author Mohammed Rashad K.M 
>>> : command not found
>>> import: unable to grab mouse `': Resource temporarily unavailable @
>>> xwindow.c/XSelectWindow/8993.
>>> import: unable to grab mouse `': Resource temporarily unavailable @
>>> xwindow.c/XSelectWindow/8993.
>>> import: unable to grab mouse `': Resource temporarily unavailable @
>>> xwindow.c/XSelectWindow/8993.
>>> import: unable to grab mouse `': Resource temporarily unavailable @
>>> xwindow.c/XSelectWindow/8993.
>>> ./wx.class.py: line 28: syntax error near unexpected token `('
>>> ./wx.class.py: line 28: `gbase = os.getenv("GISBASE") '
>>>
>>> any idea?
>>> Leonardo A. Hardtke
>>>
>>>
>>> On 09/08/2010 06:34 PM, Mohammed Rashad wrote:
>>>
>>>
>>> Hi all,
>>>
>>>   I had just created a wx version of i.class module which generates
>>> spectral signatures for an image by allowing the user to outline regions of
>>> interest. The resulting signature file can be used as input for i.maxlik or
>>> as a seed signature file for i.cluster.
>>>
>>>  Actual i.class module requires Xterm and work only in systems having
>>> Xserver installed. I created python version of i.class which works on all
>>> platform. Now windows users can use i.class module.
>>>
>>>  Currently development is in beta stage. wx.class is tested and works
>>> only for NC dataset available from grassbook.org site.
>>> It uses wxpython paintDC to draw histograms which must be changed to use
>>> python-matplotlib for drawing smooth histograms as the output needed to be.
>>>
>>>  I dont want to add a new dependency to grass as other developers but I
>>> am forced to do :(
>>>
>>>  current wx.class doesn't need any other dependencies. The needs some
>>> cleanup but as I am busy with some other works related to GRASS I don't have
>>> much time to spend on cleaning up the code. But within a month or to you can
>>> have the fully functional wx.class.
>>>
>>>  Now I am hosting to GRASS-Addons repo because the code needs
>>> testing...(although needs some cleanup)
>>>
>>>  A README is included with source which shows how to use the module. But
>>> wx.class is made to be user-friendly.
>>>
>>>
>>>  Any comments or suggestions are really welcomed :)
>>>
>>>
>>>  --
>>> Rashad
>>>
>>>
>>> ___
>>> grass-user mailing 
>>> listgrass-u...@lists.osgeo.orghttp://lists.osgeo.org/mailman/listinfo/grass-user
>>>
>>>
>>>
>>> ___
>>> grass-user mailing list
>>> grass-u...@lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/grass-user
>>>
>>>
>>
>>
>> --
>> Rashad
>>
>>
>>
>
>
> --
> Rashad
>



-- 
Rashad
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #763: r.statistics method=distribution: no percentages for negative basemap values

[GRASS GIS]

#763: r.statistics method=distribution: no percentages for negative basemap
values
--+-
 Reporter:  peifer|   Owner:  grass-...@…  
 Type:  defect|  Status:  new  
 Priority:  normal|   Milestone:  6.4.0
Component:  Raster| Version:  6.4.0 RCs
 Keywords:  r.statistics  |Platform:  Unspecified  
  Cpu:  x86-32|  
--+-
Changes (by hamish):

  * keywords:  => r.statistics


Comment:

 Replying to [comment:4 glynn]:
 > Prior to 5.x, category zero was often used as a no-data value.
 > 5.x added support for a distinguished null value (as well as
 > floating-point), but some code still follows the old zero-is-null
 > convention.
 ...
 > Given the large number of occurrences of G_get_map_row[_nomask]()
 > in 6.4, I can't help wondering whether all of the modules which
 > were converted to use Rast_get_c_row() in 7.0 were actually
 > converted correctly, or whether the function call was changed
 > without any effort made to handle nulls.

 as a test point, r.surf.contour in 6.4 still treats 0 as NULL (and is not
 FP-aware), so if there are problems in the transition, they'll probably
 show up there.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #763: r.statistics method=distribution: no percentages for negative basemap values

[GRASS GIS]

#763: r.statistics method=distribution: no percentages for negative basemap
values
+---
 Reporter:  peifer  |   Owner:  grass-...@…  
 Type:  defect  |  Status:  new  
 Priority:  normal  |   Milestone:  6.4.0
Component:  Raster  | Version:  6.4.0 RCs
 Keywords:  |Platform:  Unspecified  
  Cpu:  x86-32  |  
+---

Comment(by glynn):

 Replying to [comment:3 peifer]:

 > Why should cat=0 cause problems for r.stats or r.statistics? It is a
 legal value, by the end of the day.

 Prior to 5.x, category zero was often used as a no-data value. 5.x added
 support for a distinguished null value (as well as floating-point), but
 some code still follows the old zero-is-null convention. In particular:

  * If a raster map doesn't have a null bitmap, any zeros are converted to
 nulls upon read.

  * The functions G_get_map_row() and G_get_map_row_nomask() convert any
 nulls to zeros upon read, so any module which uses these functions cannot
 distinguish between zero and null.

 Given the large number of occurrences of G_get_map_row[_nomask]() in 6.4,
 I can't help wondering whether all of the modules which were converted to
 use Rast_get_c_row() in 7.0 were actually converted correctly, or whether
 the function call was changed without any effort made to handle nulls.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] new GRASS 6.4 modules

[Markus Neteler]

On Fri, Sep 10, 2010 at 10:09 AM, Paolo Cavallini  wrote:
> Hi all.
> In the occasion of the release of GRASS 6.4, I think it would be good to 
> revise the
> current QGIS-GRASS modules. Specifically:
> - there are modules that IMHO are of no use, and potentially confusing (e.g. 
> several
> of those who manage projections, etc.)
> - there are new and useful modules to add to the toolbox
> - not all modules have been thoroughly tested.
> I encourage therefore GRASS users to help us defining both a wishlist for 
> modules to
> be included ad a deprecated list, and to let us know if there are 
> non-functional
> modules, so they can be fixed.

Paolo - agreed, an important issue. Please suggest a
wiki page where we can collect responses.

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #991: v.out.gpsbabel export fails with layer=2

[GRASS GIS]

#991: v.out.gpsbabel export fails with layer=2
---+
  Reporter:  needelsd  |   Owner:  hamish
  Type:  defect|  Status:  closed
  Priority:  normal|   Milestone:  6.4.0 
 Component:  Vector| Version:  6.4.0 RCs 
Resolution:  fixed |Keywords:  GPS GPX export, v.out.gpsbabel, m.proj
  Platform:  MacOSX| Cpu:  Unspecified   
---+
Changes (by donxfive):

 * cc: donxfive (added)


Comment:

 I still get "Error reading categories" with vectors that have layers other
 than 1.

 I'm using GRASS version 6.4.0svn on my Ubuntu laptop (w/ GNU sed version
 4.1.5), and I fixed the problem by replacing

 {{{
 sed -e 's/^\([PLBCFKA]\)/#\1/' -e 's/^ 1 /# 1  /'
 }}}
 with

 {{{
 sed -r -e 's/^[PLBCFKA]/#&/' -e 's/^ [1-9]+  /#&/'
 }}}
 on line 253 of the
 
[http://svn.osgeo.org/grass/grass/branches/releasebranch_6_4/scripts/v.out.gpsbabel/v.out.gpsbabel
 v.out.gpsbabel script]. (The problem sed command is also used in
 v.out.gpsbabel for 6.5-svn, and in v.out.gps for 7.0-svn.)

 I've had no problems since I did this, but I'm not sure if it would work
 for everyone.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #1150: Cannot open vector for editing in digitize toolbar in GRASS 7.0

[GRASS GIS]

#1150: Cannot open vector for editing in digitize toolbar in GRASS 7.0
--+-
 Reporter:  PvB   |   Owner:  martinl
 Type:  defect|  Status:  new
 Priority:  normal|   Milestone:  6.5.0  
Component:  wxGUI | Version:  unspecified
 Keywords:  wxVdigit  |Platform:  Linux  
  Cpu:  x86-64|  
--+-

Comment(by PvB):

 Ah, ok, thanks. I am most concerned with getting it to work in GRASS 7
 though. Just out of curiosity I tried your suggestion, but for grass 7.
 The only output that it gives me is

 "make: Nothing to be done for `first'".

 This seems to be the same or similar as what was reported here: http
 ://osgeo-org.1803224.n2.nabble.com/No-module-named-grass7-wxvdigit-
 td3102096.html.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #1150: Cannot open vector for editing in digitize toolbar in GRASS 7.0

[GRASS GIS]

#1150: Cannot open vector for editing in digitize toolbar in GRASS 7.0
--+-
 Reporter:  PvB   |   Owner:  martinl
 Type:  defect|  Status:  new
 Priority:  normal|   Milestone:  6.5.0  
Component:  wxGUI | Version:  unspecified
 Keywords:  wxVdigit  |Platform:  Linux  
  Cpu:  x86-64|  
--+-

Comment(by martinl):

 Replying to [comment:4 PvB]:
 > OK, so this also is true for GRASS 7.0? I see that in 6.4 the whole
 module is removed, but in GRASS 7.0 the module is there (well, one can
 open the menu bar).

 not removed, just disabled in GRASS 6.4. You can compile it manually

 {{{
 cd gui/wxpython/vdigit
 make
 }}}

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #1150: Cannot open vector for editing in digitize toolbar in GRASS 7.0

[GRASS GIS]

#1150: Cannot open vector for editing in digitize toolbar in GRASS 7.0
--+-
 Reporter:  PvB   |   Owner:  martinl
 Type:  defect|  Status:  new
 Priority:  normal|   Milestone:  6.5.0  
Component:  wxGUI | Version:  unspecified
 Keywords:  wxVdigit  |Platform:  Linux  
  Cpu:  x86-64|  
--+-

Comment(by PvB):

 OK, so this also is true for GRASS 7.0? I see that in 6.4 the whole module
 is removed, but in GRASS 7.0 the module is there (well, one can open the
 menu bar).

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] new GRASS 6.4 modules

[Paolo Cavallini]

Hi all.
In the occasion of the release of GRASS 6.4, I think it would be good to revise 
the
current QGIS-GRASS modules. Specifically:
- there are modules that IMHO are of no use, and potentially confusing (e.g. 
several
of those who manage projections, etc.)
- there are new and useful modules to add to the toolbox
- not all modules have been thoroughly tested.
I encourage therefore GRASS users to help us defining both a wishlist for 
modules to
be included ad a deprecated list, and to let us know if there are non-functional
modules, so they can be fixed.
Thanks.
-- 
Paolo Cavallini: http://www.faunalia.it/pc
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev