Win7 GRASS 7 & i.landsat.toar

Question

Hello has anyone got experience running i.landsat.toar ?

The output files I get are empty, the command takes but a moment to complete. However when run in verbose mode all the calculations are done, it just does not complete the filling of the raster.

I am working on Win7 with GRASS7SVN. I am processing Landsat 5. I have taken care to reproject the images properly since there is incorrect metadata for Landsat in the southern hemisphere. The file paths are short and space free.

I note the following, but these don't appear to be directly related to my problem.

https://trac.osgeo.org/grass/ticket/1183

http://lists.osgeo.org/pipermail/grass-user/2010-September/057803.html

and the latest manual at

https://svn.osgeo.org/grass/grass-addons/imagery/i.landsat.toar/description.html

Any thoughts appreciated.

Some output;

BAND 5  (code 5)
   calibrated digital number (DN): 1.0 to 255.0
   calibration constants (L): -0.370 to 30.200
   at-surface radiance = 0.12035 * DN + 0.48667
   mean solar exoatmospheric irradiance (ESUN): 220.000
   at-surface reflectance = radiance / 60.70201
   the darkness DN with a least 100 pixels is 1
   the mode of DN is 0
-------------------
 BAND 6 thermal  (code 6)
   calibrated digital number (DN): 1.0 to 255.0
   calibration constants (L): 1.238 to 15.303
   at-surface radiance = 0.05537 * DN + 1.18263
   at-sensor temperature = 1260.560 / log[(607.760 /
radiance) + 1.0]
-------------------
 BAND 7  (code 7)
   calibrated digital number (DN): 1.0 to 255.0
   calibration constants (L): -0.150 to 16.500
   at-surface radiance = 0.06555 * DN + 0.16508
   mean solar exoatmospheric irradiance (ESUN): 83.440
   at-surface reflectance = radiance / 23.06338
   the darkness DN with a least 100 pixels is 1
   the mode of DN is 0
-------------------
Calculating...
Writing reflectance of <5_9384_20101227_1> to <5_9384_20101227_toar_1>...
Writing reflectance of <5_9384_20101227_2> to <5_9384_20101227_toar_2>...
Writing reflectance of <5_9384_20101227_3> to <5_9384_20101227_toar_3>...

Answer 1

I have used i.landsat.toar recently with Landsat5 (on Linux) and hence updated its documentation accordingly as now found in SVN. For me no problem with the module. Suggestion: be sure that the computational region is correct. It must match the data of course, I suspect that you are off-map right now.

For example (before running i.landsat.toar):

g.region rast=5_9384_20101227_1 -p

or in the wxGUI, use "zoom to map" and then "set computational region from display" (don't remember the precise wording).