Hanlie Pretorius wrote:
>
> I don't really know why the
> resolution in the x and y directions are not the same. Even when I set
> them explicitly, I get a slight difference:
The -a flag is missing, see my previous post.
> -
> g.region -p vect=c83a_bor...@permanent nsres=25 ewres=25
> projecti
2010/9/29, Markus Metz :
>
> In GRASS, you have full control of the computational region,
> consequently you must be able to explain (to the client/supervisor)
> every aspect of the computational region. Why is the horizontal
> resolution not only slightly off from exactly one meter, but also
> dif
Hanlie Pretoriuswrote:
> Hi,
>
> I've created subcatchments using r.watershed and I would like to
> convert these to polygons. My result at the moment contains too many
> polygons - 194. The original raster had only 9 areas, which should all
> have been contiguous seeing that they came from r.water
On 09/29/2010 02:11 PM, Hanlie Pretorius wrote:
Hi,
I've created subcatchments using r.watershed and I would like to
convert these to polygons. My result at the moment contains too many
polygons - 194. The original raster had only 9 areas, which should all
have been contiguous seeing that they c
You might consider using -s flag to smooth the corners.
Otherwise, I can't see why it doesn't work.
R.
Sab
> Hi,
>
> I've created subcatchments using r.watershed and I would like to
> convert these to polygons. My result at the moment contains too many
> polygons - 194. The original raster had on
Hi,
I've created subcatchments using r.watershed and I would like to
convert these to polygons. My result at the moment contains too many
polygons - 194. The original raster had only 9 areas, which should all
have been contiguous seeing that they came from r.watershed.
Here is the sequence of com
