Elasticsearch filter by several geo_points with different weights
I have a number of documents that, apart from other fields, have a number of geo_point
s associated with them. I want to find all documents that are associated with a particular city. To that end, I also have an index of cities, I search it first and get a list of coordinates with the _score
s from that search. Now I want to pass that data to the document search and multiply the score of the found documents by the corresponding city score.
Assuming the first query returns a list of tuples like [(city_coords, city_score), (...)]
, I want to build the query to the document index using the function_score
and the functions
array with each city as a separate function with its separate score.
However, when I construct the query in its simplest form, it fetches all the documents in my index. Here's what the query I have made:
{
'query': {
'function_score': {
'functions': [
{
"filter": {
"geo_distance": {
"distance": "1km",
"distance_type": "plane",
"points": city_coords
},
},
'weight': city_score
}
]
}
}
}
Am I missing something? How do I get only the documents that are associated with that particular city?
elasticsearch geo
add a comment |
I have a number of documents that, apart from other fields, have a number of geo_point
s associated with them. I want to find all documents that are associated with a particular city. To that end, I also have an index of cities, I search it first and get a list of coordinates with the _score
s from that search. Now I want to pass that data to the document search and multiply the score of the found documents by the corresponding city score.
Assuming the first query returns a list of tuples like [(city_coords, city_score), (...)]
, I want to build the query to the document index using the function_score
and the functions
array with each city as a separate function with its separate score.
However, when I construct the query in its simplest form, it fetches all the documents in my index. Here's what the query I have made:
{
'query': {
'function_score': {
'functions': [
{
"filter": {
"geo_distance": {
"distance": "1km",
"distance_type": "plane",
"points": city_coords
},
},
'weight': city_score
}
]
}
}
}
Am I missing something? How do I get only the documents that are associated with that particular city?
elasticsearch geo
add a comment |
I have a number of documents that, apart from other fields, have a number of geo_point
s associated with them. I want to find all documents that are associated with a particular city. To that end, I also have an index of cities, I search it first and get a list of coordinates with the _score
s from that search. Now I want to pass that data to the document search and multiply the score of the found documents by the corresponding city score.
Assuming the first query returns a list of tuples like [(city_coords, city_score), (...)]
, I want to build the query to the document index using the function_score
and the functions
array with each city as a separate function with its separate score.
However, when I construct the query in its simplest form, it fetches all the documents in my index. Here's what the query I have made:
{
'query': {
'function_score': {
'functions': [
{
"filter": {
"geo_distance": {
"distance": "1km",
"distance_type": "plane",
"points": city_coords
},
},
'weight': city_score
}
]
}
}
}
Am I missing something? How do I get only the documents that are associated with that particular city?
elasticsearch geo
I have a number of documents that, apart from other fields, have a number of geo_point
s associated with them. I want to find all documents that are associated with a particular city. To that end, I also have an index of cities, I search it first and get a list of coordinates with the _score
s from that search. Now I want to pass that data to the document search and multiply the score of the found documents by the corresponding city score.
Assuming the first query returns a list of tuples like [(city_coords, city_score), (...)]
, I want to build the query to the document index using the function_score
and the functions
array with each city as a separate function with its separate score.
However, when I construct the query in its simplest form, it fetches all the documents in my index. Here's what the query I have made:
{
'query': {
'function_score': {
'functions': [
{
"filter": {
"geo_distance": {
"distance": "1km",
"distance_type": "plane",
"points": city_coords
},
},
'weight': city_score
}
]
}
}
}
Am I missing something? How do I get only the documents that are associated with that particular city?
elasticsearch geo
elasticsearch geo
asked Jan 1 at 16:02
IbolitIbolit
5,25153663
5,25153663
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Since you don't specify a query in your function_score
part, Elastic assume a match_all query. So it returns all documents and add a boost for the documents near the selected queries.
You should add a specific query in your function_score part that will filter out any document that is not near enough of the selected cities. Something like
{
"query": {
"function_score": {
"query": {
"bool": {
"should": [
{
"geo_distance": {
"distance": "1km",
"distance_type": "plane",
"points": city_coords1
}
},
{
"geo_distance": {
"distance": "1km",
"distance_type": "plane",
"points": city_coords2
}
},
... and so on
]
}
},
"functions": [
{
"filter": {
"geo_distance": {
"distance": "1km",
"distance_type": "plane",
"points": city_coords
},
},
"weight": city_score
}
]
}
}
}
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53996900%2felasticsearch-filter-by-several-geo-points-with-different-weights%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Since you don't specify a query in your function_score
part, Elastic assume a match_all query. So it returns all documents and add a boost for the documents near the selected queries.
You should add a specific query in your function_score part that will filter out any document that is not near enough of the selected cities. Something like
{
"query": {
"function_score": {
"query": {
"bool": {
"should": [
{
"geo_distance": {
"distance": "1km",
"distance_type": "plane",
"points": city_coords1
}
},
{
"geo_distance": {
"distance": "1km",
"distance_type": "plane",
"points": city_coords2
}
},
... and so on
]
}
},
"functions": [
{
"filter": {
"geo_distance": {
"distance": "1km",
"distance_type": "plane",
"points": city_coords
},
},
"weight": city_score
}
]
}
}
}
add a comment |
Since you don't specify a query in your function_score
part, Elastic assume a match_all query. So it returns all documents and add a boost for the documents near the selected queries.
You should add a specific query in your function_score part that will filter out any document that is not near enough of the selected cities. Something like
{
"query": {
"function_score": {
"query": {
"bool": {
"should": [
{
"geo_distance": {
"distance": "1km",
"distance_type": "plane",
"points": city_coords1
}
},
{
"geo_distance": {
"distance": "1km",
"distance_type": "plane",
"points": city_coords2
}
},
... and so on
]
}
},
"functions": [
{
"filter": {
"geo_distance": {
"distance": "1km",
"distance_type": "plane",
"points": city_coords
},
},
"weight": city_score
}
]
}
}
}
add a comment |
Since you don't specify a query in your function_score
part, Elastic assume a match_all query. So it returns all documents and add a boost for the documents near the selected queries.
You should add a specific query in your function_score part that will filter out any document that is not near enough of the selected cities. Something like
{
"query": {
"function_score": {
"query": {
"bool": {
"should": [
{
"geo_distance": {
"distance": "1km",
"distance_type": "plane",
"points": city_coords1
}
},
{
"geo_distance": {
"distance": "1km",
"distance_type": "plane",
"points": city_coords2
}
},
... and so on
]
}
},
"functions": [
{
"filter": {
"geo_distance": {
"distance": "1km",
"distance_type": "plane",
"points": city_coords
},
},
"weight": city_score
}
]
}
}
}
Since you don't specify a query in your function_score
part, Elastic assume a match_all query. So it returns all documents and add a boost for the documents near the selected queries.
You should add a specific query in your function_score part that will filter out any document that is not near enough of the selected cities. Something like
{
"query": {
"function_score": {
"query": {
"bool": {
"should": [
{
"geo_distance": {
"distance": "1km",
"distance_type": "plane",
"points": city_coords1
}
},
{
"geo_distance": {
"distance": "1km",
"distance_type": "plane",
"points": city_coords2
}
},
... and so on
]
}
},
"functions": [
{
"filter": {
"geo_distance": {
"distance": "1km",
"distance_type": "plane",
"points": city_coords
},
},
"weight": city_score
}
]
}
}
}
answered Jan 2 at 10:45


Pierre MalletPierre Mallet
3,4231618
3,4231618
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53996900%2felasticsearch-filter-by-several-geo-points-with-different-weights%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown