InfoVis:Wiki - User contributions [en]

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

2005-11-22T18:35:23Z

UE-InfoVis0506 9426777: /* Visual Mapping */

==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 is the Remote hostname or IP number if DNS hostname is not available, or if DNSLookup is Off. 
remotehost is a one-dimensional discreet datatype.[6]

'''"-"''' - 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. 
date has seven dimensions in the following format: [day/month/year:hour:minute:second zone]
 
Day: ordinal, 2 digits 
Month: nominal, 3 letters 
year = ordinal, 4 digits 
hour = ordinal, 2 digits 
minute = ordinal, 2 digits 
second = ordinal, 2 digits 
zone = nominal, + or - and 4 digits[6]

'''"GET /info/index.html HTTP/1.0"''' - This is the actual request the visitor's browser made when at your page or server. 
request has three dimensions in the following format: "request method /filename HTTP/version]" 
The request method is nominal. 
The filename is discrete.[6]

'''"HTTP/1.0"''' refers to the protocol and its version, here being version 1.0 of the http protocol. 
The HTTP version is theoretically ordinal. However, so far there exists only version 0.9, 1.0 and the current version 1.0[6]

'''"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 
status is a one-dimensional nominal datatype.[6]

'''"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). 
Bytes are a one-dimensional ordinal datatype.[6]

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 
...[5]

==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===

The following techniques will be used:

* Filtering
* Linking
* Detail on Demand
* Range Slider [Ahlberg and Shneiderman, 1994] with Time Lense.

{{quotation |"Overview first, zoom and filter, then details on demand. View relationships and history..." | Visual Information-Seeking Mantra [Shneiderman, 1996] }}

First, the user is presented with a net of accessed web pages and resources. She is able to filter the information using the checkboxes of OS, browser,.. and the Time Lens Range Slider.
When clicking on a resource, the view zooms if necessary and marks all nodes linking to and from this page, image,...

===Visual Mapping===

(Datadimension => Attribute)

The log contains the following information:

IP, date, request, protocol, response code, bytes, referer, user agent, cookie

From a given IP it is possible to determin the country of origin, so IPs are mapped to the world map. <Unknown> will also be listed.

The date is listed on the date lens slider. After choosing a date range the corresponding numbers and entries will change.
Above this date slider the user will find bars of transferred bytes in this date region.

The request is mapped onto the "web site" net in the middle. Further calculation is necessary to match /file/ to /file/index.php and /file/index.php?somesessionid=2139123123.
Only successful requests are listed here (eg response code 200).

If referer is an URL from within the server, the "web site" net draws a connection between the two pages. This connection width is determined by access count and direction (ie more wide at the referer than the target page). If the page is referred from the outside, the referring page is listed on the left hand side panel "external referers"

The user agent is parsed for operating system and browser information. Each is listed on the right with checkboxes, so the user can remove or include certain browsers or OS to the data set.

The number of hits is mapped to the size of the dots in the net view and external referer list.

When following the interaction of users it is possible to estimate a page reading time. This is displayed as arc in each page dot.

===Description of Used Techniques===

===Possibilities of Interaction===

Klicking on a browser, operating system or weekday check box reduces or increases the displayed data set. Numbers next to the settings change accordingly.

Klicking on a web page in net view also updates these numbers: The time lens and filters show the number of accesses to this resource. Marked are other pages which have been visited by users, who have been watching this page. Klicking on a blank spot resets that view.

If the button "filtered list" is pressed, the program produces a list of the webserver log file according to the settings (browser, page, time, os,...)

The "hide media" check box removes, if checked, all images, css and media files from the list, keeping only html, php, ...

===Mockups / Fake Screenshots===

[[Image:Infovis_weblog_fake.png|Screenshot|800px]]

== 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

:[3] [Shneiderman, 1996] Ben Shneiderman (1996), The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations, In Proceedings of the IEEE Symposium on Visual Languages, pages 336-343, Washington. IEEE Computer Society Press.

:[4] [Ahlberg and Shneiderman, 1994] Christopher Ahlberg and Ben Shneiderman (1994), Visual Information Seeking: Tight Coupling of Dynamic Query Filters with Starfield Displays, In Proceedings of the Conference on Human Factors in Computing Systems (CHI'94), pages 313-317. ACM Press.

:[5] [Visual Complexity] World Wide Web, Access Date: 15 November 2005, http://www.visualcomplexity.com/vc/index.cfm?domain=World%20Wide%20Web

:[6] [2] [Rainer, Karim, Kargl, Akcaglayan, 2005] Rainer Andreas, Karim Muhammad Shuaib, Kargl Horst, Akcaglayan Ali, TUW - UE InfoVis WS 2005/06 - Gruppe G3 - Aufgabe 3, Access Date: 22 November 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3

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

2005-11-22T10:44:57Z

UE-InfoVis0506 9426777: Zoomfrage

''' Diskussionsbeitrag '''

[[Image:Infovis_weblog.png|Fake Screenshot|600px]]

Geht das so irgendwie in die vorgestellte Richtung?

''' Zoom '''

web site: Die Webseiten als Netz dargestellt. Je größer ein Punkt ist, um so öfter wurde die Seite besucht. Der Bogen innerhalb eines Punktes zeigt die geschätzte Verweildauer an, aber nur relativ (zu den anderen Seiten). Nicht-Text-Ressourcen werden grau dargestellt, um nicht mit normalen Seiten verwechselt zu werden.
Klickt man auf eine Seite, wird (wenn nötig) gezoomt.

Auf welche Weise wird das Zoomen im Netz gelöst? werden dann alle anderen kleiner oder verzerrt?

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

2005-11-22T10:37:00Z

UE-InfoVis0506 9426777: Techniques

==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===

The following techniques will be used:

* Filtering
* Linking
* Detail on Demand
* Range Slider [Ahlberg and Shneiderman, 1994] with Time Lense.

{{quotation |"Overview first, zoom and filter, then details on demand. View relationships and history..." | Visual Information-Seeking Mantra [Shneiderman, 1996] }}

First, the user is presented with a net of accessed web pages and resources. She is able to filter the information using the checkboxes of OS, browser,.. and the Time Lens Range Slider.
When clicking on a resource, the view zooms if necessary and marks all nodes linking to and from this page, image,...

===Visual Mapping===

(Datadimension => Attribute)

The log contains the following information:

IP, date, request, protocol, response code, bytes, referer, user agent, cookie

From a given IP it is possible to determin the country of origin, so IPs are mapped to the world map. <Unknown> will also be listed.

The date is listed on the date lens slider. After choosing a date range the corresponding numbers and entries will change.
Above this date slider the user will find bars of transferred bytes in this date region.

The request is mapped onto the "web site" net in the middle. Further calculation is necessary to match /file/ to /file/index.php and /file/index.php?somesessionid=2139123123.
Only successful requests are listed here (eg response code 200).

If referer is an URL from within the server, the "web site" net draws a connection between the two pages. If the page is referred from the outside, the referring page is listed on the left hand side panel "external referers"

The user agent is parsed for operating system and browser information. Each is listed on the right with checkboxes, so the user can remove or include certain browsers or OS to the data set.

The number of hits is mapped to the size of the dots in the net view and external referer list.

When following the interaction of users it is possible to estimate a page reading time. This is displayed as arc in each page dot.

===Description of Used Techniques===

===Possibilities of Interaction===

Klicking on a browser, operating system or weekday check box reduces or increases the displayed data set. Numbers next to the settings change accordingly.

Klicking on a web page in net view also updates these numbers: The time lens and filters show the number of accesses to this resource. Marked are other pages which have been visited by users, who have been watching this page. Klicking on a blank spot resets that view.

If the button "filtered list" is pressed, the program produces a list of the webserver log file according to the settings (browser, page, time, os,...)

The "hide media" check box removes, if checked, all images, css and media files from the list, keeping only html, php, ...

===Mockups / Fake Screenshots===

[[Image:Infovis_weblog_fake.png|Screenshot|800px]]

== 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

:[3] [Shneiderman, 1996] Ben Shneiderman (1996), The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations, In Proceedings of the IEEE Symposium on Visual Languages, pages 336-343, Washington. IEEE Computer Society Press.

:[4] [Ahlberg and Shneiderman, 1994] Christopher Ahlberg and Ben Shneiderman (1994), Visual Information Seeking: Tight Coupling of Dynamic Query Filters with Starfield Displays, In Proceedings of the Conference on Human Factors in Computing Systems (CHI'94), pages 313-317. ACM Press.

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

2005-11-21T20:35:00Z

UE-InfoVis0506 9426777: /* Possibilities of Interaction */

==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)

The log contains the following information:

IP, date, request, protocol, response code, bytes, referer, user agent, cookie

From a given IP it is possible to determin the country of origin, so IPs are mapped to the world map. <Unknown> will also be listed.

The date is listed on the date lens slider. After choosing a date range the corresponding numbers and entries will change.
Above this date slider the user will find bars of transferred bytes in this date region.

The request is mapped onto the "web site" net in the middle. Further calculation is necessary to match /file/ to /file/index.php and /file/index.php?somesessionid=2139123123.
Only successful requests are listed here (eg response code 200).

If referer is an URL from within the server, the "web site" net draws a connection between the two pages. If the page is referred from the outside, the referring page is listed on the left hand side panel "external referers"

The user agent is parsed for operating system and browser information. Each is listed on the right with checkboxes, so the user can remove or include certain browsers or OS to the data set.

The number of hits is mapped to the size of the dots in the net view and external referer list.

When following the interaction of users it is possible to estimate a page reading time. This is displayed as arc in each page dot.

===Description of Used Techniques===

===Possibilities of Interaction===

Klicking on a browser, operating system or weekday check box reduces or increases the displayed data set. Numbers next to the settings change accordingly.

Klicking on a web page in net view also updates these numbers: The time lens and filters show the number of accesses to this resource. Marked are other pages which have been visited by users, who have been watching this page. Klicking on a blank spot resets that view.

If the button "filtered list" is pressed, the program produces a list of the webserver log file according to the settings (browser, page, time, os,...)

The "hide media" check box removes, if checked, all images, css and media files from the list, keeping only html, php, ...

===Mockups / Fake Screenshots===

[[Image:Infovis_weblog_fake.png|Screenshot|800px]]

== 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-21T20:33:40Z

UE-InfoVis0506 9426777: Screenshot

==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)

The log contains the following information:

IP, date, request, protocol, response code, bytes, referer, user agent, cookie

From a given IP it is possible to determin the country of origin, so IPs are mapped to the world map. <Unknown> will also be listed.

The date is listed on the date lens slider. After choosing a date range the corresponding numbers and entries will change.
Above this date slider the user will find bars of transferred bytes in this date region.

The request is mapped onto the "web site" net in the middle. Further calculation is necessary to match /file/ to /file/index.php and /file/index.php?somesessionid=2139123123.
Only successful requests are listed here (eg response code 200).

If referer is an URL from within the server, the "web site" net draws a connection between the two pages. If the page is referred from the outside, the referring page is listed on the left hand side panel "external referers"

The user agent is parsed for operating system and browser information. Each is listed on the right with checkboxes, so the user can remove or include certain browsers or OS to the data set.

The number of hits is mapped to the size of the dots in the net view and external referer list.

When following the interaction of users it is possible to estimate a page reading time. This is displayed as arc in each page dot.

===Description of Used Techniques===

===Possibilities of Interaction===

Klicking on a browser, operating system or weekday check box reduces or increases the displayed data set. Numbers next to the settings change accordingly.

Klicking on a web page in net view also updates these numbers: The time lens and filters show the number of accesses to this resource. Klicking on a blank spot resets that view.

If the button "filtered list" is pressed, the program produces a list of the webserver log file according to the settings (browser, page, time, os,...)

The "hide media" check box removes, if checked, all images, css and media files from the list, keeping only html, php, ...

===Mockups / Fake Screenshots===

[[Image:Infovis_weblog_fake.png|Screenshot|800px]]

== 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

File:Infovis weblog fake.png

2005-11-21T20:31:07Z

UE-InfoVis0506 9426777: Fake screenshot for web log browser application

== Summary ==
Fake screenshot for web log browser application
== Copyright status ==

== Source ==
created by uploader

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

2005-11-21T20:26:14Z

UE-InfoVis0506 9426777: Possibilities of Interaction

==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)

The log contains the following information:

IP, date, request, protocol, response code, bytes, referer, user agent, cookie

From a given IP it is possible to determin the country of origin, so IPs are mapped to the world map. <Unknown> will also be listed.

The date is listed on the date lens slider. After choosing a date range the corresponding numbers and entries will change.
Above this date slider the user will find bars of transferred bytes in this date region.

The request is mapped onto the "web site" net in the middle. Further calculation is necessary to match /file/ to /file/index.php and /file/index.php?somesessionid=2139123123.
Only successful requests are listed here (eg response code 200).

If referer is an URL from within the server, the "web site" net draws a connection between the two pages. If the page is referred from the outside, the referring page is listed on the left hand side panel "external referers"

The user agent is parsed for operating system and browser information. Each is listed on the right with checkboxes, so the user can remove or include certain browsers or OS to the data set.

The number of hits is mapped to the size of the dots in the net view and external referer list.

When following the interaction of users it is possible to estimate a page reading time. This is displayed as arc in each page dot.

===Description of Used Techniques===

===Possibilities of Interaction===

Klicking on a browser, operating system or weekday check box reduces or increases the displayed data set. Numbers next to the settings change accordingly.

Klicking on a web page in net view also updates these numbers: The time lens and filters show the number of accesses to this resource. Klicking on a blank spot resets that view.

If the button "filtered list" is pressed, the program produces a list of the webserver log file according to the settings (browser, page, time, os,...)

The "hide media" check box removes, if checked, all images, css and media files from the list, keeping only html, php, ...

===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-21T10:41:21Z

UE-InfoVis0506 9426777: /* Visual Mapping */

==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)

The log contains the following information:

IP, date, request, protocol, response code, bytes, referer, user agent, cookie

From a given IP it is possible to determin the country of origin, so IPs are mapped to the world map. <Unknown> will also be listed.

The date is listed on the date lens slider. After choosing a date range the corresponding numbers and entries will change.
Above this date slider the user will find bars of transferred bytes in this date region.

The request is mapped onto the "web site" net in the middle. Further calculation is necessary to match /file/ to /file/index.php and /file/index.php?somesessionid=2139123123.
Only successful requests are listed here (eg response code 200).

If referer is an URL from within the server, the "web site" net draws a connection between the two pages. If the page is referred from the outside, the referring page is listed on the left hand side panel "external referers"

The user agent is parsed for operating system and browser information. Each is listed on the right with checkboxes, so the user can remove or include certain browsers or OS to the data set.

===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 talk:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 3

2005-11-17T16:59:37Z

UE-InfoVis0506 9426777: Fake Screenshot

''' Diskussionsbeitrag '''

[[Image:Infovis_weblog.png]]

Geht das so irgendwie in die vorgestellte Richtung?

File:Infovis weblog.png

2005-11-17T16:58:42Z

UE-InfoVis0506 9426777: Diskussionsbeitrag Fake Screenshot

== Summary ==
Diskussionsbeitrag Fake Screenshot
== Copyright status ==

== Source ==

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

2005-11-15T12:53:06Z

UE-InfoVis0506 9426777: Typos

== 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 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 easy to follow trends and market share
* shows development of the world wide car production
* simplifies comparison 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 talk:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 2

2005-11-14T09:56:57Z

UE-InfoVis0506 9426777: without lines?

== Bewertung ==
'''Punkte: 12'''

'''Begründung:'''
*Analyse OK
*Die Erklärung der Verbesserungen ist relativ kurz ausgefallen
*Die verbesserte Grafik ist selber noch verbesserungswürdig:
**Grundsätzlich ist die Wahl eines Balkendiagramm zur Darstellung dieser Daten NICHT ideal. Wichtig ist hier vor allem, wie die Werte sich über die Zeit entwickelt haben. Für diesen Zweck wäre ein Liniendiagramm wesentlich besser geeignet.
**Meiner Meinung nach würde die [http://citeseer.ist.psu.edu/havre99themerivertm.html ThemeRiver] Technik für diesen Zweck sehr gut geeignet sein, da man hier neben der Entwicklung über die Zeit auch die Verhältnismäßigkeiten zwischen den Kategorien gut verfolgen kann.
**Vertikaler Text ist schwer lesbar. Desweiteren erfolgt die die y-Achsenbeschriftung von unten nach oben und die Beschriftung der Balken von oben nach unten. Besser wäre eine horizontale Anzeige der Prozentwerte oder noch besser die Wahl einer Darstellung aus der man auch die Verhältnisse innerhalb eines Jahres ablesen kann (ohne textuell Prozentwerte angeben zu müssen).
**Die Umrandung der Balken erniedrigt den "Data-Ink Ratio" und sollte entfallen.
**Was man weiters aus eurer Grafik nicht ablesen kann, ist die Entwicklung der Autoproduktion weltweit (also die Summe aller Länder) - Ist sie gestiegen, gesunken, gleich geblieben?

Ihr habt die Möglichkeit, eure Ausarbeitung bis 16.11.2005 zu überarbeiten, um die derzeitigen Unzulänglichkeiten auszubessern. Wird das gemacht, so werden die Punkte danach klarerweise aufgewertet.

-- [[User:Iwolf|Wolfgang Aigner]] 18:56, 5 November 2005 (CET)

'' Diskussionsbeitrag Themeriver ''

[[Image:world_car_production_themeriver.jpg]]

oder: Thanx to [http://www.inkscape.org inkscape]....

Hallo Leute! Ist das eine Richtung, in die man weiter gehen kann?
--[[User:UE-InfoVis0506 9426777|UE-InfoVis0506 9426777]] 11:41, 8 November 2005 (CET)

Neue Version geuploadet.

Comments?

Wie sieht das aus mit den Werten, die in der Grafik stehen? Weglassen? Durch Prozentzahlen ersetzen/erweitern?
--[[User:UE-InfoVis0506 9426777|UE-InfoVis0506 9426777]] 11:51, 9 November 2005 (CET)

Und noch etwas:

[[Image:Infovis_worldwide_car_production2.png]]

kommt ohne vertikalen Linien aus. Besser oder schlechter?

--[[User:UE-InfoVis0506 9426777|UE-InfoVis0506 9426777]] 10:56, 14 November 2005 (CET)

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

2005-11-14T09:55:35Z

UE-InfoVis0506 9426777: change to ThemeRiver

== 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.
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

File:Infovis worldwide car production2.png

2005-11-14T09:46:15Z

UE-InfoVis0506 9426777: Worldwide Car Production 1977-80. ThemeRiver without vertical dotted lines.

== Summary ==
Worldwide Car Production 1977-80.
ThemeRiver without vertical dotted lines.
== Copyright status ==

== Source ==
created by uploader

File:Infovis worldwide car production.png

2005-11-14T09:45:28Z

UE-InfoVis0506 9426777: Worldwide Car Production 1977-80. ThemeRiver with vertical dotted lines.

== Summary ==
Worldwide Car Production 1977-80.
ThemeRiver with vertical dotted lines.
== Copyright status ==

== Source ==
created by uploader

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

2005-11-09T10:51:39Z

UE-InfoVis0506 9426777: Inkscape-Version

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

2005-11-08T10:41:26Z

UE-InfoVis0506 9426777:

== Bewertung ==
'''Punkte: 12'''

'''Begründung:'''
*Analyse OK
*Die Erklärung der Verbesserungen ist relativ kurz ausgefallen
*Die verbesserte Grafik ist selber noch verbesserungswürdig:
**Grundsätzlich ist die Wahl eines Balkendiagramm zur Darstellung dieser Daten NICHT ideal. Wichtig ist hier vor allem, wie die Werte sich über die Zeit entwickelt haben. Für diesen Zweck wäre ein Liniendiagramm wesentlich besser geeignet.
**Meiner Meinung nach würde die [http://citeseer.ist.psu.edu/havre99themerivertm.html ThemeRiver] Technik für diesen Zweck sehr gut geeignet sein, da man hier neben der Entwicklung über die Zeit auch die Verhältnismäßigkeiten zwischen den Kategorien gut verfolgen kann.
**Vertikaler Text ist schwer lesbar. Desweiteren erfolgt die die y-Achsenbeschriftung von unten nach oben und die Beschriftung der Balken von oben nach unten. Besser wäre eine horizontale Anzeige der Prozentwerte oder noch besser die Wahl einer Darstellung aus der man auch die Verhältnisse innerhalb eines Jahres ablesen kann (ohne textuell Prozentwerte angeben zu müssen).
**Die Umrandung der Balken erniedrigt den "Data-Ink Ratio" und sollte entfallen.
**Was man weiters aus eurer Grafik nicht ablesen kann, ist die Entwicklung der Autoproduktion weltweit (also die Summe aller Länder) - Ist sie gestiegen, gesunken, gleich geblieben?

Ihr habt die Möglichkeit, eure Ausarbeitung bis 16.11.2005 zu überarbeiten, um die derzeitigen Unzulänglichkeiten auszubessern. Wird das gemacht, so werden die Punkte danach klarerweise aufgewertet.

-- [[User:Iwolf|Wolfgang Aigner]] 18:56, 5 November 2005 (CET)

'' Diskussionsbeitrag Themeriver ''

[[Image:world_car_production_themeriver.jpg]]

oder: Wie zwinge ich Excel dazu, den River fließen zu lassen....

Hallo Leute! Ist das eine Richtung, in die man weiter gehen kann?
--[[User:UE-InfoVis0506 9426777|UE-InfoVis0506 9426777]] 11:41, 8 November 2005 (CET)

File:World car production themeriver.jpg

2005-11-08T10:37:04Z

UE-InfoVis0506 9426777: Diskussionsbeitrag Themeriver Worldwide car production 1977-1980

== Summary ==
Diskussionsbeitrag Themeriver
Worldwide car production 1977-1980
== Copyright status ==

== Source ==
created by uploader

File:Worldcarprod.jpg

2005-11-03T15:40:00Z

UE-InfoVis0506 9426777: /* Source */

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

== Source ==
created by uploader

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

2005-11-03T13:38:25Z

UE-InfoVis0506 9426777:

== Bewertung ==
'''Punkte: 18'''

'''Begründung:'''
*Formatierung für Literaturverweise nicht eingehalten
*Formatierung für Literaturangaben fehlerhaft
*Zitate nicht richtig formatiert / Formatierungstemplates nicht verwendet
*Formatierung der Quellenangaben bei Bildern fehlerhaft
*Ausarbeitung der Gestalt Laws sehr gut

Ihr habt die Möglichkeit, eure Ausarbeitung bis 3.11.2005 zu überarbeiten, um die derzeitigen Unzulänglichkeiten auszubessern. Wird das gemacht, so werden die Punkte danach klarerweise aufgewertet.

-- [[User:Iwolf|Wolfgang Aigner]] 18:00, 26 October 2005 (CEST)

Ich hoffe, wir haben jetzt die Fehler gefunden. Ist das Quotation-Template in "Gestalt Laws" richtig verwendet? (Bzw. war das mit "Zitate nicht richtig formatiert / Formatierungstemplates nicht verwendet" gemeint?)

--[[User:UE-InfoVis0506 9426777|UE-InfoVis0506 9426777]] 14:38, 3 November 2005 (CET)

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Relative Size

2005-11-03T13:35:25Z

UE-InfoVis0506 9426777: Copied links from discussion page

__TOC__
== Relative Size (Smaller components tend to be perceived as objects.) ==
the term "relative size" is used in the context of the [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Gestalt Laws| Gestalt Laws]] of grouping, and describes how we perceive figures of different sizes.

{{Definition|The smaller components of a figure or pattern tend to be perceived as objects while the biggest are perceived as background [Dürsteler, 2000]}}

==Examples==
[[Image:relsize.gif]]
The star on the left looks like it was placed on a circular background.

In some publications the same effect is called "smallness" [Chandler, 1997], because the visual focus lies on the smaller object.

=="relative size" in other contexts==

In visual design, the term "relative size" is also used in the following contexts:

''' next to '''

If two objects placed next to each other do not share the same size, the bigger object is perceived as being the one more important.

When these objects change size relative to each other, this gives the impression of changed importance.

[[Image:Infovis_relsize_next.png]]

Other trivial examples for static relative sizes are of course the headlines and titles in contrast to normal text on this page.

''' perspective '''

A smaller object with the same outline is seen as being farther away than the first one.

[[Image:Infovis_relsize_perspective.png]]

==Resources==

[Dürsteler, 2000] Juan C. Dürsteler, [http://www.infovis.net/printMag.php?num=19&lang=2 Gestalt and Visual Momentum]. Created at 2000-11-27, Retrieved at Oct 25, 2005. http://www.infovis.net/printMag.php?num=19&lang=2

this article is based on

[Ware, 1999] Colin Ware. Information Visualization: Perception for Design. Morgan Kaufmann series in interactive technologies, 1999

[Chandler, 1997] Daniel Chandler, [http://www.aber.ac.uk/media/Modules/MC10220/visper06.html Visual Perception 6], ''University of Texas at Austin'', Retrieved at Oct 25, 2005. http://www.aber.ac.uk/media/Modules/MC10220/visper06.html

'''Further readings'''

*[Chandler, 1997] Daniel Chandler, [http://www.aber.ac.uk/media/Modules/MC10220/visper02.html Visual Perception 2], ''University of Texas at Austin'', Retrieved at October 25, 2005 http://www.aber.ac.uk/media/Modules/MC10220/visper02.html

*[Chi, 2000] Ed H. Chi, [http://www-users.cs.umn.edu/~echi/tutorial/perception2000/2000-05-EdChi-VisualPatterns-CHI2000-notes.pdf Representing Data using Static and moving patterns], ''Xerox Parc'', 2000, Retrieved at October 25, 2005. http://www-users.cs.umn.edu/~echi/tutorial/perception2000/2000-05-EdChi-VisualPatterns-CHI2000-notes.pdf

*[Boeree, 2002] George Boeree, [http://www.ship.edu/~cgboeree/genpsyperception.html Perception and interaction], ''Shippensburg University'', 2002, Retrieved at: October 25, 2005. http://www.ship.edu/~cgboeree/genpsyperception.html

*[Allen, 2005] Chuck Allen, [http://www.csusm.edu/iits/trc/training/lessons/graphicDesign/d2Perception/2_design_perception.htm Visual Perception - Graphic Design Concepts], ''Technology Resource Center'', Cal State San Marcos, Last revised at: March 1, 2005, Retrieved at: November 3, 2005. http://www.csusm.edu/iits/trc/training/lessons/graphicDesign/d2Perception/2_design_perception.htm

*[Winkler, 2005] Compiled by Ramona Winkler, edited by Gerd Waloszek, [http://www.sapdesignguild.org/resources/optical_illusions/optical_illusions.pdf Optical Illusions], ''SAP Design Guild''. Retrieved at: November 3, 2005. http://www.sapdesignguild.org/resources/optical_illusions/optical_illusions.pdf

*[Headscape, 2005] Headcape Ltd, [http://www.headscape.co.uk/view_article.asp?PageId=5&ArticleId=54 Usability vs Graphic Design ], ''Headscape Ltd.'', Salisbury. Retrieved at: November 3, 2005. http://www.headscape.co.uk/view_article.asp?PageId=5&ArticleId=54

*[Starphoto, 2005] Ron Johnson (Curator), [http://www.startphoto.com/learn/art/principles_of_design.htm Principles of design ], ''Starphoto - online photographic art community''. Retrieved at: November 3, 2005. http://www.startphoto.com/learn/art/principles_of_design.htm

*[Unknown] Unknown Author [http://www.uark.edu/misc/lampinen/PSYC2003_PERCEPTION.html Perception], ''University of Arkansas'' Retrieved at: November 3, 2005. http://www.uark.edu/misc/lampinen/PSYC2003_PERCEPTION.html

File:Pragnanz.gif

2005-11-03T13:30:56Z

UE-InfoVis0506 9426777: /* Source */

== Summary ==

== Copyright status ==

== Source ==
[Wiley, 2001] Jennifer Wiley [http://www.uic.edu/classes/psych/psych352jw/c4.html Cognition and Memory, Course 2001 Web Page], University of Illinois at Chicago, Spring 2001, Retrieved at October 20, 2005. http://www.uic.edu/classes/psych/psych352jw/c4.html

File:Symmetry.gif

2005-11-03T13:28:15Z

UE-InfoVis0506 9426777: /* Source */

== Summary ==

== Copyright status ==

== Source ==
[Chandler, 1997] Daniel Chandler, [http://www.aber.ac.uk/media/Modules/MC10220/visper06.html Visual Perception 6], ''University of Texas at Austin'', Retrieved at October 20, 2005. http://www.aber.ac.uk/media/Modules/MC10220/visper06.html

File:Past2.gif

2005-11-03T13:27:40Z

UE-InfoVis0506 9426777: /* Source */

== Summary ==

== Copyright status ==

== Source ==
[Schmidt, 2005] Charles F. Schmidt, [http://www.rci.rutgers.edu/~cfs/305_html/Gestalt/wertheimer2.html On Perceptual Grouping]. Retrieved at: October 20, 2005. http://www.rci.rutgers.edu/~cfs/305_html/Gestalt/wertheimer2.html

File:Past3.gif

2005-11-03T13:27:29Z

UE-InfoVis0506 9426777: /* Source */

File:Past.gif

2005-11-03T13:27:19Z

UE-InfoVis0506 9426777: /* Source */

File:Figureground.gif

2005-11-03T13:05:43Z

UE-InfoVis0506 9426777: /* Source */

== Summary ==

== Copyright status ==

== Source ==
[Boeree, 2000] George Boeree, [http://www.ship.edu/~cgboeree/gestalt.html Gestalt Psychology], ''Shippensburg University'', 2002, Retrieved at: October 20, 2005. http://www.ship.edu/~cgboeree/gestalt.html

File:Common.gif

2005-11-03T13:04:28Z

UE-InfoVis0506 9426777: /* Source */

== Summary ==

== Copyright status ==

== Source ==
[Pedroza, 2005] Carlos Pedroza, [http://coe.sdsu.edu/eet/articles/visualperc1/start.htm Visual Perception: Gestalt Laws], College of Education, San Diego State University. Retrieved at: October 20, 2005. http://coe.sdsu.edu/eet/articles/visualperc1/start.htm

File:Continuation.gif

2005-11-03T13:02:22Z

UE-InfoVis0506 9426777: /* Source */

== Summary ==

== Copyright status ==

== Source ==
[Winkler, 2005] Compiled by Ramona Winkler, edited by Gerd Waloszek, [http://www.sapdesignguild.org/resources/optical_illusions/gestalt_laws.html Optical Illusions], SAP Design Guild. Retrieved at: October 20, 2005. http://www.sapdesignguild.org/resources/optical_illusions/gestalt_laws.html

File:Closure.gif

2005-11-03T13:02:13Z

UE-InfoVis0506 9426777: /* Source */

File:Similarity.gif

2005-11-03T13:02:04Z

UE-InfoVis0506 9426777: /* Source */

File:Proximity.gif

2005-11-03T13:01:47Z

UE-InfoVis0506 9426777: /* Source */

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

2005-11-03T12:52:13Z

UE-InfoVis0506 9426777: Typos

== 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: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 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.
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 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

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Relative Size

2005-11-03T12:45:05Z

UE-InfoVis0506 9426777: References reformated

Teaching talk:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Relative Size

2005-11-03T12:39:12Z

UE-InfoVis0506 9426777: Referenzen erweitert

wie könnten wir diese links als Referenzen angeben?

'''''Suche nach Autor, Seitentitel, woher die Seite kommt, ... (Angaben laut: [[Help:Citation_%26_Bibilography_Format#Web_Resources]]).'''''

http://www.csusm.edu/iits/trc/training/lessons/graphicDesign/d2Perception/2_design_perception.htm

'''''zum Beispiel:'''''
*[Allen, 2005] Chuck Allen, [http://www.csusm.edu/iits/trc/training/lessons/graphicDesign/d2Perception/2_design_perception.htm Visual Perception - Graphic Design Concepts], ''Technology Resource Center'', Cal State San Marcos, Last revised at: March 1, 2005, Retrieved at: November 3, 2005. http://www.csusm.edu/iits/trc/training/lessons/graphicDesign/d2Perception/2_design_perception.htm

*[Winkler, 2005] Compiled by Ramona Winkler, edited by Gerd Waloszek, [http://www.sapdesignguild.org/resources/optical_illusions/optical_illusions.pdf Optical Illusions], ''SAP Design Guild''. Retrieved at: November 3, 2005. http://www.sapdesignguild.org/resources/optical_illusions/optical_illusions.pdf

*[Headscape, 2005] Headcape Ltd, [http://www.headscape.co.uk/view_article.asp?PageId=5&ArticleId=54 Usability vs Graphic Design ], ''Headscape Ltd.'', Salisbury. Retrieved at: November 3, 2005. http://www.headscape.co.uk/view_article.asp?PageId=5&ArticleId=54

*[Starphoto, 2005] Ron Johnson (Curator), [http://www.startphoto.com/learn/art/principles_of_design.htm Principles of design ], ''Starphoto - online photographic art community''. Retrieved at: November 3, 2005. http://www.startphoto.com/learn/art/principles_of_design.htm

*[Unknown] Unknown Author [http://www.uark.edu/misc/lampinen/PSYC2003_PERCEPTION.html Perception], ''University of Arkansas'' Retrieved at: November 3, 2005. http://www.uark.edu/misc/lampinen/PSYC2003_PERCEPTION.html

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Relative Size

2005-10-25T21:39:08Z

UE-InfoVis0506 9426777:

== Relative Size ==
the term "relative size" is used in the context of the [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Gestalt Laws| Gestalt Laws]] of grouping, and describes how we perceive figures of different sizes.

{{Definition|The smaller components of a figure or pattern tend to be perceived as objects while the biggest are perceived as background [Dürsteler, 2000]}}

[[Image:relsize.gif]]
The star on the left looks like it was placed on a circular background.

In some publications the same effect is called "smallness" [Chandler, 1997], because the visual focus lies on the smaller object.

In visual design, the term "relative size" is also used in the following contexts:

''' next to '''

If two objects placed next to each other do not share the same size, the bigger object is perceived as being the one more important.

When these objects change size relative to each other, this gives the impression of changed importance.

[[Image:Infovis_relsize_next.png]]

Other trivial examples for static relative sizes are of course the headlines and titles in contrast to normal text on this page.

''' perspective '''

A smaller object with the same outline is seen as being farther away than the first one.

[[Image:Infovis_relsize_perspective.png]]

''' Sources '''

[Dürsteler, 2000] Juan C. Dürsteler, Gestalt and Visual Momentum. Created at 2000-11-27
http://www.infovis.net/printMag.php?num=19&lang=2

this article is based on

Colin Ware. Information Visualization: Perception for Design. Morgan Kaufmann series in interactive technologies, 1999

[Chandler, 1997] Daniel Chandler, Visual Perception 6, accessed Oct 25, 2005 http://www.aber.ac.uk/media/Modules/MC10220/visper06.html

a few other links:

http://www.startphoto.com/learn/art/principles_of_design.htm

http://www.aber.ac.uk/media/Modules/MC10220/visper02.html

!http://www.uark.edu/misc/lampinen/PSYC2003_PERCEPTION.html

!http://www-users.cs.umn.edu/~echi/tutorial/perception2000/2000-05-EdChi-VisualPatterns-CHI2000-notes.pdf

!http://lifesciassoc.home.pipeline.com/instruct/percept/e_theory.htm

http://www.csusm.edu/iits/trc/training/lessons/graphicDesign/d2Perception/2_design_perception.htm

!http://www.sapdesignguild.org/resources/optical_illusions/optical_illusions.pdf

!http://www.ship.edu/~cgboeree/genpsyperception.html

http://www.headscape.co.uk/view_article.asp?PageId=5&ArticleId=54

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Relative Size

2005-10-25T21:38:39Z

UE-InfoVis0506 9426777:

== Relative Size ==
the term "relative size" is used in the context of the [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Gestalt Laws| Gestalt Laws]] of grouping, and describes how we perceive figures of different sizes.

{{Definition|The smaller components of a figure or pattern tend to be perceived as objects while the biggest are perceived as background [Dürsteler, 2000]}}

[[Image:relsize.gif]]
The star on the left looks like it was placed on a circular background.

In some publications the same effect is called "smallness" [Chandler, 1997], because the visual focus lies on the smaller object.

In visual design, the term "relative size" is also used in the following contexts:

''' next to '''

If two objects placed next to each other do not share the same size, the bigger object is perceived as being the one more important.

When these objects change size relative to each other, this gives the impression of changed importance.

[[Image:Infovis_relsize_next.png]]

Other trivial examples for static relative sizes are of course the headlines and titles in contrast to normal text on this page.

''' perspective '''

A smaller object with the same outline is seen as being farther away than the first one.

[[Image:Infovis_relsize_perspective.png]]

''' Sources '''

[Dürsteler, 2000] Juan C. Dürsteler, Gestalt and Visual Momentum. Created at 2000-11-27
http://www.infovis.net/printMag.php?num=19&lang=2

this article is based on

Colin Ware. Information Visualization: Perception for Design. Morgan Kaufmann series in interactive technologies, 1999

[Chandler, 1997] Daniel Chandler, Visual Perception 6, accessed Oct 25, 2005 http://www.aber.ac.uk/media/Modules/MC10220/visper06.html

http://www.startphoto.com/learn/art/principles_of_design.htm

http://www.aber.ac.uk/media/Modules/MC10220/visper02.html

a few other links:

!http://www.uark.edu/misc/lampinen/PSYC2003_PERCEPTION.html

!http://www-users.cs.umn.edu/~echi/tutorial/perception2000/2000-05-EdChi-VisualPatterns-CHI2000-notes.pdf

!http://lifesciassoc.home.pipeline.com/instruct/percept/e_theory.htm

http://www.csusm.edu/iits/trc/training/lessons/graphicDesign/d2Perception/2_design_perception.htm

!http://www.sapdesignguild.org/resources/optical_illusions/optical_illusions.pdf

!http://www.ship.edu/~cgboeree/genpsyperception.html

http://www.headscape.co.uk/view_article.asp?PageId=5&ArticleId=54

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Relative Size

2005-10-25T17:47:32Z

UE-InfoVis0506 9426777:

== Relative Size ==
the term "relative size" is used in the context of the [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Gestalt Laws| Gestalt Laws]] of grouping, and describes how we perceive figures of different sizes.

{{Definition|The smaller components of a figure or pattern tend to be perceived as objects while the biggest are perceived as background [Dürsteler, 2000]}}

[[Image:relsize.gif]]
The star on the left looks like it was placed on a circular background.

In some publications the same effect is called "smallness" [Chandler, 1997], because the visual focus lies on the smaller object.

In visual design, the term "relative size" is also used in the following contexts:

''' next to '''

If two objects placed next to each other do not share the same size, the bigger object is perceived as being the one more important.

When these objects change size relative to each other, this gives the impression of changed importance.

[[Image:Infovis_relsize_next.png]]

Other trivial examples for static relative sizes are of course the headlines and titles in contrast to normal text on this page.

''' perspective '''

A smaller object with the same outline is seen as being farther away than the first one.

[[Image:Infovis_relsize_perspective.png]]

''' Sources '''

[Dürsteler, 2000] Juan C. Dürsteler, Gestalt and Visual Momentum. Created at 2000-11-27
http://www.infovis.net/printMag.php?num=19&lang=2

this article is based on

Colin Ware. Information Visualization: Perception for Design. Morgan Kaufmann series in interactive technologies, 1999

[Chandler, 1997] Daniel Chandler, Visual Perception 6, accessed Oct 25, 2005 http://www.aber.ac.uk/media/Modules/MC10220/visper06.html

http://www.startphoto.com/learn/art/principles_of_design.htm

http://www.aber.ac.uk/media/Modules/MC10220/visper02.html

!http://www.uark.edu/misc/lampinen/PSYC2003_PERCEPTION.html

!http://www-users.cs.umn.edu/~echi/tutorial/perception2000/2000-05-EdChi-VisualPatterns-CHI2000-notes.pdf
-----------------------------------------------------------
!http://lifesciassoc.home.pipeline.com/instruct/percept/e_theory.htm

http://www.csusm.edu/iits/trc/training/lessons/graphicDesign/d2Perception/2_design_perception.htm

!http://www.sapdesignguild.org/resources/optical_illusions/optical_illusions.pdf

!http://www.ship.edu/~cgboeree/genpsyperception.html

http://www.headscape.co.uk/view_article.asp?PageId=5&ArticleId=54

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Relative Size

2005-10-25T17:44:31Z

UE-InfoVis0506 9426777:

== Relative Size ==
the term "relative size" is used in the context of the [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Gestalt Laws| Gestalt Laws]] of grouping, and describes how we perceive figures of different sizes.

{{Definition|The smaller components of a figure or pattern tend to be perceived as objects while the biggest are perceived as background}} [Dürsteler, 2000]

[[Image:relsize.gif]]
The star on the left looks like it was placed on a circular background.

In some publications the same effect is called "smallness" [Chandler, 1997], because the visual focus lies on the smaller object.

In visual design, the term "relative size" is also used in the following contexts:

''' next to '''

If two objects placed next to each other do not share the same size, the bigger object is perceived as being the one more important.

When these objects change size relative to each other, this gives the impression of changed importance.

[[Image:Infovis_relsize_next.png]]

Other trivial examples for static relative sizes are of course the headlines and titles in contrast to normal text on this page.

''' perspective '''

A smaller object with the same outline is seen as being farther away than the first one.

[[Image:Infovis_relsize_perspective.png]]

''' Sources '''

[Dürsteler, 2000] Juan C. Dürsteler, Gestalt and Visual Momentum. Created at 2000-11-27
http://www.infovis.net/printMag.php?num=19&lang=2

this article is based on

Colin Ware. Information Visualization: Perception for Design. Morgan Kaufmann series in interactive technologies, 1999

[Chandler, 1997] Daniel Chandler, Visual Perception 6, accessed Oct 25, 2005 http://www.aber.ac.uk/media/Modules/MC10220/visper06.html

http://www.startphoto.com/learn/art/principles_of_design.htm

http://www.aber.ac.uk/media/Modules/MC10220/visper02.html

!http://www.uark.edu/misc/lampinen/PSYC2003_PERCEPTION.html

!http://www-users.cs.umn.edu/~echi/tutorial/perception2000/2000-05-EdChi-VisualPatterns-CHI2000-notes.pdf
-----------------------------------------------------------
!http://lifesciassoc.home.pipeline.com/instruct/percept/e_theory.htm

http://www.csusm.edu/iits/trc/training/lessons/graphicDesign/d2Perception/2_design_perception.htm

!http://www.sapdesignguild.org/resources/optical_illusions/optical_illusions.pdf

!http://www.ship.edu/~cgboeree/genpsyperception.html

http://www.headscape.co.uk/view_article.asp?PageId=5&ArticleId=54

File:Infovis relsize perspective.png

2005-10-25T17:44:12Z

UE-InfoVis0506 9426777: Smaller objects seem farther away

== Summary ==
Smaller objects seem farther away
== Copyright status ==
public domain
== Source ==
created by uploader

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Relative Size

2005-10-25T17:37:00Z

UE-InfoVis0506 9426777:

== Relative Size ==
the term "relative size" is used in the context of the [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Gestalt Laws| Gestalt Laws]] of grouping, and describes how we perceive figures of different sizes.

{{Definition|The smaller components of a figure or pattern tend to be perceived as objects while the biggest are perceived as background}} [Dürsteler, 2000]

[[Image:relsize.gif]]
The star on the left looks like it was placed on a circular background.

In some publications the same effect is called "smallness" [Chandler, 1997], because the visual focus lies on the smaller object.

In visual design, the term "relative size" is also used in the following contexts:

''' next to '''

If two objects placed next to each other do not share the same size, the bigger object is perceived as being the one more important.

When these objects change size relative to each other, this gives the impression of changed importance.

[[Image:Infovis_relsize_next.png]]

Other trivial examples for static relative sizes are of course the headlines and titles in contrast to normal text on this page.

''' perspective '''

A smaller object with the same outline is seen as being farther away than the first one.

''' Sources '''

[Dürsteler, 2000] Juan C. Dürsteler, Gestalt and Visual Momentum. Created at 2000-11-27
http://www.infovis.net/printMag.php?num=19&lang=2

this article is based on

Colin Ware. Information Visualization: Perception for Design. Morgan Kaufmann series in interactive technologies, 1999

[Chandler, 1997] Daniel Chandler, Visual Perception 6, accessed Oct 25, 2005 http://www.aber.ac.uk/media/Modules/MC10220/visper06.html

http://www.startphoto.com/learn/art/principles_of_design.htm

http://www.aber.ac.uk/media/Modules/MC10220/visper02.html

!http://www.uark.edu/misc/lampinen/PSYC2003_PERCEPTION.html

!http://www-users.cs.umn.edu/~echi/tutorial/perception2000/2000-05-EdChi-VisualPatterns-CHI2000-notes.pdf
-----------------------------------------------------------
!http://lifesciassoc.home.pipeline.com/instruct/percept/e_theory.htm

http://www.csusm.edu/iits/trc/training/lessons/graphicDesign/d2Perception/2_design_perception.htm

!http://www.sapdesignguild.org/resources/optical_illusions/optical_illusions.pdf

!http://www.ship.edu/~cgboeree/genpsyperception.html

http://www.headscape.co.uk/view_article.asp?PageId=5&ArticleId=54

File:Infovis relsize next.png

2005-10-25T17:36:32Z

UE-InfoVis0506 9426777: Change of relative size -> Change of perceived importance

== Summary ==
Change of relative size -> Change of perceived importance
== Copyright status ==
public domain
== Source ==
Created by uploader

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Relative Size

2005-10-25T17:29:16Z

UE-InfoVis0506 9426777:

== Relative Size ==
the term "relative size" is used in the context of the [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Gestalt Laws| Gestalt Laws]] of grouping, and describes how we perceive figures of different sizes.

{{Definition|The smaller components of a figure or pattern tend to be perceived as objects while the biggest are perceived as background}} [Dürsteler, 2000]

[[Image:relsize.gif]]
The star on the left looks like it was placed on a circular background.

In some publications the same effect is called "smallness" [Chandler, 1997], because the visual focus lies on the smaller object.

In visual design, the term "relative size" is also used in the following contexts:

''' next to '''

If two objects placed next to each other do not share the same size, the bigger object is perceived as being the one more important.

When these objects change size relative to each other, this gives the impression of changed importance.

Other trivial examples for static relative sizes are of course the headlines and titles in contrast to normal text on this page.

''' perspective '''

A smaller object with the same outline is seen as being farther away than the first one.

''' Sources '''

[Dürsteler, 2000] Juan C. Dürsteler, Gestalt and Visual Momentum. Created at 2000-11-27
http://www.infovis.net/printMag.php?num=19&lang=2

this article is based on

Colin Ware. Information Visualization: Perception for Design. Morgan Kaufmann series in interactive technologies, 1999

[Chandler, 1997] Daniel Chandler, Visual Perception 6, accessed Oct 25, 2005 http://www.aber.ac.uk/media/Modules/MC10220/visper06.html

http://www.startphoto.com/learn/art/principles_of_design.htm

http://www.aber.ac.uk/media/Modules/MC10220/visper02.html

!http://www.uark.edu/misc/lampinen/PSYC2003_PERCEPTION.html

!http://www-users.cs.umn.edu/~echi/tutorial/perception2000/2000-05-EdChi-VisualPatterns-CHI2000-notes.pdf
-----------------------------------------------------------
!http://lifesciassoc.home.pipeline.com/instruct/percept/e_theory.htm

http://www.csusm.edu/iits/trc/training/lessons/graphicDesign/d2Perception/2_design_perception.htm

!http://www.sapdesignguild.org/resources/optical_illusions/optical_illusions.pdf

!http://www.ship.edu/~cgboeree/genpsyperception.html

http://www.headscape.co.uk/view_article.asp?PageId=5&ArticleId=54

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Relative Size

2005-10-25T17:04:35Z

UE-InfoVis0506 9426777:

== Relative Size ==
the term "relative size" is used in the context of the [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Gestalt Laws| Gestalt Laws]] of grouping, and describes how we perceive figures of different sizes.

{{Definition|The smaller components of a figure or pattern tend to be perceived as objects while the biggest are perceived as background}} [Dürsteler, 2000]

[[Image:relsize.gif]]

The star on the left looks like it was placed on a circular background.

In visual design, the term "relative size" is also used in the following contexts:

''' next to '''

If two objects placed next to each other do not share the same size, the bigger object is perceived as being the one more important.

When these objects change size relative to each other, this gives the impression of changed importance.

Other trivial examples for static relative sizes are of course the headlines and titles in contrast to normal text on this page.

''' perspective '''

A smaller object with the same outline is seen as being farther away than the first one.

''' Sources '''

[Dürsteler, 2000] Juan C. Dürsteler, Gestalt and Visual Momentum. Created at 2000-11-27
http://www.infovis.net/printMag.php?num=19&lang=2

this article is based on

Colin Ware. Information Visualization: Perception for Design. Morgan Kaufmann series in interactive technologies, 1999

http://www.startphoto.com/learn/art/principles_of_design.htm

http://www.aber.ac.uk/media/Modules/MC10220/visper02.html

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

!http://www.uark.edu/misc/lampinen/PSYC2003_PERCEPTION.html

!http://www-users.cs.umn.edu/~echi/tutorial/perception2000/2000-05-EdChi-VisualPatterns-CHI2000-notes.pdf
-----------------------------------------------------------
!http://lifesciassoc.home.pipeline.com/instruct/percept/e_theory.htm

http://www.csusm.edu/iits/trc/training/lessons/graphicDesign/d2Perception/2_design_perception.htm

!http://www.sapdesignguild.org/resources/optical_illusions/optical_illusions.pdf

!http://www.ship.edu/~cgboeree/genpsyperception.html

http://www.headscape.co.uk/view_article.asp?PageId=5&ArticleId=54

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Relative Size

2005-10-25T08:41:26Z

UE-InfoVis0506 9426777:

== Relative Size ==
the term "relative size" refers to one of the [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Gestalt Laws| Gestalt Laws]] of grouping, and describes how we perceive figures of different sizes.

''' inside '''

A smaller figure which is placed inside a larger one is percieved as being the object, while the larger figure is seen as the background on which the smaller one rests.

[[Image:relsize.gif]]

The star on the left looks like it was placed on a circular background.

''' next to '''

If two objects placed next to each other do not share the same size, the bigger object is perceived as being the one more important.

When these objects change size relative to each other, this gives the impression of changed importance.

Other trivial examples for static relative sizes are of course the headlines and titles in contrast to normal text on this page.

''' perspective '''

A smaller object with the same outline is seen as being farther away than the first one.

''' Sources '''

The smaller components of a figure or pattern tend to be perceived as objects while the biggest are perceived as background

http://www.infovis.net/printMag.php?num=19&lang=2

http://www.startphoto.com/learn/art/principles_of_design.htm

http://www.aber.ac.uk/media/Modules/MC10220/visper02.html

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

!http://www.uark.edu/misc/lampinen/PSYC2003_PERCEPTION.html

!http://www-users.cs.umn.edu/~echi/tutorial/perception2000/2000-05-EdChi-VisualPatterns-CHI2000-notes.pdf
-----------------------------------------------------------
!http://lifesciassoc.home.pipeline.com/instruct/percept/e_theory.htm

http://www.csusm.edu/iits/trc/training/lessons/graphicDesign/d2Perception/2_design_perception.htm

!http://www.sapdesignguild.org/resources/optical_illusions/optical_illusions.pdf

!http://www.ship.edu/~cgboeree/genpsyperception.html

http://www.headscape.co.uk/view_article.asp?PageId=5&ArticleId=54

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Relative Size

2005-10-24T15:00:42Z

UE-InfoVis0506 9426777:

== Relative Size ==

''' Sources '''

The smaller components of a figure or pattern tend to be perceived as objects while the biggest are perceived as background

http://www.infovis.net/printMag.php?num=19&lang=2

http://www.headscape.co.uk/view_article.asp?PageId=5&ArticleId=54

http://www.startphoto.com/learn/art/principles_of_design.htm

http://www.aber.ac.uk/media/Modules/MC10220/visper02.html

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

http://www.csusm.edu/iits/trc/training/lessons/graphicDesign/d2Perception/2_design_perception.htm

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Relative Size

2005-10-24T14:56:24Z

UE-InfoVis0506 9426777: /* Relative Size */

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1 - Relative Size

2005-10-24T14:43:47Z

UE-InfoVis0506 9426777:

User:UE-InfoVis0506 9426777

2005-10-16T14:54:26Z

UE-InfoVis0506 9426777:

== Whoami ==
Lehrer, Thomas

9426777

881

thomas at lehrer.cc

[[Teaching:TUW_-_UE_InfoVis_WS_2005/06_-Gruppe_G7|Gruppe 7]]

== irrelevant data ==

[http://www.lehrer.cc Meine Homepage]

User:UE-InfoVis0506 9426777

2005-10-16T14:49:47Z

UE-InfoVis0506 9426777:

== Whoami ==
Lehrer, Thomas

9426777

881

thomas at lehrer.cc

== irrelevant data ==

[http://www.lehrer.cc Meine Homepage]