Closed shygnome closed 3 years ago
@shygnome Yep that is a bug. We weren't handling geo_point with lat/lon properties if they weren't set as multi-point. There's a pull request with that fix moving through now. Thanks for catching it!
@shygnome - we've published a fix with 2.2.2.
@shygnome - we've published a fix with 2.2.2.
@rgwozdz @dhatcher - Nice, it's working. Great work guys! You can close this issue.
@shygnome i am currently experiencing this problem in the latest Koop version and when i type the validate command i get the following:
Have you tried querying the geo_point in the latest koop version?
I am currently working with geo-point data in ES, and my geo_point data have a format like this [1].
When I gave it a try, accessing the FeatureServer, it gave me this error.
I found out that the location object is flattened and split into two different fields (location.lon and location.lat).
I assume that the error comes from these section of code at hitConverter (link)
This block assumes that the incoming hit with single point has a format of string only (something like "41.12,-71.34").
Is this truly an unhandled format? Or is there any extra configuration in my format case? Or should I change the format to string? Thank you :blush:
Reference
[1] Geo-point field type