Opened 12 years ago

Closed 4 years ago

#1910 closed enhancement (fixed)

GIS manager: allow dataset managing directly

Reported by: timmie Owned by: grass-dev@…
Priority: normal Milestone: 7.6.2
Component: wxGUI Version: unspecified
Keywords: map management, layer manager Cc:
CPU: Unspecified Platform: Unspecified

Description

Allow from the GIS Manager to manage datasets directly: g.remove g.rename g.copy

Once these commands are available in the context menu, any changes (e.g. renaming) shall be reflected in the layer tree.

See also: http://trac.osgeo.org/grass/ticket/1909

Change History (16)

comment:1 by martinl, 12 years ago

Keywords: map management added
Milestone: 6.4.36.4.4

comment:2 by wenzeslaus, 11 years ago

Keywords: layer manager added
Milestone: 6.4.47.0.0

Please check with the recent GRASS 7 (trunk), there is "make copy in the current mapset" for maps outside current mapset. Also, the context menu is pretty long already, so adding 2-3 new items is not ideal. Do you have any other idea how to solve this? Some concrete GUI design would be nice. For example, there is an idea of separate GRASS Catalog for managing maps and projections, but this is far from being implemented and it might be overkill for your request.

comment:3 by pvanbosgeo, 11 years ago

If I may add my opinion, I think adding these 2-3 items to the context menu would be a great addition. The easy of use this would offer would easily outweigh, i.m.h.o., the possible disadvantage of a longer context menu (I actually think it isn't that long in any case).

If the length of the context menu is really a problem, an alternative could maybe to have two or three buttons next to the layer name (now there is one, which offers the same context menu as when using right click). Using e.g., three buttons, one can have one for all options related to the visualization (opacity, zoom, rename, remove, etc), one for report options (profile, metadata, histogram) and one for file / data-set operations. Just my 2ct.

comment:4 by wenzeslaus, 10 years ago

Please check also Data Catalog tab in available in trunk (7.1), it needs some feedback.

comment:5 by martinl, 9 years ago

Milestone: 7.0.07.1.0

comment:6 by neteler, 9 years ago

Milestone: 7.1.07.2.0

Milestone renamed

comment:7 by neteler, 8 years ago

Milestone: 7.2.07.2.1

Ticket retargeted after milestone closed

comment:8 by martinl, 8 years ago

Milestone: 7.2.17.2.2

comment:9 by martinl, 7 years ago

any changes (e.g. renaming) shall be reflected in the layer tree. 

This issue is still valid.

1) add a map to layer tree

2) go to Data Catalog and rename

3) layer item in layer tree is invalid (map does not exists)

This should be fixed.

comment:10 by martinl, 7 years ago

Milestone: 7.2.27.4.0

All enhancement tickets should be assigned to 7.4 milestone.

comment:11 by neteler, 7 years ago

Milestone: 7.4.07.4.1

Ticket retargeted after milestone closed

comment:12 by neteler, 7 years ago

Milestone: 7.4.17.4.2

comment:13 by martinl, 6 years ago

Milestone: 7.4.27.6.0

All enhancement tickets should be assigned to 7.6 milestone.

comment:14 by martinl, 6 years ago

Milestone: 7.6.07.6.1

Ticket retargeted after milestone closed

comment:15 by martinl, 6 years ago

Milestone: 7.6.17.6.2

Ticket retargeted after milestone closed

comment:16 by annakrat, 4 years ago

Resolution: fixed
Status: newclosed

Closed, this can be all done now in data catalog.

Note: See TracTickets for help on using tickets.