t.info(1grass)

πŸ’– t.info β€” bestie edition πŸ’–

okay so this is a page from the GRASS User's Manual β€” it's t.info(1grass), and I'm about to make it make sense for you, i promise.


✨ NAME ✨

t.info β€” Lists information about space time datasets and maps. that's it, that's the whole thing, and she does it flawlessly πŸ’…


🏷️ 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 in shell script style
  • -h β€” Print history information in human readable shell style for space time datasets
  • -d β€” Print information about the temporal DBMI interface and exit
  • --help β€” Print usage summary
  • --verbose β€” Verbose module output
  • --quiet β€” Quiet module output
  • --ui β€” Force launching GUI dialog

πŸ¦‹ Parameters:

  • input=name [required] β€” Name of an existing space time dataset or map
  • type=name β€” Type of the input space time dataset
    • Options: strds, str3ds, stvds, raster, raster_3d, vector
    • Default: strds

πŸ‘‘ DESCRIPTION πŸ‘‘

t.info spills ALL the tea about any dataset that's registered in the temporal database β€” either in human readable style or shell script style, your call bestie. when we say "datasets" we mean raster, 3D raster and vector maps, plus their corresponding space time datasets (STRDS, STR3DS and STVDS). iconic lineup, no notes πŸ’–

so what does she actually report? only what's stored in the temporal database β€” which is:

  • basic information (id, name, mapset, creator, creation time, temporal type)
  • the temporal and spatial extent
  • dataset type specific metadata

and here's the important part, don't skip this ⚠️ β€” if you want the detailed info about raster, 3D raster and vector maps, you have to go use r.info, r3.info, v.info yourself. why? because not all map specific information and metadata are stored in the temporal database. so t.info literally cannot give you what she was never given. main character energy but with boundaries 🫢

plus β€” bonus β€” she can also report info about the chosen temporal database backend if you want it.


πŸ“ NOTES πŸ“

Temporal databases stored in other mapsets? totally usable, bestie, as long as they're in your current mapset search path. that's managed with g.mapsets, iykyk. 🌈


πŸ’« EXAMPLES πŸ’«

Temporal DBMI information πŸ”₯

In order to obtain information about temporal DBMI backend, run:

t.info -d
 +------------------- 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
 +-------------------- 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"
 |
 +----------------------------------------------------------------------------+

quick vocab check πŸ“š β€” the "granularity" is the smallest gap size between the found time instances, i.e. it the greatest common divisor between all gaps in the time series. (yes, that grammatical quirk is theirs, i'm keeping it fr fr)

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
 +-------------------- 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 one only shows up when semantic labels have been assigned to registered raster maps β€” by r.semantic.label or the t.register module. cute, conditional, slay.

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)

Latest change: Thursday Dec 18 07:11:47 2025 in commit: cf870a5e49fd2643a55de543467edf5c2e61d640

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

Β© 2003-2026 GRASS Development Team, GRASS 8.5.0 Reference Manual


and that's the whole page bestie 🫢 this was the t.info(1grass) man page from the GRASS 8.5.0 Reference Manual β€” go forth and inspect your temporal datasets, you're gonna eat πŸ’…βœ¨πŸŒˆ

πŸ“¦ where this page comes from