# Geo\_point and the logstash-\* index
**URL:** https://discuss.elastic.co/t/geo-point-and-the-logstash-index/79854
**Category:** Logstash
**Created:** [March 24, 2017, 7:05am UTC](https://discuss.elastic.co/t/geo-point-and-the-logstash-index/79854 "2017-03-24T07:05:17Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@mikemi](https://discuss.elastic.co/u/mikemi)
#### Post date: [March 24, 2017, 7:05am UTC](https://discuss.elastic.co/t/geo-point-and-the-logstash-index/79854/1 "2017-03-24T07:05:17Z")
When I use Logstash's `geoip` to encode an ip address, I get different field types in Elasticsearch when i use `logstash-foo` as an index vs `logs-foo` as an index.
`logstash-foo` (matches the default index naming convention) imports `geoip.location` as a `geo_point` field, where `logs-foo` imports `geoip.location` as a float.
I'm wondering why this happens and how I could get my arbitrary index, `logs-foo`, to import `geoip.location` fields as `geo_point`.
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [March 24, 2017, 7:08am UTC](https://discuss.elastic.co/t/geo-point-and-the-logstash-index/79854/2 "2017-03-24T07:08:06Z")
This is because Logstash installs an index template that says that the field in question should be a geo\_point field, but this index template only applies to indexes whose name matches logstash-\*.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 21, 2017, 7:08am UTC](https://discuss.elastic.co/t/geo-point-and-the-logstash-index/79854/3 "2017-04-21T07:08:09Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.