# \[SOLVED\] Geoip.location doesn't work anymore after upgrade to 5.0

**URL:** <https://discuss.elastic.co/t/solved-geoip-location-doesnt-work-anymore-after-upgrade-to-5-0/65651>\
**Category:** Logstash\
**Created:** [November 10, 2016, 11:43am UTC](https://discuss.elastic.co/t/solved-geoip-location-doesnt-work-anymore-after-upgrade-to-5-0/65651 "2016-11-10T11:43:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tileaga](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tileaga/32/13063_2.png) [@tileaga](https://discuss.elastic.co/u/tileaga)\
**Post date:** [November 10, 2016, 11:43am UTC](https://discuss.elastic.co/t/solved-geoip-location-doesnt-work-anymore-after-upgrade-to-5-0/65651/1 "2016-11-10T11:43:27Z")

</div>

I have two float fields: `valueLatitude` and `valueLongitude` and try to send them to elasticsearch as geoip.location. In logstash configuration I have this:

```
        mutate {
            add_field => ["[location]", "%{valueLongitude}" ]
            add_field => ["[location]", "%{valueLatitude}" ]
        }

        mutate {
            rename => ["[location]", "[geoip][location]" ]
            remove_field => ["valueLatitude", "valueLongitude"]
        }

```

It worked before 5.0 without problems. Now I get a strange error:

```
illegal latitude value [268.52273331955075] for geoip.location. 

```

The strange fact is that the latitude from the log file is: `47.279341`

Did the format was changed?

---

<div class="post-metadata">

**Author:** ![tileaga](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tileaga/32/13063_2.png) [@tileaga](https://discuss.elastic.co/u/tileaga)\
**Post date:** [November 10, 2016, 12:52pm UTC](https://discuss.elastic.co/t/solved-geoip-location-doesnt-work-anymore-after-upgrade-to-5-0/65651/2 "2016-11-10T12:52:37Z")

</div>

Or, how can I do that in 5.0, maybe there is another solution.

The use case is: I have two floats (latitude and longitude) and want to show them on a map in Kibana.

---

<div class="post-metadata">

**Author:** ![tileaga](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tileaga/32/13063_2.png) [@tileaga](https://discuss.elastic.co/u/tileaga)\
**Post date:** [November 10, 2016, 1:59pm UTC](https://discuss.elastic.co/t/solved-geoip-location-doesnt-work-anymore-after-upgrade-to-5-0/65651/3 "2016-11-10T13:59:16Z")

</div>

I solved the problem. So if someone has the same use case this is the configuration part to do it:

```
mutate {
            add_field => ["[location]", "%{valueLongitude}" ]
            add_field => ["[location]", "%{valueLatitude}" ]
        }

        mutate {
            rename => ["[location]", "[geoip][location]" ]
            remove_field => ["valueLatitude", "valueLongitude"]
           convert => ["[geoip][location]", "float" ]
        }
```

---

<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:** [December 8, 2016, 1:59pm UTC](https://discuss.elastic.co/t/solved-geoip-location-doesnt-work-anymore-after-upgrade-to-5-0/65651/4 "2016-12-08T13:59:31Z")

</div>

Closed on December 8, 2016, 1:59pm UTC

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