t.unregister(1grass)

💖 t.unregister — the "actually, take that back" command 💖

okay bestie, so this is t.unregister from the GRASS User's Manual, and it's genuinely one of those tools that sounds boring but is lowkey essential. Its whole job? Unregistering raster, vector and raster3d maps from the temporal database, or from one specific space time dataset. That's it. That's the gig. And it ate, fr fr. ✨

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 the usage summary, bestie. the little cheat sheet 💅
• --verbose — verbose module output, so it tells you everything it's doing
• --quiet — quiet module output. shhh. not a peep 🤫
• --ui — force launching the GUI dialog, if clicking is more your vibe

🦋 Parameters

• input=name — name of the input space time dataset
• file=name — an input file with map names, one lil map per line
• type=name — the 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) you wanna unregister

---

👑 DESCRIPTION 👑

So the t.unregister module is designed to unregister raster, 3D raster and vector map layers from space time datasets and the temporal database. Like, it's the "undo my registration" button, and honestly, we've all needed one of those. 🫶

Now — the map layer you want to unregister from the temporal database can be specified two ways: as a list of comma separated map names, or using a text file that contains one map layer name per line. Both are valid, pick your fighter. 💖

By default the map type that gets unregistered is set to raster. So if you're rolling with 3D raster or vector map layers, the option type must be used to specify those types. don't forget it, or you'll be unregistering the wrong type and crying about it. 😭

---

✨ 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? Maps can be registered in multiple space time datasets, and there's a real need to unregister them from a specific STDS without affecting the other STDS. so like, chill, nothing else gets touched. 💅

---

🍓 EXAMPLE 🍓

okay so in this example a precipitation map it is registered into temperature dataset (oops), so the wrong map will be unregister. it's giving "who put that there". 🙈

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 just pulls it out of the STDS and the second one fully lets it go from the temporal database? the range. the nuance. iconic. ⭐

---

💜 SEE ALSO 💜

• t.create
• t.info

---

🌸 AUTHOR 🌸

Sören Gebbert, Thünen Institute of Climate-Smart Agriculture — thank you for your service, king 👑

---

🧚 SOURCE CODE 🧚

Available at: t.unregister source code (history)

Latest change: Tuesday Feb 25 01:48:02 2025 in commit: 9013c3d897d7f4debcc23031c88eb6d3e7d1cc57

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 t.unregister(1grass) page, bestie — this is GRASS 8.5.0, so go forth and unregister responsibly. no cap. 💖✨🎀🦋🌸💅🫶😭🔥👑🌈⭐💀🍓🧚💜