We are working on updating this book for the latest version. Some content might be out of date.
A string representation, with
An object representation with
An array representation with
Everybody gets caught at least once: string geo-points are
"latitude,longitude", while array geo-points are
[longitude,latitude]—the opposite order!
Originally, both strings and arrays in Elasticsearch used latitude followed by longitude. However, it was decided early on to switch the order for arrays in order to conform with GeoJSON.
The result is a bear trap that captures all unsuspecting users on their journey to full geolocation nirvana.