Re: [GRASS-user] d.rast.edit does not save edited cells (?)

2008-02-22 Thread Glynn Clements
Nikos Alexandris wrote: However, this only replaces non-null cells. Any null cells result in the corresponding cells in the orignal map remaining untouched. I could fix d.rast.edit to use r.mapcalc instead of r.patch. But it might be better to add an option to r.patch to support this

Re: [GRASS-user] d.rast.edit does not save edited cells (?)

2008-02-22 Thread Nikos Alexandris
It makes (some) sense for me. I was and still am doing a lot of visual interpretation (currently upon MODIS imagery). I need to collect samples for i.smap for example and with MODIS (MOD09, 250m pix.res) this task is a challenge. And I am not only digitising samples from the scratch, but I use

Re: [GRASS-user] d.rast.edit does not save edited cells (?)

2008-02-22 Thread Hamish
Nikos Alexandris wrote: And why not having a magic key with which one can fly over pixels with the mouse pointer and assign new values instead of countless clicks. FWIW I find the old xmon terminal based d.rast.edit's 3 button click-workflow to be incredibly well thought out and implemented.

Re: [GRASS-user] d.rast.edit does not save edited cells (?)

2008-02-22 Thread Nikos Alexandris
I just now realised the use of the right mouse button. But I am not able to figure out how the middle button works. How does it work? I take back my words for the magic key if this highlight function is working ;-) Cheers, Nikos On Fri, 2008-02-22 at 04:41 -0800, Hamish wrote: Nikos Alexandris

Re: [GRASS-user] d.rast.edit does not save edited cells (?)

2008-02-22 Thread Glynn Clements
Nikos Alexandris wrote: And another question: Is it possible to ad something else besides an Aspect map? Use maybe transparencyt and a background command (like with r.digit)? What are the limitations? I'm not sure how a background map could work; it would be obscured by the map

Re: [GRASS-user] d.rast.edit does not save edited cells (?)

2008-02-21 Thread Nikos Alexandris
No errors! Hmmm... ! I though that it works as follows (and did): 1. Open a raster and give a name for the new raster (open a raster with areas, all having the same value 5) 2. edit, save, exit (I erased lots of pixels from various areas by assigning the * -- that is NULL, no?) 3. load the NEW

Re: [GRASS-user] d.rast.edit does not save edited cells (?)

2008-02-21 Thread Nikos Alexandris
O! I got it! It's the * I am using. With the value 66 for example it worked! But why not with *. It's a perfect tool if one needs to manually correct some details. And why not having a magic key with which one can fly over pixels with the mouse pointer and assign new values instead of

Re: [GRASS-user] d.rast.edit does not save edited cells (?)

2008-02-21 Thread Glynn Clements
Nikos Alexandris wrote: Hmmm... ! I though that it works as follows (and did): 1. Open a raster and give a name for the new raster (open a raster with areas, all having the same value 5) 2. edit, save, exit (I erased lots of pixels from various areas by assigning the * -- that is NULL,

Re: [GRASS-user] d.rast.edit does not save edited cells (?)

2008-02-21 Thread Nikos Alexandris
On Fri, 2008-02-22 at 02:32 +, Glynn Clements wrote: Nikos Alexandris wrote: Hmmm... ! I though that it works as follows (and did): 1. Open a raster and give a name for the new raster (open a raster with areas, all having the same value 5) 2. edit, save, exit (I erased lots

Re: [GRASS-user] d.rast.edit does not save edited cells (?)

2008-02-20 Thread Glynn Clements
Nikos Alexandris wrote: I am trying to make use of this amazing tool but whenever I save exit d.rast my new raster it looks like the old one! Is there a secret setting? No. You are looking at the new map (output=), not the original (input=), right? If you're trying to edit a map in place