[SERVER-994] Geospatial Bounding box query giving point not in range error Created: 11/Apr/10 Updated: 12/Jul/16 Resolved: 11/May/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 1.4.0, 1.5.0 |
| Fix Version/s: | 1.5.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gavin R. | Assignee: | Richard Kreuter (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
linux x86-64 |
||
| Participants: |
| Description |
|
I ran across the case where the bounding box query would sometimes give me a "point not in range" error with no discernible reason that I can find. You can recreate the issue with the following: db.foo.insert({ point : { x : -15000000, y : 10000000 } }) , { min : -21000000 , max : 21000000 } ) } }) The console shows: The mongod log shows: , 1: { 0: 0.0, 1: 15000000.0 } } } } } However running the query with a different bounding box like so: } }) I've run into quite a few of these that act the same way with various bounding boxes and data, any help will be greatly appreciated! |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 20/Jun/11 ] |
|
@ken - can you try 1.8.2 and if still occurring there open a new ticket |
| Comment by Ken Pratt [ 20/Jun/11 ] |
|
This is marked as closed. However, I have another instance where "point not in range occurs" erroneously. The geo index is set with a max of 181 and a min of -181 in my collection. The following query produces the error: { "Placemark.Point.coordinates" : { "$within" : { "$box" : [ [ 172.3265993445506 , 9.18637494622202] , [ 180.0 , 20.3450110477435]]}}} Both of these points are in range. I'm using MongoDB version 1.6.3 running on Ubuntu 11.04 64 bit using latest Java driver. |
| Comment by auto [ 15/Jul/10 ] |
|
Author: {'login': 'kreuter', 'name': 'Richard Kreuter', 'email': 'richard@10gen.com'}Message: Use FP error term in a geo bounds check. |
| Comment by Richard Kreuter (Inactive) [ 11/May/10 ] |
|
I think the bug here is fixed. |
| Comment by auto [ 11/May/10 ] |
|
Author: {'login': 'kreuter', 'name': 'Richard Kreuter', 'email': 'richard@10gen.com'}Message: Characterize and add tests for the flaw in |
| Comment by auto [ 11/May/10 ] |
|
Author: {'login': 'kreuter', 'name': 'Richard Kreuter', 'email': 'richard@10gen.com'}Message: Fix test file for |
| Comment by auto [ 11/May/10 ] |
|
Author: {'login': 'kreuter', 'name': 'Richard Kreuter', 'email': 'richard@10gen.com'}Message: Squashed commit of the following: commit b639096a76de87adaf0e62e28e29b1155ba944a9 Replace sizeDiag calls w/sizeEdge; add a test. commit 75b0a08c96bfd6e1a7e7a6d002dd2391d0433575 Rename mongo::Geo2dType::size() to ::sizeDiag(); add a sizeEdge(). |
| Comment by auto [ 11/May/10 ] |
|
Author: {'login': 'kreuter', 'name': 'Richard Kreuter', 'email': 'richard@10gen.com'}Message: Squashed commit of the following: commit b639096a76de87adaf0e62e28e29b1155ba944a9 Replace sizeDiag calls w/sizeEdge; add a test. commit 75b0a08c96bfd6e1a7e7a6d002dd2391d0433575 Rename mongo::Geo2dType::size() to ::sizeDiag(); add a sizeEdge(). |