Additionally, a note about rangemap - in the search from your question, a $2 item will appear both in the 1-2 and the 2-3 category because the ranges are both inclusive. If that's undesired behaviour you can replace the rangemap with a case expression like so: ... | eval range = case(value < 1, "<$1", value < 2, "$1-$2", ...) That way a $2 item will only be listed in $2-$3, the upper bounds of each range are treated as non-inclusive by the less-than rather than a less-than-or-equal used by rangemap. The lookup suggested by @dwaddle is still required when using case instead of rangemap. ... View more