Re: [GRASS-dev] r.mapcalc bug on max and min?

2014-10-08 Thread Glynn Clements
Pietro wrote: Perhaps we could add two new functions, like: rmin and rmax that stay for range min and range max that give this information It's not possible to implement these as functions within the current structure of r.mapcalc. r.mapcalc's functions take row buffers as inputs, and return

Re: [GRASS-dev] r.mapcalc bug on max and min?

2014-10-08 Thread Pietro
On Wed, Oct 8, 2014 at 12:38 PM, Glynn Clements gl...@gclements.plus.com wrote: do you think could be useful? Not really. Just use r.info (or r.univar if you want the min/max for the current region) and substitute the result into the expression. Yes, I did in this way. Thank you. Pietro

[GRASS-dev] r.mapcalc bug on max and min?

2014-10-06 Thread Pietro
Dear all, I would like to rescale a raster map from a -1, 1 interval to 0, 255. To make an example I've tried to normalize the elevation map: {{{ $ r.mapcalc el = elevation / max(elevation) --o 100% $ r.info el ++ |

Re: [GRASS-dev] r.mapcalc bug on max and min?

2014-10-06 Thread Anna Petrášová
On Mon, Oct 6, 2014 at 4:51 AM, Pietro peter.z...@gmail.com wrote: Dear all, I would like to rescale a raster map from a -1, 1 interval to 0, 255. To make an example I've tried to normalize the elevation map: {{{ $ r.mapcalc el = elevation / max(elevation) --o 100% $ r.info el

Re: [GRASS-dev] r.mapcalc bug on max and min?

2014-10-06 Thread Pietro
On Mon, Oct 6, 2014 at 2:25 PM, Anna Petrášová kratocha...@gmail.com wrote: On Mon, Oct 6, 2014 at 4:51 AM, Pietro peter.z...@gmail.com wrote: Again everything is NULL, I'm doing something wrong or it is a bug? Glynn could perhaps give you some more precise comment, but basically, max

Re: [GRASS-dev] r.mapcalc bug on max and min?

2014-10-06 Thread Moritz Lennert
On 06/10/14 15:07, Pietro wrote: On Mon, Oct 6, 2014 at 2:25 PM, Anna Petrášová kratocha...@gmail.com wrote: On Mon, Oct 6, 2014 at 4:51 AM, Pietro peter.z...@gmail.com wrote: Again everything is NULL, I'm doing something wrong or it is a bug? Glynn could perhaps give you some more precise

Re: [GRASS-dev] r.mapcalc bug on max and min?

2014-10-06 Thread Anna Petrášová
On Mon, Oct 6, 2014 at 9:07 AM, Pietro peter.z...@gmail.com wrote: On Mon, Oct 6, 2014 at 2:25 PM, Anna Petrášová kratocha...@gmail.com wrote: On Mon, Oct 6, 2014 at 4:51 AM, Pietro peter.z...@gmail.com wrote: Again everything is NULL, I'm doing something wrong or it is a bug? Glynn

Re: [GRASS-dev] r.mapcalc bug on max and min?

2014-10-06 Thread Vaclav Petras
On Mon, Oct 6, 2014 at 9:39 AM, Anna Petrášová kratocha...@gmail.com wrote: On Mon, Oct 6, 2014 at 9:07 AM, Pietro peter.z...@gmail.com wrote: On Mon, Oct 6, 2014 at 2:25 PM, Anna Petrášová kratocha...@gmail.com wrote: On Mon, Oct 6, 2014 at 4:51 AM, Pietro peter.z...@gmail.com wrote:

Re: [GRASS-dev] r.mapcalc bug on max and min?

2014-10-06 Thread Markus Neteler
On Mon, Oct 6, 2014 at 4:05 PM, Vaclav Petras wenzesl...@gmail.com wrote: On Mon, Oct 6, 2014 at 9:39 AM, Anna Petrášová kratocha...@gmail.com On Mon, Oct 6, 2014 at 9:07 AM, Pietro peter.z...@gmail.com wrote: Perhaps we could add two new functions, like: rmin and rmax that stay for range min

Re: [GRASS-dev] r.mapcalc bug on max and min?

2014-10-06 Thread Vaclav Petras
On Mon, Oct 6, 2014 at 10:52 AM, Markus Neteler nete...@osgeo.org wrote: On Mon, Oct 6, 2014 at 4:05 PM, Vaclav Petras wenzesl...@gmail.com wrote: On Mon, Oct 6, 2014 at 9:39 AM, Anna Petrášová kratocha...@gmail.com On Mon, Oct 6, 2014 at 9:07 AM, Pietro peter.z...@gmail.com wrote:

Re: [GRASS-dev] r.mapcalc bug on max and min?

2014-10-06 Thread Moritz Lennert
On 06/10/14 17:19, Vaclav Petras wrote: On Mon, Oct 6, 2014 at 10:52 AM, Markus Neteler nete...@osgeo.org mailto:nete...@osgeo.org wrote: On Mon, Oct 6, 2014 at 4:05 PM, Vaclav Petras wenzesl...@gmail.com mailto:wenzesl...@gmail.com wrote: On Mon, Oct 6, 2014 at 9:39 AM, Anna

Re: [GRASS-dev] r.mapcalc bug on max and min?

2014-10-06 Thread Pietro
On Mon, Oct 6, 2014 at 5:53 PM, Moritz Lennert mlenn...@club.worldonline.be wrote: I'm not going to stand in the way of those who really want to implement this, but why is this necessary ? eval(r.univar -g $map) r.mapcalc new=old/$max (and equivalent in other programming languages) works