1import{t as o,a}from"./B0Viejac.js";import"./BdGvnqIx.js";import{n}from"./DQjfI-R0.js";const s={title:"World Map of Internet Adresses",date:"2009-12-21 20:37:30",tags:["cartography","geospatial","internet","map","static","visualized"],author:"Gregor Aisch",permalink:"world-map-of-internet-adresses"},{title:c,date:d,tags:m,author:h,permalink:g}=s;var r=o('<div class="poster poster-650"><a href="/blog/images/old/networld.png"><img src="/blog/images/old/networld_2.png"></a></div> <p>The <a href="/blog/images/old/networld.png">map</a> shows the location of 1,139,441,531 ip adresses. The locations are grouped by city, divided into four categories according to the total number of ip adresses belonging to a city. The categories are <em>net-metropoles</em> (more than 10,000,000 IPs), <em>net-capitals</em> (1,000,000 up tp 10,000,000 IPs), <em>net-cities</em> (100,000 up 1,000,000 IPs) and <em>net-villages</em> (fewer than 100,000 IPs). IP adresses that cannot be allocated to a city were left out. I created this visualization using ActionScript, based on my classes for <a href="http://vis4.net/blog/2009/12/selected-map-projections-in-actionscript/" rel="nofollow">map projections</a> and <a href="http://vis4.net/blog/2009/11/polygon-operations-in-actionscript/" rel="nofollow">polygon maths</a>, which you can download for own usage. The data was extracted from the free <a href="http://www.maxmind.com/app/geolitecity" rel="nofollow">GeoLite-City database</a> by <a href="http://www.maxmind.com" rel="nofollow">MaxMind</a>.</p> <h1 id="comments">Comments</h1> <p>Facebook And Its Impact In Connecting People â vis4.net (Oct 25, 2011)</p> <blockquote><p>[â¦] After all, Facebook is âjustâ a website and websites can be accessed through the internet. So, when speaking of âconnecting people, even across oceans and bordersâ, we should demonstrate our respect for the internet. To do so, I re-created my old map of the internet: [â¦]</p></blockquote>',1);function f(e){var t=r();n(8),a(e,t)}export{f as default,s as metadata};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.