Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NewGeoBoundingBoxQuery should support Geohash input #1530

Closed
tommed opened this issue Aug 31, 2021 · 0 comments
Closed

NewGeoBoundingBoxQuery should support Geohash input #1530

tommed opened this issue Aug 31, 2021 · 0 comments
Milestone

Comments

@tommed
Copy link

@tommed tommed commented Aug 31, 2021

Please use the following questions as a guideline to help me answer
your issue/question without further inquiry. Thank you.

Which version of Elastic are you using?

[X ] elastic.v7 (for Elasticsearch 7.x)

Please describe the expected behavior

In Elastic I can specify top_left and bottom_right as geohash strings,

"query": {
  "bool": {
    "filter": [
        {
          "geo_bounding_box": {
            "metaData.location-point": {
              "top_left": "gcp7tpc",
        "bottom_right": "gcp7tpc"
              }
          }
        }
    ]
  }
}

Please describe the actual behavior

But in this API, my only options are BottomRightFromGeoPoint and TopLeftFromGeoPoint which require lat/lng type GeoPoint. The inner types are float64 so this prevents this type of query.

Any steps to reproduce the behavior?

query = query.Filter(elastic.
  NewGeoBoundingBoxQuery("metaData.location-point").
  TopLeftFromGeoPoint("dr5r9ydj2y73").
  BottomRightFromGeoPoint("dr5r9ydj2y73")
@olivere olivere added this to the 7.0.29 milestone Sep 16, 2021
@olivere olivere closed this in ef30a99 Sep 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants