rocknbil - 4:34 pm on Jun 28, 2012 (gmt 0)
Thank you everyone for your input.
LOL . . . how did I know it would be g1smd with that one. Thank you. :-)
there are no specific ranges determined for Hawaii,
Eh? Even with the light database, there's tons of IP's listed in Hawaii. The problem is, there's tons more users using bandwidth with IP's not located in Hawaii. :-)
manually clean up the database
I'd even be willing to take that impossible to maintain project on - but the problem is that those IP's are not restricted only to Hawaii. There's a reason their data center shows up in Texas - one scenario is that it's indeed a satellite, in which case thousands of mainland users would be on the same IP. Identify it as Hawaii . . . and poof, they all get zapped to the Hawaii site. No deal.
there's a ton of those kind of services that hide the 'real' location of someone.
Sometimes it's not hiding. I used to be on satellite in rural Oregon, and most of the time the geotargeted ads placed me in New Jersey. :-) When our satellite malfunctioned, it would report me as Houston, Texas.
Some of the IP-location lists use triangulation to determine someones location, basically you measure the latency to connect to the IP from various locations which can indicate where they are based on the time differences between the requests.
Fascinating! Have you got names?
I've been in communication with Maxmind, IP2Location, Geobytes, a couple others that didn't seem very promising, and I had a strong look at what Skyhook is doing (which sounds similar to your idea,) but it sounds like Skyhook's main product is an SDK to create apps on mobile devices, which seemed to mean geolocation of the device in your hand, not by IP. Abandoned.