<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 13, 2016 at 5:35 PM, Anna Petrášová <span dir="ltr"><<a href="mailto:kratochanna@gmail.com" target="_blank">kratochanna@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, Apr 13, 2016 at 11:31 AM, Paulo van Breugel<br>
<div><div class="h5"><<a href="mailto:p.vanbreugel@gmail.com">p.vanbreugel@gmail.com</a>> wrote:<br>
><br>
><br>
> On 13-04-16 15:27, Anna Petrášová wrote:<br>
>><br>
>> On Wed, Apr 13, 2016 at 2:43 AM, Paulo van Breugel<br>
>> <<a href="mailto:p.vanbreugel@gmail.com">p.vanbreugel@gmail.com</a>> wrote:<br>
>>><br>
>>><br>
>>> On 13-04-16 05:24, Anna Petrášová wrote:<br>
>>><br>
>>> On Tue, Apr 12, 2016 at 2:29 PM, Anna Petrášová <<a href="mailto:kratochanna@gmail.com">kratochanna@gmail.com</a>><br>
>>> wrote:<br>
>>><br>
>>> On Tue, Apr 12, 2016 at 2:21 PM, Paulo van Breugel<br>
>>> <<a href="mailto:p.vanbreugel@gmail.com">p.vanbreugel@gmail.com</a>> wrote:<br>
>>><br>
>>> On 12-04-16 18:21, Anna Petrášová wrote:<br>
>>><br>
>>> On Tue, Apr 12, 2016 at 10:52 AM, Paulo van Breugel<br>
>>> <<a href="mailto:p.vanbreugel@gmail.com">p.vanbreugel@gmail.com</a>> wrote:<br>
>>><br>
>>> Hi Anna<br>
>>><br>
>>> I just updated GRASS trunk version (GRASS GIS 7.1.svn r68252) to test the<br>
>>> data catalogue. However, when opening the data tab in the main GUI, after<br>
>>> some waiting, the GUI crashes with:<br>
>>><br>
>>> GRASS_INFO_ERROR(30614,1): Mapset <backup> does not exist<br>
>>><br>
>>> this error comes from g.list mapset=backup ...<br>
>>><br>
>>> and 'backup' comes from running 'g.mapsets -l' for each location.<br>
>>> Could you run it in the problematic location? Do you get then<br>
>>> 'backup'? Also you can try to switch on debug mode.<br>
>>><br>
>>> Found the problem. In one of the locations I had a copy of a mapset<br>
>>> folder<br>
>>> 'Dispersal' which I named 'Dispersal backup', so it is the space in the<br>
>>> name<br>
>>> of the second one that caused the problem.<br>
>>><br>
>>> I'll try to reproduce it and see if it can be handle this situation<br>
>>> better<br>
>>><br>
>>> I don't know what the rest of the errors mean. If you find the<br>
>>> problem, I can try to reproduce it.<br>
>>><br>
>>> Anna<br>
>>><br>
>>> Weird, I created a mapset with space in the name and everything works...<br>
>>><br>
>>><br>
>>> When I have a mapset with space, e.g., 'Dispersal backup', and I open for<br>
>>> the first time the data tab in the main GUI, grass tries to look for a<br>
>>> mapset 'Dispersal' and a mapset 'backup' (underlined below). Note that<br>
>>> there<br>
>>> also was a real mapset 'Dispersal', not sure if that makes a difference.<br>
>>><br>
>>> D1/5: grass.script.core.start_command(): g.list --q -mt<br>
>>> type=raster,raster_3d,vector<br>
>>><br>
>>> mapset=ConsStat,Dispersal,Dispersal,backup,EthiopiaJvdS,GeneticDistance,JvdS,LUCC,PERMANENT,climchange,samplesize<br>
>><br>
>> I fixed that, now it will list the maps in the mapsets correctly.<br>
><br>
> Hi, copying, renaming and displaying works great in the current location. I<br>
> can also copy and paste layers between mapsets of another location. I<br>
> cannot, however, copy maps from another location to the current<br>
> location/mapset. The context menu shows the copy option, and in the status<br>
> bar (or whatever you call the area with message at the bottom) there is the<br>
> message that the layer can be copied into the current mapset. However, the<br>
> 'paste' option is greyed out when right clicking on the current mapset.<br>
><br>
<br>
<br>
</div></div>Yes, that's how it is supposed to work now. We don't have reprojection<br>
between mapsets from different locations implemented there yet, that's<br>
why it doesn't allow it. Once this is implemented, the options will<br>
work. We could warn user about it, but I hope we can add the necessary<br>
functionality there soon.<br></blockquote><div><br></div><div>OK, that means the message in the bottom is wrong for now, but will be correct soon :-). In any case, I really like this functionality. I never think about using the data catalog, but I can see that changing now.<br><br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
><br>
>>><br>
>>><br>
>>><br>
>>> On 10-04-16 05:00, Anna Petrášová wrote:<br>
>>><br>
>>> Hi,<br>
>>><br>
>>> I was wondering what is the opinion about the new data catalog (in<br>
>>> trunk), specifically, whether users should be able to modify (copy,<br>
>>> rename, delete) maps from other mapsets and locations than the current<br>
>>> ones.<br>
>>><br>
>>> So now I could try out the new functionality. I can display or copy maps<br>
>>> from other mapsets, but only if in the same location. If I am in another<br>
>>> location, there is still the option to display or copy in the context<br>
>>> menu<br>
>>> (right click), but when selecting copy, there is the error message that<br>
>>> "failed to copy: action is allowed only within the same mapset". When<br>
>>> selecting 'display', the message is "failed to display: not in current<br>
>>> mapset or invalid layer".<br>
>>><br>
>>> sorry, I still haven't committed it yet, I haven't added the option to<br>
>>> change it from settings yet, I'll try to add it later today...<br>
>>><br>
>>> I committed the changes, please test...<br>
>>><br>
>>><br>
>>> When unlocking (clicking the lock), there is not context menu anymore at<br>
>>> right click. From the command line:<br>
>><br>
>><br>
>> Fixed, thanks<br>
>><br>
>>> GRASS 7.1.svn (nc_spm_08_grass7):~ > Traceback (most recent call last):<br>
>>><br>
>>> File<br>
>>> "/usr/local/grass7/grass-7.1.svn/gui/wxpython/gui_core/treeview.py",<br>
>>> line 58, in <lambda><br>
>>><br>
>>> self._emitSignal(evt.GetItem(), self.contextMenu))<br>
>>><br>
>>> File<br>
>>> "/usr/local/grass7/grass-7.1.svn/gui/wxpython/gui_core/treeview.py",<br>
>>> line 161, in _emitSignal<br>
>>><br>
>>> signal.emit(node=node, **kwargs)<br>
>>><br>
>>> File<br>
>>> "/usr/local/grass7/grass-7.1.svn/etc/python/grass/pydispatch/signal.py",<br>
>>> line 229, in emit<br>
>>><br>
>>> dispatcher.send(signal=self, *args, **kwargs)<br>
>>><br>
>>> File<br>
>>><br>
>>> "/usr/local/grass7/grass-7.1.svn/etc/python/grass/pydispatch/dispatcher.py",<br>
>>> line 349, in send<br>
>>><br>
>>> **named<br>
>>><br>
>>> File<br>
>>><br>
>>> "/usr/local/grass7/grass-7.1.svn/etc/python/grass/pydispatch/robustapply.py",<br>
>>> line 60, in robustApply<br>
>>><br>
>>> return receiver(*arguments, **named)<br>
>>><br>
>>> File<br>
>>> "/usr/local/grass7/grass-7.1.svn/gui/wxpython/datacatalog/tree.py",<br>
>>> line 363, in OnRightClick<br>
>>><br>
>>> self._popupMenuLayer()<br>
>>><br>
>>> File<br>
>>> "/usr/local/grass7/grass-7.1.svn/gui/wxpython/datacatalog/tree.py",<br>
>>> line 725, in _popupMenuLayer<br>
>>><br>
>>> self.selected_location.label == genv['LOCATION_NAME']:<br>
>>><br>
>>> UnboundLocalError: local variable 'genv' referenced before assignment<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> Anna<br>
>>><br>
>>><br>
>>><br>
>>> I find it very useful to edit any mapsets, but it goes against<br>
>>> the traditional GRASS approach. I have this (edit anything behavior)<br>
>>> implemented locally, but wanted to know before committing if people<br>
>>> agree with that.<br>
>>><br>
>>> Thanks,<br>
>>> Anna<br>
>>> _______________________________________________<br>
>>> grass-user mailing list<br>
>>> <a href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br>
>>> <a href="http://lists.osgeo.org/mailman/listinfo/grass-user" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/grass-user</a><br>
>>><br>
>>><br>
><br>
</div></div></blockquote></div><br></div></div>