connect error in replacement of $MAPSET

[lucadelu]

Hi all,

when I try to use a different mapset then PERMANENT using $MAPSET variable it is not changed with the right value but a $MAPSET directory is create on the location path

[huhabla]

You can use:

eval `g.gisenv`

To set $GISDBASE, $LOCATION_NAME and $MAPSET

I will modify the code of t.connect so that instead of the shell variables $GISDBASE and $LOCATION_NAME the real path variables are set in the module help to reduce confusion.

t.connect accepts as database argument a string that defines a database connection. In case of sqlite this must be a path. t.connect will not substitute shell variables itself if they are not set.

[huhabla]

Replying to huhabla:

You can use:

eval `g.gisenv`

To set $GISDBASE, $LOCATION_NAME and $MAPSET

I will modify the code of t.connect so that instead of the shell variables $GISDBASE and $LOCATION_NAME the real path variables are set in the module help to reduce confusion.

Done in r58015

t.connect accepts as database argument a string that defines a database connection. In case of sqlite this must be a path. t.connect will not substitute shell variables itself if they are not set.

[lucadelu]

Replying to huhabla:

Replying to huhabla:

You can use:

eval `g.gisenv`

To set $GISDBASE, $LOCATION_NAME and $MAPSET

I will modify the code of t.connect so that instead of the shell variables $GISDBASE and $LOCATION_NAME the real path variables are set in the module help to reduce confusion.

Done in r58015

Sorry I don't understand what was done, I have the same behavior of yesterday, If I use

t.connect database='$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite/tgis.db'

the database is created in

/grassdata/eu_laea/$MAPSET/sqlite/tgis.db

The revision I'm using is 58021.

[huhabla]

This issue is hopefully fixed in r58024.

Now the temporal framework supports '$GISBASE/$LOCATION_NAME/$MAPSET' settings and will substitute them correctly. t.connect should show now the same behavior as db.connect.

[lucadelu]

Replying to huhabla:

This issue is hopefully fixed in r58024.

Fixed, thanks a lot