-719-5315
On Monday, January 5, 2015 9:15:51 AM UTC-5, Peter Johnson wrote:
Jörg is correct in saying that the 'geo_shape' filter only supports
finding shapes within shapes and not points within shapes.
It would be great if there was a filter which *did* support finding all
points within
Jörg is correct in saying that the 'geo_shape' filter only supports finding
shapes within shapes and not points within shapes.
It would be great if there was a filter which *did* support finding all
points within a pre-indexed shape!
You may want to open an issue regarding extending the
have a look
at https://github.com/polyfractal/elasticsearch-inquisitor#analyzer-testing
On Thursday, 1 January 2015 17:05:25 UTC, Bruno Kamiche wrote:
Thanks for your replies, that gave me the clue for what I was looking for,
and now it is solved!
On Wednesday, December 31, 2014 10:36:27
Nice. Out of curiosity are the polygons ope ndata? If so could you share the
source please?
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
for the feature (this is not a corner
case)Is this feature expected to work in some other coordinate system?
Any workaround to overcome this bug? Thanks!
Andy
On Saturday, December 27, 2014 6:40:44 AM UTC-8, Peter Johnson wrote:
Hey Andy,
I tried to fix this but you're right
Hey Andy,
I tried to fix this but you're right, it seems to be a bug. I've attached a
full bug report which you might want to add to a new github issue.
https://gist.github.com/anonymous/c250d602d1e7fe6d3655
https://gist.github.com/missinglink/6e96f06e9e6032aa6416
I also tried using 'geohash'
Did you get this working in the end Maarten?
I have the same problem with the way 'intersects' works and Jilles's
solution doesn't work for me; possibly due to the 'tree_levels' accuracy
for quad tree.
As a kind of workaround, I was thinking that you could draw 2 'envelope'
geo_shape