Personally, I do not have any problems with the names of r.stats, r.univar or
r.statistics.
However, I see that r.statistics2 or r.statistics3 is not a too elegant
solution...
If you really plan to rename all these modules, what about a two-dot-name like
r.statistics.* Yet, there are more
On 02/13/14, 09:58 , Blumentrath, Stefan wrote:
Personally, I do not have any problems with the names of r.stats,
r.univar or r.statistics.
However, I see that r.statistics2 or r.statistics3 is not a too elegant
solution…
If you really plan to rename all these modules, what about a
Hi Ben,
Thanks for the reply. I tried with the band option but it looks like
gdal does not detect the multiple fields as multiple bands :
GRASS 7.0.svn (lambert93):~ r.in.gdal --o \
input=/home/manuel/Desktop/sftp/Projets/Projets/Zones-humides/base_sig/dsm_data/clc/clc06_250m
\
band=3
Hmm, the manual page does not say so explicitely,
but maybe band numbering starts with 0?
In that case your band 3 would have index number 2.
Ben
On 13/02/14 10:48, manuel.martin wrote:
Hi Ben,
Thanks for the reply. I tried with the band option but it looks like
gdal does not detect the
I had already tried this (with 2) ;-). No luck either. Reading your
email I tried with 0 (maybe would gdal detect only two bands over
three). It comes out that only band=1 works
GRASS 7.0.svn (lambert93):~ r.in.gdal --o
Ouch. I am beginning to suspect that the ESRI field
concept for raster layers does not translate well
to GRASS/GDAL. Sorry for not being able to help.
Maybe someone else on this list has experience with
this type of data structure?
At least now we know that r.in.gdal starts counting
bands with 1!
Out of the box:
Import it in R and save it as a Tiff - use GRASS to open this tiff. Maybe
it works ;P
On 13 February 2014 10:50, Benjamin Ducke bendu...@fastmail.fm wrote:
Ouch. I am beginning to suspect that the ESRI field
concept for raster layers does not translate well
to GRASS/GDAL.
I think geoTiffs do not handle categorical variables (can anyone
confirm?), neither the writeRAST6() function from spgrass6 (tested
yesterday), and that's why I looked for a full GRASS option (avoiding
using R to go from ArcGIS to GRASS). So it is true that I can import
categorical ArcGIS
On 13/02/14 13:32, manuel.martin wrote:
I think geoTiffs do not handle categorical variables (can anyone
confirm?), neither the writeRAST6() function from spgrass6 (tested
yesterday), and that's why I looked for a full GRASS option (avoiding
using R to go from ArcGIS to GRASS). So it is true
On 12/02/14 13:41, Nikos Alexandris wrote:
Salut GRASSers,
Moritz Lennert wrote:
[..]
With all the elements in place, especially with Pietro's recent work, it
should be quite easy to create a unifying module 'i.segment.classify'
which would take as input
- the segments coming out of
On 02/13/2014 04:31 PM, Moritz Lennert wrote:
On 13/02/14 13:32, manuel.martin wrote:
I think geoTiffs do not handle categorical variables (can anyone
confirm?), neither the writeRAST6() function from spgrass6 (tested
yesterday), and that's why I looked for a full GRASS option (avoiding
using R
(sorry for top posting, no time to deal with yahoo mail today)
Hi,
note for GRIB you need gdal 1.10 or newer, there were
edge coordinate bugs in earlier versions.
--- see: http://grasswiki.osgeo.org/wiki/GRIB
note grass uses the cell-center for data value convention,
not the data values at
12 matches
Mail list logo
