[GRASS-dev] [GRASS GIS] #3469: i.atcorr: Sentinel-2 support broken on some systems

[GRASS GIS]

#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 mlennert):

 I'm on Debian testing with gcc (Debian 7.2.0-17) 7.2.1 20171205.

 Using fresh trunk with the following compiler settings:

 {{{
 CFLAGS="-g -Wall -fopenmp -lgomp -Ofast -fno-fast-math
 -march=core-avx-i -fno-common -fexceptions $PENTIUM64"
 LDFLAGS="-Wl,--no-undefined -fopenmp -lgomp"
 CXXFLAGS="-g -Ofast"
 }}}

 and applying the exact commands given in this ticket, I get as result:


 {{{
 r.info -r test_atcorr
 min=NULL
 max=NULL
 }}}

 Several questions:

 * In the discussion in the mailing list, some examples were with i.atcorr
 -r, others without. Do we agree that in this case it should be with -r as
 the data contains reflectance information ?
 * What is the exact meaning and impact of the range setting ?
 * Stefan, any special reason why you import your data with '-o' ? Why not
 create an EPSG 32633 location and import the data there ?

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3469#comment:1>
GRASS GIS <https://grass.osgeo.org>