# No Compatible Fields: The "logstash-\*" index pattern does not contain any of the following field types: geo\_point
**URL:** https://discuss.elastic.co/t/no-compatible-fields-the-logstash-index-pattern-does-not-contain-any-of-the-following-field-types-geo-point/110473
**Category:** Logstash
**Created:** [December 6, 2017, 9:06am UTC](https://discuss.elastic.co/t/no-compatible-fields-the-logstash-index-pattern-does-not-contain-any-of-the-following-field-types-geo-point/110473 "2017-12-06T09:06:16Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@bianchi74](https://discuss.elastic.co/u/bianchi74)
#### Post date: [December 6, 2017, 9:06am UTC](https://discuss.elastic.co/t/no-compatible-fields-the-logstash-index-pattern-does-not-contain-any-of-the-following-field-types-geo-point/110473/1 "2017-12-06T09:06:16Z")
Hi all,
when I try to create a "Coordinate Map" I receive the following error message:
> No Compatible Fields: The "logstash-\*" index pattern does not contain any of the following field types: geo\_point
My coordinates are converted into the following logstash config file:
```
filter {
...
grok {
match => { "iotEvent_location" => "%{NUMBER:lon} %{NUMBER:lat}" }
}
mutate {
rename => ["lat", "[geoComplaint][location][lat]", "lon", "[geoComplaint][location][lon]" ]
}
mutate {
convert => ["[geoComplaint][location][lat]", "float" ]
convert => ["[geoComplaint][location][lon]", "float" ]
}
}
output {
elasticsearch {
hosts => "localhost:9200"
index => "logstash-%{+dd.MM.YYYY}"
document_type => "iotEvent"
template => "/Users/iBianchi/Documents/_dev-tools/logstash-6.0.0/bin/logstash.json"
template_name => "logstash"
template_overwrite => true
}
}
```
This is an extract of the mapping file I pass to logstash:
```
"mappings": {
"iotEvent": {
"properties": {
...
"geoComplaint": {
"dynamic": true,
"type": "object",
"path": "full",
"properties": {
"location": {
"type": "geo_point"
}
},
},
...
"dynamic_templates": [
{
"string_template": {
"match": "*",
"match_mapping_type": "string",
"mapping": {
"type": "keyword"
}
}
}
]
```
This is an extract of the mapping file returned by Elastic Search:
```
"geoComplaint" : {
"properties" : {
"location" : {
"properties" : {
"lat" : {
"type" : "float"
},
"lon" : {
"type" : "float"
}
}
}
}
}
```
Finally, this is a document indexed by Elasticsearch:
```
{
"_index": "logstash-05.12.2017",
"_type": "iotEvent",
"_id": "AWAq_n3-cKCic2a1eVPM",
"_version": 1,
"_score": null,
"_source": {
"event_certainty": 1,
"geoComplaint": {
"location": {
"lat": 7.61528,
"lon": 45.15471
}
},
"body": "",
"version": 1,
"event_type_id": 0,
"iotEvent_location": "45.15471-7.61528",
"@timestamp": "2017-12-05T04:36:20.000Z",
"iotEvent_source": "http://services.infoblu.it/BITW/data?id=teamd26lkc",
"temporal_granularity": null,
"@version": "1",
"attributes": {
"sourceCode": "35477",
"endCode": "35476",
"offset": "3",
"metric": "speed",
"dstCoordinates": "45.13841-7.62777",
"srcCoordinates": "45.15471-7.61528",
"value": "62",
"tags": "sourceCode,endCode,offset"
},
"id": "it.gov.daf.kafkaProducers.eventConverters.InfoBluTrafficConverter.1512448580000.2",
"event_subtype_id": null,
"event_annotation": null,
"coords": "7.61528,45.15471",
"ts": 1512448580000
},
"fields": {
"@timestamp": [
1512448580000
]
},
"sort": [
1512448580000
]
}
```
I have the same problem using ELK 6.0.0 and ELK 5.6.4.
Can you help me?
Thanks!
---
### Author:  [@LeeDr](https://discuss.elastic.co/u/LeeDr)
#### Post date: [December 6, 2017, 5:19pm UTC](https://discuss.elastic.co/t/no-compatible-fields-the-logstash-index-pattern-does-not-contain-any-of-the-following-field-types-geo-point/110473/2 "2017-12-06T17:19:53Z")
Hi Marco,
When you look in Kibana Management \> Index Patterns and select your index pattern you need to see the type as geo\_point as shown below. But based on the mapping you got back from Elasticsearch for your index I'm thinking you're not going to see that.
This is really a logstash/elasticsearch issue to get logstash mapping correct vs a Kibana issue so I'm probably not the best person to help you solve this issue. Here's some other related issues I found in the Kibana forum, but if these don't help you I recommend you search for geo\_point in the logstash discuss channel.
> [@Kibana showing geo-ip location as number not as geopoint](https://discuss.elastic.co/t/kibana-showing-geo-ip-location-as-number-not-as-geopoint/75600):
>
> my template is as below { "template" : "iisnew", "settings": { "index.refresh\_interval": "5s" }, "mappings" : { "iisnew" : { "properties": { "@timestamp":{"type":"date","format":"dateOptionalTime"}, "@version":{"type":"string", "index" : "not\_analyzed"}, "tags":{"type":"string"}, "type":{"type":"string"}, "geoip":{ "properties":{ "city\_name":{"type":"string", "index":"not\_analyzed"}, "continent\_code":{"type":"string"}, "country\_code2":{"type":"string"}, "country\_code3":…
> [@Getting Kibana's geo hash with geo\_point type to work](https://discuss.elastic.co/t/getting-kibanas-geo-hash-with-geo-point-type-to-work/41243):
>
> I posted an issue on Github, forgetting all about the discussion forums here. [issue outlined on github](https://github.com/elastic/kibana/issues/6159) logstash 2.2.0 kibana 4.4.0 elasticsearch 2.2.x #copy / paste from github# I have the following mapping applied to an index, pulled via \_mapping API endpoint: "cse-2016.02.09" : { "mappings" : { "event" : { "properties" : { "@timestamp" : { "type" : "date", "format" : "strict\_date\_optional\_time||epoch\_millis" }, "host" : { "type" : "string" }, "src\_ip" : { "type" : "string", …
> [@Geo\_point coming from geoip are not plotting in Kibana](https://discuss.elastic.co/t/geo-point-coming-from-geoip-are-not-plotting-in-kibana/103260):
>
> I have been tweaking my mappings and logstash pipeline configurations for days now trying to figure out hwo to plot GeoIPs to no avail. I have no idea what to do anymore. I have a template: { "template" : "httpd\*", "version" : 1, "settings" : { "index.refresh\_interval" : "5s", "number\_of\_replicas": 0 }, "mappings": { "apache\_logs": { "properties": { "@timestamp": { "type": "date" }, "@version": { "type": "text", …
> [@Expected geo\_point type on field \[geoip.location\], but got \[double\]](https://discuss.elastic.co/t/expected-geo-point-type-on-field-geoip-location-but-got-double/60004):
>
> I've a Tile Map visualisation that is throwing a "Expected geo\_point type on field [geoip.location], but got [double]" error. I'm a newbie with the ELK stack. My geoip json object is like the following: geoip": { "ip": "[182.2XX.XX.XXX](http://182.2XX.XX.XXX)", "country\_code2": "TH", "country\_code3": "THA", "country\_name": "Thailand", "continent\_code": "AS", "region\_name": "40", "city\_name": "Bangkok", "latitude": 1X.XXXXXXXXXXX999, "longitude": 1XX.XXXXXXXXXXX999, "timezone": "Asia/Bangkok", "real\_region\_…
Regasrds,
Lee
---
### Author:  [@bianchi74](https://discuss.elastic.co/u/bianchi74)
#### Post date: [December 13, 2017, 9:31am UTC](https://discuss.elastic.co/t/no-compatible-fields-the-logstash-index-pattern-does-not-contain-any-of-the-following-field-types-geo-point/110473/3 "2017-12-13T09:31:52Z")
Hi Lee,
thanks for your answer.
I think you are right: it seems logstash/elasticsearch issue because Kibana doesn't associate to my coordinates the geo\_point type. Even if the mapping file seems to be correct, the field is incorrectly seen as a double...
I'll try to post the issue on the logstash channel.
Best regards,
Marco
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 10, 2018, 9:32am UTC](https://discuss.elastic.co/t/no-compatible-fields-the-logstash-index-pattern-does-not-contain-any-of-the-following-field-types-geo-point/110473/4 "2018-01-10T09:32:15Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.