GEORADIUSBYMEMBER_RO
Deprecated: use GEOSEARCH instead.
GEORADIUSBYMEMBER_RO key member radius <M | KM | FT | MI> [WITHCOORD] [WITHDIST] [WITHHASH] [COUNT count [ANY]] [ASC | DESC]
- Group
- Geospatial
- Complexity
- O(N + log M), N being the members in the area searched
- Arity
- -5 (at least 5 words, counting the command name)
- Flags
- read-only
- Keys
- first 1, last 1, step 1
- HotKV Cloud
- All plans
- On-Premise
- no license needed
GEORADIUSBYMEMBER_RO works like
GEORADIUSBYMEMBER but is flagged as a
read-only command, so it runs on read-only replicas and in read-only scripts.
It does not accept STORE or STOREDIST.
New code should use GEOSEARCH with FROMMEMBER and
BYRADIUS.
Options
Section titled “Options”WITHCOORD, WITHDIST, WITHHASH, COUNT count [ANY], ASC and DESC, as
for GEORADIUS.
Return value
Section titled “Return value”| Case | RESP2 | RESP3 |
|---|---|---|
| Matches | Array of members, or of arrays with the extra fields | Same; coordinates are doubles |
| No such key | Empty array | Empty array |
STORE or STOREDIST reply ERR syntax error. A member that is not in a
non-empty set replies ERR could not decode requested zset member. Other
errors are those of GEORADIUS, including WRONGTYPE.
Examples
Section titled “Examples”127.0.0.1:6379> GEOADD cities 2.3522 48.8566 paris 4.3517 50.8503 brussels(integer) 2127.0.0.1:6379> GEORADIUSBYMEMBER_RO cities brussels 300 km WITHDIST1) 1) "brussels" 2) "0.0000"2) 1) "paris" 2) "264.0499"Compatibility
Section titled “Compatibility”Same as Redis 7 and Valkey 8, where it is also deprecated. Results are always sorted by distance; see GEOSEARCH.
See also
Section titled “See also”Was this page helpful?
Thanks for the feedback.