From 0871073f9b676c00e310ebb1728f593a3c08d6e0 Mon Sep 17 00:00:00 2001 From: Adrin Jalali Date: Thu, 24 Nov 2016 16:05:41 +0100 Subject: [PATCH] clarification on geo distance sorting (#21779) * clarification on geo distance sorting * applying the suggested change --- docs/reference/search/request/sort.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/search/request/sort.asciidoc b/docs/reference/search/request/sort.asciidoc index 5a7c3a51f01..431f649aa08 100644 --- a/docs/reference/search/request/sort.asciidoc +++ b/docs/reference/search/request/sort.asciidoc @@ -213,7 +213,7 @@ then Elasticsearch will handle it as if there was a mapping of type [[geo-sorting]] ==== Geo Distance Sorting -Allow to sort by `_geo_distance`. Here is an example: +Allow to sort by `_geo_distance`. Here is an example, assuming `pin.location` is a field of type `geo_point`: [source,js] -------------------------------------------------- @@ -243,7 +243,7 @@ GET /_search How to compute the distance. Can either be `sloppy_arc` (default), `arc` (slightly more precise but significantly slower) or `plane` (faster, but inaccurate on long distances and close to the poles). -`sort_mode`:: +`mode`:: What to do in case a field has several geo points. By default, the shortest distance is taken into account when sorting in ascending order and the