Find all the geo position members saved in a geoindex, which are within a certain distance and in a certain area(circular or box). This command can be used as a substitute for GEORADIUS and GEOREDIUSBYMEMBER commands, as those commands are deprecated.
Get the longitude and latitude of specific members from a geospatial index. Multiple members are allowed in the same command, so we can get the position of multiple members at the same time as an array.
Get the geohash string for one or more geo index members. We can add some members(longitude, latitude, member_name) to a geoindex using “GEOADD” command, then we can get the geohash of those members using this GEOHASH command.
Append one or more elements to the list. The element is added to the tail/right of the list, that’s why this command is named RPUSH(R+PUSH). Items are inserted to the right one by one. If multiple elements are provided to the command, then the first item is pushed to the right, then the next ones.
Get the distance between 2 members/items saved in geospatial index. Geospatial information is saved in a sorted set data structure, when added with GEOADD command. This GEODIST command helps us to get the distance between 2 members saved in the geoindex.
Add one or more geospatial items/members to a geospatial index. If the
Remove one or more items/members from a set. If the member is not present in the set, then then it is ignored. If the
Get all the members of a set. We get the full list of all the members. This is the only proper command available to get items/members from a set.
Add one or more items/members to a set. Multiple member elements are supported in the command. So we can add one or more members to the same set at the same time. If the key does not exist, then it is created and then members are added to it. If the item/member element already exists in the set, then it is ignored.
Increment the integer value of a hash field. This command increments the field value by a certain amount that is provided. If the hash does not exist, or the field does not exist, then the hash and/or the field will be created. So we will never get any error related to non-existing hash key or field. The field’s max and min allowed value is of a 64-bit signed integer.