Hi Paulo,
Thanks a lot for the update!
Best,
Anusheema
On 30 January 2015 at 13:50, Paulo van Breugel
wrote:
> Hi, there is an updated version for grass 7 which you can install using
> g.extension.
>
> On Sat, 27 Dec 2014 18:40 Anusheema Chakraborty
> wrote:
>
>> Thanks for the response!
>>
>
Danilo,
While developing we used Ubuntu and it was grass 7.0
Maxi
Il giorno mer 28 gen 2015 15:42 DEBERNARDI DANILO <
d.debernar...@studenti.uninsubria.it> ha scritto:
> I think that the quickest solution for this problem could be to change my
> pc platform or use a virtual platform (virtual box
On Wed, Jan 28, 2015, at 04:14 PM, Markus Neteler wrote:
> On Wed, Jan 28, 2015 at 9:50 PM, Tyler Smith wrote:
> ...
> > So is there a way to run a grass job in batch mode without invoking a
> > script?
>
> Yes, you just need to set some environment variables, see e.g. here:
>
> http://grasswiki
Thanks for clarifying.
We always have to answer claims such as: "...but Arc* does like
this...".
We noticed the problem when compositing Landsat tiles in an area
with very uniform landscape. The slight shift in RGB values with
the default level=32 led to many ad
Markus Metz wrote:
> On Wed, Jan 28, 2015 at 10:34 PM, Micha Silver wrote:
> > When I use r.composite to create, i.e., a false_color composite from three
> > Landsat bands, the RGB values in the composite are slightly different than
> > the values in the original bands. Why is that?
>
> Because
Dear grass-user members,
to identify nodes of lines and to analyse the geometry of line
crossings the output of the dump of v.build seems to be very useful.
However I do not benefit fully of this data, because I did not find any
explanation of the output format. Where can I find a documentatio
Hi, there is an updated version for grass 7 which you can install using
g.extension.
On Sat, 27 Dec 2014 18:40 Anusheema Chakraborty wrote:
> Thanks for the response!
>
> I was trying to use the shell script in GRASS 6. And I am working on a
> Windows system. I'll use the updated version of the
