r.quant(1grass)
π r.quant π β straight from the GRASS User's Manual
okay bestie, welcome to r.quant β the GRASS module that produces the quantization file for a floating-point map. that's it, that's the whole assignment, and she does it flawlessly. let's get into it π¦
β¨ NAME β¨
r.quant β produces the quantization file for a floating-point map. no cap, that's literally the name and the job. π
π·οΈ KEYWORDS π·οΈ
raster, statistics, quantization π
πΈ SYNOPSIS πΈ
r.quant
r.quant --help
r.quant [-tr] input=string[,string,...] [rules=name] [basemap=string]
[fprange=dmin,dmax] [range=min,max] [--help] [--verbose] [--quiet]
[--ui]
π Flags π
-tβ truncate floating point data. just chop it, no rounding, bye βοΈ-rβ round floating point data. she's polite, she rounds π«Ά--helpβ print usage summary. when u need the cheat sheet π--verboseβ verbose module output. she will tell u everything π£οΈ--quietβ quiet module output. shhh, main character silence π€«--uiβ force launching GUI dialog. buttons and sliders era π±οΈβ¨
π Parameters π
input=string[,string,...][required] β raster map(s) to be quantized. yes bestie, it's required, u literally cannot skip her πrules=nameβ path to rules file ("-"to read from stdin). yes, the literal hyphen means "read it from stdin", iconic behavior πbasemap=stringβ base map to take quant rules from. borrow the rules from another map, real sisterhood energy π―fprange=dmin,dmaxβ floating point range:dmin,dmaxπrange=min,maxβ integer range:min,maxπ’
π DESCRIPTION π
r.quant produces the quantization file for a floating-point map. that's the vibe, that's the mission. β¨
the map parameter defines the map for which the rules are to be created. and here's the tea π΅: if more than one map is specified, then this implies that the floating-point range is the minimum and maximum of all the maps together β unless either basemap=map or fprange=min,max is specified. so if u don't hand her a basemap or an fprange, she's out here calculating the range across literally all of them. she's thorough like that π
π Quant rules π
the quant rules have to be entered interactively. yes, it's giving conversation, not automation π
if rules is specified, the input has the form:
value1:value2:cat1:[cat2]
where value1 and value2 are floating point values and cat1 and cat2 are integers. if cat2 is missing, it is taken to be equal to cat1. and plot twist: all values can be "*" which means infinity. stars meaning infinity?? she's dramatic and correct at the same time πβ
β οΈ bestie, listen: it is an error to specify bothbasemapandfprange. pick a lane, queen, she will not do both π«π
π SEE ALSO π
r.supportr.null
go read those too, iykyk π
π«Ά AUTHORS π«Ά
- Michael Shapiro
- Olga Waupotitsch
- U.S.Army Construction Engineering Research Laboratory
legends, honestly. ate and left no crumbs π
π§ SOURCE CODE π§
Available at: r.quant source code (history) π
Latest change: Thursday May 08 20:58:05 2025 in commit:
4144ba81fa125e1549fc52e1cf5feb4fa004be8b
Main index | Raster index | Topics index | Keywords index | Graphical index | Full index
and that's the whole page, bestie!! π tysm for reading, mwah π oh also the cute little sign-off at the bottom of the original says Β© 2003-2026 GRASS Development Team, GRASS 8.5.0 Reference Manual, and the footer tag is GRASS 8.5.0 β so when u see r.quant(1grass), that's her. go quantize something, u got this βππ
π¦ where this page comes from
- alpine 3.24: grass-gis-doc 8.5.0-r1 Β· GPL-2.0-or-later
- ubuntu stonking: grass-doc 8.5.0-1ubuntu1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms