<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
><channel><title>Datavisualization.ch &#187; Traffic</title> <atom:link href="http://datavisualization.ch/tag/traffic/feed/" rel="self" type="application/rss+xml" /><link>http://datavisualization.ch</link> <description>Datavisualization.ch is the premier news and knowledge resource for data visualization and infographics.</description> <lastBuildDate>Wed, 01 Feb 2012 07:23:31 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>Traffic on GoogleMaps</title><link>http://datavisualization.ch/showcases/traffic-on-googlemaps/</link> <comments>http://datavisualization.ch/showcases/traffic-on-googlemaps/#comments</comments> <pubDate>Wed, 26 Aug 2009 06:54:32 +0000</pubDate> <dc:creator>Benjamin Wiederkehr</dc:creator> <category><![CDATA[Showcases]]></category> <category><![CDATA[Crowdsourcing]]></category> <category><![CDATA[Google]]></category> <category><![CDATA[Mapping]]></category> <category><![CDATA[Traffic]]></category><guid
isPermaLink="false">http://datavisualization.ch/?p=2968</guid> <description><![CDATA[Google just launched a new and exciting feature for GoogleMaps: traffic conditions on highways and arterial roads. The simple and very usable display works well in conjunction with Google's way of gathering the data: crowd sourcing.]]></description> <content:encoded><![CDATA[<p><a
href="http://www.google.com">Google</a> just launched a new and exciting feature for <a
href="http://maps.google.com">GoogleMaps</a>: <strong>traffic conditions on highways and arterial roads</strong>. The simple and very usable display works well in conjunction with Google&#8217;s way of gathering the data: crowd sourcing.</p><p>The interface is clutter-free and really easy to understand:</p><blockquote><p>As you zoom in closer to an area of interest, we&#8217;ll color the arterial roads, in addition to the highways, to show current traffic conditions. Just as with the highways, the colors correspond to the speed of traffic (relative to the speed limit of the road): green is free sailing, yellow is medium congestion, red is heavy congestion, and red/black is stop-and-go traffic.</p></blockquote><p><img
class="alignnone size-full wp-image-2969" title="google_traffic_01" src="http://www.datavisualization.ch/wp-content/uploads/2009/08/google_traffic_01.png" alt="google_traffic_01" width="710" height="300" /></p><p>What more do we need to read the conditions of a road? Well done, Google.</p><p>Here&#8217;s how you can help making the the crowd sourcing work:</p><blockquote><p>Using <a
href="http://www.google.com/mobile/products/maps.html">Google Maps for mobile</a> with GPS enabled on your phone is required. When you choose to enable Google Maps with <a
href="http://www.google.com/mobile/gmm/mylocation/index.html">My Location</a>, your phone sends anonymous bits of data back to Google describing how fast you&#8217;re moving. When we combine your speed with the speed of other phones on the road, across thousands of phones moving around a city at any given time, we can get a pretty good picture of live traffic conditions.</p></blockquote><p><span
class="source read_on">Read the <a
title="The bright side of sitting in traffic: Crowdsourcing road congestion data" href="http://googleblog.blogspot.com/2009/08/bright-side-of-sitting-in-traffic.html" target="_blank">original blogpost</a> from Google or<br
/> the <a
title="Arterial traffic available on Google Maps" href="http://google-latlong.blogspot.com/2009/08/arterial-traffic-available-on-google.html" target="_blank">blogpost</a> from the Goggle LatLong blog</span></p> ]]></content:encoded> <wfw:commentRss>http://datavisualization.ch/showcases/traffic-on-googlemaps/feed/</wfw:commentRss> <slash:comments>2</slash:comments> </item> <item><title>How Twitter got Attacked By A DDoS</title><link>http://datavisualization.ch/showcases/how-twitter-got-attacked-by-a-ddos/</link> <comments>http://datavisualization.ch/showcases/how-twitter-got-attacked-by-a-ddos/#comments</comments> <pubDate>Thu, 06 Aug 2009 22:55:26 +0000</pubDate> <dc:creator>Benjamin Wiederkehr</dc:creator> <category><![CDATA[Showcases]]></category> <category><![CDATA[Internet]]></category> <category><![CDATA[Network]]></category> <category><![CDATA[Social]]></category> <category><![CDATA[Traffic]]></category><guid
isPermaLink="false">http://datavisualization.ch/?p=2793</guid> <description><![CDATA[Today Twitter was down for some time which led to quite a bit confusion and discussion. What happened? The consensus is that it was a DDoS that caused the downtime of the poular social network. Back in 2007 WIRED has created a visualization on how a Denial of Service attack works.]]></description> <content:encoded><![CDATA[<p>Today Twitter was down for some time which led to quite a bit confusion and discussion. What happened? <a
href="http://mashable.com/2009/08/06/twitter-cyber-warfare/">The consensus</a> is that it was a DDoS that caused the downtime of the poular social network. The attack was not solely on Twitter but also directed on Facebook, LiveJournal and YouTube. Back in 2007 <a
href="http://www.wired.com/politics/security/magazine/15-09/ff_estonia_bots">WIRED</a> has created <a
href="http://www.wired.com/politics/security/magazine/15-09/ff_estonia_bots">a visualization</a> on how a Denial of Service attack works:</p><p><a
href="http://www.wired.com/politics/security/magazine/15-09/ff_estonia_bots"><img
class="alignnone size-full wp-image-2794" title="ff_estonia_map_w" src="http://www.datavisualization.ch/wp-content/uploads/2009/08/ff_estonia_map_w.jpg" alt="ff_estonia_map_w" width="710" height="434" /></a></p><p>While the todays attack wasn&#8217;t a traditional DDoS the concept remains mainly the same.</p> ]]></content:encoded> <wfw:commentRss>http://datavisualization.ch/showcases/how-twitter-got-attacked-by-a-ddos/feed/</wfw:commentRss> <slash:comments>10</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced (User agent is rejected)
Database Caching 9/16 queries in 0.026 seconds using disk: basic

Served from: datavisualization.ch @ 2012-02-09 01:52:42 -->
