As of Redis version 6.2.0, this command is regarded as deprecated.
It can be replaced by
GEOSEARCHSTORE with the
BYRADIUS argument when migrating or writing new code.
GEORADIUS key longitude latitude radius <M | KM | FT | MI> [WITHCOORD] [WITHDIST] [WITHHASH] [COUNT count [ANY]] [ASC | DESC] [STORE key | STOREDIST key]
- Available since:
- Time complexity:
- O(N+log(M)) where N is the number of elements inside the bounding box of the circular area delimited by center and radius and M is the number of items inside the index.
- ACL categories:
Return the members of a sorted set populated with geospatial information using
GEOADD, which are within the borders of the area specified with the center location and the maximum distance from the center (the radius).
This manual page also covers the
GEORADIUSBYMEMBER_RO variants (see the section below for more information).
The common use case for this command is to retrieve geospatial items near a specified point not farther than a given amount of meters (or other units). This allows, for example, to suggest mobile users of an application nearby places.
The radius is specified in one of the following units:
- m for meters.
- km for kilometers.
- mi for miles.
- ft for feet.
The command optionally returns additional information using the following options:
WITHDIST: Also return the distance of the returned items from the specified center. The distance is returned in the same unit as the unit specified as the radius argument of the command.
WITHCOORD: Also return the longitude,latitude coordinates of the matching items.
WITHHASH: Also return the raw geohash-encoded sorted set score of the item, in the form of a 52 bit unsigned integer. This is only useful for low level hacks or debugging and is otherwise of little interest for the general user.
The command default is to return unsorted items. Two different sorting methods can be invoked using the following two options:
ASC: Sort returned items from the nearest to the farthest, relative to the center.
DESC: Sort returned items from the farthest to the nearest, relative to the center.
By default all the matching items are returned. It is possible to limit the results to the first N matching items by using the COUNT
ANY is provided the command will return as soon as enough matches are found,
so the results may not be the ones closest to the specified point, but on the other hand, the effort invested by the server is significantly lower.
ANY is not provided, the command will perform an effort that is proportional to the number of items matching the specified area and sort them,
so to query very large areas with a very small
COUNT option may be slow even if just a few results are returned.
By default the command returns the items to the client. It is possible to store the results with one of these options:
STORE: Store the items in a sorted set populated with their geospatial information.
STOREDIST: Store the items in a sorted set populated with their distance from the center as a floating point number, in the same unit specified in the radius.
Array reply, specifically:
- Without any
WITHoption specified, the command just returns a linear array like ["New York","Milan","Paris"].
WITHHASHoptions are specified, the command returns an array of arrays, where each sub-array represents a single item.
When additional information is returned as an array of arrays for each item, the first item in the sub-array is always the name of the returned item. The other information is returned in the following order as successive elements of the sub-array.
- The distance from the center as a floating point number, in the same unit specified in the radius.
- The geohash integer.
- The coordinates as a two items x,y array (longitude,latitude).
So for example the command
GEORADIUS Sicily 15 37 200 km WITHCOORD WITHDIST will return each item in the following way:
GEORADIUSBYMEMBER have a
STOREDIST option they are technically flagged as writing commands in the Redis command table. For this reason read-only replicas will flag them, and Redis Cluster replicas will redirect them to the master instance even if the connection is in read-only mode (see the
READONLY command of Redis Cluster).
Breaking the compatibility with the past was considered but rejected, at least for Redis 4.0, so instead two read-only variants of the commands were added. They are exactly like the original commands but refuse the
STOREDIST options. The two variants are called
GEORADIUSBYMEMBER_RO, and can safely be used in replicas.
- Starting with Redis version 6.2.0: Added the
- Starting with Redis version 7.0.0: Added support for uppercase unit names.