-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
issue with GeoPoint #4389
Comments
Can you provide the logs when running with VERBOSE=1 for this query please? |
used curl example from docs http://docs.parseplatform.org/rest/guide/#geopoint
|
Your curl only shows creating an object with a single point, can you please provide the query logs? |
|
the query you’re sending is not using polygons as constraints. Is that intended? |
Oh, I'm sorry it was my mistake, the query some how works fine. But still there is a difference in types which actually confused me at first and I thought it was a reason from parse
from mongo
Is it by design? Anyway issue can be closed. Thanks a lot for your response |
Yes it’s by design, the way data is stored is not 1-1 from mongo to parse, you’ll see also that ACL’s are split to have a better index performance. |
Issue Description
I used GeoPoint parse field type, as described in documentation but did not succeed trying to use
{"$within": {"$box": {[southwestGeoPoint, northeastGeoPoint]}}}
for queries, it always return empty results. Then I tried to reproduce everything with mongo shell, and there is a difference between GeoPoint which is created in parse and a way which is described in mongo docsOutput when creating GeoPoint field manually according to mongo docs is
Output when creating GeoPoint field with parse server as documented
"__type": "GeoPoint", "latitude": 40.0, "longitude": -30.0
In first case Geo Queries works, in second does not. I'm new to mongo geo data, so maybe there is some confusion with mongo versions or engine about which i don't know.
Thanks!
Environment Setup
Server
Database
The text was updated successfully, but these errors were encountered: