Re: [GRASS-user] r.out.gdal to AAIGrid

2017-08-04 Thread Pedro Venâncio
Hi Markus, You are also completely right! Some of data I exported (elevation, slope, aspect) did not have NULL cells. And in the other data that have NULLs, I used r.null to ensure that the NULL value was -. With that I simply transformed the NULL cells to the value -, wich are exported as

Re: [GRASS-user] r.out.gdal to AAIGrid

2017-08-04 Thread Markus Neteler
Hi Pedro, I created a test case with the North Carolina sample dataset (by zooming in the GUI to the elevation map border and setting that as computational region): # GRASS 7.2.2svn (nc_spm_08_grass7):~ > # set computational region around east elevation map border g.region n=216820 s=216770 w=64

Re: [GRASS-user] r.out.gdal to AAIGrid

2017-08-04 Thread Pedro Venâncio
Hi Jeshua, You're completely right! I'd tried it, but it gaves me an error, and I did not read it correctly, but it clearly it said that it was not possible to assign that nodata value, because of the selected datatype! Thank you very much for the hint! And sorry for the noise! Best regards, Ped

Re: [GRASS-user] r.out.gdal to AAIGrid

2017-08-03 Thread Jeshua Lacock
> On Aug 3, 2017, at 12:24 PM, Pedro Venâncio wrote: > > I'm using r.out.gdal to export raster data from GRASS to Arc/Info ASCII Grid > format, to use in another software (Farsite). > > However, the resulting ASCII files does not have the NODATA_value parameter > in the header. > > I've tr

[GRASS-user] r.out.gdal to AAIGrid

2017-08-03 Thread Pedro Venâncio
Hi, I'm using r.out.gdal to export raster data from GRASS to Arc/Info ASCII Grid format, to use in another software (Farsite). However, the resulting ASCII files does not have the NODATA_value parameter in the header. I've tried gdal_translate and it creates, by default, NODATA_value -999 Shou