# Geo\_point not plotted correctly on tile map

**URL:** <https://discuss.elastic.co/t/geo-point-not-plotted-correctly-on-tile-map/29325>\
**Category:** Kibana\
**Created:** [September 15, 2015, 3:03pm UTC](https://discuss.elastic.co/t/geo-point-not-plotted-correctly-on-tile-map/29325 "2015-09-15T15:03:06Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pontipine](https://avatars.discourse-cdn.com/v4/letter/p/f0a364/32.png) [@pontipine](https://discuss.elastic.co/u/pontipine)\
**Post date:** [September 15, 2015, 3:03pm UTC](https://discuss.elastic.co/t/geo-point-not-plotted-correctly-on-tile-map/29325/1 "2015-09-15T15:03:06Z")

</div>

Hi

Kibana v4.1.1 is showing two geo\_point fields in my index, called geo1 and geo1.  
1 document I have in there have both fields, which when put into any other map plot correctly to London, UK and Surrey, UK. However when I try to plot with either of these fields in the Tile Map visualisation it plots in the Indian Ocean, as if it can't recognise the coordinates. The document itself is provided below, the mapping for both coordinate fields in elastic specifies geo\_point. Any idea what could be going on?

{  
"\_index": "logstash-2015.09.15",  
"\_type": "bro-conn\_log",  
"\_id": "AU\_RRetAm7Ywd7rqXe30",  
"\_score": null,  
"\_source": {  
"message": [ "1442316288.334983\tCi7BOD1UJatE5hbCwa\t123.123.123.123\t58186\t124.124.124.124\t80\ttcp\thttp\t11.164395\t611\t406997\tSF\tF\t0\tShADadfF\t212\t12247\t291\t427897\t(empty)"  
],  
"@version": "1",  
"@timestamp": "2015-09-15T11:24:48.334Z",  
"type": "bro-conn\_log",  
"host": "userpc",  
"uid": "Ci7BOD1UJatE5hbCwa",  
"id.orig\_h": "123.123.123.123",  
"id.orig\_p": 58186,  
"id.resp\_h": "124.124.124.124",  
"id.resp\_p": 80,  
"proto": "tcp",  
"service": "http",  
"duration": "11.164395",  
"orig\_bytes": 611,  
"resp\_bytes": 406997,  
"conn\_state": "SF",  
"local\_orig": "F",  
"missed\_bytes": 0,  
"history": "ShADadfF",  
"orig\_pkts": 212,  
"orig\_ip\_bytes": 12247,  
"resp\_pkts": 291,  
"resp\_ip\_bytes": 427897,  
"tunnel\_parents": "(empty)",  
"conn\_state\_full": "Normal SYN/FIN completion",  
"id.orig\_h\_geo": {  
"country\_code3": "GBR",  
"country\_name": "United Kingdom",  
"latitude": 51.5,  
"longitude": -0.12999999999999545,  
"coordinates": [  
51.5,  
-0.12999999999999545  
]  
},  
"id.resp\_h\_geo": {  
"country\_code3": "GBR",  
"country\_name": "United Kingdom",  
"region\_name": "N7",  
"city\_name": "Tadworth",  
"latitude": 51.2833,  
"longitude": -0.23330000000001405,  
"coordinates": [  
51.2833,  
-0.23330000000001405  
]  
}  
},  
"fields": {  
"@timestamp": [  
1442316288334  
]  
},  
"sort": [  
1442316288334  
]  
}

---

<div class="post-metadata">

**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:** [September 15, 2015, 10:23pm UTC](https://discuss.elastic.co/t/geo-point-not-plotted-correctly-on-tile-map/29325/2 "2015-09-15T22:23:04Z")

</div>

Weird, that looks correct.  
Can we see the mapping as well?

---

<div class="post-metadata">

**Author:** ![pontipine](https://avatars.discourse-cdn.com/v4/letter/p/f0a364/32.png) [@pontipine](https://discuss.elastic.co/u/pontipine)\
**Post date:** [September 17, 2015, 1:02pm UTC](https://discuss.elastic.co/t/geo-point-not-plotted-correctly-on-tile-map/29325/3 "2015-09-17T13:02:20Z")

</div>

Below is the mapping. Looking at the docs here: [https://www.elastic.co/guide/en/logstash/current/plugins-filters-geoip.html#plugins-filters-geoip-target](https://www.elastic.co/guide/en/logstash/current/plugins-filters-geoip.html#plugins-filters-geoip-target), I think it's saying if you want to use non-standard target fields with the geo filter plugin, which I do as I need 2 geoip fields per document, I need to use managed templates in the elasticsearch output section of the logstash configuration I'm using, is that right? Mapping below:

```
curl -XPUT 'http://localhost:9200/test/_mapping/bro-conn_log' -d '

```

{  
"bro-conn\_log": {  
"properties": {  
"uid": {  
"norms": {  
"enabled": false  
},  
"type": "string",  
"fields": {  
"raw": {  
"index": "not\_analyzed",  
"ignore\_above": 256,  
"type": "string"  
}  
}  
},  
"id.orig\_h\_geo": {  
"type": "nested",  
"properties": {  
"coordinates": {  
"type": "geo\_point"  
},  
"country\_code3": {  
"norms": {  
"enabled": false  
},  
"type": "string",  
"fields": {  
"raw": {  
"index": "not\_analyzed",  
"ignore\_above": 256,  
"type": "string"  
}  
}  
},  
"longitude": {  
"type": "double"  
},  
"latitude": {  
"type": "double"  
},  
"country\_name": {  
"norms": {  
"enabled": false  
},  
"type": "string",  
"fields": {  
"raw": {  
"index": "not\_analyzed",  
"ignore\_above": 256,  
"type": "string"  
}  
}  
}  
}  
},  
"host": {  
"norms": {  
"enabled": false  
},  
"type": "string",  
"fields": {  
"raw": {  
"index": "not\_analyzed",  
"ignore\_above": 256,  
"type": "string"  
}  
}  
},  
"id.resp\_h\_geo": {  
"type": "nested",  
"properties": {  
"coordinates": {  
"type": "geo\_point"  
},  
"region\_name": {  
"norms": {  
"enabled": false  
},  
"type": "string",  
"fields": {  
"raw": {  
"index": "not\_analyzed",  
"ignore\_above": 256,  
"type": "string"  
}  
}  
},  
"city\_name": {  
"norms": {  
"enabled": false  
},  
"type": "string",  
"fields": {  
"raw": {  
"index": "not\_analyzed",  
"ignore\_above": 256,  
"type": "string"  
}  
}  
},  
"country\_code3": {  
"norms": {  
"enabled": false  
},  
"type": "string",  
"fields": {  
"raw": {  
"index": "not\_analyzed",  
"ignore\_above": 256,  
"type": "string"  
}  
}  
},  
"longitude": {  
"type": "double"  
},  
"latitude": {  
"type": "double"  
},  
"country\_name": {  
"norms": {  
"enabled": false  
},  
"type": "string",  
"fields": {  
"raw": {  
"index": "not\_analyzed",  
"ignore\_above": 256,  
"type": "string"  
}  
}  
}  
}  
},  
"id.orig\_h": {  
"norms": {  
"enabled": false  
},  
"type": "string",  
"fields": {  
"raw": {  
"index": "not\_analyzed",  
"ignore\_above": 256,  
"type": "string"  
}  
}  
},  
"geoip": {  
"dynamic": "true",  
"properties": {  
"location": {  
"type": "geo\_point"  
}  
}  
},  
"type": {  
"norms": {  
"enabled": false  
},  
"type": "string",  
"fields": {  
"raw": {  
"index": "not\_analyzed",  
"ignore\_above": 256,  
"type": "string"  
}  
}  
},  
"local\_orig": {  
"norms": {  
"enabled": false  
},  
"type": "string",  
"fields": {  
"raw": {  
"index": "not\_analyzed",  
"ignore\_above": 256,  
"type": "string"  
}  
}  
},  
"@version": {  
"index": "not\_analyzed",  
"type": "string"  
},  
"id.resp\_h": {  
"norms": {  
"enabled": false  
},  
"type": "string",  
"fields": {  
"raw": {  
"index": "not\_analyzed",  
"ignore\_above": 256,  
"type": "string"  
}  
}  
},

---

<div class="post-metadata">

**Author:** ![dkanbier](https://avatars.discourse-cdn.com/v4/letter/d/4491bb/32.png) [@dkanbier](https://discuss.elastic.co/u/dkanbier)\
**Post date:** [November 12, 2015, 7:34pm UTC](https://discuss.elastic.co/t/geo-point-not-plotted-correctly-on-tile-map/29325/4 "2015-11-12T19:34:13Z")

</div>

Did you ever get this sorted? I'm having the same issue.

---

<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, 2:09pm UTC](https://discuss.elastic.co/t/geo-point-not-plotted-correctly-on-tile-map/29325/5 "2017-07-06T14:09:14Z")

</div>


