t.connect(1grass)

✨ t.connect ✨

okay bestie, so this is t.connect from the GRASS User's Manual 💖 it's the little tool that handles your general temporal GIS database connection for the current mapset. yeah. that's the vibe.

🏷️ NAME

t.connect — prints/sets the general temporal GIS database connection for the 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 the current connection parameters and dip out ✌️
• -c — check the connection parameters, set them if they're uninitialized, and exit. it's giving "trust but verify"
• -d — set from default settings and exit. heads up: this overwrites your current settings if they're already initialized 😳
• -g — print the current connection parameter in shell style and exit 🐚
• --help — print usage summary
• --verbose — verbose module output (she's chatty 💬)
• --quiet — quiet module output (she's mysterious 🤫)
• --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

so t.connect lets you set the temporal database connection. the default setting? your temporal database of type sqlite3 lives right there in the current mapset directory. cozy. 🏠

the -p flag displays the current temporal database connection parameters. periodt.

the -pg flag displays the current temporal database connection parameters using shell style. 🐚✨

the -c flag silently checks whether the temporal database connection parameters have been set, and if they haven't, it sets them to use GRASS's default values. no drama, no output, just doing her job 🫶

---

📝 NOTES

setting the connection with t.connect will not test the connection for validity. so like… a database connection will not be established. it's just writing down the address, not knocking on the door 🚪😭

the connection values are stored in the mapset's VAR file. the -d flag sets the default TGIS connection parameters. a SQLite database "tgis/sqlite.db" will be created in the current mapset directory. and the way it gets tucked into the "tgis" sub-directory so it doesn't interfere with the sqlite3 database used for vector attribute storage? iconic. no cap. 👑

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 using a PostgreSQL connection instead. that's the upgrade arc. 🔥

be aware that you have to set the PostgreSQL connection explicitly in every mapset that should store temporal information in the temporal database. every single one, bestie. don't skip 💀

PostgreSQL and SQLite databases can not be mixed in a project. ✋🚫 do not attempt. it's giving chaos.

---

🧪 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: Thursday Nov 06 22:27:54 2025 in commit: 298b38614712934179355ea767403d6bfea8f5f9

main index | temporal index | topics index | keywords index | graphical index | full index

---

okay that's the whole thing, mwah 💋 this was GRASS 8.5.0 (yes the source/version info is right there, we said it), the manual is © 2003-2026 GRASS Development Team, GRASS 8.5.0 Reference Manual, and the page is literally called t.connect(1grass). slay, go set up your temporal database responsibly 🌈✨