{"id":935,"date":"2009-06-29T21:37:17","date_gmt":"2009-06-30T02:37:17","guid":{"rendered":"http:\/\/unitstep.net\/?p=935"},"modified":"2009-06-29T22:20:59","modified_gmt":"2009-06-30T03:20:59","slug":"determine-your-visitors-location-based-on-ip-address","status":"publish","type":"post","link":"https:\/\/unitstep.net\/blog\/2009\/06\/29\/determine-your-visitors-location-based-on-ip-address\/","title":{"rendered":"Determine your visitor’s location based on IP address"},"content":{"rendered":"

If you’re running a website that provides a service, it’s likely that it would be beneficial to know a user’s location (or have a rough idea) so that the content could be tailored to their specific geographic area. But how do you get their location, without having to ask them? By using their IP address, it’s possibly to determine their general area with fairly good accuracy. In this tutorial, I’ll explain how to do that using the free IP address geolocation database<\/a> from IPInfoDB<\/a>.<\/p>\n

<\/p>\n

Motivation and Usage<\/h2>\n

There are numerous reasons for using the user’s location to improve the quality of a service. For example, the restaurant guide and review site, Restaurantica<\/a>, automatically makes a guess as to your location and populates the “Search” field so that you are one click away from finding information tailored to your geographic area. <\/p>\n

This determination is based on the user’s IP address. Usually, the lookup is done based on a static set of mappings from IP addresses to geographical locations, like cities. In fact, this is exactly what the IP address geolocation database<\/a> (that we’ll use) does. It has the advantage of being easy to understand but unfortunately the accuracy can degrade over time, as IP addresses are usually not hardwired to specific locations. For example, most DSL users are subject to DHCP, so the same IP address may be re-used across different cities. (The IP address database from IPInfoDB is updated periodically to help reduce this inaccuracy)<\/p>\n

Thus, you should not rely on the information provided to be 100% accurate; it should only be used as a suggestion. This is why Restaurantica<\/a> only populates<\/em> the search field with your estimated location, rather than giving you the results for that location right away; if it was wrong, the results for a different location would certainly be confusing to a user. This gives the user a chance to correct any inaccurate lookups.<\/p>\n

Using the IP Address geolocation database<\/h2>\n

The first step is to download the database<\/a> and import it into your local database; for this example I’ll use MySQL. Note that the site also offers an IP location Lookup API<\/a>, which has the advantage of not requiring a local database but may be subject to usage limits; if you’ll be getting a lot of traffic you’ll be better off using the local database.<\/p>\n

Import the contents into MySQL<\/h3>\n

I downloaded the Complete (City) database as one table in SQL format<\/a>. Extracting the file from the archive, you’ll see that it’s well over 300 MB in size. If you’re fond of using phpMyAdmin<\/a>, you unfortunately won’t be able to import such a large file using that tool, so we’ll have to rely on the command line to import the contents. Go to your mysql\/bin<\/code> folder and enter the following command, assuming you extracted the SQL file to the same location:<\/p>\n

mysql -u root -p [name of database] < ipinfodb_one_table_full.sql<\/code><\/pre>\n
Running this command will take some time, as it won’t be fast having to import such a huge table<\/strong>.  Take a break and come back in a few minutes. \ud83d\ude42 (You may want to create a new database to hold just this table, do that before running this command)  After that’s done, you should be able to see the contents in phpMyAdmin, like below:<\/p>\n
\n\"ip-geolocation-1\"<\/a>\n<\/p>\n
Using the database<\/h3>\n
Querying the database is straightforward, and the IP Info DB website has plenty of examples at the bottom of the download page<\/a>.  Basically, once you have the user’s IP, you can use a query like this to find the most likely city it originated from:<\/p>\n
SELECT * \r\nFROM `ip_group_city` \r\nWHERE `ip_start` <= INET_ATON([ip address as a string])\r\nORDER BY ip_start DESC\r\nLIMIT 1;<\/code><\/pre>\n
The INET_ATON function converts a string that is the dotted-quad octet form of an IP address (the form you’re most used to seeing) into a 32-bit unsigned integer.  This integer is then used to locate the record that most likely corresponds to the geographical location.  The database is structured such that row with the highest ip_start<\/code> value not greater than the given IP address is deemed to be the most likely location.<\/p>\n
An example:<\/p>\n
SELECT * FROM `ip_group_city` WHERE `ip_start` <= INET_ATON('69.156.150.155') ORDER BY ip_start DESC limit 1;<\/code><\/pre>\n
(This returns the city of Toronto, Ontario, Canada) If you want to get a list of likely locations, just increase the LIMIT argument to something like 10, and this will return 10 locations that are likely close to where the IP address is located.  Note that there may be duplicates in this list<\/strong>.<\/p>\n
A simple example<\/h2>\n
Here’s a simple PHP<\/acronym> script that takes the user’s IP address and displays their most likely location on a map using the Google Static Maps API<\/a>.<\/p>\n
<?php\r\n$ipGeolocationDatabaseName = 'ip_geolocation';\r\n\r\n$link = mysql_connect('localhost', 'root', '');\r\n$ipAddress = mysql_real_escape_string($_SERVER['REMOTE_ADDR']);\r\n\r\necho $ipAddress;\r\n\r\nmysql_select_db($ipGeolocationDatabaseName, $link);\r\n\r\n$query = \"SELECT * FROM `ip_group_city` \" . \r\n         \"WHERE `ip_start` <= INET_ATON( '$ipAddress' ) \" . \r\n         \"ORDER BY ip_start DESC \" . \r\n         \"LIMIT 1\";\r\n$resultLocation = mysql_query($query);\r\n  \r\n$numRows = mysql_num_rows($resultLocation);\r\n  \r\nif (0 == $numRows)\r\n{\r\n  echo \"No likely locations found.\";\r\n}\r\n\r\nwhile ($row = mysql_fetch_array($resultLocation))\r\n{\r\n  echo \"<pre>\";\r\n  print_r($row);\r\n  echo \"<\/pre>\";\r\n\r\n  $lat = urlencode($row['latitude']);\r\n  $lng = urlencode($row['longitude']);\r\n  if (!empty($lat) && !empty($lng))\r\n  {\r\n    \/\/ NOTE: Replace the `key` parameter with your own, obtained from:\r\n    \/\/ http:\/\/code.google.com\/apis\/maps\/signup.html\r\n    \/\/ (The one in use is only good for URLs on `localhost`)\r\n    $queryString = \"center=$lat,$lng\";\r\n    $queryString .= \"&zoom=10\";\r\n    $queryString .= \"&size=300x300\";\r\n    $queryString .= \"&markers=$lat,$lng,blue\";\r\n    $queryString .= \"&key=ABQIAAAAicCf6MqoHlR-MsfivtVWPRT2yXp_ZAY8_ufC3CFXhHIE1NvwkxTNmqRdvnM9orG9QdyALHoUZfmFuQ\";\r\n    $queryString .= \"&sensor=false\";\r\n    \r\n    echo '<img src=\"http:\/\/maps.google.com\/staticmap?' . htmlentities($queryString) . '\" alt=\"location\" \/>';\r\n  }\r\n}\r\n?><\/code><\/pre>\n
Here’s what it display for my IP address:<\/p>\n
\n\"ip-geolocation-2\"<\/a>\n<\/p>\n
As you can see, it’s not always accurate, but it’s a good start to enhancing your website to offer localized services and features.<\/p>","protected":false},"excerpt":{"rendered":"
If you’re running a website that provides a service, it’s likely that it would be beneficial to know a user’s location (or have a rough idea) so that the content could be tailored to their specific geographic area. But how do you get their location, without having to ask them? By using their IP address, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[208,356,139,277],"tags":[358,357,359,439],"_links":{"self":[{"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/posts\/935"}],"collection":[{"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/comments?post=935"}],"version-history":[{"count":15,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/posts\/935\/revisions"}],"predecessor-version":[{"id":959,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/posts\/935\/revisions\/959"}],"wp:attachment":[{"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/media?parent=935"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/categories?post=935"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/tags?post=935"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}