The short answer is yes, it will be difficult. The GRASS-internal
vector buffering algorithm has a number of bugs, the only vector
buffering method that is AFAICT bug-free is v.buffer in trunk with
GEOS support which uses the GEOS buffering algorithm which in turn
does not (yet?) support geodesic distances in latlong.
Markus M
I was just using v.buffer yesterday, and found it was ignoring my region settings, it processed the entire map instead of a small area.
I updated GRASS yesterday, and am compiled with GEOS. Am I missing something else, should v.buffer respect the region?
On Fri, Sep 7, 2012 at 5:00 PM, Eric Momsen <eric.momsen@gmail.com> wrote:
I was just using v.buffer yesterday, and found it was ignoring my region
settings, it processed the entire map instead of a small area.
I updated GRASS yesterday, and am compiled with GEOS. Am I missing
something else, should v.buffer respect the region?
To my knowledge no. As before, all vector modules work on full maps while
raster operations are done in the computational region (with a few exceptions).
To limit a vector area you need to clip it first (e.g., v.in.region +
v.overlay/v.select).