On Sun, Feb 22, 2015 at 8:36 AM, RichardCooper richtcoo...@hotmail.com wrote:
I've resolved - I hadn't set g.region aligning to the raster prior to
v.to.rast:
g.region -a res=0.22 does not align the region to the raster, but to
the resolution. This is an important difference reflected in the
Hi Markus,
Thanks for your comments.
It still appears that v.rast.stats is giving me different values to
r.univar.
Essentially I'd like to clarify how the values are derived from
v.rast.stats. I'm guessing that the discrepancy between my r.univar and
v.rast.stats outputs relates to how I'm
I've resolved - I hadn't set g.region aligning to the raster prior to
v.to.rast:
This appears to work,with outputs from r.univar matching v.rast.stats:
g.region -p -a raster=cahpa_i0apr_05216_nc_remapped_nc_1@prcp05216ijk
res=0.22
g.region -p
On Fri, Feb 20, 2015 at 12:33 PM, RichardCooper richtcoo...@hotmail.com wrote:
I seem to be getting an error with r.univar when using a zone file.
I run, g.region as follows:
g.region -a raster=cahpa_i0apr_05216_nc_remapped_nc_1@prcp05216ijk res=0.22
When you use g.region -a res=, the new
On 20/02/15 12:33, RichardCooper wrote:
I seem to be getting an error with r.univar when using a zone file.
I run, g.region as follows:
g.region -a raster=cahpa_i0apr_05216_nc_remapped_nc_1@prcp05216ijk res=0.22
What does g.region -p show ?
Then r.univar (see below).
There are 6 categories
The output from g.region:
g.region -p
projection: 3 (Latitude-Longitude)
zone: 0
datum: wgs84
ellipsoid: wgs84
north: 35:38:24N
south: 15:10:48S
west: 89:45:36E
east: 140:34:48E
nsres:
