t.info(1)

📦
version 8.4.2 · 8 versions
, in fedora 44

💖 t.info(1) — GRASS GIS User's Manual 💖

okay bestie, sit down, grab a boba, because we're about to read the temporal gossip column of GRASS GIS. this is from the GRASS GIS User's Manual, and it's literally just "tell me everything about this dataset" energy. 🫶

✨ NAME ✨

t.info — lists info about space time datasets and maps. like, the whole ~vibe report~. 💅

🏷️ KEYWORDS 🏷️

temporal, metadata, extent, time

🌸 SYNOPSIS 🌸

t.info
t.info --help
t.info [-ghd] input=name  [type=name]   [--help]  [--verbose]  [--quiet]
[--ui]

🎀 Flags 🎀

  • -g — print it in shell script style, so your scripts can eat it up 🍓
  • -h — print history info in human readable shell style, but only for space time datasets
  • -d — print info about the temporal DBMI interface and then dip out (exit) 👋
  • --help — print the usage summary
  • --verbose — verbose module output (chatty mode, we love her)
  • --quiet — quiet module output (shy mode 🙈)
  • --ui — force launching the GUI dialog

🦋 Parameters 🦋

  • input=name [required] — name of an existing space time dataset or map. yeah she's required, no skipping, periodt.
  • type=name — the type of the input space time dataset
    • Options: strds, str3ds, stvds, raster, raster_3d, vector
    • Default: strds

👑 DESCRIPTION 👑

t.info reports information about any dataset that's registered in the temporal database — and it can do it in human readable style or shell script style. the datasets in question are raster, 3D raster and vector maps, plus their corresponding space time datasets (STRDS, STR3DS and STVDS). 🧚

so what does this module actually spill? it reports the information that is stored in the temporal database. that means:

  • basic info — id, name, mapset, creator, creation time, temporal type
  • the temporal extent and the spatial extent
  • dataset type specific metadata
⚠️ important bestie note: the user has to utilize r.info, r3.info, v.info to report detailed information about raster, 3D raster and vector maps, because not all map specific information and metadata are stored in the temporal database. t.info can't read minds, she only reads the temporal DB. 😭

plus, information about the chosen temporal database backend can be reported too. iconic.

📝 NOTES 📝

temporal databases stored in other mapsets can be used as long as they're in the user's current mapset search path — and that's managed with g.mapsets. no cap. 🗺️

🌈 EXAMPLES 🌈

💾 Temporal DBMI information

in order to obtain information about the temporal DBMI backend, run:

t.info -d

and you get this absolute beauty:

 +------------------- Temporal DBMI backend information ----------------------+
 | DBMI Python interface:...... sqlite3
 | Temporal database string:... /grassdata/nc_spm_temporal_workshop/climate_2000_2012/tgis/sqlite.db
 | SQL template path:.......... /usr/local/grass-7.0.0/etc/sql
 | tgis_db_version .......... 2
 | creation_time .......... 2014-11-22 20:06:46.863733
 | tgis_version .......... 2
 +----------------------------------------------------------------------------+

🗂️ Space time dataset information

in order to obtain information about a space time dataset, run:

t.info input=tempmean_monthly

and boom:

 +-------------------- Space Time Raster Dataset -----------------------------+
 |                                                                            |
 +-------------------- Basic information -------------------------------------+
 | Id: ........................ tempmean_monthly@climate_2000_2012
 | Name: ...................... tempmean_monthly
 | Mapset: .................... climate_2000_2012
 | Creator: ................... lucadelu
 | Temporal type: ............. absolute
 | Creation time: ............. 2014-11-27 08:50:48.443229
 | Modification time:.......... 2014-11-27 09:44:32.800282
 | Semantic type:.............. mean
 +-------------------- Absolute time -----------------------------------------+
 | Start time:................. 2009-01-01 00:00:00
 | End time:................... 2013-01-01 00:00:00
 | Granularity:................ 1 month
 | Temporal type of maps:...... interval
 +-------------------- Spatial extent ----------------------------------------+
 | North:...................... 320000.0
 | South:...................... 10000.0
 | East:.. .................... 935000.0
 | West:....................... 120000.0
 | Top:........................ 0.0
 | Bottom:..................... 0.0
 +-------------------- Metadata information ----------------------------------+
 | Raster register table:...... raster_map_register_d567423784c740bea1fba75dc7c0fa3d
 | North-South resolution min:. 500.0
 | North-South resolution max:. 500.0
 | East-west resolution min:... 500.0
 | East-west resolution max:... 500.0
 | Minimum value min:.......... -6.464337
 | Minimum value max:.......... 18.54137
 | Maximum value min:.......... 4.247691
 | Maximum value max:.......... 28.805381
 | Aggregation type:........... None
 | Number of registered maps:.. 48
 |
 | Title:
 | Monthly precipitation
 | Description:
 | Dataset with monthly precipitation
 | Command history:
 | # 2014-11-27 08:50:48
 | t.create type="strds" temporaltype="absolute"
 |     output="tempmean_monthly" title="Monthly precipitation"
 |     description="Dataset with monthly precipitation"
 | # 2014-11-27 09:44:32
 | t.register -i type="rast" input="tempmean_monthly" maps="2009_01_tempmean,...,2012_12_tempmean" start="2009-01-01" increment="1 months"
 |
 +----------------------------------------------------------------------------+

so about the granularity — it's the smallest gap size between the found time instances, i.e. it the greatest common divisor between all gaps in the time series. she's the math girlie of the group. ✨

🔍 Temporal maps information

in order to obtain information about a map in a space time dataset, run:

t.info input=2009_01_tempmean type=raster

and:

 +-------------------- Raster Dataset ----------------------------------------+
 |                                                                            |
 +-------------------- Basic information -------------------------------------+
 | Id: ........................ 2009_01_tempmean@climate_2000_2012
 | Name: ...................... 2009_01_tempmean
 | Mapset: .................... climate_2000_2012
 | Creator: ................... lucadelu
 | Temporal type: ............. absolute
 | Creation time: ............. 2014-11-27 09:44:26.280147
 +-------------------- Absolute time -----------------------------------------+
 | Start time:................. 2009-01-01 00:00:00
 | End time:................... 2009-02-01 00:00:00
 +-------------------- Spatial extent ----------------------------------------+
 | North:...................... 320000.0
 | South:...................... 10000.0
 | East:.. .................... 935000.0
 | West:....................... 120000.0
 | Top:........................ 0.0
 | Bottom:..................... 0.0
 +-------------------- Metadata information ----------------------------------+
 | Datatype:................... DCELL
 | Number of columns:.......... 620
 | Number of rows:............. 1630
 | Number of cells:............ 1010600
 | North-South resolution:..... 500.0
 | East-west resolution:....... 500.0
 | Minimum value:.............. -3.380823
 | Maximum value:.............. 7.426054
 | Registered datasets ........ tempmean_monthly@climate_2000_2012
 +----------------------------------------------------------------------------+

🏷️ Space time dataset with semantic labels assigned

this information is printed only when semantic labels have been assigned to registered raster maps by r.semantic.label or t.register module. 💜

t.info input=test
...
+-------------------- Metadata information ----------------------------------+
...
 | Number of registered bands:. 13
...

similarly for temporal maps information:

t.info input=T33UYP_20190331T094039_B01 type=raster
...
 +-------------------- Metadata information ----------------------------------+
 | Semantic label:............. S2_1
...

👀 SEE ALSO 👀

t.create, t.list, t.register, r.info, r3.info, v.info

✍️ AUTHOR ✍️

Sören Gebbert, Thünen Institute of Climate-Smart Agriculture

🔗 SOURCE CODE 🔗

Available at: t.info source code (history)

Accessed: Saturday Jan 17 05:41:53 2026

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

💖 that's the whole page bestie!! okay so this was t.info from GRASS GIS 8.4.2, the reference manual dated Saturday Jan 17 05:41:53 2026, © 2003-2025 GRASS Development Team. now go read your temporal database like the main character you are. slay, periodt, bye!! 💅✨🌸
📦 where this page comes from