Visualization: Tor nodes on Google Maps and Google Earth

[Ted Smith]

The KML file works great in Marble
(<https://secure.wikimedia.org/wikipedia/en/wiki/Marble_%28software%9>),
a free software Google Earth-like program. It's also available in Debian
and derivatives under the package "marble".

Apologies to anyone who got this twice, but I wanted to make sure that
both lists were aware of this (since I don't really like the "look at
the Tor network on Google" thing).

On Wed, 2010-12-15 at 15:47 +0100, Eugen Leitl wrote:
> ----- Forwarded message from Moritz Bartl <moritz at torservers.net> -----
>
> From: Moritz Bartl <moritz at torservers.net>
> Date: Wed, 15 Dec 2010 15:43:38 +0100
> To: or-talk at freehaven.net
> Subject: Visualization: Tor nodes on Google Maps and Google Earth
> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13)
Gecko/20101207 Thunderbird/3.1.7
> Reply-To: or-talk at freehaven.net
>
> Hi,
>
> I wrote a small ugly Python script to visualize Tor relays on Google
> Maps and Google Earth. You can see the result here:
>
> * Open KML file in Google Maps:
>
http://maps.google.com/maps?q=http:%2F%2Fwww.torservers.net%2Fmisc%2Ftormap%2
Ftormap.kml
>
> * Download tormap.kml for Google Earth
> http://www.torservers.net/misc/tormap/tormap.kml
>
> The KML standard is being pushed by Google and should work for
> OpenStreetMap, too, but I couldn't get it to load there. Feel free to
> modify the script to generate other outputs.
> The initial idea was to scale the marker size to show the relay's
> bandwidth, but Google Maps does not support this.
>
> The markers might give a false impression of accuracy. Most IPs can only
> be tracked to city level (or even region), ie. the markers are somewhat
> near, not necessarily at the real location of the relay.
>
> You can download the script here:
> http://www.torservers.net/misc/tormap/tormap.py (LGPL)
>
> This is a one-time snapshot and I will not update it regularly, unless
> there is public interest to do so. The bandwidth categories are based on
> the reported "observed bandwidth" at the time of creation, so the actual
> number of high bandwidth nodes will fluctuate every time the script is
> run. It would be nice to extend this script to use longer-term bandwidth
> calculation like TorStatus does, and to generate a map over time using
> all the consensus data provided at http://archive.torproject.org/. An
> example of what this could look like is Vis4Net's Wikileaks Mirror World
> Map at http://labs.vis4.net/wikileaks/mirrors/ .
>
> ( Mostly copied from my blog at
>
http://moblog.wiredwings.com/archives/20101213/Visualization-Tor-nodes-on-Goo
gle-Maps-and-Google-Earth.html
> )
> --
> Moritz
> http://www.torservers.net/
> ***********************************************************************
> To unsubscribe, send an e-mail to majordomo at torproject.org with
> unsubscribe or-talk    in the body. http://archives.seul.org/or/talk/
>
> ----- End forwarded message -----

[demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]