# \[ANNOUNCEMENT\] Logstash H3 filter plugin released **URL:** \ **Category:** Community Ecosystem\ **Created:** [November 14, 2019, 7:54am UTC](https://discuss.elastic.co/t/announcement-logstash-h3-filter-plugin-released/207830 "2019-11-14T07:54:35Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![val](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/val/32/138203_2.png) [@val](https://discuss.elastic.co/u/val)\ **Post date:** [November 14, 2019, 7:54am UTC](https://discuss.elastic.co/t/announcement-logstash-h3-filter-plugin-released/207830/1 "2019-11-14T07:54:35Z")
Following up on the release of the [`ingest-h3` ingest processor](https://discuss.elastic.co/t/announcement-ingest-h3-plugin-released/205275) a few weeks ago, I'm happy to announce that a [Logstash `h3` filter](https://github.com/consulthys/logstash-filter-h3) is now also available for generating [Uber H3](https://uber.github.io/h3/#/) indexes from a given geolocation point at specific resolutions. This Logstash plugin can provide an alternative when using the `elasticsearch` output plugin in update mode (i.e. with `action => update`), since [ingest processors cannot be used when updating documents](https://github.com/elastic/elasticsearch/issues/17895), and hence the [`ingest-h3` processor](https://discuss.elastic.co/t/announcement-ingest-h3-plugin-released/205275) cannot be used in such a situation. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [June 23, 2020, 6:03am UTC](https://discuss.elastic.co/t/announcement-logstash-h3-filter-plugin-released/207830/2 "2020-06-23T06:03:55Z")