[GRASS-dev] [GRASS GIS] #3979: G79: problem with i.sentinel.import and importer.write_metadata()

GRASS GIS trac at osgeo.org
Thu Nov 21 13:12:52 PST 2019

#3979: G79: problem with i.sentinel.import and importer.write_metadata()
  Reporter:  neteler     |      Owner:  grass-dev@…
      Type:  defect      |     Status:  new
  Priority:  normal      |  Milestone:
 Component:  Imagery     |    Version:  svn-trunk
Resolution:              |   Keywords:  i.sentinel.import, image
       CPU:              |  collections
  Unspecified            |   Platform:  Unspecified

Comment (by neteler):

 Replying to [comment:8 sbl]:
 > Hm, I think I have a hunch. Can you try to
 > 1) delete all SAFE directories (or use a different unzip dir)
 > 2) run i.sentinel.import again and see if the error remains?

 Bingo! Now it ran through, finally.

 > If you don`t link (l-flag) the unpacked SAFE dirs should actually be
 removed automatically...

 I didn't use -l this time.

 > If they are present, i.sentinel.import does not unpack again (anymore
 after my changes). If an import is interrupted it may lead to issues like

 I see. May I suggest that, if present, the SAFE directory be actually
 removed before unpacking? Less confusion :-)

 Rationale: it may happen then a `i.sentinel.import` job is interrupted, be
 by the user, for disk-full reasons or whatever else might occur...

Ticket URL: <https://trac.osgeo.org/grass/ticket/3979#comment:9>
GRASS GIS <https://grass.osgeo.org>

More information about the grass-dev mailing list