t.connect - GRASS GIS manual

NAME

t.connect - Prints/sets general temporal GIS database connection for current mapset.

KEYWORDS

temporal, settings, metadata

SYNOPSIS

t.connect

t.connect --help

t.connect [-pcdg] [driver=name] [database=name] [--help] [--verbose] [--quiet] [--ui]

Flags:

-p: Print current connection parameters and exit
-c: Check connection parameters, set if uninitialized, and exit
-d: Set from default settings and exit; Overwrite current settings if initialized
-g: Print current connection parameter in shell style and exit
--help: Print usage summary
--verbose: Verbose module output
--quiet: Quiet module output
--ui: Force launching GUI dialog

Parameters:

driver=name: Name of database driver; Options: sqlite, pg; Default: sqlite
database=name: Name of database; Default: $GISDBASE/$LOCATION_NAME/$MAPSET/tgis/sqlite.db

DESCRIPTION
NOTES
EXAMPLES
- SQLite
- PostgreSQL
AUTHOR

DESCRIPTION

t.connect allows the user to set the temporal database connection. The default setting is that the temporal database of type sqlite3 is located in the current mapset directory.

The -p flag will display the current temporal database connection parameters.

The -pg flag will display the current temporal database connection parameters using shell style.

The -c flag will silently check if the temporal database connection parameters have been set, and if not will set them to use GRASS's default values.

NOTES

Setting the connection with t.connect will not test the connection for validity. Hence a database connection will not be established.

The connection values are stored in the mapset's VAR file. The -d flag will set the default TGIS connection parameters. A SQLite database "tgis/sqlite.db" will be created in the current mapset directory. It will be located in the "tgis" sub-directory to not interfere with the sqlite3 database used for vector attribute storage.

In case you have tens of thousands of maps to register in the temporal database or you need concurrent read and write access in the temporal database, consider to use a PostgreSQL connection instead.

Be aware that you have to set the PostgreSQL connection explicitly in every mapset that should store temporal information in the temporal database.

PostgreSQL and SQLite databases can not be mixed in a location.

EXAMPLES

SQLite

The SQLite database is created automatically when used the first time.

# use single quotes here
t.connect driver=sqlite database='$GISDBASE/$LOCATION_NAME/PERMANENT/tgis/sqlite.db'
t.connect -p
t.info -s

PostgreSQL

When using a PostgreSQL database, the user will need to specify the TGIS database connection for each mapset.

t.connect driver=pg database="dbname=grass_test user=soeren password=abcdefgh"
t.connect -p
t.info -s

AUTHOR

Soeren Gebbert, Thünen Institute of Climate-Smart Agriculture

SOURCE CODE

Available at: t.connect source code (history)

Latest change: Thu Feb 3 11:10:06 2022 in commit: 73413160a81ed43e7a5ca0dc16f0b56e450e9fef