Prefer GEOSEARCH with FROMMEMBER and BYRADIUS in new code: GEOSEARCH <key> FROMMEMBER <member> BYRADIUS <radius> (m | km | ft | mi). In place of STORE and STOREDIST, use GEOSEARCHSTORE with the same query.
Use GEORADIUSBYMEMBER to find the members of a geospatial index that lie within a given radius of another member.
It works exactly like GEORADIUS except that the center is the stored position of a member instead of an explicit coordinate pair, which saves a lookup when the reference point is already in the index (a store, a driver, a landmark). The reference member itself always matches, since its distance from itself is zero, so remember to filter it out or ask for one result more than you need.
The same WITHCOORD, WITHDIST, WITHHASH, COUNT, sorting, and STORE or STOREDIST options apply.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
<key> | Yes | No | Redis key targeted by the command. |
<member> | Yes | No | Member name. |
<radius> | Yes | No | Search radius, in the unit given after it. |
(m | km | ft | mi) | Yes | No | Distance unit: m (meters), km (kilometers), ft (feet), or mi (miles). |
WITHCOORD | No | No | Also return the longitude and latitude of each match. |
WITHDIST | No | No | Also return the distance from the center, in the requested unit. |
WITHHASH | No | No | Also return the raw 52-bit geohash score of each match. |
COUNT <count> [ANY] | No | No | Return at most <count> matches. ANY returns as soon as enough matches are found, instead of sorting every match first. |
(ASC | DESC) | No | No | Sort the matches by distance from the center: ASC (nearest first) or DESC (farthest first). Unsorted when omitted. |
(STORE <storekey> | STOREDIST <storedistkey>) | No | No | Store the matches in a sorted set instead of returning them: STORE scores them by geohash, so the destination stays a geospatial index, and STOREDIST scores them by their distance from the center. |
Response#
The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
| Protocol | Reply |
|---|---|
| RESP2 | Array of bulk-string members or member-detail arrays, or Integer when storing |
| RESP3 | Array of bulk-string members or member-detail arrays, or Integer when storing |
Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
Examples#
TCP examples use the TLS REDIS_URL from the Upstash console. REST examples use UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN.
Redis CLI
@upstash/redis
This command is not supported yet in @upstash/redis.