# Why does logstash not mark \[geoip\]\[location\] as "geo\_point"?

**URL:** <https://discuss.elastic.co/t/why-does-logstash-not-mark-geoip-location-as-geo-point/197309>\
**Category:** Logstash\
**Created:** [August 29, 2019, 9:52am UTC](https://discuss.elastic.co/t/why-does-logstash-not-mark-geoip-location-as-geo-point/197309 "2019-08-29T09:52:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Igor\_Belyakov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_belyakov/32/52615_2.png) [@Igor\_Belyakov](https://discuss.elastic.co/u/Igor_Belyakov)\
**Post date:** [August 29, 2019, 9:52am UTC](https://discuss.elastic.co/t/why-does-logstash-not-mark-geoip-location-as-geo-point/197309/1 "2019-08-29T09:52:20Z")

</div>

Hi. I use logstash to analyze web requests. To build a map of query, I use the geoIP module.  
When using this module I found a small error 🤓  
The documentation says:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/4/540154fe38562bd76976d37cfa2a493938eb484a.png)  
In practice, the data received does not have an any type:  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/f/bf272e5c34a28142ba54e973bcb208b978a484ea.png)  
To solve this problem, i need to use custom mapping.

Why is this field incorrectly mapped in elastic?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [August 30, 2019, 5:03pm UTC](https://discuss.elastic.co/t/why-does-logstash-not-mark-geoip-location-as-geo-point/197309/2 "2019-08-30T17:03:28Z")

</div>

Logstash and Filebeat typically creates index templates that matches indices with the standard names containing the custom mapping required for this. As your index has a custom name, these index templates does not apply and dynamic mapping instead takes place, which (correctly) identifies these two fields as float fields.

This is why you need to add a custom index template for your index.

---

<div class="post-metadata">

**Author:** ![Igor\_Belyakov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_belyakov/32/52615_2.png) [@Igor\_Belyakov](https://discuss.elastic.co/u/Igor_Belyakov)\
**Post date:** [September 11, 2019, 12:03pm UTC](https://discuss.elastic.co/t/why-does-logstash-not-mark-geoip-location-as-geo-point/197309/3 "2019-09-11T12:03:24Z")

</div>

What a surprise))) Interesting.  
Thank you!

---

<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:** [October 9, 2019, 12:12pm UTC](https://discuss.elastic.co/t/why-does-logstash-not-mark-geoip-location-as-geo-point/197309/4 "2019-10-09T12:12:01Z")

</div>

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