# Geo sorting in Elastic 5

**URL:** <https://discuss.elastic.co/t/geo-sorting-in-elastic-5/84122>\
**Category:** Elasticsearch\
**Created:** [May 1, 2017, 12:58am UTC](https://discuss.elastic.co/t/geo-sorting-in-elastic-5/84122 "2017-05-01T00:58:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mattfrater](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattfrater/32/15169_2.png) [@mattfrater](https://discuss.elastic.co/u/mattfrater)\
**Post date:** [May 1, 2017, 12:58am UTC](https://discuss.elastic.co/t/geo-sorting-in-elastic-5/84122/1 "2017-05-01T00:58:24Z")

</div>

Hi Elasticsearch. We're currently updating our clusters from 2.x to 5.x, and have noticed a large (20% +) discrepancy in goe-sorting values. The mapping uses the `geo_point` type with decimal lat/lon values, the unit type used is `km`, and the sort method we've used has always been `plane`. Is this a known issue?

Thanks

Matt Frater  
Senior Developer  
Fairfax Media

---

<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:** [May 1, 2017, 1:34am UTC](https://discuss.elastic.co/t/geo-sorting-in-elastic-5/84122/2 "2017-05-01T01:34:42Z")

</div>

Just shifting this one to #elasticsearch as it's not a specific Cloud question 🙂

---

<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:** [May 4, 2017, 1:34am UTC](https://discuss.elastic.co/t/geo-sorting-in-elastic-5/84122/3 "2017-05-04T01:34:54Z")

</div>

Closed on May 4, 2017, 1:34am UTC

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