[SERVER-1720] can't store points at extreme edges in geo index Created: 02/Sep/10  Updated: 12/Jul/16  Resolved: 05/Apr/11

Status: Closed
Project: Core Server
Component/s: Geo
Affects Version/s: None
Fix Version/s: 1.9.0

Type: Bug Priority: Minor - P4
Reporter: Mathias Stearn Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-2388 Cleanup of bounds-handling cases Closed
Operating System: ALL
Participants:

 Description   

These work and are correct:

PRINT(Point(180-g._error,180-g._error).hash(&g).toString());
PRINT(Point(-180+g._error,-180+g._error).hash(&g).toString());

Works but incorrect ("00000...')
PRINT(Point(180,180).hash(&g).toString());

Asserts:
PRINT(Point(-180,-180).hash(&g).toString());



 Comments   
Comment by Greg Studer [ 05/Apr/11 ]

Pretty sure this is solved by the solution to SERVER-2388

Points must be in bounds interval [min, max) , so users just need to mod their coordinates by the interval range to avoid insert errors. Also integrates well with future wrapping functionality, if desired.

Comment by auto [ 03/Sep/10 ]

Author:

{'login': 'RedBeard0531', 'name': 'Mathias Stearn', 'email': 'mathias@10gen.com'}

Message: Limit generated points to [-179.9, 179.9] due to SERVER-1720
http://github.com/mongodb/mongo/commit/b5e57bae310b4f097fcb4c7230cbe3de42477dab

Comment by Mathias Stearn [ 02/Sep/10 ]

This would probably require a reindex to fix

Generated at Thu Feb 08 02:57:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.