# Geo point type error for map visualization in kibana

**URL:** <https://discuss.elastic.co/t/geo-point-type-error-for-map-visualization-in-kibana/233182>\
**Category:** Kibana\
**Created:** [May 18, 2020, 7:10pm UTC](https://discuss.elastic.co/t/geo-point-type-error-for-map-visualization-in-kibana/233182 "2020-05-18T19:10:33Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ramalakshmi](https://avatars.discourse-cdn.com/v4/letter/r/f9ae1b/32.png) [@Ramalakshmi](https://discuss.elastic.co/u/Ramalakshmi)\
**Post date:** [May 18, 2020, 7:10pm UTC](https://discuss.elastic.co/t/geo-point-type-error-for-map-visualization-in-kibana/233182/1 "2020-05-18T19:10:33Z")

</div>

Hi,  
I am getting error for geo\_point type in kibana visualizations.It's showing to set the fielddata=true,That setting of fielddata=true is coming after every rollover of the index.  
PUT indexname/\_mapping  
{  
"properties" : {  
"destination" : {  
"properties" : {  
"geo" : {  
"properties" : {  
"location" : {  
"type" : "geo\_point",  
"fielddata" : true  
}

```
      }
    
      
    }

```

}  
}  
}  
}  
By running above API in kibana devtool showing below error but fielddat= true is available for text fields but it's showing for geo\_point.Please help me, how to resolve this issue.  
{  
"error": {  
"root\_cause": [  
{  
"type": "mapper\_parsing\_exception",  
"reason": "Mapping definition for [location] has unsupported parameters: [fielddata : true]"  
}  
],  
"type": "mapper\_parsing\_exception",  
"reason": "Mapping definition for [location] has unsupported parameters: [fielddata : true]"  
},  
"status": 400  
}

Thank you

---

<div class="post-metadata">

**Author:** ![Nathan\_Reese](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nathan_reese/32/84829_2.png) [@Nathan\_Reese](https://discuss.elastic.co/u/Nathan_Reese)\
**Post date:** [May 18, 2020, 11:51pm UTC](https://discuss.elastic.co/t/geo-point-type-error-for-map-visualization-in-kibana/233182/2 "2020-05-18T23:51:28Z")

</div>

It looks like your mapping is incorrect. You do not need to set `fielddata` when declaring your geo\_point. Try

```auto
PUT indexname/_mapping
{
"properties" : {
"destination" : {
"properties" : {
"geo" : {
"properties" : {
"location" : {
"type" : "geo_point",
}
}
}
}
}
}
}

```

---

<div class="post-metadata">

**Author:** ![Sreekanth3](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@Sreekanth3](https://discuss.elastic.co/u/Sreekanth3)\
**Post date:** [May 19, 2020, 12:22pm UTC](https://discuss.elastic.co/t/geo-point-type-error-for-map-visualization-in-kibana/233182/3 "2020-05-19T12:22:15Z")

</div>

Hey @Nathan_Reese  
she's asking about the problem after the rollover of the index happened, that's where she got the problem of setting field value true .  
As far i knew the elastic, we don't set the field values for geo\_point . But this is a wierd behaviour of elastic asking to set the field value for geo\_point.

---

<div class="post-metadata">

**Author:** ![Nathan\_Reese](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nathan_reese/32/84829_2.png) [@Nathan\_Reese](https://discuss.elastic.co/u/Nathan_Reese)\
**Post date:** [May 19, 2020, 2:52pm UTC](https://discuss.elastic.co/t/geo-point-type-error-for-map-visualization-in-kibana/233182/4 "2020-05-19T14:52:39Z")

</div>

> she's asking about the problem after the rollover of the index happened, that's where she got the problem of setting field value true .

This sounds like a bug with rollover. Can you provide some details about your environment and configuration and how this occurred?

---

<div class="post-metadata">

**Author:** ![Sreekanth3](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@Sreekanth3](https://discuss.elastic.co/u/Sreekanth3)\
**Post date:** [May 19, 2020, 3:30pm UTC](https://discuss.elastic.co/t/geo-point-type-error-for-map-visualization-in-kibana/233182/5 "2020-05-19T15:30:20Z")

</div>

Sure , Will provide you  
The version of elastic and kibana are 7.5.2  
logstash version is of 7.6 .  
Well I have used the Geoip filter plugin for the fields enrichment .  
Steps :

1. Created a mapping with the geoip fields with type geo\_point.
2. Indexed the data to the elasticsearch and created maps in kibana.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/4/44954ecd3589d73d5543e15e42fb2661e52c6d86.png)

> {  
> "took": 617,  
> "timed\_out": false,  
> "\_shards": {  
> "total": 21,  
> "successful": 12,  
> "skipped": 0,  
> "failed": 9,  
> "failures": [  
> {  
> "shard": 0,  
> "index": "logstashflowdata-000005",  
> "node": "AqAZ\_WKARj6a18vAjJNt\_Q",  
> "reason": {  
> "type": "query\_shard\_exception",  
> "reason": "field [destination.geo.location] is not a geo\_point field",  
> "index\_uuid": "GqTtWSnXSWKunprDR8quqQ",  
> "index": "logstashflowdata-000005"  
> }  
> },  
> {  
> "shard": 0,  
> "index": "logstashflowdata-000006",  
> "node": "AqAZ\_WKARj6a18vAjJNt\_Q",  
> "reason": {  
> "type": "query\_shard\_exception",  
> "reason": "field [destination.geo.location] is not a geo\_point field",  
> "index\_uuid": "c4WaClzxS7yJ4Arx3M9BlA",  
> "index": "logstashflowdata-000006"  
> }  
> },  
> {  
> "shard": 0,  
> "index": "logstashflowdata-000007",  
> "node": "AqAZ\_WKARj6a18vAjJNt\_Q",  
> "reason": {  
> "type": "query\_shard\_exception",  
> "reason": "field [destination.geo.location] is not a geo\_point field",  
> "index\_uuid": "ubX3KYBwTuOaHt0pUcN9zg",  
> "index": "logstashflowdata-000007"  
> }  
> }  
> ]  
> },  
> "hits": {  
> "total": 0,  
> "max\_score": null,  
> "hits":   
> },  
> "aggregations": {  
> "filter\_agg": {  
> "2": {  
> "buckets":   
> },  
> "doc\_count": 0  
> }  
> }  
> }

This the response now i'm getting for these indices but , before to it it was to the geo\_point only .

---

<div class="post-metadata">

**Author:** ![Nathan\_Reese](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nathan_reese/32/84829_2.png) [@Nathan\_Reese](https://discuss.elastic.co/u/Nathan_Reese)\
**Post date:** [May 19, 2020, 3:47pm UTC](https://discuss.elastic.co/t/geo-point-type-error-for-map-visualization-in-kibana/233182/6 "2020-05-19T15:47:48Z")

</div>

What changed that caused the mapping to get updated? What action was taken before the problem occurred?

What does your logstash configuration look like?

---

<div class="post-metadata">

**Author:** ![Sreekanth3](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@Sreekanth3](https://discuss.elastic.co/u/Sreekanth3)\
**Post date:** [May 19, 2020, 3:53pm UTC](https://discuss.elastic.co/t/geo-point-type-error-for-map-visualization-in-kibana/233182/7 "2020-05-19T15:53:47Z")

</div>

This is the sample conf . I'm showing , those are the geo ip filter i have used.

> input {  
> udp {  
> host =\> "localhost"  
> port =\> 2055  
> codec =\> netflow  
> {  
> versions =\> [5, 7, 9]  
> }  
> type =\> netflow  
> }  
> }

> filter{  
> geoip {  
> source =\> "[source][ip]"  
> target =\> "source\_geoip"  
> }  
> geoip {  
> source =\> "[destination][ip]"  
> target =\> "destination\_geoip"  
> }

> if [destination\_geoip][location][lon] and [destination\_geoip][location][lat] {  
> mutate { add\_field =\> { "[destination][geo][location]" =\> "%{[destination\_geoip][location][lon]} , %{[destination\_geoip][location][lat]}" }}  
> }  
> if [source\_geoip][location][lon] and [source\_geoip][location][lat] {  
> mutate { add\_field =\> { "[source][geo][location]" =\> "%{[source\_geoip][location][lon]} , %{[source\_geoip][location][lat]}" }}  
> }  
> }

> output to elasticsearch

---

<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 16, 2020, 3:53pm UTC](https://discuss.elastic.co/t/geo-point-type-error-for-map-visualization-in-kibana/233182/8 "2020-06-16T15:53:51Z")

</div>

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