[GRASS-dev] [GRASS GIS] #3668: gselect for space data dataset stop working when creating new mapset

GRASS GIS trac at osgeo.org
Fri Sep 28 00:39:39 PDT 2018


#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 at test> not found in temporal database

 g.mapsets map=modis

 g.mapsets -p
 Accessible mapsets:
 test PERMANENT modis

 t.info modis at modis
  +-------------------- Space Time Raster Dataset
 -----------------------------+
  |
 |
  +-------------------- Basic information
 -------------------------------------+
  | Id: ........................ modis at modis
 ...
 }}}

 Raster or vector data can be access even the mapset is not in the path.

 {{{
 g.mapsets -p
 Accessible mapsets:
 test PERMANENT

 r.info rast_map at modis
 +----------------------------------------------------------------------------+
  | Map:      rast_map at modis                 Date: Fri Sep 28 09:37:26 2018
 |
 ...
 }}}

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/3668#comment:1>
GRASS GIS <https://grass.osgeo.org>



More information about the grass-dev mailing list