So r.recode works, although it seems to have a bug.
Maybe that is the key to having i.pansharpen work better with a wider range of
input values. The user would still need to input the min and max possible
range, but it could default to 0 and 255 for 8 bit data.
This changes original values of
Sorry, I meant r.recode.
r.recode infile outfile min:max:0:255
should do it.
MIchael
__
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
Tempe, AZ 8528
On 01/08/13 14:01, Nikos Alexandris wrote:
Moritz:
r.rescale is just a frontend to r.reclass. and as such is meant for
CELLmaps. It should'nt make a difference whether it is 8-bit or more,
though. For DCELL you can try to use r.recode.
Nikos:
Didn't work also (tried the previous days) -- I ca
Moritz:
> > r.rescale is just a frontend to r.reclass. and as such is meant for
> > CELLmaps. It should'nt make a difference whether it is 8-bit or more,
> > though. For DCELL you can try to use r.recode.
Nikos:
> > >>> Didn't work also (tried the previous days) -- I can try again.
On Thursday 01 of August 2013 13:42:03 Moritz Lennert wrote:
> On 01/08/13 13:43, Nikos Alexandris wrote:
> > Michael:
> >> What about just using r.rescale to rescale this?
> >
> > Nikos:
> > Already tried (in the past) and I don't think it works from DCELL>
> > 8-bit. It seems to chew
On 01/08/13 13:43, Nikos Alexandris wrote:
Michael:
What about just using r.rescale to rescale this?
Nikos:
Already tried (in the past) and I don't think it works from DCELL>
8-bit. It seems to chew-up (silently, as Moritz mentioned I think among
the lines in ticket #2^11) values.
It see
Michael:
> What about just using r.rescale to rescale this?
Nikos:
> >>> Already tried (in the past) and I don't think it works from DCELL>
> >>> 8-bit. It seems to chew-up (silently, as Moritz mentioned I think among
> >>> the lines in ticket #2^11) values.
> >>> It seems that "integeri
On 01/08/13 11:40, Nikos Alexandris wrote:
Michael:
What about just using r.rescale to rescale this?
Nikos:
Already tried (in the past) and I don't think it works from DCELL> 8-bit.
It seems to chew-up (silently, as Moritz mentioned I think among the
lines in ticket #2^11) values.
It se
Michael:
> >> What about just using r.rescale to rescale this?
Nikos:
> > Already tried (in the past) and I don't think it works from DCELL> 8-bit.
> > It seems to chew-up (silently, as Moritz mentioned I think among the
> > lines in ticket #2^11) values.
> >
> > It seems that "integerising"
On 01/08/13 11:04, Nikos Alexandris wrote:
Michael Barton wrote:
Nikos,
What about just using r.rescale to rescale this?
Already tried (in the past) and I don't think it works from DCELL> 8-bit. It
seems to chew-up (silently, as Moritz mentioned I think among the lines in
ticket #2^11) valu
Michael Barton wrote:
> Nikos,
>
> What about just using r.rescale to rescale this?
Already tried (in the past) and I don't think it works from DCELL > 8-bit. It
seems to chew-up (silently, as Moritz mentioned I think among the lines in
ticket #2^11) values.
It seems that "integerising" manua
>>
Subject: Re: [GRASS-dev] On i.histo.match (Re: On (Landsat) imagery naming
patterns)
Date: July 31, 2013 3:38:24 PM MST
To: Hamish mailto:hamis...@yahoo.com>>
Cc: mailto:grass-dev@lists.osgeo.org>>, Markus Metz
mailto:markus.metz.gisw...@gmail.com>>
Nikos wrote:
Just FYI, r
>>
Subject: Re: [GRASS-dev] On i.histo.match (Re: On (Landsat) imagery naming
patterns)
Date: July 31, 2013 3:38:24 PM MST
To: Hamish mailto:hamis...@yahoo.com>>
Cc: mailto:grass-dev@lists.osgeo.org>>, Markus Metz
mailto:markus.metz.gisw...@gmail.com>>
Nikos wrote:
Just FYI, r
Nikos wrote:
> > Just FYI, results look nice! I even convert back to 0-1.0 via
> > r.mapcalc --o "${HistoMatchedMap} = ${HistoMatchedMap} / 1000.0"
> > ps- I wonder if *1 is *better* for higher precision?
By the way, that was Landsat5!
> depending on the sensor's 8-bitnesss or not, you can
Nikos wrote:
> > Just FYI, results look nice! I even convert back to 0-1.0 via
> > r.mapcalc --o "${HistoMatchedMap} = ${HistoMatchedMap} / 1000.0"
..
> > ps- I wonder if *1 is *better* for higher precision?
Hamish wrote:
> depending on the sensor's 8-bitnesss or not, you can probably calc
Nikos wrote:
> Just FYI, results look nice! I even convert back to
> 0-1.0 via
>
> r.mapcalc --o "${HistoMatchedMap} = ${HistoMatchedMap} / 1000.0"
...
> ps- I wonder if *1 is *better* for higher precision?
depending on the sensor's 8-bitnesss or not, you can probably calculate by hand
now
MM:
> > >> For rescaling to 0-1000, you could try something like
> > >> r.mapcalc "bandX_int = round(1000 * bandX)"
NA:
> > > Nice! But I wonder why round-ing is required?
MM:
> > rounding is not required, just a bit more accurate than truncating
> > with int(1000 * bandX).
Just FYI, results lo
MM:
> >> For rescaling to 0-1000, you could try something like
> >> r.mapcalc "bandX_int = round(1000 * bandX)"
NA:
> > Nice! But I wonder why round-ing is required?
MM:
> rounding is not required, just a bit more accurate than truncating
> with int(1000 * bandX).
Great Wizard, thnx :-)
N
ps-
On Wed, Feb 20, 2013 at 4:19 PM, Nikos Alexandris
wrote:
> Nikos Alexandris:
>
> Markus Metz wrote:
>
>
>> For rescaling to 0-1000, you could try something like
>> r.mapcalc "bandX_int = round(1000 * bandX)"
>
> Nice! But I wonder why round-ing is required?
rounding is not required, just a bit m
Nikos Alexandris:
> >> Greetings to the dev-list.
> >> I successfully tested , by feeding it with 12 Landsat
> >> scenes (working on identical bands, different Path/Row tiles) in one go.
> >> It works and I really enjoy it.
Nikos A:
> > Could it be that histo-matching works nicely only on 0-255
On Wed, Feb 20, 2013 at 3:27 PM, Nikos Alexandris
wrote:
> On Wednesday 20 of February 2013 13:31:07 Nikos Alexandris wrote:
>> Greetings to the dev-list.
>
>> I successfully tested , by feeding it with 12 Landsat scenes
>> (working on identical bands, different Path/Row tiles) in one go. It work
On Wednesday 20 of February 2013 13:31:07 Nikos Alexandris wrote:
> Greetings to the dev-list.
> I successfully tested , by feeding it with 12 Landsat scenes
> (working on identical bands, different Path/Row tiles) in one go. It works
> and I really enjoy it.
Could it be that histo-matching work
22 matches
Mail list logo
