firebase / firebase/geofire-js

GeoQuery is only returning nearby keys if a huge radius is set

Open
#159 2 comments 0 reactions 0 assignees View on GitHub
type: bug
Dominant language
TypeScript
Stars
1.4k
Forks
339
PR merge metrics
No merged PRs in 30d

Description

### DESCRIPTION
This issue is similar to the ticket [https://github.com/firebase/geofire-js/issues/80](url) .

GeoQuery returning near by records from firebase geofire directory after setting the radius of a large area.

### Version info
**Firebase:**
"^4.3.0"

**GeoFire:**
"^4.1.2"
**Other (e.g. Node, browser, operating system) (if applicable):**
Mac / Chrome
npm 5.2.0

### Test case
GeoQuery must return all records within the radius specified.

### Steps to reproduce
Set smaller radius with records in firebase and the Geoquery returns no records unless we set a wider range to the radius parameter.

### Expected behaviour
GeoQuery must return all records within the radius specified.

### Actual behaviour
I have 3 records within few meters but GeoQuery returns nearby records only when a wider range of radius say in kilometres is set.

### CIRCLE RADIUS to 300 METRES

### After setting GeoQuery RADIUS to 1
screen shot 2017-08-19 at 17 23 03

### After setting GeoQuery RADIUS to 6
screen shot 2017-08-19 at 17 22 01

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the GeoQuery radius behavior described for GeoFire 4.1.2 and Firebase 4.3.0, comparing a radius of 1 with a radius of 6. The payload names no source file or test, so trace the GeoQuery implementation and add a regression test covering records within the specified radius; done means all nearby records are returned at the smaller radius.

Written by the indexing model from the issue text.

Assessment

Tech stack
firebase, typescript
Domain
backend, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.