Upstash Documentation

GEORADIUSBYMEMBER

Find members within a radius of another member.
3 min read
Warning

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#

ArgumentRequiredRepeatableDescription
<key>YesNoRedis key targeted by the command.
<member>YesNoMember name.
<radius>YesNoSearch radius, in the unit given after it.
(m | km | ft | mi)YesNoDistance unit: m (meters), km (kilometers), ft (feet), or mi (miles).
WITHCOORDNoNoAlso return the longitude and latitude of each match.
WITHDISTNoNoAlso return the distance from the center, in the requested unit.
WITHHASHNoNoAlso return the raw 52-bit geohash score of each match.
COUNT <count> [ANY]NoNoReturn at most <count> matches. ANY returns as soon as enough matches are found, instead of sorting every match first.
(ASC | DESC)NoNoSort the matches by distance from the center: ASC (nearest first) or DESC (farthest first). Unsorted when omitted.
(STORE <storekey> | STOREDIST <storedistkey>)NoNoStore 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.

ProtocolReply
RESP2Array of bulk-string members or member-detail arrays, or Integer when storing
RESP3Array of bulk-string members or member-detail arrays, or Integer when storing
Note

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
Note

This command is not supported yet in @upstash/redis.

upstash_redis
ioredis
node-redis
redis-py
go-redis
jedis
redis-rs