[SERVER-40203] Ability use a GeoHash string vs. Lat/Long coordinates Created: 18/Mar/19 Updated: 27/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Geo |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Sigfrido Narvaez | Assignee: | Backlog - Query Integration |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | qi-geo | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Integration
|
| Participants: |
| Description |
|
Many geo-location devices used in Scooters, Bikes and other IoT devices send their geo location using GeoHash vs. Lat/Long pairs. It would be great to be able to pass a GeoHash string on all of the geo-spatial Query & Agg operators.
|
| Comments |
| Comment by Sigfrido Narvaez [ 19/Mar/19 ] |
|
It would be great if either geohash or long/lat can be stored in the database & indexed, and be able to query also using either geohash or long/lat |
| Comment by Asya Kamsky [ 18/Mar/19 ] |
|
What would be stored in the database? Are they asking to be able to store geohash and query by geohash? Or store long/lat but be able to query via geohash?
|