Re: [GRASS-user] r.mapcalculator and r.mapcalc

Thank you very much! In terms of best practices, if I work with several images with different resolutions, should I always set the region resolution before executing some raster calculation? Or is it better to have different locations according to my images resolutions? Thanks again! Regards!

Re: [GRASS-user] r.mapcalculator and r.mapcalc

On Feb 21, 2017 1:34 AM, "Luiz Andrade" wrote: > > Thanks! > Can you help me with another thing? > My images have 15m pixels, after processing in r.mapcalc and exporting they have 62m pixels. How can I solve this? You will need to set the

Re: [GRASS-user] r.mapcalculator and r.mapcalc

Hi Pedro, On Mon, Feb 20, 2017 at 7:36 PM, Pedro Venâncio wrote: > Hi Vaclav, > > The problem with r.mapcalc in QGIS was this one: > > https://hub.qgis.org/issues/6894 > > I forgot about this ticket. If I interpret the comments correctly there are still people who

Re: [GRASS-user] r.mapcalculator and r.mapcalc

Hi Vaclav, The problem with r.mapcalc in QGIS was this one: https://hub.qgis.org/issues/6894 It was partially solved, but not completely. So, Victor had created a new raster calculator using native QGIS classes: https://github.com/qgis/QGIS/pull/3779 Best regards, Pedro 2017-02-21 0:11

Re: [GRASS-user] r.mapcalculator and r.mapcalc

Thanks! Can you help me with another thing? My images have 15m pixels, after processing in r.mapcalc and exporting they have 62m pixels. How can I solve this? Thanks again Regards, Luiz Claudio > Em 20 de fev de 2017, à(s) 18:42, Helmut Kudrnovsky escreveu: > >> 1 - Why

Re: [GRASS-user] r.mapcalculator and r.mapcalc

Thank you very much! That was very helpful! Atenciosamente, Luiz Claudio > Em 20 de fev de 2017, à(s) 21:11, Vaclav Petras > escreveu: > > > On Mon, Feb 20, 2017 at 4:22 PM, Luiz Andrade > wrote: > 1 - Why wasn’t

Re: [GRASS-user] r.mapcalculator and r.mapcalc

On Mon, Feb 20, 2017 at 4:22 PM, Luiz Andrade wrote: > 1 - Why wasn’t r.mapcalculator ported to grass7? It is great to use it > from within QGIS. Nobody really asked for that as far as I know. The porting should be quite simple if you are interested in that. But that was

Re: [GRASS-user] r.mapcalculator and r.mapcalc

>1 - Why wasn’t r.mapcalculator ported to grass7? It is great to use it from within QGIS. can't answer this one >My r.mapcalc outputs int32 rasters (I want float32). Is there a way to choose the output type? from the manual [1] [...] Functions The functions currently

[GRASS-user] r.mapcalculator and r.mapcalc

Hi there, I have some questions regarding r.mapcalc questions: 1 - Why wasn’t r.mapcalculator ported to grass7? It is great to use it from within QGIS. 2 - My r.mapcalc outputs int32 rasters (I want float32). Is there a way to choose the output type? Thanks! Regards, Luiz Claudio

[GRASS-user] r.mapcalculator / r.mapcalc not producing raster

Hi all, I'm trying to combine two raster using the r.mapcalc/r.mapcalculator but am getting no where. I'm using python. # I did this previously... so dem and rain exist as rasters grass.run_command(r.in.gdal,input=location/dem.tif,output=dem)

Re: [GRASS-user] r.mapcalculator

Hello On 24/10/2010 19:29, ALT SHN wrote: Regarding your first question, (convert floating point raster to integer) you can use: r.mapcalc "int_raster = int(fp_raster) Hello users, I really could use some hints

[GRASS-user] r.mapcalculator

Hello users, I really could use some hints regarding this problem. I want to generate a new raster from the following expression (using r.mapcalculator from QGIS GRASS plugin): A*0.5+B*0.05+C*0.2+D*0.2+E*0.05 All rasters are integer16 geotiff anda have the same resolution. I just get this