Zipwise Geotargeting
Database
Convert IP addresses into latitude, longitude, country, and more
The Zipwise Geotargeting Database is used to determine the latitude
and longitude of any given IP address. Here are the fields that
the database contains:
| Field |
Description |
| ip_start |
Beginning range
of IP address (converted to a decimal number) |
| ip_end |
End range of
IP addresses (converted to a decimal number) |
| country_code |
2-letter country
code |
| state_province |
State or province |
| city |
City name |
| zip_code |
US ZIP Code |
| latitude |
Latitude |
| longtiude |
Longitude |
View a sample of the database here.
The complete database contains approximately 3 million records
(as of July 2009). See the FAQ section below for
more information on how to work with the database.
The Zipwise Geotargeting Database is available in three licenses,
and can be downloaded immediately upon purchase:
| Click
to purchase |
Single
User
Licensed for access by a single user on a single workstation
only. Not for web sites. |
| $249 |
Buy -
One time download |
| $499 |
Buy -
With 4 quarterly updates (5 in all) |
| $899 |
Buy -
With 12 monthly updates (13 in all) |
|
Corporate
License
Licensed for access by two or more users within a company.
Not for web sites. |
| $299 |
Buy -
One time download |
| $599 |
Buy -
With 4 quarterly updates (5 in all) |
| $1099 |
Buy -
With 12 monthly updates (13 in all) |
|
Web
License
No restrictions on use. Can be used to provide real-time services
on your web site. |
| $349 |
Buy -
One time download |
| $699 |
Buy -
With 4 quarterly updates (5 in all) |
| $1299 |
Buy -
With 12 monthly updates (13 in all) |
|
FAQ
How and why are the IP addresses expressed
as integers in the database?
IP addresses are expressed as integer numbers to make it possible
to do SQL range searches on the data.
We use the most common method of converting an IP address to
an integer. The address 12.34.56.78 is converted like this:
12 * 256^3 = 201,326,592
34 * 256^2 = 2,228,224
56 * 256^1 = 14,336
78 * 256^0 = 78
Add them all up to get 203,569,230. Once you have a simple integer
like this, it's much faster and easier to search the database
to find the matching record for retrieval of latitude and longitude.
You can also use the SQL commands INET_ATON() and INET_NTOA()
to automatically convert the IP address to a searchable numeric
value in the database.
So how does that fit in with the ip_start
and ip_end fields in the database?
IP addresses come in ranges, so each location in the database
has a beginning IP address (the ip_start field) and an ending
IP address (the ip_end field). All you need to do is find the
latitude and longitude for IP address 12.34.56.78 is convert
it by the method above to get 203,569,230 and then search for:
ip_start ≤ 203569230 ≤ ip_end
It shows my IP address in a nearby major
city, not in the city where I am located. What's up with that?
In many cases, the latitude and longitude that's registered
is for your ISP, and this can often be in a nearby city. Since
many IP addresses are shared among an ISP's customers in many
cities, this is as accurate as is technically feasible.
Any other questions about this product? Please
ask us! |
