Geofield plugin to extend proximity filtering based on postal address with option to use HTML5 location

I have done some testing and it seems to be working really well so far. Rik, I have PM'd you with a link so you can see your work out there in the wild.

Nice! At a glance, looks good, I'll take a look later to provide notes/commit.

after applying this, I did as the filter config picture says.

I get this error:
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'A' in 'where clause'

part of the views query:
AND (( A * ACOS( COS( RADIANS(45.3101717) ) * COS( RADIANS(field_data_field_geofield.field_geofield_lat) ) * COS( RADIANS(field_data_field_geofield.field_geofield_lon) - RADIANS(-89.0166135) ) + SIN( RADIANS(45.3101717) ) * SIN( RADIANS(field_data_field_geofield.field_geofield_lat) ) ) ) <= A) ))

I have to say that we have been running this patch for the last few weeks without issue. @SocialNicheGuru when you get a chance, can you follow up to see if running update.php fixes your issue, so we can push this patch along?

This patch worked great for me as well, it threw an error until I ran update.php, so that might be @SocualNicheGuru issue.

I have tried this recently and I keep getting "Visitor Location not available" - I can see this is called from the new .inc file - does this suggest something wrong with the geolocating?

go to admin/config/system/ip_geoloc and make sure you select some user roles for which the HTML5 location may be sampled and reverse-geocoded to a street address

the above works. I re-installed and applied.

maybe it is better to put a "my location" button there, so that the user can easily locate to the current position anytime. just like the geolocation field widget.

Agreed that a "My location" button would be a good prompt.

mention branch to use

Re #4 RdeBoer-

Alternatively, using a hook or CTools plugin approach the proximity plugin system in Geofield could be made more extensible, so that the above geofieldProximityGeocoderWithHTML5.inc plugin could live in the IPGV&M module.

I think that's what is being requested in #2134777: Allow other modules to define their own proximity plugins which would then make it easy for this to live in IPGV&M.

I really need the "My location" Option, anyone has any idea or can point me where and how to modify the code to accomplish this?

Thanks!

Hello,

• I would like to confirm that this patch works as described.
• Feature Request to pre-populate the field with the visitor's city and state data as text.

Thanks RdeBoer this is going to help my site shine.

Jay

Rik,

Is this going to get committed?

Jay

This seems like a really helpful enhancement.

Are we at all close to getting this committed?

Thanks.

I have tried the patch, and it seems quite good but I have 2 questions:

- When the user inputs an address, the proximity field seems to provide the distance from the user, not from the address that was input

- When the user inputs an address, the map is centered on the user's location, not the location that was input

Perhaps these issues are related, and perhaps there is some user error involved?

Is there something I should be doing differently on my end?

I am getting a lot of this warning, Anyway to debug the reason for this or how to improve the location detection?

Thanks

@jsibley have you found a solution? I also need to center the map on the input location.

@rofsky, I haven't found a solution yet, but I might have a clue.

I don't know the internals of Drupal and of views well, but I think that the patch takes care of filters and sorting in views, but might not have patched where the actual field that gets displayed.

When I look at the SQL returned by the view and put in a location as an exposed filter, I see the values for the filter change, but the value of the field does not.

So, here is what I see for the field after I have put an address into the exposed filter:

( 3959 * ACOS( COS( RADIANS(40.813642200000004) ) * COS( RADIANS(field_collection_item_field_data_field_address_plus_phone__field_data_field_geoaddress.field_geoaddress_lat) ) * COS( RADIANS(field_collection_item_field_data_field_address_plus_phone__field_data_field_geoaddress.field_geoaddress_lon) - RADIANS(-74.21709899999999) ) + SIN( RADIANS(40.813642200000004) ) * SIN( RADIANS(field_collection_item_field_data_field_address_plus_phone__field_data_field_geoaddress.field_geoaddress_lat) ) ) ) AS field_collection_item_field_data_field_address_plus_phone__f

Here is what I see in the filter:

where ......(( 3959 * ACOS( COS( RADIANS(40.9792645) ) * COS( RADIANS(field_collection_item_field_data_field_address_plus_phone__field_data_field_geoaddress.field_geoaddress_lat) ) * COS( RADIANS(field_collection_item_field_data_field_address_plus_phone__field_data_field_geoaddress.field_geoaddress_lon) - RADIANS(-74.1165313) ) + SIN( RADIANS(40.9792645) ) * SIN( RADIANS(field_collection_item_field_data_field_address_plus_phone__field_data_field_geoaddress.field_geoaddress_lat) ) ) ) <= 10) ))

The sort uses a label from the field, so it will also be incorrect.

Unfortunately, I don't know where this would need to be changed in the code. Hope this helps, though.

Jonathan

Rik, are you saying that once the patch mentioned in #15 is committed, you would be willing to create a new patch with the HTML5 functionality? Would that potentially resolve the proximity field issue mentioned in #22 and #25, as well?

Also, in the meantime, do you know where the proximity calculation is defined?

Thanks!

Not contributing anything other than to say that this patch works incredibly well for what I'm doing. Hope to see it incorporated in one way or another!

I would love this functionality. Am not confident about applying any patches, so the sooner it gets implemented or a new module created the better. Great work folks. Will follow thread with interest.

This seems great, but I'm confused about which versions (dev, patched, downloaded version of a customized module) of geofield and ip geolocation now represent the "latest and greatest" (html5 default, refine location block, etc.)

With the various issues and patches adding functionality, I'm unclear what I should be using now.

Thanks!

Are the above supposed to include the html5 default patch? I'm not seeing that option in my view, but maybe I'm not looking in the right place.

Thanks!

It says I don't have any updates to run, so I think I'm up to date.

I think I'm also seeing the wrong "refine my location" block, as I only see a place to write an address, not the radio buttons.

Thanks. I must have made a mistake at some point, as I thought I was running the correct dev version but was not.

Is there something I need to do to recode existing addressfield values? I have them in a field collection in a profile2 profile.

I see geoaddress longitude and latitude but am getting this with a new view:

None of the 11 result rows in view maptest (Page) had their ip_geoloc_latitude set. Therefore those rows could not be displayed as locations on the map. Are you using the correct field names?

I have tried running update.php again but it says there is nothing to update.

Thanks.

When and where is ip_geoloc_latitude set and where is it required?

It appears that I can use these versions of geofield and ip_geolocation to create some maps. I'm not sure if it is the html5 option and/or the set my location that is creating the problem and am still running some tests.

Thanks.

Also, in case it helps, this is from the error message I am getting:

field_field_geoaddress = Array ( [0] => Array ( [rendered] => Array ( [#markup] => Latitude: 55.378051000000
Longitude: -3.435973000000 [#access] => 1 ) [raw] => Array ( [geom] => POINT (-3.435973 55.378051) [geo_type] => point [lat] => 55.378051000000 [lon] => -3.435973000000 [left] => -3.435973000000 [top] => 55.378051000000 [right] => -3.435973000000 [bottom] => 55.378051000000 [geohash] => gcve1c6080bv ) ) )

and in watchdog:

Notice: Undefined index: lon in geofieldProximityManual->getSourceValue() (line 39 of /srv/bindings/0c0af6161f58491a8df36a8322c62f11/code/sites/all/modules/geofield/views/proximity_plugins/geofieldProximityManual.inc).

So, the good news (I hope) is that while you were hopefully asleep I have made some significant progress.

ip_geoloc_latitude had been filled in automatically, somehow, in the text box below the name of latitude dropbox. It definitely isn't something that I had typed in.

It appears that, even though I have relationships in the views from user to profile to addressplusphone (the field collection allowing multiple addresses with corresponding phone numbers for each user), choosing field collection item: geoaddress for name of latitude field seems to provide a map.

However, selecting [type field name] and putting in field_geoaddress gives an error.

Also, I have a proximity field that shows when a user's icon is clicked on in the map. If use geocoded location (without html5), the distance always shows as 0. If I use geocoded location with html5 the distance appears to work.

Finally, if this isn't too much at one time, it seems that if I select the "here" radio button after "there" has already been selected, it doesn't switch to the current location with "apply".

Thanks!

Oops. As you probably realized, I was using the IPGV&M set my location block rather than the geofield proximity filter exposed as a block.

I think I was confused about what was geofield functionality and what belonged to IPGV&M. Sorry about that.

So, the option to filter by proximity using html5 or a geocoded address comes from geofield, where one can select either "geocoded address" or "geocoded address with html5 default".

Then, one can use "exposed geocoded proximity filter" in Fields and/or Sort Criteria (and this is true whether using "with html5 default" or not), right?

And, this much is true whether showing a table or an IPGV&M map, right?

If using an IPGV&M map, when can then add, in addition to the exposed filter, the "IPGV&M set my location" block. I assume that this block doesn't do anything if just using a table, yes?

So, my map seems to be working now. I am using the map as a block, with the exposed filter as a block using the Views Block Filter Block module as well as the set my location block. It is still just a dev site or I would provide a link.

Where I think that I am still having an issue is on a different page of the website where a table view with an exposed filter seems to work properly when the proximity filter is set to "geocoded address". Distances seem to be correct and the sort seems to work. As soon as I switch the proximity filter to "geocoded address with html5 default" changing the "from" field in the proximity filter and hitting apply, even multiple times, seems to have no effect. All distances seem to be calculated from the current location, no matter what. The only change I make is from "geocoded address" to "geocoded address with html5 default" in the proximity filter. If I change back to "geocoded address", distances seem to work again. Any thoughts?

Thank you for all of your great work on both modules!

Thanks, it's great to know that "set my location" can work with a table view.

As for my last question in #47, I'm not sure that the IPGV&M readme applies, as I was using a table view without "set my location".

So, even creating a simple view page (not blocks) with only the proximity as an exposed filter, it seems like the "apply" button when I change the address isn't doing anything when I use the html5 as default proximity filter.

FWIW, if I do add the IPGV&M "set my location" block to the table view, even if I use the block-based view, I do see the changes. It's just without any IPGV&M stuff that the distances don't get updated.

If there is some way you would like me to troubleshoot this, let me know and I'll do my best.

Thanks.

Thanks, Rik.

Just to be clear, even though it is a view that doesn't use IPGV&M (just a regular views table) and doesn't use the IPGV&M "set my location" block, it is still an IPGV&M bug? Is the option to use "geocoded address with html5 default" coming from IPGV&M and not from geofield?

Jonathan

I'm a little confused.
Is the patch and associated file at the top of this issue needed any longer?

So, @RdeBoer, since #2134777: Allow other modules to define their own proximity plugins was committed, can we close this issue, or am I missing a patch?

H'ok, marking as fixed.

This is an effort to add some functionality to use HTML5 geocoding for proximity search with views. This will introduce a new config to the Geocoded location to enable HTMl5 geocoding.

Hello
I need to display users around (into a radius defined in the exposed filter of a view) for anonymous users or logged in users as well.
(It's been one week, 15h/day I'm fighting against this geo proximity. I tried out locations, geofield, leaflet, smart ip, IPGM, openlayers etc etc, banging my head on the walls without any result.)
I followed up every single path on the web, and in this issue queue, I downloaded the dev modules required in #52, patching as asked... But ... "Geocoded location with HTML5" doesn't show up...
And my distance from user(if I choose this option) is always mesured from user logged in, whatever I type in 'from'. The kms works though. But only for logged in users ( :/ (My distance-proximity field keep on showing 0)
Could you add a little summary or step by step, or list of modules, and patches maybe, in order to display anonymous or logged in users around...
It would be very useful if we could do that in Drupal...
Thx

Gorgeous site ! Just what I want. (and the little icon made me actually cry ...so nice, sob...;-)
Thx for the direction anyway.
I'm going to check it out.
cu

I installed
- geofield 7 x 2.3
- IPGV&M 7.x-1.27
- geocoder 7.x-1.2
I added an addressfield and a geofield, (geocode from another field) on user profile. They are well displayed with Leaflet.
On my view :
I added a proximity field plugged on "...from exposed filter"
I added an exposed filter, but into origin I dont find 'Geocode location with HTML5'.
And I dont receive the html5 question in popup on my site, and nothing happens...

What did I miss please : it's on a fresh vanilla latest Drupal... No need to Smart IP or another ... option to set up ?
PS it's online if you wanna check...

Thanks for your time Rik. I do appreciate.
But things dont improve. I uninstalled evreything : location, openlayers, leaflet, Smart IP, geofield, etc. Everything. I left only views and so...
Then I reinstalled everything, step by step.
But for the moment, my Users geocoded aren't geocoded anymore. I have an adressfield, and the 'geocoded address' field is set to "geocode from another field, which is plugged on the adressfield.
I saved each user, resaved, and... nothing. (See attachment adopt1.jpg). The field proximity should not display 0...
Geocoder is enabled....
Last but not least : under chrome logged or not, I dont get the question from the browser after clicking 'find me'. Under Firefox, I got the popup, but it never finds me .... The wheel keeps on rolling...
I dont copy :/

I made another step forward : if I enable "Employ a free Google service..." then Google find me. But I got a yellow warning "my address cannot be geocoded"...
:/
I think there is something roten in my Kingdom.
I'm going to test the config in Melbourne-Coffee (i.e. with a new true Content Type, not with only users....)

Thx for the test !
I've found a strange behaviour in geocoding.
I re-built a fresh Drupal, and enhanced the basic article type with addressfield and geofield. I choosed as a display : WKT.
Then, as I mentioned previously (cf adopt1...), the geocoded address field is not filled when saving.
Then I enabled Leaflet, and in the content type, I choosed this display.
As Soon as I resave the articles, the map shows up. And a new View shows the field, filled up, and perfectly displayed in ... WKT if I want!
I'm not sure which module is involved, probably Geocoder...

Now everything works ! (but I found another ... bug : when you enable IPVM, you can then choose Map(leaflet...) for your display in Views, although you didnt enable Leaflet. Of course this doesnt work until you enable Leaflet and Leaflet Views. )

As I tried to explain, if you dont enable leaflet (or another map system I think) the geocoder doesnt fire. Geocoded field from addressfield are NOT geocoded.(f.i. if you choose WKT in the content type display.(-> with only geofield + geocoder installed).
As soon as you enable Leaflet (IPGM alone didnt help), in the Content type Display, re-save each content, then you're geocoded.
I think nobody have seen this issue because you mainly set up the three module at once...
I hope I'm clear...

bad news : I'm still unable to display this field on the user page. I set the same parameters for my Articles and my User : addressfield -> geocoding from anotherfield-> display leaflet map.
No map are displayed on users page. :/
When I set this field I used the same field instance than for articles.
I must add that on my previous devsite, I can see the map on users pages. With stictly the same modules.
After Leaflet, I tried the 'geofield map' for display : in vain.

Does anybody have a working solution to where I can output a view that automatically can detect a user's current position (after user allows site to access gps) and then sort listings based on that location? I've read many threads about how it should work and different methods to get it to work, but have not found a single working instance at all. I got it to kind of work with Smart IP, but it couldn't detect my location only the location of my ISP.