t.unregister(1)

πŸ’… t.unregister β€” the GRASS GIS girlies' guide (section 1 of the manual, iykyk)

okay so bestie, you know how your temporal database is basically a whole closet and sometimes a map ends up hanging in the wrong section? t.unregister is the module that takes it off the rack. It's from the GRASS GIS User's Manual, and it's giving cleanup era ✨


πŸŽ€ NAME πŸŽ€

t.unregister β€” unregisters raster, vector and raster3d maps from the temporal database or a specific space time dataset. literally it's the "girl, you're not on this list anymore" module πŸ’…


πŸ”‘ KEYWORDS πŸ”‘

temporal, map management, unregister, time


✨ SYNOPSIS ✨

t.unregister
t.unregister --help
t.unregister  [input=name]   [file=name]   [type=name]
[maps=name[,name,...]]   [--help]  [--verbose]  [--quiet]  [--ui]

🫢 Flags:

  • --help β€” print usage summary. your lil cheat sheet πŸ₯°
  • --verbose β€” verbose module output. it tells you everything, no cap
  • --quiet β€” quiet module output. shhh 🀫
  • --ui β€” force launching GUI dialog. for the visual girlies πŸŽ€

🌸 Parameters:

  • input=name β€” name of the input space time dataset
  • file=name β€” input file with map names, one per line
  • type=name β€” type of the input map. options: raster, vector, raster_3d. default: raster
  • maps=name[,name,...] β€” name(s) of existing raster, vector or raster3d map(s) to unregister

πŸ’– DESCRIPTION πŸ’–

The t.unregister module is designed to unregister raster, 3D raster and vector map layers from space time datasets and the temporal database. periodt. ✨

A map layer that should be unregistered from the temporal database can be specified as a list of comma separated map names, or by using a text file that contains one map layer name per line. By default the map type that should be unregistered is set to raster. The option type must be used to specify 3D raster or vector map layer types. no shortcuts, bestie, you gotta say what it is πŸ¦‹


πŸ“„ INPUT FILE FORMAT πŸ“„

Specification of map names:

a1
a2
a3
a4
a5
a6

⚠️ NOTE

In case the input option is used to specify a space time dataset, the maps are only unregistered from the space time dataset, but not from the temporal database. The reason is that maps can be registered in multiple space time datasets and there is a need to unregister them from a specific STDS without affecting other STDS.

like, the map is still in the database's group chat, it just left this one STDS. iconic but careful πŸ’€


🌈 EXAMPLE 🌈

In this example a precipitation map it is registered into temperature dataset, so the wrong map will be unregister.

t.register -i type=raster input=tempmean_monthly@climate_2009_2012 \
    maps=2012_01_precip \
    start="2013-01-01" increment="1 month"
# We unregister raster map 2012_01_precip from a space time dataset,
# the raster maps are still present in the temporal database
t.unregister type=raster input=tempmean_monthly@climate_2009_2012 maps=2012_01_precip
# We unregister raster map 2012_01_precip from the temporal database, hence
# the time stamps are removed
t.unregister type=raster maps=2012_01_precip

see how the first one is a soft launch and the second one is a full block? that's the difference, bestie πŸ‘‘


πŸ‘€ SEE ALSO πŸ‘€

t.create, t.info


πŸ‘‘ AUTHOR πŸ‘‘

SΓΆren Gebbert, ThΓΌnen Institute of Climate-Smart Agriculture β€” thank you for your service πŸ«‘πŸ’–


πŸ’» SOURCE CODE πŸ’»

Available at: t.unregister 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


okay that's the whole page, mwah πŸ’‹ this was GRASS 8.4.2, t.unregister(1), and the tea was accessed Saturday Jan 17 05:41:53 2026, brought to you by the GRASS Development Team Β© 2003-2025 β€” go unregister something, slay πŸ¦‹βœ¨

πŸ“¦ where this page comes from