Closed yeroc closed 4 years ago
@colings86 what do you think?
I would find this feature very useful as well. We would generate density maps from those aggregation!
Any update on this? Does this require some additional features in Lucene or does this require changes to ElasticSearch only?
No additional Lucene features required to support this feature. I'm currently refactoring some legacy geo_point
code to reuse geo_shape
logic that fixes polygonal ambiguity issues. Once that's done adding support for this request will be relatively straight-forward.
@nknize Thanks a lot for the update.
Great
Any planned date for release?
@nknize just assigned this to you so you don't miss it
@nknize just pinging for an update on this.
+1
2.2 for sure and can be back ported to 2.0+ (@clintongormley thoughts on back porting?).
@nknize new features/enhancements go into the current stable branch and above only (ie 2.2+ at the moment)
What is the latest on this?
This was put on hold to prioritize spatial indexing performance issues in lucene 6.0. Once we get that stable this will move back up in the list.
Ok cool thanks for letting me know. Do you know if this will add support to allow aggregation of geoshape polygons or is this just for aggregation of points by polygons?
Yes, its to provide geo_bounds
support for geo_shape
field types. So geo_shape
fields will be aggregated into a single bounding box.
@nknize I see the Lucene 6.1 release notes mention improvements to spatial indexing so assume the work you mention in your previous notes has been completed. Does this mean this ticket is on deck now or is there still more work to be done prior? Thanks!
+1
How are we doing on this feature?
+1 this would be very useful functionality
@nknize Do you have an update on this?
👍
👍 @nknize @sherry-ger Any updates on this issue?
Is there any technical difficulty hard to solve for this issue?
What ever happened with this issue? Is there a branch where the work for this was started?
@sherry-ger @nknize - any updates on this issue?
We won't be working on this until BKD-backed geoshapes are merged
@clintongormley when is the "BKD-backed geoshapes" planned to be merged?
@hanoch when it is ready. I can't be any more specific than that
Hi, this feature has complate? @clintongormley
+1
+1
any progress on that?
Have any updates on that ?
@nknize is this now addressed with the ES 6.5.0 release and https://github.com/elastic/elasticsearch/pull/32730 PR merge?
@hanoch no, we still need get #32039 in first
We also won't be able to add geo_shape
aggregations until we come up w/ a reasonable doc value representation for geo_shape
. WKB seems the best option at the moment but we need to investigate docValue size limits in lucene.
It is possible that we will need to limit the number of shape vertices to comply w/ Lucene docValue size limits for geo_shape
fields that have docValues enabled. /brainstorm /cc @jpountz
Depends on #37206
Apparently Kibana believes this has been fixed already. See this bug report https://github.com/elastic/kibana/issues/31589
This is a requirement to be able to do layer-fitting on layers backed by geo_shape
fields in the maps app. cf. https://github.com/elastic/kibana/issues/33509
Any progress on this issue? any ETA?
@hanoch there is some progress. there is a feature branch that this issue is tracking: https://github.com/elastic/elasticsearch/issues/37206.
The feature branch has partial support for aggregations for now, one being geo_bounds
: https://github.com/elastic/elasticsearch/pull/45413
Unfortunately, I cannot share an ETA for this work, but I can say that it is actively being worked on!
this was implemented in https://github.com/elastic/elasticsearch/pull/55328!
Some time ago I created an enhancement request to support a bounding box aggregation (#5634) as this is very useful for mapping applications to allow a map to zoom to the extent (bounding box) of all matches. This was implemented in v1.3.0 but unfortunately only for the geo_point type.