I made some contour lines with r.contour. AFAIK, these are vector lines. But I cannot edit them in the digitizer. When I click on a vertex, nothing happens. I can make and edit other lines, but not contour lines. No error in the console either. Anyone know why?
I’m using GRASS 7 compiled yesterday.
Michael
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
On Feb 6, 2013, at 8:17 PM, grass-dev-request@lists.osgeo.org wrote:
Send grass-dev mailing list submissions to
grass-dev@lists.osgeo.orgTo subscribe or unsubscribe via the World Wide Web, visit
grass-dev Info Page
or, via email, send a message with subject or body ‘help’ to
grass-dev-request@lists.osgeo.orgYou can reach the person managing the list at
grass-dev-owner@lists.osgeo.orgWhen replying, please edit your Subject line so it is more specific
than “Re: Contents of grass-dev digest…”
Today’s Topics:
- Re: reg i.pca module (Nikos Alexandris)
- Re: reg i.pca module (Nikos Alexandris)
- Re: does GRASS 7 for Mac compile yet? (Nikos Alexandris)
- Re: does GRASS 7 for Mac compile yet? (Nikos Alexandris)
- Re: [GRASS GIS] #1874: latitudinal bias in sample points
created with r.random (GRASS GIS)- Re: [GRASS GIS] #1874: latitudinal bias in sample points
created with r.random (GRASS GIS)- Re: does GRASS 7 for Mac compile yet? (Michael Barton)
- Re: programming manual GRASS 7 (Hamish)
From: Nikos Alexandris nik@nikosalexandris.net
Subject: Re: [GRASS-dev] reg i.pca module
Date: February 6, 2013 5:11:39 PM MST
On Wednesday 06 of February 2013 23:19:36 Rashad M wrote:
Hi All,
Hi Rashad!
i.pca outputs raster bands and the pixel values are transformed obivously.
But anyone can tell me how the transformation worksif a pixel P1 has value X after i.pca it will be Y
Is there any specific math equation that is applied to every pixel by PCA?
For sure. There are two good grassy-sources to start with:
- the i.pca’s manual
i.pca - GRASS GIS manual2.the GRASS-Wiki page explains all one needs to know – even if it requires
some clean-up
http://grasswiki.osgeo.org/wiki/Principal_Components_AnalysisAnd, of course (sorry for insisting and self-advertising) my work (available
at the link I’ve PMed to you). I’ve put a lot of effort to compile material &
explain what PCA is, what it does and how it does it. It would be really
nice, for me, to have some feedback if it helps, in any way, to understand
PCA.If you had a look and found the material useless, please, be so kind and tell
me so – strait (PM or ML, the same). I’d really like to know what you think
as I am planing to continue this effort in time, and expand it.Best, Nikos
From: Nikos Alexandris nik@nikosalexandris.net
Subject: Re: [GRASS-dev] reg i.pca module
Date: February 6, 2013 5:13:38 PM MST
Rashad M wrote:
Hi All,
i.pca outputs raster bands and the pixel values are transformed
obivously. But anyone can tell me how the transformation worksif a pixel P1 has value X after i.pca it will be Y
Is there any specific math equation that is applied to every pixel by PCA?
Moritz Lennert wrote:
Principal component analysis - Wikipedia
and
Principal Components Analysis - GRASS-WikiEhm, right – I’ve overlooked your post Moritz, apologies.
Nikos
From: Nikos Alexandris nik@nikosalexandris.net
Subject: Re: [GRASS-dev] does GRASS 7 for Mac compile yet?
Date: February 6, 2013 5:20:40 PM MST
Cc: Michael Barton michael.barton@asu.edu, William Kyngesburye kyngchaos@kyngchaos.com
On Tuesday 05 of February 2013 04:24:51 Nikos Alexandris wrote:
On the wxpython-problematic for OS-X:
I can compile grass_trunk which ends up with various wxpython related
errors. So, the gui wont launch. Could it be that we only need to
properly install
- python 2.7
http://python.org/ftp/python/2.7.3/python-2.7.3-macosx10.6.dmg - wxpython
2.9 (the cocoa build)
<wxPython - Browse Files at SourceForge.net
.7.dmg>and then set up properly GRASS to pick those up?
@Michael, @William
I did what I describe(d) above and, with the help of AnnaK, we got the GUI
running.Yes, 2.7 and 2.9. It may be that it bears other, non-desired, sideeffects or
dangers (?). However, I never really use OS-X and since the GUI is launching,
we can go bug-hunting.Thanks, Nikos
From: Nikos Alexandris nik@nikosalexandris.net
Subject: Re: [GRASS-dev] does GRASS 7 for Mac compile yet?
Date: February 6, 2013 5:16:28 PM MST
On Thursday 31 of January 2013 10:51:58 Margherita Di Leo wrote:
I think we should consider to promote a fund rising for buying a (used,
discounted, whatever) mac computer for the use of developers who are
developing or are willing to test on it. What do you think?my 2 c
madiAs I am planning to move in a non-Apple machine, I am considering at either
giving it away for free (to someone that I know will use it) or at a very low
price.my 2 old drachmas
NikosFrom: GRASS GIS trac@osgeo.org
Subject: Re: [GRASS-dev] [GRASS GIS] #1874: latitudinal bias in sample points created with r.random
Date: February 6, 2013 6:41:01 PM MST
To: undisclosed-recipients:;
Reply-To: grass-dev@lists.osgeo.org
#1874: latitudinal bias in sample points created with r.random
------------------------±--------------------------------------------------
Reporter: pvanbosgeo | Owner: grass-dev@…
Type: defect | Status: new
Priority: major | Milestone: 7.0.0
Component: Raster | Version: svn-trunk
Keywords: r.random | Platform: Linux
Cpu: x86-64 |
------------------------±--------------------------------------------------Comment(by hamish):
Replying to [ticket:1874 pvanbosgeo]:
Note that points created with v.random do no show a bias.
However, this is not really an alternative for creating
random points within a irregular area.the v.random.cover addon script for grass 6 exists to do that.
AddOns/GRASS 6 - GRASS-Wiki‘’ v.random.cover is a shell script for creating random points constrained
within an irregularly shaped vector area. (v.random places points only in
current region rectangle). Optionally the user can upload raster values at
the points. See also ‘r.random cover= vector_output=’ ‘’It’s internal method is not especially efficient, but it gets the job done
all the same.Hamish
–
Ticket URL: https://trac.osgeo.org/grass/ticket/1874#comment:5
GRASS GIS http://grass.osgeo.orgFrom: GRASS GIS trac@osgeo.org
Subject: Re: [GRASS-dev] [GRASS GIS] #1874: latitudinal bias in sample points created with r.random
Date: February 6, 2013 6:44:31 PM MST
To: undisclosed-recipients:;
Reply-To: grass-dev@lists.osgeo.org
#1874: latitudinal bias in sample points created with r.random
------------------------±--------------------------------------------------
Reporter: pvanbosgeo | Owner: grass-dev@…
Type: defect | Status: new
Priority: major | Milestone: 7.0.0
Component: Raster | Version: svn-trunk
Keywords: r.random | Platform: Linux
Cpu: x86-64 |
------------------------±--------------------------------------------------Comment(by hamish):
It’s internal
(a friend was terrible with apostrophes and to/too/two & after too many
emails it begins to look natural and the bad habit has rubbed off on me!
argh!)–
Ticket URL: https://trac.osgeo.org/grass/ticket/1874#comment:6
GRASS GIS http://grass.osgeo.orgFrom: Michael Barton Michael.Barton@asu.edu
Subject: Re: [GRASS-dev] does GRASS 7 for Mac compile yet?
Date: February 6, 2013 8:14:04 PM MST
To: Nikos Alexandris nik@nikosalexandris.net
Cc: “grass-dev@lists.osgeo.org” grass-dev@lists.osgeo.org, “William Kyngesburye” kyngchaos@kyngchaos.com
That’s very good that wxPython 2.9 runs. My hope has been that with a bit of tweaking it would work. So I’m glad that you’ve had time to try it out. Thanks much.
Michael
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State Universityvoice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.eduOn Feb 6, 2013, at 5:20 PM, Nikos Alexandris nik@nikosalexandris.net
wrote:On Tuesday 05 of February 2013 04:24:51 Nikos Alexandris wrote:
On the wxpython-problematic for OS-X:
I can compile grass_trunk which ends up with various wxpython related
errors. So, the gui wont launch. Could it be that we only need to
properly install
- python 2.7
http://python.org/ftp/python/2.7.3/python-2.7.3-macosx10.6.dmg - wxpython
2.9 (the cocoa build)
<wxPython - Browse Files at SourceForge.net
.7.dmg>and then set up properly GRASS to pick those up?
@Michael, @William
I did what I describe(d) above and, with the help of AnnaK, we got the GUI
running.Yes, 2.7 and 2.9. It may be that it bears other, non-desired, sideeffects or
dangers (?). However, I never really use OS-X and since the GUI is launching,
we can go bug-hunting.Thanks, Nikos
From: Hamish hamish_b@yahoo.com
Subject: Re: [GRASS-dev] programming manual GRASS 7
Date: February 6, 2013 8:17:11 PM MST
To: Markus Neteler neteler@osgeo.org, Luca Delucchi lucadeluge@gmail.com
Cc: GRASS-dev grass-dev@lists.osgeo.org
Luca wrote:
Instead manually, could you change in a daily cronjob?
keep in mind that the shared VM that it is run on is generally
under considerable load (but not at capacity), and anything extra
on top won’t help that situation. Maybe we could put a nightly
build on the adhoc VM and keep the existing one once a week?best,
Hamish
grass-dev mailing list
grass-dev@lists.osgeo.org
grass-dev Info Page
