Currently the 2d index supports specifying min and max fields out of the [-180, 180] range of values.

However, if specifying a min value of an absurdly large negative number like -6.362424895860688e+161 results in a confusing error that doesn't say what the actual issue is:

MongoServerError[Location4799400]: Invalid GeoHashConverter parameters

As values outside of the [-180, 180] range make no mathematical sense in a 2d plane we should consider limiting the range of values accepted in the command.