[GRASS-dev] [GRASS GIS] #3317: t.remove -rf does not unregister removed maps from temporal database
GRASS GIS
trac at osgeo.org
Sun Mar 19 15:16:30 PDT 2017
#3317: t.remove -rf does not unregister removed maps from temporal database
------------------------+-------------------------
Reporter: veroandreo | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.2.1
Component: Temporal | Version: svn-trunk
Keywords: t.remove | CPU: x86-64
Platform: Linux |
------------------------+-------------------------
I used {{{t.remove -rf inputs=bla1,bla2,bla3}}} to remove all strds and
corresponding maps from a certain mapset I use for testing. However, I
found that even though maps and strds were indeed removed (i.e.: they no
longer appeared after {{{t.list type=strds}}} or {{{g.list
type=raster}}}), maps were not unregistered from the temporal database. I
only discovered this when I used {{{t.list type=raster}}}. I had to remove
those maps (i.e.: the corresponding entries for those maps in the temporal
database) with G7:t.unregister.
I understand that maps are not unregistered from the temporal database
when one only removes the strds, but if one removes both strds and maps
(by means of -rf flags), wouldn't it be better to also unregister those
maps from the temporal database by default? It seems confusing to also
have to run t.unregister after having removed strds and maps.
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3317>
GRASS GIS <https://grass.osgeo.org>
More information about the grass-dev
mailing list