On 26-07-14 07:58, Paulo van Breugel wrote:
On 24-07-14 16:21, Glynn Clements wrote:
Paulo van Breugel wrote:
How do I use this new flag / seed parameter for r.mapcalc in python
scripts?
The grass.script.mapcalc() function has been updated to accept a seed=
parameter, which should be either
On 24-07-14 16:21, Glynn Clements wrote:
Paulo van Breugel wrote:
How do I use this new flag / seed parameter for r.mapcalc in python
scripts?
The grass.script.mapcalc() function has been updated to accept a seed=
parameter, which should be either an integer or the string 'auto' for
a random s
1. What did you get done this week?
I significantly improved the test file page which is the central page of
the report in the sense that there you can get all the details. I also
added details about successful and failed (individual) tests to main index
page (the one with links to all test files)
Hi,
1. What did you get done this week:
I updated documentation and added flowline integration in both directions.
I wrote tests (using the new testing framework) and I must still add more.
2. What do you plan on doing next week?
There are couple of options. I will experiment with different tile
#2381: lighting/shading for vector objects backward in nviz
-+--
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal |
#2381: lighting/shading for vector objects backward in nviz
-+--
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal |
#2381: lighting/shading for vector objects backward in nviz
-+--
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal |
#2377: wxGUI mapswipe: refresh issue
--+-
Reporter: neteler | Owner: grass-dev@…
Type: defect | Status: closed
Priority: normal | Milestone: 7.0.0
Hi all,
Below is my weekly report:
**
- fixed some bugs:
- in xml exporting module
- in wx metadata generator
- created and tested modified jinja template for inspire and grass
profile
- worked on GUI features in g.gui.metadata
- added and connected data-catalog
- s
#2381: lighting/shading for vector objects backward in nviz
-+--
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal |
#2381: lighting/shading for vector objects backward in nviz
-+--
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal |
Hi,
unfortunately t.rast.series or t.rast.aggregate do not support
weighting. And i am not completely sure how weighting should work in
your specific case. But you can try to use t.rast.aggregate first to
compute the average for each year and then use t.rast.mapcalc2 to
perform weighting based on t
#2381: lighting/shading for vector objects backward in nviz
-+--
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal |
#2380: d.legend "use" argument makes legend disappear
-+--
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Miles
#2381: lighting/shading for vector objects backward in nviz
-+--
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal |
#2380: d.legend "use" argument makes legend disappear
-+--
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Miles
#2380: d.legend "use" argument makes legend disappear
-+--
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Miles
#2381: lighting/shading for vector objects backward in nviz
-+--
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal |
#2380: d.legend "use" argument makes legend disappear
-+--
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Miles
#2380: d.legend "use" argument makes legend disappear
-+--
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Miles
So, what is the pythonic way to manipulate region then? I ended up with:
reg.vect(parcels.name)
regbuffer = 100
reg.north += regbuffer
...
reg.set_current()
# set_current() not working right now
# so using r.raster for being sure:
g.region(n=str(reg.north), s=str(reg.south), w=str(reg.west),
e=str
#2290: Wrong file permissions for grassXY.py on Windows (was: Grass not
starting)
--+-
Reporter: dnewcomb | Owner: grass-dev@…
Type: defect| Status: new
Pr
#2290: Wrong file permissions for grassXY.py on Windows (was: Grass not
starting)
--+-
Reporter: dnewcomb | Owner: grass-dev@…
Type: defect| Status: new
Pr
On Fri, Jul 25, 2014 at 5:05 AM, Pietro wrote:
> On Fri, Jul 25, 2014 at 10:39 AM, Martin Zbinden
> wrote:
> > If I understand correctly, Region.set_current() can be used
> > to effectively change the region currently used by GRASS. But changing
> > extent of Raster()-object and executing set_cu
Hi Martin,
On Fri, Jul 25, 2014 at 10:39 AM, Martin Zbinden
wrote:
> If I understand correctly, Region.set_current() can be used
> to effectively change the region currently used by GRASS. But changing
> extent of Raster()-object and executing set_current() does not have
> any effect.
I found th
Hi everybody,
I just wanted to tell you that uploaded my first two addons for G7:
- r.in.wcs : Import data for region from WCS-server
- r.soillossbare: Calculate soilloss for bare soil according to
Neteler & Mitasova, 2008 [1]
Well, I'm open to read your feedback and learn from it. I know that it
Hi,
I've come across some trouble defining the computational region from pygrass:
If I understand correctly, Region.set_current() can be used
to effectively change the region currently used by GRASS. But changing
extent of Raster()-object and executing set_current() does not have
any effect.
Bel
27 matches
Mail list logo
