Wrong order of passed parameters in GeoBoundingBox method

[akisiel]

Hi!

During development in our project we have discovered that in current version (we're using 1.1.1) there is wrong order of given parameters in GeoBoundingBox method.

In this method's signature you ask for: topLeftX (means top left corner longitide), topLeftY (top left corner latitude), bottomRightX (bottom right corner longitude) and bottomRightY (bottom right corner latitude) - https://github.com/elasticsearch/elasticsearch-net/blob/8a93e9d5afd21b075d8c5ddec489f7c5b4bbeceb/src/Nest/DSL/Filter/FilterDescriptor.cs#L175 . Parameters are passed to the json as a string in same order (means long, lat) while in elasticsearch documentation says that if you're passing data as a string you should pass first latitude and then longitude (http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-geo-bounding-box-filter.html#_lat_lon_as_string_3). Can you please check this and correct?

[gmarz]

@akisiel

You are absolutely right, this is definitely a bug- a pretty bad one at that. I just pushed the above fix and we'll try and get a new release out asap. Thank you very much for finding and reporting this!

[akisiel]

No problem and thanks for quick solving :)