# Ignore\_z\_value is not supported

**URL:** <https://discuss.elastic.co/t/ignore-z-value-is-not-supported/333571>\
**Category:** Elasticsearch\
**Created:** [May 16, 2023, 1:22pm UTC](https://discuss.elastic.co/t/ignore-z-value-is-not-supported/333571 "2023-05-16T13:22:11Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![gabi939](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gabi939/32/121079_2.png) [@gabi939](https://discuss.elastic.co/u/gabi939)\
**Post date:** [May 16, 2023, 1:22pm UTC](https://discuss.elastic.co/t/ignore-z-value-is-not-supported/333571/1 "2023-05-16T13:22:11Z")

</div>

### Elasticsearch Version

7.7.0

### Java Version

1.8.0\_252

### OS Version

Ubuntu 18.04

### Problem Description

According to:

> **[Geo-point datatype | Elasticsearch Guide \[7.7\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.7/geo-point.html)**

I should be able to use parameter ignore\_z\_value to ignore z values indexed to geo\_point field.

But it doesn't work, instead I get the following exception:

```auto
{
"error" : {
"root_cause" : [
{
"type" : "parse_exception",
"reason" : "field must be either [lat], [lon] or [geohash]"
}
],
"type" : "mapper_parsing_exception",
"reason" : "failed to parse field [location] of type [geo_point]",
"caused_by" : {
"type" : "parse_exception",
"reason" : "field must be either [lat], [lon] or [geohash]"
}
},
"status" : 400
}

```

### Steps to Reproduce

1. I have created an index with the following mapping:

```auto
`{
"eren" : {
"mappings" : {
"properties" : {
"location" : {
"type" : "geo_point"
}
}
}
}
}

```

1. I have tried to upload the following document:

```auto
{

"location": {
"lat":40,
"lon":40,
"z":20
}

}

```

---

<div class="post-metadata">

**Author:** ![Ignacio\_Vera](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ignacio_vera/32/36674_2.png) [@Ignacio\_Vera](https://discuss.elastic.co/u/Ignacio_Vera)\
**Post date:** [May 17, 2023, 6:47am UTC](https://discuss.elastic.co/t/ignore-z-value-is-not-supported/333571/2 "2023-05-17T06:47:24Z")

</div>

Hello @gabi939!

Welcome to the community. First of all, just say that the version of Elasticsearch is way too old, you should consider upgrading as a matter of urgency.

In regards the issue, I think the format you are referring was never supported for those old versions. It was not until Elasticsearch 8.3 that that format was supported. This was done as a side effect of adding Geojson support to geo\_point field: [Support GeoJSON for geo\_point by craigtaverner · Pull Request #85120 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/pull/85120)

Note that in your version you can probably use other formats to add a z value, e.g the following should work (I haven't tried):

```auto
{
   "location": [40, 40, 20]
}

```

where the positions are [lon, lat, z].

Therefore your options are upgrading your Elasticsearch cluster to 8.3+ or use a different format to define your geo\_points.

Hope this helps!

---

<div class="post-metadata">

**Author:** ![gabi939](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gabi939/32/121079_2.png) [@gabi939](https://discuss.elastic.co/u/gabi939)\
**Post date:** [May 17, 2023, 7:45am UTC](https://discuss.elastic.co/t/ignore-z-value-is-not-supported/333571/3 "2023-05-17T07:45:05Z")

</div>

Hey,

Thank you for the clarification, you should consider then updating the documentation:  
[https://www.elastic.co/guide/en/elasticsearch/reference/7.7/geo-point.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.7/geo-point.html)

---

<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:** [June 14, 2023, 7:45am UTC](https://discuss.elastic.co/t/ignore-z-value-is-not-supported/333571/4 "2023-06-14T07:45:59Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.