New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug in geo_bounding_box #9067
Labels
:Analytics/Geo
Indexing, search aggregations of geo points and shapes
Comments
The co-ordinates you specified are see: #9080 |
clintongormley
added
the
:Analytics/Geo
Indexing, search aggregations of geo points and shapes
label
Dec 29, 2014
nknize
added a commit
to nknize/elasticsearch
that referenced
this issue
Dec 30, 2014
ShapeBuilder expected coordinates for Envelope types in strict Top-Left, Bottom-Right order. Given that GeoJSON does not enforce coordinate order (as seen in elastic#8672) clients could specify envelope bounds in any order and be compliant with the GeoJSON spec but not the ES ShapeBuilder logic. This change loosens the ShapeBuilder requirements on envelope coordinate order, reordering where necessary. closes elastic#2544 closes elastic#9067 closes elastic#9079 closes elastic#9080
nknize
added a commit
that referenced
this issue
Dec 30, 2014
ShapeBuilder expected coordinates for Envelope types in strict Top-Left, Bottom-Right order. Given that GeoJSON does not enforce coordinate order (as seen in #8672) clients could specify envelope bounds in any order and be compliant with the GeoJSON spec but not the ES ShapeBuilder logic. This change loosens the ShapeBuilder requirements on envelope coordinate order, reordering where necessary. closes #2544 closes #9067 closes #9079 closes #9080
nknize
added a commit
that referenced
this issue
Dec 30, 2014
ShapeBuilder expected coordinates for Envelope types in strict Top-Left, Bottom-Right order. Given that GeoJSON does not enforce coordinate order (as seen in #8672) clients could specify envelope bounds in any order and be compliant with the GeoJSON spec but not the ES ShapeBuilder logic. This change loosens the ShapeBuilder requirements on envelope coordinate order, reordering where necessary. closes #2544 closes #9067 closes #9079 closes #9080
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
ShapeBuilder expected coordinates for Envelope types in strict Top-Left, Bottom-Right order. Given that GeoJSON does not enforce coordinate order (as seen in elastic#8672) clients could specify envelope bounds in any order and be compliant with the GeoJSON spec but not the ES ShapeBuilder logic. This change loosens the ShapeBuilder requirements on envelope coordinate order, reordering where necessary. closes elastic#2544 closes elastic#9067 closes elastic#9079 closes elastic#9080
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, i have many objects.
Create index:
But when i search objects with current request:
I have many right results, but one or two objects have these coordinates:
[lat] => 55.1100127
[lon] => 37.9883611
This object is close, but not in requested area.
How can it be?
Sorry, i am from Russia.
The text was updated successfully, but these errors were encountered: