Opened 2 years ago

Last modified 12 months ago

#3582 new enhancement

Removing a Mapset from inside a GRASS GIS session

Reported by: Nikos Alexandris Owned by: grass-dev@…
Priority: normal Milestone: 7.8.3
Component: Default Version: unspecified
Keywords: mapset, remove, delete, erase Cc: wenzeslaus
CPU: Unspecified Platform: Unspecified

Description

Would it possible to add a way to remove a Mapset, or multiple Mapsets, from the command line? For example, add a "remove" or "delete" or "erase" function to the existing g.mapset module.

Points to consider:

  • This functionality should not be allowed, of course!, to request for a removal of the current Mapset. It should only allow for removal of other(s) than the current Mapset.
  • Only the owner of another, than the current, Mapset, or the "admin" (creator of PERMANENT?), will be able to remove it.
  • Following the existing way of removing "elements" of a Mapset, a force flag -f could be required, in order to actually remove such a directory, and all of its contents.
  • Such an option would, maybe, make for a safer practice, if implemented correctly, rather than leaving as the only option to remove a Mapset directory, directly via the host OS' deletion functions.

See also https://trac.osgeo.org/grass/ticket/3577

Change History (3)

comment:1 Changed 12 months ago by jidanni

Indeed without using the GUI, there is no way to

  • remove locations
  • remove mapsets.

When one day there finally are, they should be added to the SEE ALSO of g.remove.

And mentioned on grass7.html, which tells one how to create them from the command line, but forgets to then add how to remove them!

comment:2 Changed 12 months ago by neteler

Milestone: 7.8.3

comment:3 in reply to:  1 Changed 12 months ago by neteler

Replying to jidanni:

And mentioned on grass7.html, which tells one how to create them from the command line, but forgets to then add how to remove them!

If you can, please suggest an edit (PR) here:

https://github.com/OSGeo/grass/blob/master/lib/init/grass7.html

Note: See TracTickets for help on using tickets.