See also this Mongoose issue that is possibly related: Automattic/mongoose#664

I have fixed the issue which was in db_command.js. It wasn't using min and max options when it built up the command. This code probably wants tidying up, but all tests pass and it solves the issue.

This seems to still be broken for me. I was having the same issue and while searching for a potential solution, I found this page. I just installed [email protected] in order to fix the problem (was running a much older version), but when I reran my code I got the same "point not in interval of [-180, 180)]" error.

Here's my code:

dbConnector.open(function(err, db) {
  if(err) {
    console.log(err.message);
  } else {
    db.collection('artistLocations',function(err,collection){
        if(err){
            console.log(err.message);
        } else {
        collection.ensureIndex({pos:'2d'},{min:200,max:1400},function(err){
            if(err)
                console.log(err.message);
        cursor = collection.find({});
        //global var
        cursor.count(function(err, total) {
          if(err) {
            console.log(err.message);
          } else {

        cursor.each(function(err, artist) {
          if(err) {
            console.log(err.message);
          } else if(artist != null) {
            collection.findAndModify({'_id':artist._id}, [['_id','asc']],
            {$set : {'pos': [600,600]}},function(err){
                if(err) console.log(err);
                else{
                    count++;
                    if(count == total)
                        process.exit();
                }
            });         
            }
        });
        }});

I get the exact same error as antz29 first did. @antz29 have the errors from running the above code gone away for you?

This test passes for me and does exactly what you are trying to do. I'm running MongoDB 2.0.3. I might be you are running an earlier version without min, max support ?

exports.shouldCorrectlyUseMinMaxForSettingRangeInEnsureIndex = function(test) {
  // Establish connection to db  
  client.createCollection('shouldCorrectlyUseMinMaxForSettingRangeInEnsureIndex', function(err, collection) {
    test.equal(null, err);

    collection.ensureIndex({loc:'2d'}, {min:200, max:1400, safe:true}, function(err, indexName) {
      test.equal(null, err);

      collection.insert({loc:[600, 600]}, {safe:true}, function(err, result) {
        test.equal(null, err);
        test.done();
      });
    });
  });    
}

hmmm that's really weird. it seems that the area is in my usage of the variable "pos" instead of "loc". using my same code, if i switch it to say "loc", it works totally fine. i didn't realize that word needed to be exact in the past. i've always used other variables, just the altered ranges have been small (-1 to 1 or something like that) where they haven't gotten out of the standard range.

sami

wait nvm, that's not true. I just got code to work with another variable elsewhere using a simple insert (a la your code above).

I guess the only other difference between my code and others is that I was using collection.findAndModify() to set new 2D location variables. Maybe the code for findAndModify isn't working properly? (though it does seem to work fine now that I've switched my "pos:'2d'" to "loc:'2d'")

it could be you had an existing index with no min/max

I tried using dropIndex() numerous times and the index just didn't exist. I wonder in retrospect if the issue was that the index simply wasn't created a bunch of times for who-knows-what-reason?

whatever the case, it works now. thanks for responding!

you need to call it with safe:true to ensure the error message is returned

yeah i noticed that in your code and updated it in mine as well. thanks!