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
Markus Metz wrote:
On Wed, Jan 28, 2015 at 10:34 PM, Micha Silver mi...@arava.co.il 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?
On Wed, Jan 28, 2015 at 10:34 PM, Micha Silver mi...@arava.co.il 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 the number of
Hi Markus:
Thanks for the quick reply. That indeed was my problem:
misunderstanding the implications of the levels param.
Best,
Micha
On 29-Jan-15 12:28 PM, Markus Metz
wrote:
On Wed, Jan 28, 2015 at 10:34 PM, Micha Silver mi...@arava.co.il
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?
Here's an example:
# Import three bands
GRASS 7.0.0svn (UTM33N):~/Downloads for b in 2 3 4; do
