This repository was archived by the owner on Apr 23, 2025. It is now read-only.
search_api + elasticsearch + location_cck spatial indexing working#94
Open
woutersf wants to merge 3 commits intoBrianAltenhofel:7.x-1.xfrom
Open
search_api + elasticsearch + location_cck spatial indexing working#94woutersf wants to merge 3 commits intoBrianAltenhofel:7.x-1.xfrom
woutersf wants to merge 3 commits intoBrianAltenhofel:7.x-1.xfrom
Conversation
Author
|
I also don't understand why the Travis CI gives all these errors. Help is more than welcome. |
Author
|
When the search_api_location FILTER (distance + radius) is enabled this will now also be passed on to the elastica query (see last commit) . //todo add view handler that allows "far to near/near to far" selection in views widget. |
Author
|
@VeggieMeat can you please advise me on how to make the continuous build succeed? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related drupal.org issue:
https://www.drupal.org/node/2804437
My Drupal 7 use case (and what problem does this fix):
I have a content-type (e.g. Organisation) with a location Field (e.g.field_organisation_location - location_cck).
I want the organisations sorted by distance and filtered on a 5 km range close to a location (in my case this is a custom elastic query).
This pull request allows the cck_location field to be indexed and filtered/sorted spatially.
The patch allows to
Custom queries already work with sorting/filtering by location/distance (which is nice).
I know this code is not perfect, but the latlong from location_cck is indexed in elasticsearch.
By the way: I am looking for advice on how to use these location data for filtering and sorting in views.