t.remove: add dual-step removal as in g.remove
|Reported by:||neteler||Owned by:|
At time t.remove removes data without warning and force flag.
There are two disadvantages:
- the user being familiar with g.remove's behaviour will be surprised
- there is no chance to catch the lack of using -rf (of course a user error), leading to the situation:
GRASS 7.1.svn (eu_laea):~ > t.remove lst_aggreg_modis_week@modis_lst_reconstructed_europe_daily Note: registered maps themselves have not been removed, only the strds
... user's thought in this moment: "Heck, now the strds is gone but I forgot to specify -rf to also get rid of the related raster maps and no easy way to do that now... nor how to figure out their map names!"
I refer to situations where thousands of maps are stored in a mapset with similar names which is common in time series processing.
At time it is a bit confusing since -f would be the best flag name (as it is used in g.remove). I don't think that it would be a problem to even redefine the meaning of -f in G7 since t.remove is still rather new. Hence:
- change meaning of -f to "force removal" (without -f only show what would be done, yet don't remove). Advertise also -rf in the message.
- -d Remove all registered maps from the temporal and also from the spatial database (required for actual deletion of files)