gmane.comp.gis.grass.devel

stop button in GUI?

Michael Barton — 2012-05-24T08:04:13

There is a "stop" button in the GUI of all modules. When I press it, the GUI dialog returns to a state where I can reinitiate the module process. But looking in my system monitor, the old process is still continuing. Is this the case for all systems or just the Mac? If for all systems, the "stop" button seems somewhat misleading.

Michael

_____________________
C. Michael Barton
Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research &
University Consortium for Atmospheric Research
303-497-2889 (voice)

Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu<http://csdc.asu.edu/>





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

Re: broken stuff in vector modules

Michael Barton — 2012-05-23T14:55:54

Further efforts show that the distance upload is giving the correct value. I had the wrong flag checked (not as clear as it might be in the GUI). The other issues remain. But at least I CAN get useful analysis results.

Michael



On May 23, 2012, at 4:49 PM, <grass-dev-request< at >lists.osgeo.org>
 wrote:


_____________________
C. Michael Barton
Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research &
University Consortium for Atmospheric Research
303-497-2889 (voice)

Director, Center for Social Dynamics & Complexity 
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu





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

[GRASS GIS] #1661: Wish: port the new wxgui histogram plotting tool from grass7 to grass6

GRASS GIS — 2012-05-23T14:56:18

#1661: Wish: port the new wxgui histogram plotting tool from grass7 to grass6
-------------------------+--------------------------------------------------
 Reporter:  mlennert     |       Owner:  grass-dev< at >…              
     Type:  enhancement  |      Status:  new                      
 Priority:  normal       |   Milestone:  6.4.3                    
Component:  wxGUI        |     Version:  unspecified              
 Keywords:  histogram    |    Platform:  Unspecified              
      Cpu:  Unspecified  |  
-------------------------+--------------------------------------------------
 Michael's wxgui histogram tool in trunk is _very_ nice and useful. Any
 chance that this could be backported to the grass6 line ?

 Moritz

v.distance values bogus in GRASS 6.4.2 also

Michael Barton — 2012-05-23T14:48:37

So the values for point to line distances are just as bad in GRASS 6.4.2 as they are in GRASS 7. Any suggestions on how to get this information for a latlon region?

Michael 
_____________________
C. Michael Barton
Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research &
University Consortium for Atmospheric Research
303-497-2889 (voice)

Director, Center for Social Dynamics & Complexity 
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu





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

another bug in v.distance

Michael Barton — 2012-05-23T14:47:08

Forgot to mention that the table selection pull-downs do not work in any version of the v.distance GUI--from 6.4.2 to 7.0

Michael
_____________________
C. Michael Barton
Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research &
University Consortium for Atmospheric Research
303-497-2889 (voice)

Director, Center for Social Dynamics & Complexity 
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu





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

broken stuff in vector modules

Michael Barton — 2012-05-23T14:43:11

Hi,

I don't use the vector modules a lot and so they don't get a lot of testing from me. I'm trying to do a project with someone that uses vector module and I find that some key things are broken. The following apply to GRASS 7 and GRASS 6.4.3.

1) v.distance gives bogus results for point to line distance uploads in a latlon region. For example, the distance uploaded from one site point to the nearest waterway is 5767967.05475, yet measuring this with the distance tool gives a much more reasonable 33211 m. The uploaded distance is off by an order of 173X -- an enormous error. Nothing in the docs says that you cannot use v.distance with latlon regions.

2) To get around this, I thought I'd try to get the length of the line that connects each site point with its nearest waterway (a v.distance option). But when I tried to make a new table for this in the table manager, I find that I cannot access the "table description" section of the "manage layers" page in the attribute table manager. This is again because wx.StaticBox needs to be defined in a particular order or the Mac interface cannot access it. This has been a recurrent problem with wx.StaticBox. The StaticBox must be instantiated before any of its contents.

3) After creating a linked table using v.db.addtable instead of the attribute manager, I tried to modify the layer in the attribute table manager, but only received a message that "<flag> is not a valid value". Another bug.

I did manage to get a length value into the lines connecting the points and they are quite reasonable values. But of course I have no way that I can see to link the distance lines back to the points from which they were created with v.distance. So I still don't have analysis results and my colleague is ready to try this in ArcGIS.

Any suggestion for a workaround would be much appreciated. And of course, the multiple bugs here need to be fixed.

Michael

_____________________
C. Michael Barton
Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research &
University Consortium for Atmospheric Research
303-497-2889 (voice)

Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu

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

Re: GRASS GIS Community Sprint, May 23-28,2012 in Prague, CZ

Markus Neteler — 2012-05-22T13:03:35

The GRASS GIS Community Sprint 2012 in Prague is approaching
quickly. A draft agenda is now available at:

http://grass.osgeo.org/wiki/Talk:GRASS_Community_Sprint_Prague_2012

See you there, either in person or via chat!

On Sat, Mar 31, 2012 at 12:04 PM, Markus Neteler <neteler< at >osgeo.org> wrote:

Summer of Code is upon us

Hamish — 2012-05-22T11:27:58

Hi,

as Anne noted in her Hello World message*, the Summer of Code has just
begun.  [*] http://lists.osgeo.org/pipermail/soc/2012-May/001734.html


In case you missed the selection efforts, GRASS was funded for 3 projects
this year.


They are:

(see the wiki for detailed links)
   http://grass.osgeo.org/wiki/GRASS_SoC_Ideas_2012#Accepted_Ideas


   1.  Python high level map interaction for GRASS GIS (abstract)

          Student: Pietro Zambelli 
          Mentor: Sören Gebbert 
          Backup mentors: Luca Delucchi, Martin Landa 
          Wiki page: GRASS SoC Ideas 2012/High level map interaction 

H:--- pythonize the grass py libs; the wiki page demonstrates the idea well


   2. GRASS GIS WxGui front end for vector analysis modules (abstract)

          Student: Stepan Turek 
          Mentor: Martin Landa 
          Backup mentor: Markus Metz 
          Wiki page: GRASS GSoC 2012 WxGUI front end for vector analysis modules 

H:--- interactive v.net gui app (d.path^2, dynamically redraw network paths+)


   3. Image Segmentation in GRASS GIS (abstract)

          Student: Eric Momsen 
          Mentor: Markus Metz 
          Backup mentors: Moritz Lennert, Pierre Roudier 
          Wiki page: GRASS GSoC 2012 Image Segmentation 

H:--- advanced image classification & clumping techniques


Please (everyone!) read through the abstracts & proposals and get a
feeling for what's been planned for the next few months. The students
will be posting weekly updates here to keep you informed, but all 3
projects are all ambitious, and all will need all of our help to succeed!
This is not a "consume" exercise, the student does the coding but it's
supposed to be a collaborative process with all of us helping out. The
more we put in to the students, the more we get out of them. do I make
my point? :)


I hope that those meeting for the upcoming Code Sprint can take some time
to go through each of the proposals in a detailed way, and take the
opportunity to discuss the path the student should take/brainstorm as a
group. (No point in them spending all summer working on a project which
has no developer buy-in at the end because we devs communicated poorly
our wants ..)  I'll try to be available via IRC as the GMT+12 timezone &
work allows.


So Stepan, Pietro, and Eric, a big welcome! I hope you have fun here.
There are some really talented coders on this list who know the codebase
top to bottom and can help you out night or day. Any questions just
drop an email or five.


cheers,
Hamish
(OSGeo SoC co-admin)

Re: PIxel-wise regression contribution

Hamish — 2012-05-22T10:45:12

Damien wrote:


let's race 'em!



it's only 8 months old :)


Hamish

Re: PIxel-wise regression contribution

Damien O'Grady — 2012-05-22T10:22:34

Yes, you are quite right, and r.regression.series is far more elegant.
I wish I'd seen it three years ago, when I really needed it!

Thanks

Damien

On Tue, 2012-05-22 at 12:04 +0200, Markus Metz wrote:

Re: PIxel-wise regression contribution

Markus Metz — 2012-05-22T10:04:33

It seems that your script is doing the same like the C module
r.regression.series in grass-addons [0] ?

Markus M


[0] https://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.regression.series

Re: Re: PIxel-wise regression contribution

Markus Neteler — 2012-05-22T07:24:34

Well, please to the grass-psc list... and we also need the statement
about RFC2 as explained in

http://trac.osgeo.org/grass/wiki/HowToContribute#WriteaccesstotheGRASS-Addons-SVNrepository

Best
Markus

Re: [GRASS-user] XY trace plots

Glynn Clements — 2012-05-21T23:07:59

Hamish wrote:


import grass.lib.raster as rast
...
in_val = rast.CELL(in_rast[col])
G_is_null_value(byref(in_val), data_type)

ctypes automatically converts the result of an array acces to a Python
type, while byref() requires a ctypes type. And pointer arithmetic
still isn't implemented (i.e. there's no simple way to get a pointer
to any element of an array other than the first).

Re: PIxel-wise regression contribution

Helmut Kudrnovsky — 2012-05-21T13:33:40

just ask for addons-write-access in the dev-ML (and giving your
osgeo-userid), that's all.

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.n6.nabble.com/PIxel-wise-regression-contribution-tp4975696p4975923.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

Re: on the subject of toolboxes ...

Moritz Lennert — 2012-05-21T08:11:57


+1


+1


Not just out in the field. We train people from countries where even
power is not a certainty, and internet more a question of chance, even
when they sit in their office.

Re: on the subject of toolboxes ...

Paolo Cavallini — 2012-05-21T07:09:52

Thanks Hamish for this discussion.

Il 20/05/2012 03:51, Hamish ha scritto:


I think there are two issues here:
- development cycle
- distribution.
I agree warmly that distribution should make life as easy as possible for users, so a
single package (standalone installer) is the main way to go.
As for development, I think splitting the release cycle of GUI and CLI would be
advisable, as they have different cycles, speed of development, and dependencies.
More clearly: if a [new|fixed|improved] command is ready, and its native GUI is not,
are we sure we want to keep this away form users that can profit form this using the
CLI or a different GUI?


I find filtering (as done in QGIS and in Sextante) quite simple and useful. Adding
tagging would be enough IMHO. Views could be interesting.


Agreed - that's why I'm still uncomfortable with addons (even though I understand its
rationale).


Agreed fully. Modularity, however, is always a Good Thing (e.g., I appreciated very
much your splitting because I do not want to install GUI stuff on a server, etc.).


Agreed.


Hoe this mine will be useful.
All the best.

Re: Re: PIxel-wise regression contribution

Luca Delucchi — 2012-05-21T05:47:08

On 21 May 2012 02:18, "Damien O&apos;Grady" <damien.ogrady< at >my.jcu.edu.au>
wrote:

Please read this

http://trac.osgeo.org/grass/wiki/HowToContribute#WriteaccesstotheGRASS-Addons-SVNrepository


--
Ciao
Luca

http://www.lucadelu.org
http://gis.cri.fmach.it/delucchi
_______________________________________________
grass-dev mailing list
grass-dev< at >lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

RE: on the subject of toolboxes ...

Chemin, Yann (IWMI — 2012-05-21T00:49:58

+1
________________________________
From: grass-dev-bounces< at >lists.osgeo.org [grass-dev-bounces< at >lists.osgeo.org] on behalf of Sylvain Maillard [sylvain.maillard< at >gmail.com]
Sent: Sunday, May 20, 2012 4:00 PM
To: Hamish
Cc: grass-dev< at >lists.osgeo.org
Subject: Re: [GRASS-dev] on the subject of toolboxes ...

Hi dev's,

2012/5/20 Hamish <hamish_b< at >yahoo.com<mailto:hamish_b< at >yahoo.com>>

Namely, implement "views" in the wxGUI preferences section, with
tick boxes where you can hide or show groups of modules as desired.
A core set of common modules would always be ticked in a greyed-out box,
and an "enable all" button would be present. Beyond that you can pick
and choose.

As a user I fully apply to this proposal !
that's already how it works in some other software like QGis or Drupal, and everyone seems to like it  ...

I see an other good reason for this choice: it would be possible to have a box with the full index of modules and some explanations (like on the web manual), I think it will help new users to find the module they need !

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

Re: Re: PIxel-wise regression contribution

Damien O'Grady — 2012-05-21T00:17:59

I am not sure from the documentation how to do this.  I have an
osgeo-userid, but no write access to the addons list (I assume).  I
would be grateful if you would point me in the right direction.

Regards

Damien

 On Sat, 2012-05-19 at 02:51 -0700, Helmut Kudrnovsky wrote:

Re: [GRASS-user] XY trace plots

Hamish — 2012-05-20T21:04:10

[moved to -dev list]

Markus Metz wrote:

no joy, both those come back with:

    if not G_is_null_value(byref(in_rast[col]), data_type):
TypeError: byref() argument must be a ctypes instance, not 'int'

(tried with a CELL map)

https://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.to.vect.lines/r.to.vect.lines.py#L155


the cast happens early on at malloc time,
 in_fd   = G_open_cell_old(inmap, mapset)
 in_rast = G_allocate_raster_buf(data_type)
 in_rast = cast(c_void_p(in_rast), ptype)

right after data_type is determined.
here ptype = POINTER(c_int)


?,
Hamish

Re: on the subject of toolboxes ...

Sylvain Maillard — 2012-05-20T10:30:02

Hi dev's,

2012/5/20 Hamish <hamish_b< at >yahoo.com>


As a user I fully apply to this proposal !
that's already how it works in some other software like QGis or Drupal, and
everyone seems to like it  ...

I see an other good reason for this choice: it would be possible to have a
box with the full index of modules and some explanations (like on the web
manual), I think it will help new users to find the module they need !


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