Skip to content
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

Added basic support for solr spatial search features while using ezgmaplocation extension #61

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

chaosversum
Copy link

Added basic support for solr spatial search features (http://wiki.apache.org/solr/SpatialSearch) while using ezgmaplocation extension

Documentation: https://docs.google.com/document/d/1uHjLy550dsgpzIR6d5jdjcmKA__rRuXj6Ka5SQcRszg/edit

@joekepley
Copy link
Contributor

Thanks, this sounds like a great addition! I'll try it out and take a look this week.
--Joe Kepley, eZ Diff Squad
(More Info: http://bit.ly/KMicCO)

@gggeek
Copy link
Collaborator

gggeek commented May 15, 2015

would be nice to have :-)

I'd use _lat, _long for the names of solr fields storing the separate coordinates instead of 0 and 1

Also, not sure about the roadmap for ezfind adopting solr 5 (if ever getting a new release at all). Solr 5 has a new field type which might be even better than "location": see https://cwiki.apache.org/confluence/display/solr/Spatial+Search

@@ -44,6 +45,7 @@ public function getData()
if ( !empty( $longitude ) && !empty( $latitude ) )
{
$data[self::getFieldName( $contentClassAttribute, 'coordinates' )] = $longitude . ',' . $latitude;
$data[self::getFieldName( $contentClassAttribute, 'location' )] = $latitude . ',' . $longitude;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cs (coding standards: indentation, there is a tab here)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants