InfoVis:Wiki - User contributions [en]

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 3

2005-11-21T09:39:33Z

UE-InfoVis0506 0125718:

==Topic==
Webserver Logfile Visualization

==Area of Application==

===Analysis of Application Area===

====General Description====
Webservers typically generate logfiles containing huge amounts of information on page accesses, used client software, type of access, and many more. Analysis tools like for example AWStats try to make use of this information and present simple statistics mostly in form of tables or simple bar graphs. Unfortunately, they are mostly very limited and "low-level" regarding their information representation. More interesting questions like user behavior in combination with site structure, dead ends, changes in behavior regarding to time (evolution), typical behavioral patterns, finding groups of users that share similar behavioral patterns, site entry points, or intrusion detection cannot be answered by using similar tools. For being able to deal with this kind of topics, more advanced visual tools are needed that unveil this information. [Behlendorf et al., 2005]

====Special Issues====

There are many different known solutions/methods to visualize Webeserver Logfiles. Most of them make use of simple chart or bar diagrams. The question is, if it is possible to present this huge set of informations in just one diagram, that illustrates all the data in a simple and undastandable way.

===Analysis of the Dataset===

Here is an example of such a logfile entry: [Cooper,2004]

205.218.110.166 - - [08/Dec/1996:15:02:10 -0800] "GET /info/index.html HTTP/1.0" 200 14912 "http://www.yourcompany.com/index.html " "Mozilla/3.0Gold (Win95; I)" "35bebd61b31211cfbdcd00c04fd611cf"

The content of this entry explained, from left to right:

'''"205.218.110.166"''' - - This is the IP address of the machine making a request of your web server - its domain name can be determined in HitList by enabling Reverse DNS lookups, assuming your server hasn't put this information in already - many so, some don't. (if the domain name was in there, you'd see its URL instead of the raw IP).

'''"-"''' - this first dash is typically the server's IP address, which most NCSA format servers don't insert by default.

'''"-"''' - this second dash is typically authenticated usernames, which again many NCSA format servers don't insert by default.

'''"[08/Dec/1996:15:02:10 -0800]"''' - This is the date and time of the access, including the offset from Greenwich Mean Time - the latter is the "-800", meaning the web server being accessed is 8 hours ahead of GMT.

'''"GET /info/index.html HTTP/1.0"''' - This is the actual request the visitor's browser made when at your page or server.

'''"HTTP/1.0"''' refers to the protocol and its version, here being version 1.0 of the http protocol.

'''"200"''' - this is the server response code - a "successful" request (meaning the visitor's browser loaded the entire HTML/GIF/JPEG, etc.) generates a response code of 200. Others include:

206 - Partial request successful (not complete)
302 - URL has been redirected to another document
400 - Bad request was made by the client
401 - Authorization is required for this document
403 - Access to this document is forbidden
404 - Document not found
500 - Server internal error
501 - Application method (either GET or POST) is not implemented
503 - Server is out of resources

'''"14912"''' - This is the number of bytes transferred to the client during the visit. Since every request has some response, even erroneous requests will have a non-zero value for this field.
"http://www.yourcompany.com/index.html" - This is the referrer field, or the site the visitor was on immediately prior to making this entry's request - in this case, the person was looking at the index.html (probably the home page) page before going to the /info/index.html page in this entry.
"Mozilla/3.0Gold (Win95; I)" - this is the user-agent field, meaning the actual browser and OS used by the visitor - in this case, Mozilla is Netscape, the next value is the version (here, 3.0Gold), and the final value is the OS it was using (Windows 95).

Finally, the '''"35bebd61b31211cfbdcd00c04fd611cf"''' is the cookie information, which may or may not be there, depending on whether the webserver used has cookies enabled and whether one was passed from webserver to the visitor's computer.

There are several different specific Logfile Formats, for example: Microsoft IIS 3.0 and 2.0, Microsoft IIS4.0 (W3SVC format), Netscape (NCSA format with/without unique format header), Lotus Domino format, O'Reilly WebSite format...

==Target Group==

===Identifying the Target===
We identified the following Target groups:
#Software Companies: especially those who develop browsers and web based applications
#Web Dsigners
#Administrators
#Advertising Companys
#Web Users

===Special Issues of the Target Group===

Software Companies: In order to optimize their software, they have to explore the user's needs. Logfiles can offer them some useful informations.

For Web Designers it can be helpful to know some facts about their visitors. Logfiles tell them, which browsers they use, when they access the site, traffic, and so on. This Informations allow them to organize the webpage in a convenient and reliable way. It's the same with Web Administrators.

Advertising Companies strive to study user behaviour in order to orientate their adds more effectively.

===Known Solutions / Methods (related to the target group)===
#Radial Tree Viewer
#Anemone
#Internet Cartographer
#WebTracer
#WebHopper
#WebPath
#The Chicago Tribune Website
#Visualizing the online debate on the European Constitution
#Mercator 
...

==Intended Purpose==

===Goals and Objectives===
#Which client software is used, which browsers
#How users behave, in combination with site structure, dead ends, changes in behavior regarding to time.
#Identify groups of users who act in a similar way.
#Identify "hot" topics

===Problems and Tasks to Solve===
- '''Improve the Servers''': Administrators, Web Designers and Software Companies need this information, to improve the Servers. They need to know what people are interested in, if there are special groups, which have similar behavior, navigate to the same themes and in a similar way. What kind of themes are often searched for, and how. With this information, they can help Users to get the things they want faster and easier. They can adapt the Server to the needs of the Users. 
In order to effectively manage a web server, it is necessary to get feedback about the activity and performance of the server as well as any problems that may be occuring 
- '''Adapt Advertising to Users interests''':Advertising Companys can use the information to identify themes and products of interest to a group of users. You get an overview of groups of things people are interessted in. So they can adapt the topics of their advertisement to this information.

==Proposed Design==

===Types of Visualization Applied===

===Visual Mapping===

(Datadimension => Attribute)

===Description of Used Techniques===

===Possibilities of Interaction===

===Mockups / Fake Screenshots===

== Resources ==

:[1] [Behlendorf et al., 2005] Brian Behlendorf, Apache HTTP Server Logfiles, Apache HTTP Server Project, Access Date: 17 October 2005, http://httpd.apache.org/docs/1.3/logs.html

:[2] [Cooper, 2004] Colin Cooper, Logfile Definitions and Examples, Intranet Software Solutions (Europe) Limited [ISSEL], Access Date: 17 October 2005, http://www.issel.co.uk/FAQ/logfile_definitions_examples.htm

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 3

2005-11-21T08:58:37Z

UE-InfoVis0506 0125718:

==Topic==
Webserver Logfile Visualization

==Area of Application==

===Analysis of Application Area===

====General Description====
Webservers typically generate logfiles containing huge amounts of information on page accesses, used client software, type of access, and many more. Analysis tools like for example AWStats try to make use of this information and present simple statistics mostly in form of tables or simple bar graphs. Unfortunately, they are mostly very limited and "low-level" regarding their information representation. More interesting questions like user behavior in combination with site structure, dead ends, changes in behavior regarding to time (evolution), typical behavioral patterns, finding groups of users that share similar behavioral patterns, site entry points, or intrusion detection cannot be answered by using similar tools. For being able to deal with this kind of topics, more advanced visual tools are needed that unveil this information.

====Special Issues====

There are many different known solutions/methods to visualize Webeserver Logfiles. Most of them make use of simple chart or bar diagrams. The question is, if it is possible to present this huge set of informations in just one diagram, that illustrates all the data in a simple and undastandable way.

===Analysis of the Dataset===

Here is an example of such a logfile entry:

205.218.110.166 - - [08/Dec/1996:15:02:10 -0800] "GET /info/index.html HTTP/1.0" 200 14912 "http://www.yourcompany.com/index.html " "Mozilla/3.0Gold (Win95; I)" "35bebd61b31211cfbdcd00c04fd611cf"

The content of this entry explained, from left to right:

'''"205.218.110.166"''' - - This is the IP address of the machine making a request of your web server - its domain name can be determined in HitList by enabling Reverse DNS lookups, assuming your server hasn't put this information in already - many so, some don't. (if the domain name was in there, you'd see its URL instead of the raw IP).

'''"-"''' - this first dash is typically the server's IP address, which most NCSA format servers don't insert by default.

'''"-"''' - this second dash is typically authenticated usernames, which again many NCSA format servers don't insert by default.

'''"[08/Dec/1996:15:02:10 -0800]"''' - This is the date and time of the access, including the offset from Greenwich Mean Time - the latter is the "-800", meaning the web server being accessed is 8 hours ahead of GMT.

'''"GET /info/index.html HTTP/1.0"''' - This is the actual request the visitor's browser made when at your page or server.

'''"HTTP/1.0"''' refers to the protocol and its version, here being version 1.0 of the http protocol.

'''"200"''' - this is the server response code - a "successful" request (meaning the visitor's browser loaded the entire HTML/GIF/JPEG, etc.) generates a response code of 200. Others include:

206 - Partial request successful (not complete)
302 - URL has been redirected to another document
400 - Bad request was made by the client
401 - Authorization is required for this document
403 - Access to this document is forbidden
404 - Document not found
500 - Server internal error
501 - Application method (either GET or POST) is not implemented
503 - Server is out of resources

'''"14912"''' - This is the number of bytes transferred to the client during the visit. Since every request has some response, even erroneous requests will have a non-zero value for this field.
"http://www.yourcompany.com/index.html" - This is the referrer field, or the site the visitor was on immediately prior to making this entry's request - in this case, the person was looking at the index.html (probably the home page) page before going to the /info/index.html page in this entry.
"Mozilla/3.0Gold (Win95; I)" - this is the user-agent field, meaning the actual browser and OS used by the visitor - in this case, Mozilla is Netscape, the next value is the version (here, 3.0Gold), and the final value is the OS it was using (Windows 95).

Finally, the '''"35bebd61b31211cfbdcd00c04fd611cf"''' is the cookie information, which may or may not be there, depending on whether the webserver used has cookies enabled and whether one was passed from webserver to the visitor's computer.

There are several different specific Logfile Formats, for example: Microsoft IIS 3.0 and 2.0, Microsoft IIS4.0 (W3SVC format), Netscape (NCSA format with/without unique format header), Lotus Domino format, O'Reilly WebSite format...

==Target Group==

===Identifying the Target===
We identified the following Target groups:
#Software Companies: especially those who develop browsers and web based applications
#Web Dsigners
#Administrators
#Advertising Companys
#Web Users

===Special Issues of the Target Group===

Software Companies: In order to optimize their software, they have to explore the user's needs. Logfiles can offer them some useful informations.

For Web Designers it can be helpful to know some facts about their visitors. Logfiles tell them, which browsers they use, when they access the site, traffic, and so on. This Informations allow them to organize the webpage in a convenient and reliable way. It's the same with Web Administrators.

Advertising Companies strive to study user behaviour in order to orientate their adds more effectively.

===Known Solutions / Methods (related to the target group)===
#Radial Tree Viewer
#Anemone
#Internet Cartographer
#WebTracer
#WebHopper
#WebPath
#The Chicago Tribune Website
#Visualizing the online debate on the European Constitution
#Mercator 
...

==Intended Purpose==

===Goals and Objectives===
#Which client software is used, which browsers
#How users behave, in combination with site structure, dead ends, changes in behavior regarding to time.
#Identify groups of users who act in a similar way.
#Identify "hot" topics

===Problems and Tasks to Solve===
- '''Improve the Servers''': Administrators, Web Designers and Software Companies need this information, to improve the Servers. They need to know what people are interested in, if there are special groups, which have similar behavior, navigate to the same themes and in a similar way. What kind of themes are often searched for, and how. With this information, they can help Users to get the things they want faster and easier. They can adapt the Server to the needs of the Users. 
In order to effectively manage a web server, it is necessary to get feedback about the activity and performance of the server as well as any problems that may be occuring 
- '''Adapt Advertising to Users interests''':Advertising Companys can use the information to identify themes and products of interest to a group of users. You get an overview of groups of things people are interessted in. So they can adapt the topics of their advertisement to this information.

==Proposed Design==

===Types of Visualization Applied===

===Visual Mapping===

(Datadimension => Attribute)

===Description of Used Techniques===

===Possibilities of Interaction===

===Mockups / Fake Screenshots===

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 3

2005-11-21T08:53:38Z

UE-InfoVis0506 0125718:

==Topic==
Webserver Logfile Visualization

==Area of Application==

===Analysis of Application Area===

====General Description====
Webservers typically generate logfiles containing huge amounts of information on page accesses, used client software, type of access, and many more. Analysis tools like for example AWStats try to make use of this information and present simple statistics mostly in form of tables or simple bar graphs. Unfortunately, they are mostly very limited and "low-level" regarding their information representation. More interesting questions like user behavior in combination with site structure, dead ends, changes in behavior regarding to time (evolution), typical behavioral patterns, finding groups of users that share similar behavioral patterns, site entry points, or intrusion detection cannot be answered by using similar tools. For being able to deal with this kind of topics, more advanced visual tools are needed that unveil this information.

====Special Issues====

===Analysis of the Dataset===

Here is an example of such a logfile entry:

205.218.110.166 - - [08/Dec/1996:15:02:10 -0800] "GET /info/index.html HTTP/1.0" 200 14912 "http://www.yourcompany.com/index.html " "Mozilla/3.0Gold (Win95; I)" "35bebd61b31211cfbdcd00c04fd611cf"

The content of this entry explained, from left to right:

'''"205.218.110.166"''' - - This is the IP address of the machine making a request of your web server - its domain name can be determined in HitList by enabling Reverse DNS lookups, assuming your server hasn't put this information in already - many so, some don't. (if the domain name was in there, you'd see its URL instead of the raw IP).

'''"-"''' - this first dash is typically the server's IP address, which most NCSA format servers don't insert by default.

'''"-"''' - this second dash is typically authenticated usernames, which again many NCSA format servers don't insert by default.

'''"[08/Dec/1996:15:02:10 -0800]"''' - This is the date and time of the access, including the offset from Greenwich Mean Time - the latter is the "-800", meaning the web server being accessed is 8 hours ahead of GMT.

'''"GET /info/index.html HTTP/1.0"''' - This is the actual request the visitor's browser made when at your page or server.

'''"HTTP/1.0"''' refers to the protocol and its version, here being version 1.0 of the http protocol.

'''"200"''' - this is the server response code - a "successful" request (meaning the visitor's browser loaded the entire HTML/GIF/JPEG, etc.) generates a response code of 200. Others include:

206 - Partial request successful (not complete)
302 - URL has been redirected to another document
400 - Bad request was made by the client
401 - Authorization is required for this document
403 - Access to this document is forbidden
404 - Document not found
500 - Server internal error
501 - Application method (either GET or POST) is not implemented
503 - Server is out of resources

'''"14912"''' - This is the number of bytes transferred to the client during the visit. Since every request has some response, even erroneous requests will have a non-zero value for this field.
"http://www.yourcompany.com/index.html" - This is the referrer field, or the site the visitor was on immediately prior to making this entry's request - in this case, the person was looking at the index.html (probably the home page) page before going to the /info/index.html page in this entry.
"Mozilla/3.0Gold (Win95; I)" - this is the user-agent field, meaning the actual browser and OS used by the visitor - in this case, Mozilla is Netscape, the next value is the version (here, 3.0Gold), and the final value is the OS it was using (Windows 95).

Finally, the '''"35bebd61b31211cfbdcd00c04fd611cf"''' is the cookie information, which may or may not be there, depending on whether the webserver used has cookies enabled and whether one was passed from webserver to the visitor's computer.

There are several different specific Logfile Formats, for example: Microsoft IIS 3.0 and 2.0, Microsoft IIS4.0 (W3SVC format), Netscape (NCSA format with/without unique format header), Lotus Domino format, O'Reilly WebSite format...

==Target Group==

===Identifying the Target===
We identified the following Target groups:
#Software Companies: especially those who develop browsers and web based applications
#Web Dsigners
#Administrators
#Advertising Companys
#Web Users

===Special Issues of the Target Group===

Software Companies: In order to optimize their software, they have to explore the user's needs. Logfiles can offer them some useful informations.

For Web Designers it can be helpful to know some facts about their visitors. Logfiles tell them, which browsers they use, when they access the site, traffic, and so on. This Informations allow them to organize the webpage in a convenient and reliable way. It's the same with Web Administrators.

Advertising Companies strive to study user behaviour in order to orientate their adds more effectively.

===Known Solutions / Methods (related to the target group)===
#Radial Tree Viewer
#Anemone
#Internet Cartographer
#WebTracer
#WebHopper
#WebPath
#The Chicago Tribune Website
#Visualizing the online debate on the European Constitution
#Mercator 
...

==Intended Purpose==

===Goals and Objectives===
#Which client software is used, which browsers
#How users behave, in combination with site structure, dead ends, changes in behavior regarding to time.
#Identify groups of users who act in a similar way.
#Identify "hot" topics

===Problems and Tasks to Solve===
- '''Improve the Servers''': Administrators, Web Designers and Software Companies need this information, to improve the Servers. They need to know what people are interested in, if there are special groups, which have similar behavior, navigate to the same themes and in a similar way. What kind of themes are often searched for, and how. With this information, they can help Users to get the things they want faster and easier. They can adapt the Server to the needs of the Users. 
In order to effectively manage a web server, it is necessary to get feedback about the activity and performance of the server as well as any problems that may be occuring 
- '''Adapt Advertising to Users interests''':Advertising Companys can use the information to identify themes and products of interest to a group of users. You get an overview of groups of things people are interessted in. So they can adapt the topics of their advertisement to this information.

==Proposed Design==

===Types of Visualization Applied===

===Visual Mapping===

(Datadimension => Attribute)

===Description of Used Techniques===

===Possibilities of Interaction===

===Mockups / Fake Screenshots===

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 3

2005-11-18T11:27:50Z

UE-InfoVis0506 0125718:

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 3

2005-11-18T11:04:02Z

UE-InfoVis0506 0125718: /* Special Issues of the Target Group */

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 3

2005-11-18T11:03:40Z

UE-InfoVis0506 0125718: /* Problems and Tasks to Solve */

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 3

2005-11-18T10:55:49Z

UE-InfoVis0506 0125718: /* General Description */

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 2

2005-11-15T11:28:29Z

UE-InfoVis0506 0125718:

== Poor Graphic ==
[[Image:Perceptualedge03world-car-production.gif|none|thumb|600px|World Car Production 1977-80 (click on image for larger version)]]

== Drawbacks ==

This image is far away from a good Visualization of the underlying Data. It has drawbacks according to some well known Design Principles, which we will explain in the following:

- '''data ink''':

Everything that communicates actual data is data ink and is needed.[Few,2004] But our image contains some unnecessary data ink. The white Border around all the charts and the white lines around each single chart and between the pies of the charts are unnecessary data ink.

- '''color''':

Lines, bars and charts should be colored in a way, that not one color stands out more prominently than the others, thus supporting the equal importance of the three data sets.[Few,2004] In our image the red and blue pies of the charts violate this principle because they stand out more prominently than the others.

- '''lie factor''':

The lie lactor is a value to describe the relation between the size of effect shown in a graphic and the size of effect shown in the data.[Muster et al.,2005] The first problem is, it seems that we look at the image not from the front but a little from the side. That distorts the message since neither the angles nor the areas are in proportion to the data.[Seyfang et al., 2005] The second one is that the charts have different distances to each other. The distance of the chart 1977 to the chart 1978 is shorter than that from 1979 to 1980. It schould be the same.

- '''past experience''':

That means that past experience have an effect on how we see and interpret things.[Starl and Froschauer, 2005] You can say that our image somehow violates this principle. We are used to read from left to right, but the charts on the image are organized from right to left. This can be confusing.

- '''simplicity''':

You should keep your image as simple as possible, which also means that you have to reduce redundant information.[Few,2004] Our image violates this principle. The percentage of a lands contribution to the world production is shown on one hand via the angle and size of the pies and on the other hand it is written numerical above the pies.

== Updated Picture ==

[[Image:Infovis_worldwide_car_production.png]]

== Changes ==

Our objective was to present the information as simple and transparent as possible. In order to achieve this, we use a ThemeRiver [Havre et al., 1999] influenced diagram. The ThemeRiver visualization helps users identify time-related patterns, trends, and relationships. The themes are represented by a "river" that flows left to right through time. The river widens or narrows to depict changes in the underlying data. Individual themes are represented as colored "currents" flowing within the river. The theme currents narrow or widen to indicate changes in individual theme strength at any point in time.

Because of the flowing structure it is now much simpler to follow trends and changes in market share, as well as overall changes in the world wide car production.

It is much easier to compare the different values with one another than it was before. The different colours are clearly distinguishable on white background, the values are good readable and the temporal sequence goes from left to right. We intentionally abstained from a three-dimensional look because it is not necessary and moreover confuses the viewer.

Major advantages:

* makes it eays to follow trends and market share
* shows development of the world wide car production
* simplifies comparisson of different values over time

== Resources ==

:[1] [Few, 2004] Stephen Few, Elegance Through Simplicity, Intelligent Enterprise, Access Date: 26 October 2005, http://www.intelligententerprise.com/showArticle.jhtml;jsessionid=N2ATDQWY5VYKSQSNDBGCKHSCJUMEKJVN?articleID=49400920

:[2] [Seyfang et al., 2005] Leonhard Seyfang, Heinrich Fritz, Stefan Schnabl, Gioia Baldass , Gruppe G8 - Aufgabe 1 - Chart Junk, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G8_-_Aufgabe_1_-_Chart_Junk

:[3] [Muster et al.,2005] Anna Muster, Jürgen Puchta, Christian Rainer, Christoph Sölder, Gruppe G4 - Aufgabe 1 - Lie Factor, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G4_-_Aufgabe_1_-_Lie_Factor

:[4] [Starl and Froschauer, 2005] Erwin Starl, Joseph Froschauer, Gruppe G7 - Aufgabe 1, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G7_-_Aufgabe_1_-_Gestalt_Laws

:[5] [Havre et al., 1999] Susan Havre, Beth Hetzler, Lucy Nowell, ThemeRiver(TM): In Search of Trends, Patterns, and Relationships, Battelle Pacific Northwest Division, 1999. http://citeseer.ist.psu.edu/havre99themerivertm.html

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 2

2005-11-15T11:27:41Z

UE-InfoVis0506 0125718:

== Poor Graphic ==
[[Image:Perceptualedge03world-car-production.gif|none|thumb|600px|World Car Production 1977-80 (click on image for larger version)]]

== Drawbacks ==

This image is far away from a good Visualization of the underlying Data. It has drawbacks according to some well known Design Principles, which we will explain in the following:

- '''data ink''':

Everything that communicates actual data is data ink and is needed.[Few,2004] But our image contains some unnecessary data ink. The white Border around all the charts and the white lines around each single chart and between the pies of the charts are unnecessary data ink.

- '''color''':

Lines, bars and charts should be colored in a way, that not one color stands out more prominently than the others, thus supporting the equal importance of the three data sets.[Few,2004] In our image the red and blue pies of the charts violate this principle because they stand out more prominently than the others.

- '''lie factor''':

The lie lactor is a value to describe the relation between the size of effect shown in a graphic and the size of effect shown in the data.[Muster et al.,2005] The first problem is, it seems that we look at the image not from the front but a little from the side. That distorts the message since neither the angles nor the areas are in proportion to the data.[Seyfang et al., 2005] The second one is that the charts have different distances to each other. The distance of the chart 1977 to the chart 1978 is shorter than that from 1979 to 1980. It schould be the same.

- '''past experience''':

That means that past experience have an effect on how we see and interpret things.[Starl and Froschauer, 2005] You can say that our image somehow violates this principle. We are used to read from left to right, but the charts on the image are organized from right to left. This can be confusing.

- '''simplicity''':

You should keep your image as simple as possible, which also means that you have to reduce redundant information.[Few,2004] Our image violates this principle. The percentage of a lands contribution to the world production is shown on one hand via the angle and size of the pies and on the other hand it is written numerical above the pies.

== Updated Picture ==

[[Image:Infovis_worldwide_car_production.png]]

== Changes ==

Our objective was to present the information as simple and transparent as possible. In order to achieve this, we use a ThemeRiver [Havre et al., 1999] influenced diagram. The ThemeRiver visualization helps users identify time-related patterns, trends, and relationships. The themes are represented by a "river" that flows left to right through time. The river widens or narrows to depict changes in the underlying data. Individual themes are represented as colored "currents" flowing within the river. The theme currents narrow or widen to indicate changes in individual theme strength at any point in time.

Because of the flowing structure it is now much simpler to follow trends and changes in market share, as well as overall changes in the world wide car production.

It is much easier to compare the different values with one another than it was before. The different colours are clearly distinguishable on white background, the values are good readable and the temporal sequence goes from left to right. We intentionally abstained from a three-dimensional look because it is not necessary and moreover confuses the viewer.

Major advantages:

- makes it eays to follow trends and market share
- shows development of the world wide car production
- simplifies comparisson of different values over time

== Resources ==

:[1] [Few, 2004] Stephen Few, Elegance Through Simplicity, Intelligent Enterprise, Access Date: 26 October 2005, http://www.intelligententerprise.com/showArticle.jhtml;jsessionid=N2ATDQWY5VYKSQSNDBGCKHSCJUMEKJVN?articleID=49400920

:[2] [Seyfang et al., 2005] Leonhard Seyfang, Heinrich Fritz, Stefan Schnabl, Gioia Baldass , Gruppe G8 - Aufgabe 1 - Chart Junk, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G8_-_Aufgabe_1_-_Chart_Junk

:[3] [Muster et al.,2005] Anna Muster, Jürgen Puchta, Christian Rainer, Christoph Sölder, Gruppe G4 - Aufgabe 1 - Lie Factor, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G4_-_Aufgabe_1_-_Lie_Factor

:[4] [Starl and Froschauer, 2005] Erwin Starl, Joseph Froschauer, Gruppe G7 - Aufgabe 1, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G7_-_Aufgabe_1_-_Gestalt_Laws

:[5] [Havre et al., 1999] Susan Havre, Beth Hetzler, Lucy Nowell, ThemeRiver(TM): In Search of Trends, Patterns, and Relationships, Battelle Pacific Northwest Division, 1999. http://citeseer.ist.psu.edu/havre99themerivertm.html

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 2

2005-11-15T11:04:19Z

UE-InfoVis0506 0125718:

== Poor Graphic ==
[[Image:Perceptualedge03world-car-production.gif|none|thumb|600px|World Car Production 1977-80 (click on image for larger version)]]

== Drawbacks ==

This image is far away from a good Visualization of the underlying Data. It has drawbacks according to some well known Design Principles, which we will explain in the following:

- '''data ink''':

Everything that communicates actual data is data ink and is needed.[Few,2004] But our image contains some unnecessary data ink. The white Border around all the charts and the white lines around each single chart and between the pies of the charts are unnecessary data ink.

- '''color''':

Lines, bars and charts should be colored in a way, that not one color stands out more prominently than the others, thus supporting the equal importance of the three data sets.[Few,2004] In our image the red and blue pies of the charts violate this principle because they stand out more prominently than the others.

- '''lie factor''':

The lie lactor is a value to describe the relation between the size of effect shown in a graphic and the size of effect shown in the data.[Muster et al.,2005] The first problem is, it seems that we look at the image not from the front but a little from the side. That distorts the message since neither the angles nor the areas are in proportion to the data.[Seyfang et al., 2005] The second one is that the charts have different distances to each other. The distance of the chart 1977 to the chart 1978 is shorter than that from 1979 to 1980. It schould be the same.

- '''past experience''':

That means that past experience have an effect on how we see and interpret things.[Starl and Froschauer, 2005] You can say that our image somehow violates this principle. We are used to read from left to right, but the charts on the image are organized from right to left. This can be confusing.

- '''simplicity''':

You should keep your image as simple as possible, which also means that you have to reduce redundant information.[Few,2004] Our image violates this principle. The percentage of a lands contribution to the world production is shown on one hand via the angle and size of the pies and on the other hand it is written numerical above the pies.

== Updated Picture ==

[[Image:Infovis_worldwide_car_production.png]]

== Changes ==

Our objective was to present the information as simple and transparent as possible. In order to achieve this, we use a ThemeRiver [Havre et al., 1999] influenced diagram. The ThemeRiver visualization helps users identify time-related patterns, trends, and relationships. The themes are represented by a "river" that flows left to right through time. The river widens or narrows to depict changes in the underlying data. Individual themes are represented as colored "currents" flowing within the river. The theme currents narrow or widen to indicate changes in individual theme strength at any point in time.

Because of the flowing structure it is now much simpler to follow trends and changes in market share, as well as overall changes in the world wide car production.

It is much easier to compare the different values with one another than it was before. The different colours are clearly distinguishable on white background, the values are good readable and the temporal sequence goes from left to right. We intentionally abstained from a three-dimensional look because it is not necessary and moreover confuses the viewer.

== Resources ==

:[1] [Few, 2004] Stephen Few, Elegance Through Simplicity, Intelligent Enterprise, Access Date: 26 October 2005, http://www.intelligententerprise.com/showArticle.jhtml;jsessionid=N2ATDQWY5VYKSQSNDBGCKHSCJUMEKJVN?articleID=49400920

:[2] [Seyfang et al., 2005] Leonhard Seyfang, Heinrich Fritz, Stefan Schnabl, Gioia Baldass , Gruppe G8 - Aufgabe 1 - Chart Junk, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G8_-_Aufgabe_1_-_Chart_Junk

:[3] [Muster et al.,2005] Anna Muster, Jürgen Puchta, Christian Rainer, Christoph Sölder, Gruppe G4 - Aufgabe 1 - Lie Factor, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G4_-_Aufgabe_1_-_Lie_Factor

:[4] [Starl and Froschauer, 2005] Erwin Starl, Joseph Froschauer, Gruppe G7 - Aufgabe 1, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G7_-_Aufgabe_1_-_Gestalt_Laws

:[5] [Havre et al., 1999] Susan Havre, Beth Hetzler, Lucy Nowell, ThemeRiver(TM): In Search of Trends, Patterns, and Relationships, Battelle Pacific Northwest Division, 1999. http://citeseer.ist.psu.edu/havre99themerivertm.html

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 2

2005-11-02T17:31:22Z

UE-InfoVis0506 0125718:

== Poor Graphic ==
[[Image:Perceptualedge03world-car-production.gif|none|thumb|600px|World Car Production 1977-80 (click on image for larger version)]]

== Drawbacks ==

This image is far away from a good Visualization of the underlying Data. It has drawbacks according to some well known Design Principles, which we will explain in the following:

- '''data ink''':

Everything that communicates actual data is data ink and is needed.[1] But our image contains some unnecessary data ink. The white Border around all the charts and the white lines around each single chart and between the pies of the charts are unnecessary data ink.

- '''color''':

Lines, bars and charts should be colored in a way, that that no one color stands out more prominently than the others, thus supporting the equal importance of the three data sets.[1] In our image the red and blue pies of the charts violate this principle because they stand out more promonently than the others.

- '''lie factor''':

The lie lactor is a value to describe the relation between the size of effect shown in a graphic and the size of effect shown in the data.[3] The first problem is, it seems that we look at the image not from the front but a little from the side. That distorts the message since neither the angles nor the areas are in proportion to the data.[2] The second one is that the charts have different distances to each other. The distance of the chart 1977 to the chart 1978 is shorter than that from 1979 to 1980. It schould be the same.

- '''past experience''':

That means that past experience have an effect of how we see and interpret things.[4] You can say that our image somehow violates this principle. We are used to read from left to right, but the charts on the image are organized from right to left. This can be confusing.

- '''simplicity''':

You should keep your image as simple as possible, which also means that you have to reduce redundant information.[1] Our image violates this principle. The percentage of a lands contribution to the world production is shown on one hand via the angle and size of the pies and on the other hand it is written numerical above the pies.

== Updated Picture ==

[[Image:worldcarprod.jpg]]

== Changes ==

Our objective was to present the information as simple and transparent as possible. In order to achieve this, we use a two-dimensional diagram with grouped bars. It is much easier to compare the different values with one another than it was before. The different colours are clearly distinguishable on white background, the values are good readable and the temporally sequence goes from left to right. We intentionally abstaint from a three-dimensional look because it is not necessary and moreover confuses the viewer.
All in all the graphic looks much more orderly and simplified.

== Resources ==

:[1] [Few, 2004] Stephen Few, Elegance Through Simplicity, Intelligent Enterprise, Access Date: 26 October 2005, http://www.intelligententerprise.com/showArticle.jhtml;jsessionid=N2ATDQWY5VYKSQSNDBGCKHSCJUMEKJVN?articleID=49400920

:[2] [Seyfang, Fritz, Schnabl, Baldass, 2005] Leonhard Seyfang, Heinrich Fritz, Stefan Schnabl, Gioia Baldass , Gruppe G8 - Aufgabe 1 - Chart Junk, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G8_-_Aufgabe_1_-_Chart_Junk

:[3] [Muster, Puchta, Rainer, Sölder, 2005] Anna Muster, Jürgen Puchta, Christian Rainer, Christoph Sölder, Gruppe G4 - Aufgabe 1 - Lie Factor, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G4_-_Aufgabe_1_-_Lie_Factor

:[4] [Starl, Froschauer, 2005] Erwin Starl, Joseph Froschauer, Gruppe G7 - Aufgabe 1, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G7_-_Aufgabe_1_-_Gestalt_Laws

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 2

2005-10-27T14:48:51Z

UE-InfoVis0506 0125718:

== Poor Graphic ==
[[Image:Perceptualedge03world-car-production.gif|none|thumb|600px|World Car Production 1977-80 (click on image for larger version)]]

== Drawbacks ==

This image is far away from a good Visualization of the underlying Data. It has drawbacks according to some well known Design Principles, which we will explain in the following:

- '''data ink''':

Everything that communicates actual data is data ink and is needed.[1] But our image contains some unnecessary data ink. The white Border around all the charts and the white lines around each single chart and between the pies of the charts are unnecessary data ink.

- '''color''':

Lines, bars and charts should be colored in a way, that that no one color stands out more prominently than the others, thus supporting the equal importance of the three data sets.[1] In our image the red and blue pies of the charts violate this principle because they stand out more promonently than the others.

- '''lie factor''':

The lie lactor is a value to describe the relation between the size of effect shown in a graphic and the size of effect shown in the data.[3] The first problem is, it seems that we look at the image not from the front but a little from the side. That distorts the message since neither the angles nor the areas are in proportion to the data.[2] The second one is that the charts have different distances to each other. The distance of the chart 1977 to the chart 1978 is shorter than that from 1979 to 1980. It schould be the same.

- '''past experience''':

That means that past experience have an effect of how we see and interpret things.[4] You can say that our image somehow violates this principle. We are used to read from left to right, but the charts on the image are organized from right to left. This can be confusing.

- '''simplicity''':

You should keep your image as simple as possible, which also means that you have to reduce redundant information.[1] Our image violates this principle. The percentage of a lands contribution to the world production is shown on one hand via the angle and size of the pies and on the other hand it is written numerical above the pies.

== Updated Picture ==

[[Image:worldcarprod.jpg]]

== Changes ==

Our objective was to present the information as simple and transparent as possible. In order to achieve this, we use a two-dimensional diagram with grouped bars. It is much easier to compare the different values with one another than it was before. The different colours are clearly distinguishable on white background, the values are good readable and the temporally sequence goes from left to right. We intentionally abstaint from a three-dimensional look because it is not necessary and moreover confuses the viewer.
All in all the graphic looks much more orderly and simplified.

== Resources ==

:[1] [Few, 2004] Stephen Few, Elegance Through Simplicity, Intelligent Enterprise, Access Date: 26 October 2005, http://www.intelligententerprise.com/showArticle.jhtml;jsessionid=N2ATDQWY5VYKSQSNDBGCKHSCJUMEKJVN?articleID=49400920

:[2] [Seyfang, Fritz, Schnabl, Baldass, 2005] Leonhard Seyfang, Heinrich Fritz, Stefan Schnabl, Gioia Baldass , Gruppe G8 - Aufgabe 1 - Chart Junk, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G8_-_Aufgabe_1_-_Chart_Junk

:[3] [Muster, Puchta, Rainer, Sölder, 2005] Anna Muster, Jürgen Puchta, Christian Rainer, Christoph Sölder, Gruppe G4 - Aufgabe 1 - Lie Factor, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G4_-_Aufgabe_1_-_Lie_Factor

:[4] [Starl, Froschauer, 205] Erwin Starl, Joseph Froschauer, Gruppe G7 - Aufgabe 1, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G7_-_Aufgabe_1_-_Gestalt_Laws

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 2

2005-10-27T09:49:51Z

UE-InfoVis0506 0125718:

File:Worldcarprod.jpg

2005-10-27T09:47:58Z

UE-InfoVis0506 0125718: World Car Production 1977-80

== Summary ==
World Car Production 1977-80
== Copyright status ==

== Source ==

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 2

2005-10-27T09:26:51Z

UE-InfoVis0506 0125718:

File:Carprod80.jpg

2005-10-27T09:02:28Z

UE-InfoVis0506 0125718: World Car Production 1980

== Summary ==
World Car Production 1980
== Copyright status ==

== Source ==

File:Carprod79.jpg

2005-10-27T09:02:08Z

UE-InfoVis0506 0125718: World Car Production 1979

== Summary ==
World Car Production 1979
== Copyright status ==

== Source ==

File:Carprod78.jpg

2005-10-27T09:01:52Z

UE-InfoVis0506 0125718: World Car Production 1978

== Summary ==
World Car Production 1978
== Copyright status ==

== Source ==

File:Carprod77.jpg

2005-10-27T09:01:05Z

UE-InfoVis0506 0125718: World Car Production 1977

== Summary ==
World Car Production 1977
== Copyright status ==

== Source ==

File:Past3.gif

2005-10-20T15:29:35Z

UE-InfoVis0506 0125718:

== Summary ==

== Copyright status ==

== Source ==
http://www.rci.rutgers.edu/~cfs/305_html/Gestalt/wertheimer2.html

File:Past2.gif

2005-10-20T15:29:29Z

UE-InfoVis0506 0125718:

== Summary ==

== Copyright status ==

== Source ==
http://www.rci.rutgers.edu/~cfs/305_html/Gestalt/wertheimer2.html

File:Past.gif

2005-10-20T15:28:42Z

UE-InfoVis0506 0125718:

== Summary ==

== Copyright status ==

== Source ==
http://www.rci.rutgers.edu/~cfs/305_html/Gestalt/wertheimer2.html

File:Figureground.gif

2005-10-20T15:01:02Z

UE-InfoVis0506 0125718:

== Summary ==

== Copyright status ==

== Source ==
http://www.ship.edu/~cgboeree/gestalt.html

File:Pragnanz.gif

2005-10-20T14:51:46Z

UE-InfoVis0506 0125718:

== Summary ==

== Copyright status ==

== Source ==
http://www.uic.edu/classes/psych/psych352jw/pragnanz1.gif

File:Symmetry.gif

2005-10-20T14:48:54Z

UE-InfoVis0506 0125718:

== Summary ==

== Copyright status ==

== Source ==
http://www.aber.ac.uk/media/Modules/MC10220/visper06.html

File:Common.gif

2005-10-20T14:43:02Z

UE-InfoVis0506 0125718:

== Summary ==

== Copyright status ==

== Source ==
http://coe.sdsu.edu/eet/articles/visualperc1/start.htm

File:Continuation.gif

2005-10-20T14:34:16Z

UE-InfoVis0506 0125718: