i.modis.import writes wrong dates for 8- and 16-day MODIS products

[veroandreo]

G7A:i.modis.import has a -w flag to write a text file consisting of map name, start and end date that can then be used directly with G7:t.register. However, when MODIS products have a granularity of 8 or 16 days, the final date of last map of the year is wrongly set since the code (IIUC) uses a timedelta(days) to create dates for the outfile (See: ​https://trac.osgeo.org/grass/browser/grass-addons/grass7/imagery/i.modis/i.modis.import/i.modis.import.py#L301). If more than one year is downloaded and imported at once, all maps after the first year will have shifted timestamps.

[lucadelu]

In 73415:

i.modis.import: improve t.register output, see #3654

[veroandreo]

Tested here with:

i.modis.download settings=gisdata/SETTING folder=. \
tiles=h18v02 product=lst_terra_eight_1000 \
startday=2017-12-01 endday=2018-01-01

i.modis.import -w files=listfileMOD11A2.006.txt \
spectral='( 1 0 0 0 0 0 0 0 0 0 0 0 )' outfile=tlist-mod.txt

t.create output=modis title="MODIS 2017" desc="MODIS data for Norway"

t.register input=modis file=tlist-mod.txt

the file tlist-mod.txt (output of G7A:i.modis.import) has correct start and end dates now and therefore, also the output of G7:t.info and G7:t.rast.list is now fine:

t.rast.list modis
name|mapset|start_time|end_time
MOD11A2.A2017337.h18v02.single_LST_Day_1km|user1|2017-12-03 00:00:00|2017-12-11 00:00:00
MOD11A2.A2017345.h18v02.single_LST_Day_1km|user1|2017-12-11 00:00:00|2017-12-19 00:00:00
MOD11A2.A2017353.h18v02.single_LST_Day_1km|user1|2017-12-19 00:00:00|2017-12-27 00:00:00
MOD11A2.A2017361.h18v02.single_LST_Day_1km|user1|2017-12-27 00:00:00|2018-01-01 00:00:00 <<--
MOD11A2.A2018001.h18v02.single_LST_Day_1km|user1|2018-01-01 00:00:00|2018-01-09 00:00:00

Thanks!

[veroandreo]

Tested also for leap years and with 16-day NDVI product. Reported issue seems solved :)

closing... reopen if needed