CiviCRM does not provide proximity search functionality via its Views module. This project aims to add that functionality so views created as member directories or constituent search forms can have a proximity search field as well. The skeleton of this project was taken from the OpenLayers Proximity project, but has been heavily modified to work with CiviCRM.

Currently no other projects implement this functionality.

Comments

qjensen’s picture

qjensen commented
Title: CiviCRM Proximity Search » Forgot project link

Here is a link to the project page. Forgot to add to description

http://drupal.org/sandbox/qjensen/1103348

attiks’s picture

attiks commented
Title: Forgot project link » CiviCRM Proximity Search
Status: Active » Needs review

resetting title

sreynen’s picture

sreynen commented
Component: new project application » module
Issue tags: +PAReview: CiviCRM

Tagging this to make it easier for CiviCRM reviewers to find.

ralt’s picture

ralt commented
Priority: Normal » Critical

Changing priority according to the new priority guidelines.

pillarsdotnet’s picture

pillarsdotnet commented

Will review as soon as I fix current problems in my own CiviCRM installation.

klausi’s picture

klausi
he/him||they/them
Primary language German
Location 🇦🇹 Vienna
commented
Priority: Critical » Normal
Status: Needs review » Needs work

Have you researched existing civicrm modules? could your functionality live in one of those modules? It is always better to join forces than to fragment the efforts over a wide range of modules. Please consider this option or explain why you need to do it on your own.

Other issues:
* Git release branch is missing, see http://drupal.org/node/1015226
* remove LICENSE.txt, it will be added by drupal.org packaging.
* module file: @file doc block is missing, see http://drupal.org/node/1354#files
* array formatting: the closing ")" should be one level to the right
* "module_invoke_all('measurement_units');" hooks defined by your module should be prefixed with your module name
* If your module defines hooks ==> a .api.php file would be nice
* "@param $address Address or location name." the parameter description should be on a new line, see http://drupal.org/node/1354#functions
* your module depends on PHP curl. I'm not sure if the civicrm module already requires this, if not you should add hook_requirements().
* Views classes have no doc block

petednz’s picture

petednz commented

am i right in thinking that the main functionality this provides is that it enables 'things' other than nodes (in this case civievents) to be indexed and then have that indexing utilised via Views

qjensen’s picture

qjensen commented

Thanks for the feedback and issues list. I will work on getting those fixed.

I looked around before creating the module to see if the concept would fit with another active module and I didn't find anything, which is why I started from scratch. CiviCRM maintains its own lat/long info with contact records so the module works directly with the CiviCRM tables to enable the views exposed filter by distance. It is very specific to CiviCRM and maybe it would make sense to see if I can get it included with CiviCRM's views integration in the future. The module would need more testing and feedback for that to happen so I started out creating it as a separate project.

If anyone has suggestions for other modules that would be a good home for this feature I am open.

misc’s picture

misc commented

@qjensen has been contacted to ask if the application is abandoned.

After ten weeks with a status of needs work: the applicant may be contacted by a reviewer to determine whether the application was indeed abandoned. The action taken by the reviewer should be documented in the project application issue.

http://drupal.org/node/894256

misc’s picture

misc commented
Status: Needs work » Closed (won't fix)

The application has been closed. If you would like to reopen it, you are free to do so.
See http://drupal.org/node/894256#abandonedtwoweekscontact