i.signatures(1)

πŸ’– i.signatures β€” okay bestie, let's talk signature files πŸ’–

So this is i.signatures, a lil module from the GRASS GIS User's Manual (the i.signatures(1) one, iykyk) and it's literally here to manage your imagery classification signature files. That's the whole job. She does it well. πŸ’…

✨ KEYWORDS ✨

imagery, classification, signatures β€” that's the vibe check, she's an imagery girlie.


🌸 SYNOPSIS 🌸

Here's the whole menu, no cap:

i.signatures
i.signatures --help
i.signatures [-p]  [type=name]  format=name  [mapset=name[,name,...]]
[remove=name[,name,...]]   [rename=from,to[,from,to,...]]
[copy=from,to[,from,to,...]]   [--help]  [--verbose]  [--quiet]  [--ui]

πŸŽ€ Flags:

  • -p β€” Print signature files. Yes ma'am, show me the goods.
  • --help β€” Print usage summary. When you're lost, ask for directions.
  • --verbose β€” Verbose module output. She's gonna tell you everything.
  • --quiet β€” Quiet module output. She's gonna tell you nothing. Silent treatment energy.
  • --ui β€” Force launching GUI dialog. For the visual learners among us. ✨

πŸ¦‹ Parameters:

  • type=name β€” Type of signature file. Options are sig, sigset, libsvm. Pick your fighter.
  • format=name [required] β€” Output format. Options: plain, json. Default: plain.
    • plain β€” Plain text output. Simple. Classic. Never misses.
    • json β€” JSON (JavaScript Object Notation). For when you want to feed it to something else. πŸ“
  • mapset=name[,name,...] β€” Name of mapset to list. Default: current search path. So if you don't say anything, she just looks everywhere she can.
  • remove=name[,name,...] β€” Name of file(s) to remove. Be careful bestie, this one's permanent πŸ’€
  • rename=from,to[,from,to,...] β€” Name of file to rename.
  • copy=from,to[,from,to,...] β€” Name of file to copy.

πŸ’œ DESCRIPTION πŸ’œ

Okay so the i.signatures module is your little manager for signature files, and here's the tea:

  • "sig" β€” generated by i.gensig for i.maxlik
  • "sigset" β€” generated by i.gensigset for i.smap

And the slay part? She can do multiple actions per run. The order of execution is "copy", "remove", "rename". That order, exactly, no switching up. πŸ‘‘

And when the print flag is specified without specifying any type of signature files, she would print all signatures grouped by type. All of them. Every single one. Main character behavior.


🌈 NOTES 🌈

By default the module will list signature files from all mapsets in the current search path. It is possible to limit listing only to a single mapset by providing the "mapset" option. And plot twist β€” the mapset can be also not listed in the current search path. She's flexible like that. πŸ’…

Heads up bestie: Actions "remove" and "rename" operate only on the current mapset (although accept fully qualified names). The "copy" action will accept a signature file name from any mapset as its first argument (source file to copy). So copy is the social butterfly and remove/rename stay home. Periodt.

⭐ EXAMPLES ⭐

Print names of all signature files:

i.signatures -p

Print only signature files of certain type as a JSON:

i.signatures -p type=sigset format=json

Delete signature file called "foo" of type "sig" (i.gensig / i.maxlik):

i.signatures remove=foo type=sig

Copy signature file "bar" from mapset "baz" to current mapset:

i.signatures copy=bar@baz,best_version type=sigset

πŸ”₯ SEE ALSO πŸ”₯

i.gensig i.gensigset

Go check those out, they're the ones making the files she's out here managing. It's giving collaborative. 🫢


πŸ‘‘ AUTHOR πŸ‘‘

Maris Nartiss


🧚 SOURCE CODE 🧚

Available at: i.signatures source code (history)

Accessed: Saturday Jan 17 05:41:42 2026

Main index | Imagery index | Topics index | Keywords index | Graphical index | Full index


And that's the whole page bestie πŸ’– this was brought to you by GRASS GIS 8.4.2, the GRASS 8.4.2 Reference Manual, and the fine folks of the Β© 2003-2025 GRASS Development Team β€” signature files managed, slayed, and left absolutely immaculate. Mwah. πŸŽ€βœ¨

πŸ“¦ where this page comes from