# Geo\_point fielddata

**URL:** https://discuss.elastic.co/t/geo-point-fielddata/46106
**Category:** Elasticsearch
**Created:** [April 1, 2016, 9:42pm UTC](https://discuss.elastic.co/t/geo-point-fielddata/46106 "2016-04-01T21:42:28Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Brian\_Hudson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brian_hudson/32/1306_2.png) [@Brian\_Hudson](https://discuss.elastic.co/u/Brian_Hudson)
#### Post date: [April 1, 2016, 9:42pm UTC](https://discuss.elastic.co/t/geo-point-fielddata/46106/1 "2016-04-01T21:42:28Z")

</div>

Is it possible to avoid loading geo\_points into field data when performing a geo distance query and/or a geohash cell aggregation?

I am running elasticsearch 2.0.0 and was hoping that the use of doc\_values (default) for geo\_points would avoid loading them into field data. However it appears that is not the case; as soon as I execute a query including a geo distance query or run a geohash grid aggregation my field data usage increases dramatically, maxing out the amount of RAM I allow for field data.

I am using optimizeBBox("indexed") so that "memory" isn't used but that also did not seem to help.

If it isn't possible with 2.0.0, will the improvements in 2.2 assist with this?

Mapping details: lat\_lon: true, geohash: true

---

<div class="post-metadata">

### Author: ![Brian\_Hudson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brian_hudson/32/1306_2.png) [@Brian\_Hudson](https://discuss.elastic.co/u/Brian_Hudson)
#### Post date: [April 2, 2016, 11:52am UTC](https://discuss.elastic.co/t/geo-point-fielddata/46106/2 "2016-04-02T11:52:24Z")

</div>

I found some discussion that looks related to this: [https://github.com/elastic/elasticsearch/issues/4562](https://github.com/elastic/elasticsearch/issues/4562) it doesn't answer the question really but gives me some hope things will be better if/when I can upgrade to 2.2+.

---

<div class="post-metadata">

### Author: ![Brian\_Hudson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brian_hudson/32/1306_2.png) [@Brian\_Hudson](https://discuss.elastic.co/u/Brian_Hudson)
#### Post date: [April 2, 2016, 12:39pm UTC](https://discuss.elastic.co/t/geo-point-fielddata/46106/3 "2016-04-02T12:39:52Z")

</div>

I just tested geo distance queries and geohash grid aggregation on my local dev machine using 2.3.0 and my field data cache stays 0.

Awesome work guys! Can't wait to upgrade our real server(s) once we're willing to reindex again.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 11:03pm UTC](https://discuss.elastic.co/t/geo-point-fielddata/46106/4 "2017-07-05T23:03:00Z")

</div>


