Closed (duplicate)
Project:
Geofield
Version:
7.x-2.x-dev
Component:
User interface
Priority:
Major
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
22 Mar 2013 at 06:15 UTC
Updated:
15 Nov 2013 at 14:57 UTC
Jump to comment: Most recent
Comments
Comment #1
simon georges commentedBy using the Addressfield module to handle the address part, I think you may force the country.
Comment #2
benjmarr commentedunfortunately this doesn't work. We are using the proximity exposed filter with the source of origin point being"geocoded location" using the google geocoder service.
Comment #3
benjmarr commentedHi All,
This is now major... when searching a postcode say 3000 no results are shown. The user has to search 3000, Australia. I have gone through the code and tried a few things but no success is there anywhere that i can add ,Australia so it processes the users entry with ,Australia appended?
Thanks,
Ben
Comment #4
benjmarr commentedstill messing around trying to get geofield to process a geocoded location by appending ,t(Australia) but cant get it to work.
Comment #5
benjmarr commentedany gurus here to weigh in on wether this is possible or not?
Comment #6
p_stampy commentedWe've just come across the same problem too, will be interested to see if there is an outcome.
Comment #7
p_stampy commentedSome additional information, typing in "2012, Australia" actually brings up results around Adelaide/SA instead of Sydney...
Comment #8
benjmarr commentedstill trying to find a solution for this but this is certainly not our forte!!
Comment #9
p_stampy commentedHi,
I'm not sure if this is in the right place, but this has worked for us when using "openlayers_proximity" to do the proximity search on aussie post codes.
In sites\all\modules\openlayers_proximity open up openlayers_proximity.module
For me it starts on line 387...
Anyway, hope that might help a little bit...
Comment #10
bneil commentedDuplicate in favor of #2014621: Geofield proximity + postal code to find a solution as its obviously a non-specific country issue. Comment 14 in that issue also provides a work around that can be used via a new hook.