What happens if coordinates are stored lat,lon instead of lon,lat?


I have a big index in which i have used geo_point and geo_shape (of type lineString).

The way i have stored coordinates in both above field is (lat,lon) and not (lon,lat as per documentation).

My distance queries work good, as my search queries too are with (lat,lon).

Can you foresee any problem if i continue using this format ?
What can go wrong ?

(Mark Walkom) #2

We support all these formats - https://www.elastic.co/guide/en/elasticsearch/reference/6.3/geo-point.html

So it really depends how they are mapped I guess. But if someone assumes it's lon,lat and starts querying, then they will have a weird time :wink:


Thanks Mark. This question was mostly related to array format. And you are correct i had stored [lat lon] for my geo_shape, and it gives weird results. After making it [lon lat] as per GeoJson standard, it started behaving properly.
I have increased the precision to get better results. Now i am struggling with the indexing time vs accuracy problem.

(system) #4

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