CiviCRM Community Forums (archive)

I just created a new project that adds proximity search to exposed search forms in Views. The project is available on github right now - https://github.com/qjensen/CiviCRM-Proximity-Search and I hope to have it approved and available at d.o soon. In the meantime any testing, bug reports, feedback etc are greatly appreciated.

Thanks to a suggestion from Lobo, this project is built on code from the OpenLayers Proximity project.

If you have any questions, please feel free to get in touch.

The module was written to work with the lat/long info stored with contact records, but I don't think it would be difficult to add event support. I am going to be out of the office much of today but I can take a look later.

Thanks for the bump. You question fell off my radar because of some other craziness - sorry for the delay.

The short answer is that it looks like this can be done. Event address isn't exposed in views currently so that would have to be included in the module before the proximity search would be available. It would require a little bit of work, but all the parts are there.

I haven't had a chance to make the changes requested for the module. I decided to go back to school this fall and it has been a little more difficult than I expected to juggle all of the pieces Hopefully I can finish that in the next couple of weeks.

I see that newer versions of CiviCRM already have the event address field exposed. The module was originally developed on a site running 3.3 and that version is lacking an event address field. In that case it would be fairly easy to duplicate the code that is there for contacts and replicate the functionality for events. I will take a look at it later and see what would be involved.

I appreciate you may not have the time to answer or engage - but i may as well ask.
having installed your module and i now have an exposed filter including 'great circle' but I am still not getting all the bits of the puzzle
i followed http://drupal.org/node/1112308 ie unlocked 'location' and unset Force Single and Optional.
But I still get the warning that 'location not found'
My understanding is that Open Layers Proximity requires an index to be built that I presume normally works off the geocode fields of nodes. Maybe that isn't required if we already have Lat Long (which I do and the Events are showing as a Data Layer on the Map page)
admin/build/openlayers/proximity

Looks like i am also seeing a Distance field. Not sure if that is part of the puzzle but adding it made no difference.

Can you attach your View so I can fire it up and work backwards?

Thanks Q - will give it a whirl soon(ish) - always happy to test and feedback and help document/promote

Hey qjensen and petendz: Just wondering how this all panned out, whether anyone's had a crack at porting it for D7/Views3 and Civi 4.x, and if not, where the latest version of the D6/Civi3 code lives and who wants to work at bringing it up to speed? I've got a client with geocoded data in Civi, but who's less happy with the Civi proximity search workflow and would love to be able to do this from a Views3 display and Openlayers, etc.

Our organization is willing to support development for D7/views 3. We have a budget of $100, would that cover getting it upgraded?