#3668: gselect for space data dataset stop working when creating new mapset
-------------------------------+-------------------------
Reporter: martinl | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.4.2
Component: wxGUI | Version: 7.4.0
Keywords: temporal, gselect | CPU: Unspecified
Platform: Unspecified |
-------------------------------+-------------------------
Steps to reproduce:
1. open t.info dialog and select dataset, works
2. create new mapset (Settings -> GRASS working environment -> Create new
mapset)
3. open t.info and select dataset, fails with
{{{
GRASS_INFO_MESSAGE(16125,1): ERROR: Unable to execute sql statement. You
have no permission to access mapset <test>, or mapset <test> has no
temporal database. Accessible mapsets are: <modis>
GRASS_INFO_END(16125,1)
Temporal GIS error:
Unable to execute sql statement. You have no permission to access mapset
<test>, or mapset <test> has no temporal database. Accessible mapsets are:
<modis>
...
Traceback (most recent call last):
File "/opt/src/grass7_trunk/dist.x86_64-pc-linux-
gnu/gui/wxpython/gui_core/gselect.py", line 448, in OnPopup
self.GetElementList(selected, exclude)
File "/opt/src/grass7_trunk/dist.x86_64-pc-linux-
gnu/gui/wxpython/gui_core/gselect.py", line 460, in GetElementList
self._getElementList(self.type, self.mapsets, elements, exclude)
File "/opt/src/grass7_trunk/dist.x86_64-pc-linux-
gnu/gui/wxpython/gui_core/gselect.py", line 550, in _getElementList
if mapset not in filesdict:
TypeError: argument of type 'NoneType' is not iterable
}}}
#3668: gselect for space data dataset stop working when creating new mapset
--------------------------+-------------------------------
Reporter: martinl | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.4.2
Component: wxGUI | Version: 7.4.0
Resolution: | Keywords: temporal, gselect
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------------
Comment (by martinl):
It seems that only st datasets in the path can be accessed. There is
inconsistency compared to raster/vector data you can access even its
mapset is not the path.
{{{
g.mapsets -p
Accessible mapsets:
test PERMANENT
t.info modis
WARNING: Temporal database connection defined as:
/home/user/grassdata/oslo-region/test/tgis/sqlite.db
But database file does not exist.
Creating temporal database:
/home/user/grassdata/oslo-region/test/tgis/sqlite.db
ERROR: Dataset <modis@test> not found in temporal database
g.mapsets map=modis
g.mapsets -p
Accessible mapsets:
test PERMANENT modis
t.info modis@modis
+-------------------- Space Time Raster Dataset
-----------------------------+
|
|
+-------------------- Basic information
-------------------------------------+
| Id: ........................ modis@modis
...
}}}
Raster or vector data can be access even the mapset is not in the path.
{{{
g.mapsets -p
Accessible mapsets:
test PERMANENT