Posted by Scott Reynolds on May 15, 2009 at 4:27pm
Jump to:
| Project: | Localsolr Integration |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Scott Reynolds |
| Status: | needs review |
Issue Summary
Heres a patch. Haven't tested it unfort, I have my own little location module and it provides only this Views stuff. But from what I saw in the code, this should work. Notice the funny document.write(). That allows us to have the Google map code in the footer instead of in the header. Performance boost.
Does the Geocoding in JS, which I suggest as Google limits the geocode requests per Ip address. So the JS hits with the client IP address instead of the server, netting virtually unlimited Geocodes.
Probably could work to expose the radius form element as well. Something to consider.
Also it hardcodes US as the country, this probably needs to be evaluated as the users country via location module.
Them be my notes.
| Attachment | Size |
|---|---|
| localsolr.views_.inc_.txt | 1.09 KB |
| apachesolr_views_location_filter.inc_.txt | 4.94 KB |
Comments
#1
geocoder link: http://code.google.com/support/bin/answer.py?answer=93464&topic=12266
#2
hey there,
it appears the maintainer may have been inactive for over a year on this project but this is something im specifically interested in, especially with the proximity/radius filter though so im going to look into integrating this and trying to advance it but at this immediate moment am unsure how to go about that. doesnt help that im not familiar with views includes and api implementations either so perhaps thats where i should start