[SERVER-757] GeoSpatial queries should support maxDist parameter Created: 15/Mar/10  Updated: 15/Mar/10  Resolved: 15/Mar/10

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

Type: New Feature Priority: Major - P3
Reporter: Greg White Assignee: Eliot Horowitz (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

All


Participants:

 Description   

It would be extremely useful to have a maxDist parameter for GeoSpatial queries. This would allow bounding box queries not to send results that are not of interest.

Ideally, there would be three new parameters: maxDist (sets maximum distance along both axes), maxDistX and maxDistY (allowing the user to scale the queries if they are on a spherical surface, or if a non-square bounding box is what is desired.)

The parameter(s) should be in the same units as the index.

It is entirely fine if these use simplistic distance calcs (i.e., simply looking for values that are between (x-maxdistX and x+maxDistX). It might be simpler and clearer to just support minX/maxY and minY/maxY.

Any of the above would be great and very useful for my target application, which is likely generate a lot of empty result sets.



 Comments   
Comment by Michael Dirolf [ 15/Mar/10 ]

I think this is a duplicate of SERVER-690

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