# Elasticsearch not accepting data for geoip.location where the latitude is above \[-90.0\]

**URL:** <https://discuss.elastic.co/t/elasticsearch-not-accepting-data-for-geoip-location-where-the-latitude-is-above-90-0/40058>\
**Category:** Elasticsearch\
**Created:** [January 25, 2016, 7:36pm UTC](https://discuss.elastic.co/t/elasticsearch-not-accepting-data-for-geoip-location-where-the-latitude-is-above-90-0/40058 "2016-01-25T19:36:00Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rahul](https://avatars.discourse-cdn.com/v4/letter/r/f14d63/32.png) [@Rahul](https://discuss.elastic.co/u/Rahul)\
**Post date:** [January 25, 2016, 7:36pm UTC](https://discuss.elastic.co/t/elasticsearch-not-accepting-data-for-geoip-location-where-the-latitude-is-above-90-0/40058/1 "2016-01-25T19:36:00Z")

</div>

We are trying to load the webserver logs to ElasticSearch version: 2.1.1. where we have created proper template and able to index data.

However, we are having issue with the latitude value which are above [-90.0] for geoip.location.

**Mapping is:**  
:  
"geoip": {  
:  
"location": {  
"doc\_values": true,  
"type": "geo\_point"  
},  
:  
}

**Sample:**  
curl -XPOST "localhost:9204/server\_access\_log\_2016.01.26/data?ignore\_conflicts=true" -d '{"geoip":{"ip":"127.0.0.1","country\_code2":"US","region\_name":"NA","city\_name":"NA","postal\_code":"0","latitude":"38.0","longitude":"-97.0","dma\_code":"0","area\_code":"0","timezone":"NA","real\_region\_name":"NA","location":"-97.0,38.0","coordinates":"-97.0,38.0"}}'

**Error:**  
type:"illegal\_argument\_exception" reason:"illegal latitude value [-97.0] for geoip.location"}}

---

<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:** [January 25, 2016, 8:41pm UTC](https://discuss.elastic.co/t/elasticsearch-not-accepting-data-for-geoip-location-where-the-latitude-is-above-90-0/40058/2 "2016-01-25T20:41:52Z")

</div>

It only goes from (+)90 to -90, that's 180 degrees which is half the earth.

-97 would be actually +7.

---

<div class="post-metadata">

**Author:** ![Rahul](https://avatars.discourse-cdn.com/v4/letter/r/f14d63/32.png) [@Rahul](https://discuss.elastic.co/u/Rahul)\
**Post date:** [January 25, 2016, 9:10pm UTC](https://discuss.elastic.co/t/elasticsearch-not-accepting-data-for-geoip-location-where-the-latitude-is-above-90-0/40058/3 "2016-01-25T21:10:28Z")

</div>

I see, but we are migrated from old Elastic search version 1.4.4 where this was not an issue. We are able to successfully post this data where latitude is [-97] for this version no. 1.4.4.  
Is the new elastic search version 2.1.1 has certain upgrades/filters?

---

<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:** [January 25, 2016, 10:46pm UTC](https://discuss.elastic.co/t/elasticsearch-not-accepting-data-for-geoip-location-where-the-latitude-is-above-90-0/40058/4 "2016-01-25T22:46:23Z")

</div>

You'd have to consult the release notes for that, I don't know that off the top of my head.

---

<div class="post-metadata">

**Author:** ![Rahul](https://avatars.discourse-cdn.com/v4/letter/r/f14d63/32.png) [@Rahul](https://discuss.elastic.co/u/Rahul)\
**Post date:** [January 27, 2016, 8:14pm UTC](https://discuss.elastic.co/t/elasticsearch-not-accepting-data-for-geoip-location-where-the-latitude-is-above-90-0/40058/5 "2016-01-27T20:14:32Z")

</div>

Sure Mark, will check that. Thanks.

---

<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 5, 2017, 11:20pm UTC](https://discuss.elastic.co/t/elasticsearch-not-accepting-data-for-geoip-location-where-the-latitude-is-above-90-0/40058/6 "2017-07-05T23:20:58Z")

</div>