-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarification on Radius #131
Comments
i get completely weird results ... with 3 data points all in an area of 3 km i can not really filter for the ones in a 1km range only to 2 points .... i even get the far away point of 3 km but missing one close point of <1km i am let to believe that the within function also have troubles here. |
Will check it next week. Thank you! |
The plugin makes use of GeoHashes. The problem with GeoHash based queries can be summarised as:
There is a possibility that the problem is due to boundary issues between two edge case geohashes. |
same here . in my case it always return item 0 if distance was less than 100 . so i when i increase radius to 500 so it returns results ,even though after hard tested i realized the problem was from .within method and not only radius because i am sure this plugin uses native geo hash wrapping to flutter , i am use the same geo hash native in my java app , and there no issues into it and it can have a very accurate vision with distance , i hope this package solve it's issues |
same here. I've used the next code:
it show me: 14.069 kms when my radius 'within' was 10.
|
While testing the
.within
method, I realized that theradius
property does not seem to be in Km as stated in the example project.I base this statement because I have a document in my database of the following structure:
As can be seen, the LatLng is
(26.628408, -81.874084)
When calling the method:
I am using:
If you use a tool such as https://www.nhc.noaa.gov/gccalc.shtml, you can see that the there is approximately only 7km between these points, but even with radius 50, GeoFlutterFire returns 0 items.
Increasing the radius to 200 does return the correct item.
Thus, I am led to believe that the radius is indeed not in km.
I would like to get some more details on this and correct the documentation if that is the case.
The text was updated successfully, but these errors were encountered: