#3469: i.atcorr: Sentinel-2 support broken on some systems
--------------------------+-------------------------
Reporter: sbl | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.4.0
Component: Packaging | Version: unspecified
Resolution: | Keywords: i.atcorr
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by sbl):
Replying to [comment:13 mmetz]:
> So there is some non-NULL output, but it differs between systems. Not so
nice.
Sorry, we should have reported the command we used. If I run exactly your
case:
{{{
i.atcorr -r input=B08 elevation=dem range=0,10000 output=test_atcorr
rescale=0,10000 parameters=p6s.txt
}}}
I get the same output as you:
{{{
r.info -r test_atcorr
min=8.708314e-10
max=10000
}}}
So, it seems to be essential to use both range and rescale option if one
wants the data to be exactly in a given range of values...
Maybe something to clarify in the manual or set as a parser rule / warning
in the module?
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3469#comment:14>
GRASS GIS <https://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/grass-dev
