GEOSEARCHSTORE

Queries a geospatial index for members inside an area of a box or a circle, optionally stores the result.

Browse all commands · Upstream source documentation

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

Syntax

GEOSEARCHSTORE destination source <FROMMEMBER member |
  FROMLONLAT longitude latitude> <BYRADIUS radius <M | KM | FT | MI>
  | BYBOX width height <M | KM | FT | MI>> [ASC | DESC] [COUNT count
  [ANY]] [STOREDIST]

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(N+log(M)) where N is the number of elements in the grid-aligned bounding box area around the shape provided as the filter and M is the number of items inside the shape

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

Command flags: WRITE, DENYOOM.

ACL categories: GEO.

Argument structure

Argument	Type	Constraints / metadata
destination	key	key_spec_index: 0
source	key	key_spec_index: 1
from	oneof	Required
↳ member	string	token: FROMMEMBER
↳ fromlonlat	block	token: FROMLONLAT
↳ ↳ longitude	double	Required
↳ ↳ latitude	double	Required
by	oneof	Required
↳ circle	block	Required
↳ ↳ radius	double	token: BYRADIUS
↳ ↳ unit	oneof	Required
↳ ↳ ↳ m	pure-token	token: m
↳ ↳ ↳ km	pure-token	token: km
↳ ↳ ↳ ft	pure-token	token: ft
↳ ↳ ↳ mi	pure-token	token: mi
↳ box	block	Required
↳ ↳ width	double	token: BYBOX
↳ ↳ height	double	Required
↳ ↳ unit	oneof	Required
↳ ↳ ↳ m	pure-token	token: m
↳ ↳ ↳ km	pure-token	token: km
↳ ↳ ↳ ft	pure-token	token: ft
↳ ↳ ↳ mi	pure-token	token: mi
order	oneof	optional
↳ asc	pure-token	token: ASC
↳ desc	pure-token	token: DESC
count-block	block	optional
↳ count	integer	token: COUNT
↳ any	pure-token	optional; token: ANY
storedist	pure-token	optional; token: STOREDIST

Key specifications

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

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

Additional pinned upstream metadata

{
  "group": "geo",
  "since": "6.2.0",
  "history": [
    [
      "7.0.0",
      "Added support for uppercase unit names."
    ]
  ]
}

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

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.

• Box search and stored distance scores replace a destination with selected members — tests/bdd/features/geo.feature:125; command tag and invocation observed.
• Underflowing geo arguments cannot delete an aliased source destination (Scenario Outline) — tests/bdd/features/geo.feature:165; command tag and invocation observed.
• Explicit zero and representable subnormal geo numbers are valid (Scenario Outline) — tests/bdd/features/geo.feature:200; command tag and 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.

Explicit zero and representable subnormal geo numbers are valid — tests/bdd/features/geo.feature:210 (I execute:)

Expanded from an actual Examples row: number=0.

[
  "GEOSEARCHSTORE",
  "geo",
  "geo",
  "FROMMEMBER",
  "a",
  "BYRADIUS",
  "0",
  "m"
]

Next source assertion: the reply equals:

1

Box search and stored distance scores replace a destination with selected members — tests/bdd/features/geo.feature:139 (I execute:)

[
  "GEOSEARCHSTORE",
  "nearby",
  "sicily",
  "FROMMEMBER",
  "Palermo",
  "BYRADIUS",
  200,
  "km",
  "STOREDIST"
]

Next source assertion: the reply equals:

2

Underflowing geo arguments cannot delete an aliased source destination — tests/bdd/features/geo.feature:171 (I execute:)

Expanded from an actual Examples row: longitude=0, latitude=0, radius=1e-9999.

[
  "GEOSEARCHSTORE",
  "geo",
  "geo",
  "FROMLONLAT",
  "0",
  "0",
  "BYRADIUS",
  "1e-9999",
  "m"
]

Next source assertion: the reply is an error with code “ERR”