From f667b576f13b68b98eedfc6f033deac8c87a48ac Mon Sep 17 00:00:00 2001 From: Guillaume Mourier Date: Fri, 15 Oct 2021 10:59:01 +0200 Subject: [PATCH] =?UTF-8?q?GeoSearch=20=E2=80=94=20Support=20string=20type?= =?UTF-8?q?=20for=20`=5Fgeo`=20`lat`=20and=20`lng`=20fields=20(#83)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Update specification to support string type for _geo lat and lng fields * mention types mixing for _geo object --- text/0059-geo-search.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/text/0059-geo-search.md b/text/0059-geo-search.md index 60c2af62..22a4dccd 100644 --- a/text/0059-geo-search.md +++ b/text/0059-geo-search.md @@ -42,11 +42,12 @@ According to our user feedback, the lack of a geosearch feature is mentioned as - Name: `_geo` - Type: Object -- Format: `{lat:float, lng:float}` +- Format: `{lat:number|string, lng:number|string}` - Not required > 💡 if `_geo` is found in the document payload, `lat` and `lng` are required. > 💡 `lat` and `lng` must be of float value. +> 💡 `lat` and `lng` field type can be mixed. e.g. `lat` can be a string while `lng` is a number in the same `_geo` object. ##### **CSV Format** @@ -101,8 +102,8 @@ csv format example "brand": "F40 LM", "brand": "Ferrari", "_geo": { - "lat": 48.862725, - "lng": 2.287592 + "lat": "48.862725", + "lng": "2.287592" } } ]