t.connect(1)

💖 t.connect(1) 💖

okay bestie, welcome to the GRASS GIS User's Manual — yes, the whole thing, and today's main character is t.connect. It's a temporal lil guy, filed under temporal, settings, metadata 🗂️✨

---

✨ NAME ✨

t.connect — prints and/or sets the general temporal GIS database connection for the current mapset. That's it, that's the job. 💅

---

🌸 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. exit stage left 🚪
• -c — Check the connection parameters, and if they're uninitialized, set them, then exit. Lowkey the responsible friend. 🫶
• -d — Set everything from default settings and exit. It will overwrite your current settings if they're initialized, so, like, be aware bestie ⚠️
• -g — Print the current connection parameter in shell style and exit. Fancy formatting moment. 🐚✨
• --help — Print the usage summary. The classic. 💫
• --verbose — Verbose module output. It's giving talkative. 🗣️
• --quiet — Quiet module output. Shhh. 🤫
• --ui — Force launching the GUI dialog. Buttons and windows, slay. 🪟💖

---

🍓 Parameters 🍓

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

---

🌈 DESCRIPTION 🌈

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

The -p flag shows you the current temporal database connection parameters. Peek at the vibes. 👀

The -pg flag shows you those same current temporal database connection parameters, but in shell style. Same tea, cuter cup. 🫖

The -c flag silently checks whether the temporal database connection parameters have been set — and if they haven't, it sets them to GRASS's default values. It just handles it. No drama. 🤐💅

---

💀 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 giving manifesting, not doing. 😭

The connection values are stored in the mapset's VAR file. The -d flag sets the default TGIS connection parameters, and a SQLite database "tgis/sqlite.db" will be created in the current mapset directory. It lives in the "tgis" sub-directory specifically so it does not interfere with the sqlite3 database used for vector attribute storage. Respectful roommates fr fr. 🏡✨

If you've got tens of thousands of maps to register in the temporal database, or you need concurrent read and write access in the temporal database — bestie, consider using 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. Every single one. No shortcuts. 🚨

PostgreSQL and SQLite databases can not be mixed in a project. Pick a lane, bestie. 🚫

---

⭐ EXAMPLES ⭐

🐚 SQLite

The SQLite database is created automatically when you use it 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 you're 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)

Accessed: Saturday Jan 17 05:41:53 2026

Main index | Temporal index | Topics index | Keywords index | Graphical index | Full index

---

© 2003-2025 GRASS Development Team, GRASS GIS 8.4.2 Reference Manual

and that's the whole page, bestie — GRASS 8.4.2, t.connect(1), no cap, that's the footer, mwah 💋🫶