suggestions for atlas service
Hi Two suggestions: 1. Some looking-glass from the probe. Simpe ping/traceroute from the probe triggered from the web interface could be nice. 2. Better probe location display. Currently I host two probes, both 10cm one from each other, put into two different ASes. When I have put exactly the same geo data, the "display" mechanism put one of it onto the other one. Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski@polsl.pl
Hi, On 2011.05.05. 17:15, Piotr Strzyzewski wrote:
Hi
Two suggestions:
1. Some looking-glass from the probe. Simpe ping/traceroute from the probe triggered from the web interface could be nice.
I would think that this will be covered by the user defined measurements feature, where the measurement is a one-off, not a continuous one.
2. Better probe location display. Currently I host two probes, both 10cm one from each other, put into two different ASes. When I have put exactly the same geo data, the "display" mechanism put one of it onto the other one.
This is a tricky one. Background information: we'd rather not publish the exact geo-coordinates the hosts put in, because of privacy concerns. So what we do now is that whenever we display probes on a map, we round the geo-coordinates to two digits. This introduces a "random" error of up to 1000 meters or so. (If you zoom in on Amsterdam, where we have enough probes, you'll see that all probes are aligned into a neat, sparse matrix; it's because of this.) As a consequence, if two probes are located very close to each other, the rounding makes them show up as overlapping. You could try to move your probe a bit, like to the next street or so to see if that helps. The RTT map is probably the best page to check the outcome. Regards, Robert
Piotr
On Fri, May 13, 2011 at 11:56:01AM +0200, Robert Kisteleki wrote:
2. Better probe location display. Currently I host two probes, both 10cm one from each other, put into two different ASes. When I have put exactly the same geo data, the "display" mechanism put one of it onto the other one.
This is a tricky one.
Background information: we'd rather not publish the exact geo-coordinates the hosts put in, because of privacy concerns. So what we do now is that whenever we display probes on a map, we round the geo-coordinates to two digits. This introduces a "random" error of up to 1000 meters or so. (If you zoom in on Amsterdam, where we have enough probes, you'll see that all probes are aligned into a neat, sparse matrix; it's because of this.)
It seems to be relatively easy to round the geo-coordinates to two digits (as you do it right now) and then add some random number from 0.00000 to 0.00999 to it. Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski@polsl.pl
Background information: we'd rather not publish the exact geo-coordinates the hosts put in, because of privacy concerns. So what we do now is that whenever we display probes on a map, we round the geo-coordinates to two digits. This introduces a "random" error of up to 1000 meters or so. (If you zoom in on Amsterdam, where we have enough probes, you'll see that all probes are aligned into a neat, sparse matrix; it's because of this.)
It seems to be relatively easy to round the geo-coordinates to two digits (as you do it right now) and then add some random number from 0.00000 to 0.00999 to it.
Yes, but it would also make the probes dance around at each page load. I'm sure it would be entertaining, but not so sure about the usefulness :-) We'll try to come up with a solution that emits consistent coordinates. Regards, Robert
On Wed, May 18, 2011 at 12:19:28PM +0200, Robert Kisteleki wrote:
Background information: we'd rather not publish the exact geo-coordinates the hosts put in, because of privacy concerns. So what we do now is that whenever we display probes on a map, we round the geo-coordinates to two digits. This introduces a "random" error of up to 1000 meters or so. (If you zoom in on Amsterdam, where we have enough probes, you'll see that all probes are aligned into a neat, sparse matrix; it's because of this.)
It seems to be relatively easy to round the geo-coordinates to two digits (as you do it right now) and then add some random number from 0.00000 to 0.00999 to it.
Yes, but it would also make the probes dance around at each page load. I'm sure it would be entertaining, but not so sure about the usefulness :-)
I was rather thinking about some random, but fixed (put into database) number for each probe. OTOH it would be nice to see a movie from such a dance. ;-) Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski@polsl.pl
participants (2)
-
Piotr Strzyzewski -
Robert Kisteleki