# Geospatial features

**URL:** <https://discuss.elastic.co/t/geospatial-features/26648>\
**Category:** Elasticsearch\
**Tags:** es-hadoop\
**Created:** [July 31, 2015, 2:45pm UTC](https://discuss.elastic.co/t/geospatial-features/26648 "2015-07-31T14:45:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ravenrani](https://avatars.discourse-cdn.com/v4/letter/r/a698b9/32.png) [@ravenrani](https://discuss.elastic.co/u/ravenrani)\
**Post date:** [July 31, 2015, 2:45pm UTC](https://discuss.elastic.co/t/geospatial-features/26648/1 "2015-07-31T14:45:23Z")

</div>

Are the geospatial indexes (geohash and quadtree) supported in the elasticsearch for hadoop  
, fo example through hive.

---

<div class="post-metadata">

**Author:** ![costin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/costin/32/44950_2.png) [@costin](https://discuss.elastic.co/u/costin)\
**Post date:** [July 31, 2015, 3:04pm UTC](https://discuss.elastic.co/t/geospatial-features/26648/2 "2015-07-31T15:04:11Z")

</div>

Hive, Pig, etc.. don't have a type for geospatial units. The connector thus has to map these types to a string which is later which can be manipulated in Hive accordingly. However there's nothing preventing the usage of such fields in queries...

---

<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 6, 2017, 1:27pm UTC](https://discuss.elastic.co/t/geospatial-features/26648/3 "2017-07-06T13:27:45Z")

</div>


