Geolocation Rest always returns same result

[ldmtam]

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!

• You've met the prerequisites.
• You're running the latest version of Parse Server.
• You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup

Steps to reproduce

Logs/Trace

I'm using geolocation feature provided from parse server. But parse server always returns the same result array including every location object although i have used the $nearSphere and $maxDistanceInMiles. Please help me out. Thanks in advance.

[flovilmart]

Can you post the request you'r doing?

[ldmtam]

Assume i have a class with 5 geo elements like this:

And i want to get 3 objects that are nearest the longitude and latitude coordinate that i have included in the query and with max distance is 1 miles

But the result array always return all of my geolocation objects

Please help me. Thanks!

[tahoecoop]

I have this issue as well, thanks!

[ldmtam]

Can anyone help me?

[drew-gross]

We have lots of tests that cover Geo Queries, so the information you've provided so far is not enough for us to help you. The best thing you would be able to do is create a reproducible failing test case that demonstrates the issue.

[msniff16]

Haven't had time to write a test case, but I have investigated this issue and can confirm that it occurs when using an $or query that is composed of two queries with separate "geoPoint" objects. When I do the same query with the usual parse server (api.parse.com) it does not fail. When I use my new parse-server with an $or query that is composed of one internal query with a geoPoint (nearSphere) object it works. Adding the second query with geoPoint makes it fail. Again, doing the $or with both geoPoint queries inside the $or works when using api.parse.com and not when using parse-server.

[hramos]

We are closing this issue due to a lack of sufficient information.

Please refer to this issue for an example of a great bug report.

You may use Server Fault for questions about managing Parse Server.

For code-level and/or implementation-related questions or technical support, please refer to Stack Overflow.

[msniff16]

If I find more time to write up a test case, I will in the future. Wanted to make the community aware that this is a likely issue that has not been addressed.

[javaboyjunior]

Confused as to why this doesn't have enough information - the exact steps to reproduce are in the original bug report. Create a class with a geopoint column, add some data, query the class with a $nearSphere query with a limit and a distance and you always get back all results. I also have this issue. There's even screen shots...

[flovilmart]

@javaboyjunior We have tests covering this feature, https://github.com/parse-community/parse-server/blob/master/spec/ParseGeoPoint.spec.js#L187 . I'm not sure why you experience such issue.

[javaboyjunior]

@flovilmart This was very helpful - thank you for the response. For those facing the same problem as myself and others on this thread, the issue was that we were storing the lat and lng components of a geopoint as strings. It isn't obvious from the console as they look like numbers but when I ran a query, latitude and longitude values were in quotes. I edited the values manually in the console which converted them to numbers and distance queries started working. Hopefully this information helps someone as it was tricky to track down.

@flovimart quick question if you don't mind. Now we have this working, we have discovered that 'limit' doesn't work. Shall I open a new ticket for that?

[flovilmart]

@javaboyjunior I should probably not allow strings or convert the strings to numbers for geopoints. We miss that validation somewhere.

For the limit, I'm curious, if you can provide the full logs as well with the newly opened issue that would be helpful!

[javaboyjunior]

@flovilmart I will get on that - thanks very much for your help!