query.withinMiles() will not work while query.near() works fine #2075

Activity

1. drew-gross commented on Jun 16, 2016

   

   drew-gross

   on Jun 16, 2016

   Contributor

   More actions

   We have lots of passing test cases that cover these features. Can you post some code that reliably reproduces your issue, including the code that creates the data? Ideally as a test case we can add to our test suite.
2. Siraris commented on Jun 16, 2016

   

   Siraris

   on Jun 16, 2016

   Author

   More actions

   This is the exact code that I'm using. Do you see something wrong that I'm doing?

   Parse.Cloud.define("minimumUsersForAccess", function(request, response){
     if (!request.user) {
       response.error("Must be signed in to call this Cloud Function.")
       return;
     }
   
     // Max Distance to search should either be set by request, or default to 20 miles
     var maxDistance = (request.params.maxDistance) 
       ? request.params.maxDistance : 20,
       query = new Parse.Query(Parse.User);
   
   // THIS DOES NOT WORK
     query.withinMiles('currentLocation',
         new Parse.GeoPoint(-73.96939568075399, 40.83514669005315), 
         maxDistance
     );
   
   // THIS WORKS
     query.near('currentLocation',
       new Parse.GeoPoint(-73.96939568075399, 40.83514669005315));
   
     query.find({
       success: function(users) {
         // return true if more than 50 users returned, otherwise not enough
         // users for access
         console.log(users);
         response.success((users.length >= 50) ? true : false);
       }
     });
   });
   

   I don't have access to the code that creates the data unfortunately. Regardless, this is the shape of the location data in mongo:

   "currentLocation": [
   -71.1670245290879,
   42.33827739107621
   ]
3. drew-gross commented on Jun 16, 2016

   

   drew-gross

   on Jun 16, 2016

   Contributor

   More actions

   We have multiple tests for the withinMiles feature in the ParseGeoPoint.spec.js file that all pass. Without a complete set of steps to reproduce this issue, it's very difficult for us to help.

   If you aren't using mongodb version 3.0.8, try switching to that version, as other versions have had some issues with geo queries.
4. hramos commented on Jun 24, 2016

   

   hramos

   on Jun 24, 2016

   Contributor

   More actions

   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.
5. hramos

   closed this as completedon Jun 24, 2016