GEOHASH

Returns members from a geospatial index as geohash strings.

Browse all commands · Upstream source documentation

Reference field	Value
Canonical name	GEOHASH
Catalog group	Geospatial commands
Upstream since	3.2.0 — upstream Redis/module version, not an ffkv release
Pinned catalog	Redis 8.10.0

Syntax

GEOHASH key [member [member ...]]

ffkv behavior and limits

Geo indexes use sorted-set storage and Morton encoding. Units and radius/box bounds are significant; distance results are floating-point estimates.

Source: README.md:281; src/engine/geospatial.rs; tests/bdd/features/geo.feature.

All requests share the 8 MiB framing/1,024-argument ingress limit; normal RESP replies have 64 MiB wire/logical budgets with bounded nesting/value counts. Management and Lua origins impose smaller budgets. These are not a process RSS cap. Catalog inclusion is not exhaustive option or wire-format parity. See limits and compatibility.

Upstream metadata

The following fields come from the pinned Redis metadata, not measured ffkv performance or an assertion that ffkv enforces every upstream flag. Running COMMAND INFO/COMMAND DOCS describe the current engine.

Upstream Redis complexity: O(1) for each member requested.

Upstream arity: -2 (includes the command name; a negative number is a minimum).

Command flags: READONLY.

ACL categories: GEO.

Argument structure

Argument	Type	Constraints / metadata
key	key	key_spec_index: 0
member	string	optional; multiple

Key specifications

Upstream key discovery descriptors (indexes are relative to the full command vector):

[
  {
    "flags": [
      "RO",
      "ACCESS"
    ],
    "begin_search": {
      "index": {
        "pos": 1
      }
    },
    "find_keys": {
      "range": {
        "lastkey": 0,
        "step": 1,
        "limit": 0
      }
    }
  }
]

Additional pinned upstream metadata

{
  "group": "geo",
  "since": "3.2.0"
}

Metadata source · Local snapshot: src/command_metadata.json, key geohash.

BDD coverage and source examples

These are source observations, not a test run performed by this documentation build. A tag identifies scenario intent; an extracted vector identifies a command invocation, which may intentionally produce an error. Scenarios may require setup, multiple connections, persistence, cluster nodes or native-module fixtures.

• Coordinates and hashes identify indexed members and absent locations — tests/bdd/features/geo.feature:5; command tag and invocation observed.
• Radius queries honor coordinate and member centers and distance ordering — tests/bdd/features/geo.feature:70; invocation observed.

Extracted command vectors

The following JSON arrays are the test harness’s argument vectors, not shell commands. Numeric arguments are converted by the harness; objects of the form {"base64":"…"} represent decoded binary bytes, not a literal JSON command argument. Preserve scenario setup and connection ordering. See the CLI guide for shell quoting and binary stdin. No reply is invented or inferred.

Coordinates and hashes identify indexed members and absent locations — tests/bdd/features/geo.feature:61 (I execute:)

[
  "GEOHASH",
  "sicily",
  "Palermo"
]

Next source assertion: the reply equals:

["sqc8b49rny0"]

Radius queries honor coordinate and member centers and distance ordering — tests/bdd/features/geo.feature:116 (I execute:)

[
  "GEOHASH",
  "nearby",
  "Palermo",
  "Catania"
]

Next source assertion: the reply equals:

["sqc8b49rny0",null]

Coordinates and hashes identify indexed members and absent locations — tests/bdd/features/geo.feature:31 (I execute:)

[
  "GEOHASH",
  "sicily",
  "Palermo",
  "Catania",
  "absent"
]

Next source assertion: the reply equals:

["sqc8b49rny0","sqdtr74hyu0",null]