Am I looking at the area in which the majority of circles intersect, a la Venn?
Intersect? In my case they intersect in a weird way: http://i.imgur.com/eFqyCEq.png
Those circle centres don't even look right.
Passive TCP/IP Geo-Location
11–20 of 91 posts
Re: Passive TCP/IP Geo-Location
#12Am I looking at the area in which the majority of circles intersect, a la Venn?
>The common area of all circles show your likely location.
Re: Passive TCP/IP Geo-Location
#13Smart, but I don't know how granular you could get unless you had known servers at every possible datacenter.
Just use a CDN with decent edge coverage. I'm sure those results can be improved drastically.
You did notice that the backend code is Go code snippet that needs to run at the end points?
Re: Passive TCP/IP Geo-Location
#14Smart, but I don't know how granular you could get unless you had known servers at every possible datacenter.
For me it roughly the right continent where I am (if I am on VPN, otherwise it also include greenland and arctic regions).
But with servers in more locations, and possibly accounting for network topology (could be mined with traceroute?), accuracy could go quite up.
Re: Passive TCP/IP Geo-Location
#15The ping times seem sensible, but I can't work out any correlation between them and the map. Just seems like a random collection of circles...
I assume each circle has a radius proportional to the rtt, thus the area in which the circles overlap is roughly where you should be. The limited amount of servers + wide range of rtt gives a massive margin of errors, but this is probably easily improvable through some extra servers and some kind of knn-ish analysis.
Re: Passive TCP/IP Geo-Location
#16Earlier quoted context omitted.
Just use a CDN with decent edge coverage. I'm sure those results can be improved drastically.
You did notice that the backend code is Go code snippet that needs to run at the end points?
So? I'm sure some CDN out there allow you to run your own code, hence it could be more granular (as OP was interested in).
Re: Passive TCP/IP Geo-Location
#17The ping times seem sensible, but I can't work out any correlation between them and the map. Just seems like a random collection of circles...
You're in the most heavily shaded region. Some of the areas reach most of the way around the world, so they look like a lighter circle that you're actually outside, some are smaller and look darker which you're inside, some are about halfway and look like a sine wave, but they're all really circles. (Damn you, Mercator!)
Re: Passive TCP/IP Geo-Location
#18The ping times seem sensible, but I can't work out any correlation between them and the map. Just seems like a random collection of circles...
I assume each circle has a radius proportional to the rtt, thus the area in which the circles overlap is roughly where you should be. The limited amount of servers + wide range of rtt gives a massive margin of errors, but this is probably easily improvable through some extra servers and some kind of knn-ish analysis.
Well in my case somehow javascript places Singapore circles center to middle of Indian ocean close to Antarctica. San Francisco and Bangalore are in South America.
Re: Passive TCP/IP Geo-Location
#19I think there's a bug in the circle placement. They don't appear to be correct for me. I'm assuming they're supposed to be centred on the locations listed.
Re: Passive TCP/IP Geo-Location
#20I think there's a bug in the circle placement. They don't appear to be correct for me. I'm assuming they're supposed to be centred on the locations listed.
I though that too at first, but they are correct. It looks like this because these are circles on a globe. The outline of a very big circle around a location is the same as the outline of a small circle around the point on the opposite side of the globe.
Look at the color-tint to find out what is inside and what is outside a circle.