A recent discussion on an issue pointed to the fact that elasticsearch geo format for location defined as array does not match the ones defined in GeoJSON. Instead of having the values in the array in the format of [lon, lat] (as in GeoJSON), it is expected to be in [lat, lon].
This only applies when providing the location information in arrays (and not explicit lat/lon field names). I would like to change this to match GeoJSON.
This is a breaking change, but I think it will make interoperability with other systems much simpler. If you have concerns, shout, otherwise, I will work on making this change for upcoming 0.15.
-shay.banon
On Monday, January 31, 2011 at 12:30 AM, Shay Banon wrote:
Hi fellows,
A recent discussion on an issue pointed to the fact that elasticsearch geo format for location defined as array does not match the ones defined in GeoJSON. Instead of having the values in the array in the format of [lon, lat] (as in GeoJSON), it is expected to be in [lat, lon].
This only applies when providing the location information in arrays (and not explicit lat/lon field names). I would like to change this to match GeoJSON.
This is a breaking change, but I think it will make interoperability with other systems much simpler. If you have concerns, shout, otherwise, I will work on making this change for upcoming 0.15.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.