Using Views Global Filter with Geofield 7.x-2.x proximity

Hi Nico,
Thanks for your interest in Views Global Filter.
Yep I'm about to do the same thing. One thing for sure: use Geofield 7.x-2.0-xxxx as 7.x-1.x does not have the Views filter capabilities.

Are you just using a tabular View or is the end game to filter maps by proximity to an entered location or visitor location?
How is the location entered? Via postal address, lat/long or widget? If so, which one?

Rik

Hi Nico,

Which DrupalCon presentation?
The Sydney one? http://www.youtube.com/watch?v=iznuDhjAFbg
Or the Portland one? http://www.youtube.com/watch?v=BPXDrln0QB0&feature=youtu.be

Both might be relevant to you (the first one mentions Foursquare and has a demo of IP Geolocation Views and Maps with Views Global Filter, albeit in a different context to yours.

This site goes half way where you want to go I think: http://greatcalgaryfestivals.ca/ (scroll down for the map)

Also, are you aware of the "IP Geolocation Views and Maps" for mapping and how it features Location-Based Services HTML5 to locate the user with Smart IP as a backup?

Will you need location marker differentiation by content type, taxonomy or any field in your View? See this lovely site: http://stallspot.co.nz/discover

Rik

Hi Nico,

Thanks! And more goodies coming in IPGV&M....
No I didn't personally do the Calgary site, but gave the site builder a few hints, in particular w.r.t to the animated marker clustering.

I'll set up a test rig as I've been wanting to use Views Global Filter with Geofield 7.x-2.x for a while myself.
I'll make an estimate of the work involved, so I can plan next steps.

This may involve patches/extensions on the Geofield as well as on the Gloal Filter sides.

I was in the panel presentation with Brandonian the current maintainer of Geofield, so hopefully between all of us we can push this on through.

Rik

Sooo.... after closer inspection... the first issue is that Geofield 7.x-2.x does not feature a Views contextual filter for proximity -- it only has a "normal" UI filter.

We need Geofield to expose a Views contextual filter for Views Global Filter to do its thing.

So we need to either submit a feature request with the maintainer of the Geofield module or submit a patch to him.

Then we can create a Views Global Filter option for global proximity filtering, along the lines of what already exists for the Location module when used with Views Global Filter.

Switching to the Location module may in fact be the quickest implementation path for you, Nico, unless you're already entrenched in Geofield as the location coordinates storage module.
Architecturally I prefer Geofield over Location, as Geofield uses the D7 field & entity API's, but to the end user that makes little difference.

Rik

What if Views Global Filter supported regular filters?

That would be both wonderful and very ambitious... It's a thought that will keep lingering in the back of my mind...

So from that first patch in #1901750: Integrate Smart IP with Geofield's Views proximity handlers, if you change:

      // Use Smart IP location, if module loaded.
      if (module_exists('smart_ip')) {
        return array(
         'latitude' => $_SESSION['smart_ip']['location']['latitude'],
         'longitude' => $_SESSION['smart_ip']['location']['longitude']
       );
        ....

to

      // Use IP Geolocation, if module loaded.
      if (module_exists('ip_geoloc')) {
        $location = ip_geoloc_get_visitor_location(); 
        return isset($location['latitude'] ? 
          ? array('latitude' => $location['latitude'], 'longitude' => $location['longitude'])
          : array('latitude' => 0, 'longitude' => 0);
      ....

then you get the visitor's HTML5 location (satellite and Wifi based), with the IP address-based lookup by Smart IP as a backup.

You'll probably want to to do a similar thing for the second part of the patch:

    if (module_exists('smart_ip') && !empty($_SESSION['smart_ip']['location']['city'])) {
      $smartip_city = $_SESSION['smart_ip']['location']['city'];
      $smartip_country = $_SESSION['smart_ip']['location']['country'];
      ...

becomes:

    if (module_exists('ip_geoloc')) {
       $location = ip_geoloc_get_visitor_location(); 
       if (isset($location['locality'])) {
         $smartip_city = $location['locality'];
         $smartip_country = $location['country'];
         ...

Actually forget all of the above in #9.
I just created this #2011340: Geofield plugin to extend proximity filtering based on postal address with option to use HTML5 location.
Give that a go. It works nicely for me.
All it needs is a bit of CSS to style the distance and address input fields.

Haha... maybe there's a career for me as Santa...

The latest version of Views Global Filter 7.x-1.x-dev has a Proximity global filter that works with the Location module as well as Geofield 7.x-2.x (provided this patch, #2014345: Geofield plugin for Contextual Proximity Filter is applied).

The Proximity filter comes with its own widget, which prompts the user for a distance from a reference point. The reference point can be entered as a partial address (eg "Broadway, New York") or left blank, in which case the visitor's current HTML5-retrieved location will be used.

I think would be nice to put efforts on:

Geofield Proximity Filter

To make it a real project :)

Tried both field and views solutions and can't seem to put it together to create a views global filter block to work with geofield proximity.
Is it currently working for everybody else ?

Set up is:
------------

- a content type has addressfield and geofield. Geofield gets its input from geocoded addressfield.
- trying to filter two views with the same views global filter block.

Problem: Can't seem to find geofield proximity filter field selection in global views block.
There is only geofield field. When this field is selected, non of the widget selections comes up with
a solution...

Tried creating a view instead of using field to feed the global views block... Still no luck.

Thanks for any input.

@sbydrupal
Sorry it's not working for you.

Can you please confirm you're using Geofield 2.x with the patch from #13 in this thread?
And Global Filter 7.x-1.x ?

Rik

Thanks Rik for your quick reply as I got stuck on this subject, and much appreciate your help.

Yes, Global Filter version is 7.x-1.11
and Geofield version is 7.x-2.1

They are both last versions posted.

Just applied patch #34 to geofield handler argument proximity #24 at the link below:
https://drupal.org/node/2014345#comment-7638461

There is no change in the results so far. In the global view filter block, I see "geo field" and select it. Then, the only widget related to geo field is "Inherit geocoder widget from field Geofield", which doesn't provide any results...

What am I doing wrong here ?

Thanks!

Hmmm... Not sure. I'm not even near a computer right now.
You'll have to wait for my help till the weekend
Rik

Thanks Rik. The set up is as mentioned above:

In a content type,

- created addressfield
- created geofield as having input from addressfield

In Global Views filter block, I see only geofield and widget is "inherit geocode widget..."

Thanks!