Hi guys,

I built and maintain the Visitor Info module and would like to use the APIs available in GeoIP. Basically what Visitor Info does is it grabs the IP of a sites visitor, stashes it in the database, then periodically gets geo information (country, region, city, zipcode, latitude, longitude) using the APIs here.

Roball made me aware of GeoIP a few weeks ago here http://drupal.org/node/952328 and I agree with him that "this would avoid lots of internet queries/traffic/performance issues".

I just installed your module and ran a quick test and looks like it'll work out just fine. You can see the results here.

A couple of things I noted are that the city stuff didn't work using 6.x-1.2 but did using 6.x-1.x-dev dated 2010-Oct-28. Also I'm obviously using the GeoLiteCity.dat file and so I had to rename it to 'GeoIP.dat' in order to pass validation in your geoip.admin.inc file.

I'd like to rewrite my module to rely on GeoIP and also I want to strip out all the Google API key stuff, integrate better with Views and let the user choose their own mapping solution.

Visitor Info + Views + OpenLayers works pretty well - http://wootenswebdesign.com/visitorinfo-map-openlayers

Any feedback before I do a rewrite would be appreciated.

Tim

Comments

roball’s picture

roball commented

Excellent!

Do you know why

1) 6.x-1.2 doesn't work with the city stuff
2) The 'GeoLiteCity.dat' file had to be renamed to 'GeoIP.dat'

?

izmeez’s picture

izmeez commented

subscribing,

drewish’s picture

drewish commented

I don't think you need to rename the dat file. You just need to update the filename in the settings form.

drewish’s picture

drewish commented
Status: Active » Fixed

Yeah just tested that. Just put in the filename and it's fine.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

scott.olipra’s picture

scott.olipra commented

Another option is a sym link in the sites/all/libraries/geoapi directory.
The command would be

ln -s GeoLiteCity.dat GeoIP.dat