near()'s maxDistance seems to be being ignored

Hey there,

I’m trying to write a simple query in Mongoose that returns a number of nearby results that all have GeoJSON properties. However, I’m getting a different number of results from my Mongoose script to that of a query directly in mongo.

Here’s a raw Mongo script:

var conn = new Mongo(),
    db = conn.getDB("my_db"),
    collection;

collection = db.my_moodels.find({
  geo: {
    $nearSphere: {
      $geometry: {
        type: "Point",
        coordinates: [-0.02028, 51.50703]
      },
      $maxDistance: 3000 // 3k I'm assuming
    }
  }
});

print(collection.length()); // I get 6 (which is round about right)

Here’s my Mongoose script:

MyModel
  .find()
  .where('geo')
  .near({
    center: [-0.02028, 51.50703],
    maxDistance: 3000,
    spherical: yes
  })
  .exec(function (err, results) {
    if (err) {
      throw err;
    } else {
      console.log(results.length); // Here I get over 340, which I think is all of the possible results.
    }
  });

As you can see, the result count is entirely different. In fact, changing the maxDistance property in the Mongoose script seems to do nothing.

I’ve also found that putting the query directly in to the find() method brings back the correct amount of results:

MyModel
  .find({
    geo: {
      $nearSphere: {
        $geometry: {
          type: "Point",
          coordinates: [-0.02028, 51.50703]
        },
        $maxDistance: 3000
      }
    }
  })
  .exec(function (err, results) {
    if (err) {
      throw err;
    } else {
      console.log(results.length); // Now I get 6
    }
  });

Is there a problem with using the near() method or am I using it wrong?

[ghost]

Confirmed nothing wrong with $near or $maxDistance. The problem was elsewhere in my code. Sorry! 🐑

[ghost]

Thanks for pointing that out. I’ll try that now. However, the query examples for geoJSON data with 2dsphere indexes do show $maxDistance as a sub-key of $near. https://docs.mongodb.com/manual/reference/operator/query/near/#query-on-geojson-data

After fooling around in the past few days, I am now almost completely sure the problem is in my code.