On Fri, 2009-04-24 at 23:51 +0200, Markus Neteler wrote:
> On Wed, Apr 22, 2009 at 10:58 PM, Jack Lonsdale wrote:
> > I am continuing to try and use Grass to process my LiDAR data. However,
> > having completed v.lidar.edgedetect successfully I am unable to complete
> > v.lidar.growing
> >
> > fir
On Wed, Apr 22, 2009 at 10:58 PM, Jack Lonsdale wrote:
> I am continuing to try and use Grass to process my LiDAR data. However,
> having completed v.lidar.edgedetect successfully I am unable to complete
> v.lidar.growing
>
> firstly, just to check, the 'first' parameter is the raw dataset? If not
> First we need to know what you use:
>
> db.connect -p
>
> The db.connect manual page also shows how to switch to the
> SQLite backend: ideally done in a new mapset. Then add the
> previous mapset to the search path with g.mapsets and
> repeat there the v.lidar.* commands the in new mapset.
>
Isn't it possible to make a new module within grass that support AHP.
Arcview support AHP. Why don't GRASS.
best
zahid
On Thu, Apr 23, 2009 at 3:04 AM, Milton Cezar Ribeiro <
miltinho.astrona...@gmail.com> wrote:
> How about some python solution?
> Just a curious..
>
> milton
>
> 2009/4/22 Raine
Annalisa
Thanks for your help, but there is a little problem: I calculate the
agricultural land around a city, then i buffer the vector, transform it
into a raster map and subtract all the "not possible land". At the end,
there is less agricultural land than I calculated. There must be a
buffering
Martin,
after you have done the buffering operation (as Moritz said), and
transformed vector map (buffer_areas) in raster (v.to rast), you can easily
extract only the interested areas by using a mapalgebra operation.. for
example:
if "agri" is the map of your agricultural areas (green map)
and "bu
