https://infovis-wiki.net/w/api.php?action=feedcontributions&feedformat=atom&user=UE-InfoVis0910+0126013 2026-05-31T13:30:36Z User contributions MediaWiki 1.45.3 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2009/10_-_Gruppe_08_-_Aufgabe_4&diff=24136 2010-01-27T22:58:19Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Aufgabenstellung ==<br /> [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]<br /> === Zu erstellende Visualisierung ===<br /> -------------------------------<br /> * Stammbaum der Nachkommen von Lisa und Bart Simpson*<br /> <br /> ...Visualisierung der Nachkommen von Lisa Simpson sowie der Nachkommen von Bart Simpson. Dabei sollen zwei Stammbäume entstehen - einer von Bart und einer von Lisa - die dann miteinander verglichen werden können. Zuerst kommen Lisa und Bart, dann deren Kinder, ihre Enkel, etc. (mind 4 Generationen). Da es noch keine Nachkommen gibt, können diese frei erfunden werden.<br /> <br /> Die Visualisierung soll folgende Informationen darstellen:<br /> <br /> - Verwandtschaftsverhältnisse (zumindest Eltern-Kinder),<br /> <br /> - Unterscheidung zwischen Blutsverwandtschaft und angeheirateten Familienmitgliedern,<br /> <br /> - Geburts- und Todestag sowie Lebensdauer von allen Familienmitgliedern,<br /> <br /> - wichtige Ereignisse im Leben jedes Familienmitglieds (z.B., Anzeigen, Gefängnisaufenthalte, Schulzeit, Studienzeit, Nobelpreise, Arbeitslosigkeit etc.)<br /> <br /> - Zufriedenheit jedes Familienmitglieds (Skala: sehr niedrig - niedrig - mittel - hoch - sehr hoch); kann sich im Laufe des Lebens ändern.<br /> <br /> Die Visualisierung soll die interaktive Auseinandersetzung mit den Daten ermöglichen.<br /> Verpflichtend:<br /> Möglichkeiten zum besseren Vergleich von einzelnen Abschnitten der Stammbäume bzw. Vergleich von Ausschnitten aus Lisas und Barts Stammbäumen.<br /> + mind. 2 weitere Interaktionsmöglichkeiten (z.B., Details on Demand, Filteroptionen)<br /> <br /> Allgemein:<br /> <br /> - Die Daten sollen zur Analyse von Zusammenhängen zwischen Familienverhältnissen, wichtigen Ereignissen und Zufriedenheit visualisiert werden (die Anwendungsgebiets- und Zielgruppenanalyse kann kurz gehalten werden).<br /> <br /> - Die bisher erlernten Design-Prinzipien sollen umgesetzt werden z.B.: Optimierung der Data-ink ratio (keine Comics!), visuelle Attribute (Größe, Farbe, Position, etc.) sollen sinnvoll eingesetzt werden (Information darstellen).<br /> <br /> - Die Mockups sollten zumindest 1) die beiden Stammbäume im Überblick und 2) eine detaillierte Vergleichsansicht von 2 Teil-Stammbäumen wiedergeben.<br /> <br /> - Alle nicht angeführten Daten können frei erfunden werden.<br /> <br /> ------------------------------<br /> <br /> == Links ==<br /> <br /> * [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]<br /> <br /> * [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]<br /> <br /> *[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08|Gruppe 08]]<br /> <br /> ==Point A: Description of application area, data, target group and tasks==<br /> <br /> ===Application area and data===<br /> A family tree is a chart representing family relationships in a conventional tree structure. The tree shows the parents-children connection. The tree should show detail information of a person as well as important events and emotions (happiness). The family tree should visualize hierarchical structures. In our case we will add some additional information as hereditary diseases.<br /> <br /> ===Target group===<br /> The target audience of this visualization would be:<br /> <br /> - family members of the Simpsons<br /> <br /> - characters of the Simpsons-Universe<br /> <br /> - cast and crew of 'The Simpsons'-Television-Show<br /> <br /> No, seriously:<br /> <br /> - just folks who are interested - the family tree data is fictional anyway. Laymen, no prior knowledge needed.<br /> <br /> Target group for family trees are usually people, who would like to know more about specified family relationships. It serves as well for next family generations who would like to know more about their family members. The family tree is also very useful for medical matter because hereditary diseases are shown (epilepsy).In our case the target group is each person who would like to know more about The Simpsons characters.<br /> <br /> ===Goals===<br /> - The tree should be made very simple so everybody could be able to read the most important information about each person listed on the tree.<br /> <br /> - For the visualization of the data we will use miscellaneous visual attributes and high data-per-ink ratio. The goal is to keep the reader focused on the important information and give him maximum information about the persons and their relationships among each other on the tree. <br /> <br /> ==Point B: Concept==<br /> <br /> [[ Image:Gesamt2.jpg|Figure 1]]<br /> <br /> <br /> [[ Image:Vergleich2.jpg|frame|Figure 2]]<br /> <br /> <br /> <br /> <br /> ===Type of Visualization===<br /> The family tree is visualized by the use of a hierarchical graph - in our case not to be mistaken for a tree since we have more than one higher-ranking node (= two parents) for each node.<br /> <br /> We wanted the root (Lisa and Bart) at the top of the visualisation to highlight that everything else (the offspring) follows unidirectional (-- in reality: time, in our visualisation: vertical axis).<br /> <br /> ===Visual mapping / Visual Attributes===<br /> <br /> ====Blood relationship -&gt; Annulus (around portrait)====<br /> Blue Annulus = existence of blood relationship<br /> <br /> Red Annulus = no existence of blood relationship<br /> <br /> ''Explanatory statement:'' Since the blood relationship to Lisa and Bart is a key information we decided to choose an Annulus around the portraits. In that manner it is fast to extract this particular information for the viewer.<br /> <br /> ====Marriage -&gt; dual wedding ring symbol (between two parents of a child)====<br /> dual wedding ring symbol = the parents are/were married with each other.<br /> <br /> ''Explanatory statement:''In many cultures two interlooped wedding rings are a symbol for marriage. &lt;ref name=&quot;ring&quot;&gt;Wikipedia.de: Ring(Schmuck). Retrieved at: 2010. [http://de.wikipedia.org/wiki/Ring_(Schmuck)#Ehering]&lt;/ref&gt;<br /> <br /> <br /> ====Relationship -&gt; Black persistent lines====<br /> Horizontal black persistent lines between persons indicate relationship based on partnership.<br /> <br /> Vertical black persistent lines between persons indicate relationship between parents and their child/children.<br /> <br /> <br /> ====Relationship -&gt; Black dashed lines====<br /> Horizontal black dashed lines in Comparison Mode indicate not shown siblings (due to eg. zoom level).<br /> <br /> Vertical black dashed lines in Comparison Mode indicate indirect parent-child-relationship - meaning one or more generations inbetween the dashed lines are left out.<br /> <br /> <br /> ===Interaction===<br /> <br /> ====Navigation====<br /> Navigation takes place via mouse controls. A modifier key on the keyboard is also used ('Control'-key). The program starts in the Overview mode showing the whole family tree.<br /> <br /> Mouse-hovering over a person brings up a popup window revealing all kinds of person-related information (name, gender, birth date, profession, events, satisfaction graph). Selecting an event item in this popup-window causes highlighting the corresponding time-section in the satisfaction graph.<br /> <br /> Selecting more than one person via 'Control'+Left-Mouse-Button-clicking several persons or drawing a selection frame around several persons (- via holding Left-Mouse-Button and moving the Mouse). Via 'Enter'-key on the keyboard the selected persons are shown in the Comparison Mode - non-selected persons are left out by dashed black lines (- see text on Visual Mapping).<br /> <br /> ====Zooming and Panning====<br /> In the Comparison Mode the program allows for each split side (left and right) a separately adjustable zoom level and area by panning. A change of the zoom level is accomplished by the use of holding the 'Control'-key on the keyboard and turning the mouse wheel. Panning is accomplished by holding the left mouse button and moving the mouse in direction of desire.<br /> <br /> ====Split Screen Mode====<br /> The Comparison Mode splits the window into two separate sub-windows to allow for separately adjusting (by zooming and panning) the region of interest for each side (= lisa as well as bart) of the family tree.<br /> <br /> Note that without any character selected, the family relationships is not shown.<br /> In that case, moving with the mouse over a character causes the system to show the relationships relative to this character (e.g. Alberta Simpson is labeled as Pamelas daughter when the user moves the mouse over Pamelas picture, as shown in Figure 2).<br /> <br /> ====Dynamic Queries====<br /> There are several search queries the user can choose from - they are accessible in the Comparison Mode.<br /> <br /> One filter in the comparison mode allows the user for filtering with the help of regular expressions - this searches for matching strings in all data fields in the family tree and highlights the corresponding persons.<br /> <br /> More filters:<br /> <br /> - filter by gender<br /> <br /> - filter by Blood relationship (- blood related? Yes/ No.)<br /> <br /> - filter by time range (- see section 'Range Slider' below)<br /> <br /> ====Range Slider====<br /> The user can choose an arbitrary range of time to show the family tree only in the corresponding range.<br /> <br /> ====Details on Demand====<br /> On user demand the information of a person in the family tree is shown in a separate popup window. This window is divided into three different parts. One third shows the name, gender, date of birth and profession. The second one shows all mentionable events in the lifetime of the person - the last third of the window visualizes the 'satisfaction-over-time'-graph.<br /> <br /> As you can see, the 'satisfaction-over-time'-graph also includes various icone, representing the previous mentioned events. When the user moves the mouse over these icons, additional informations is shown.<br /> The system should include a set of predefined icons (e.g., school, career, prison) as well as a symbol for other events (e.g. internship in our graphic). If the user is not familiar with these icons and needs help, it is possible to display a legend via the help-symbol (?).<br /> <br /> ====Focus and Context====<br /> Usage of the Dynamic Queries causes the program to focus on the matching search results. The search results are visualized by adding a mask layer on top of the family tree, allowing only for the resulting persons to be shown clearly through the mask layer - the non-matching persons are overlaid by the dark but opaque layer.<br /> <br /> ===How are the users supported in their tasks?===<br /> A top priority for the team was to create a great experience for the user by making the controls as intuitive and easy to use as possible. Many of the Navigation Methods (left-clicking / zooming and panning) are commonly known from surfing the internet. Moreover an extensive help documentation is supplied with the family tree software package. <br /> <br /> ===What special features are there?===<br /> Dynamic query search with regular expression engine, range slider for time filtering, intuitive easy-to-use-interface, clear design (with priority on data-ink-ratio)<br /> <br /> ==References==<br /> <br /> &lt;references /&gt;<br /> <br /> <br /> -[Ball, 2004]: Robert Ball, Details on Demand vs. High Resolution, 2004.<br /> <br /> -[Shneiderman, 1996] Ben Shneiderman, 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, 1996.<br /> <br /> -[Card et al, 1999] Card, S.K., Mackinlay, J.D., and Shneiderman, B. (Eds.) Readings in Information Visualization: Using Vision to Think, pp. 1-34, Morgan Kaufmann Publishers, San Francisco, Califomia, 1999.</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2009/10_-_Gruppe_08_-_Aufgabe_4&diff=24131 2010-01-27T22:26:13Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Aufgabenstellung ==<br /> [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]<br /> === Zu erstellende Visualisierung ===<br /> -------------------------------<br /> * Stammbaum der Nachkommen von Lisa und Bart Simpson*<br /> <br /> ...Visualisierung der Nachkommen von Lisa Simpson sowie der Nachkommen von Bart Simpson. Dabei sollen zwei Stammbäume entstehen - einer von Bart und einer von Lisa - die dann miteinander verglichen werden können. Zuerst kommen Lisa und Bart, dann deren Kinder, ihre Enkel, etc. (mind 4 Generationen). Da es noch keine Nachkommen gibt, können diese frei erfunden werden.<br /> <br /> Die Visualisierung soll folgende Informationen darstellen:<br /> <br /> - Verwandtschaftsverhältnisse (zumindest Eltern-Kinder),<br /> <br /> - Unterscheidung zwischen Blutsverwandtschaft und angeheirateten Familienmitgliedern,<br /> <br /> - Geburts- und Todestag sowie Lebensdauer von allen Familienmitgliedern,<br /> <br /> - wichtige Ereignisse im Leben jedes Familienmitglieds (z.B., Anzeigen, Gefängnisaufenthalte, Schulzeit, Studienzeit, Nobelpreise, Arbeitslosigkeit etc.)<br /> <br /> - Zufriedenheit jedes Familienmitglieds (Skala: sehr niedrig - niedrig - mittel - hoch - sehr hoch); kann sich im Laufe des Lebens ändern.<br /> <br /> Die Visualisierung soll die interaktive Auseinandersetzung mit den Daten ermöglichen.<br /> Verpflichtend:<br /> Möglichkeiten zum besseren Vergleich von einzelnen Abschnitten der Stammbäume bzw. Vergleich von Ausschnitten aus Lisas und Barts Stammbäumen.<br /> + mind. 2 weitere Interaktionsmöglichkeiten (z.B., Details on Demand, Filteroptionen)<br /> <br /> Allgemein:<br /> <br /> - Die Daten sollen zur Analyse von Zusammenhängen zwischen Familienverhältnissen, wichtigen Ereignissen und Zufriedenheit visualisiert werden (die Anwendungsgebiets- und Zielgruppenanalyse kann kurz gehalten werden).<br /> <br /> - Die bisher erlernten Design-Prinzipien sollen umgesetzt werden z.B.: Optimierung der Data-ink ratio (keine Comics!), visuelle Attribute (Größe, Farbe, Position, etc.) sollen sinnvoll eingesetzt werden (Information darstellen).<br /> <br /> - Die Mockups sollten zumindest 1) die beiden Stammbäume im Überblick und 2) eine detaillierte Vergleichsansicht von 2 Teil-Stammbäumen wiedergeben.<br /> <br /> - Alle nicht angeführten Daten können frei erfunden werden.<br /> <br /> ------------------------------<br /> <br /> == Links ==<br /> <br /> * [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]<br /> <br /> * [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]<br /> <br /> *[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08|Gruppe 08]]<br /> <br /> ==Point A: Description of application area, data, target group and tasks==<br /> <br /> ===Application area and data===<br /> A family tree is a chart representing family relationships in a conventional tree structure. The tree shows the parents-children connection. The tree should show detail information of a person as well as important events and emotions (happiness). The family tree should visualize hierarchical structures. In our case we will add some additional information as hereditary diseases.<br /> <br /> ===Target group===<br /> The target audience of this visualization would be:<br /> <br /> - family members of the Simpsons<br /> <br /> - characters of the Simpsons-Universe<br /> <br /> - cast and crew of 'The Simpsons'-Television-Show<br /> <br /> No, seriously:<br /> <br /> - just folks who are interested - the family tree data is fictional anyway. Laymen, no prior knowledge needed.<br /> <br /> Target group for family trees are usually people, who would like to know more about specified family relationships. It serves as well for next family generations who would like to know more about their family members. The family tree is also very useful for medical matter because hereditary diseases are shown (epilepsy).In our case the target group is each person who would like to know more about The Simpsons characters.<br /> <br /> ===Goals===<br /> - The tree should be made very simple so everybody could be able to read the most important information about each person listed on the tree.<br /> <br /> - For the visualization of the data we will use miscellaneous visual attributes and high data-per-ink ratio. The goal is to keep the reader focused on the important information and give him maximum information about the persons and their relationships among each other on the tree. <br /> <br /> ==Point B: Concept==<br /> <br /> [[ Image:Gesamt2.jpg|Figure 1]]<br /> <br /> [[ Image:StammBaum.jpg|1000px|Figure 1]]<br /> <br /> [[ Image:Vergleich2.jpg|frame|Figure 2]]<br /> <br /> [[ Image:BaumVergleich.jpg|1000px|Figure 2]]<br /> <br /> <br /> ===Type of Visualization===<br /> The family tree is visualized by the use of a hierarchical graph - in our case not to be mistaken for a tree since we have more than one higher-ranking node (= two parents) for each node.<br /> <br /> We wanted the root (Lisa and Bart) at the top of the visualisation to highlight that everything else (the offspring) follows unidirectional (-- in reality: time, in our visualisation: vertical axis).<br /> <br /> ===Visual mapping / Visual Attributes===<br /> <br /> ====Blood relationship -&gt; Annulus (around portrait)====<br /> Blue Annulus = existence of blood relationship<br /> <br /> Red Annulus = no existence of blood relationship<br /> <br /> ''Explanatory statement:'' Since the blood relationship to Lisa and Bart is a key information we decided to choose an Annulus around the portraits. In that manner it is fast to extract this particular information for the viewer.<br /> <br /> ====Marriage -&gt; dual wedding ring symbol (between two parents of a child)====<br /> dual wedding ring symbol = the parents are/were married with each other.<br /> <br /> ''Explanatory statement:''In many cultures two interlooped wedding rings are a symbol for marriage. &lt;ref name=&quot;ring&quot;&gt;Wikipedia.de: Ring(Schmuck). Retrieved at: 2010. [http://de.wikipedia.org/wiki/Ring_(Schmuck)#Ehering]&lt;/ref&gt;<br /> <br /> <br /> ====Relationship -&gt; Black persistent lines====<br /> Horizontal black persistent lines between persons indicate relationship based on partnership.<br /> <br /> Vertical black persistent lines between persons indicate relationship between parents and their child/children.<br /> <br /> <br /> ====Relationship -&gt; Black dashed lines====<br /> Horizontal black dashed lines in Comparison Mode indicate not shown siblings (due to eg. zoom level).<br /> <br /> Vertical black dashed lines in Comparison Mode indicate indirect parent-child-relationship - meaning one or more generations inbetween the dashed lines are left out.<br /> <br /> <br /> ===Interaction===<br /> <br /> ====Navigation====<br /> Navigation takes place via mouse controls. A modifier key on the keyboard is also used ('Control'-key). The program starts in the Overview mode showing the whole family tree.<br /> <br /> Mouse-hovering over a person brings up a popup window revealing all kinds of person-related information (name, gender, birth date, profession, events, satisfaction graph). Selecting an event item in this popup-window causes highlighting the corresponding time-section in the satisfaction graph.<br /> <br /> Selecting more than one person via 'Control'+Left-Mouse-Button-clicking several persons or drawing a selection frame around several persons (- via holding Left-Mouse-Button and moving the Mouse). Via 'Enter'-key on the keyboard the selected persons are shown in the Comparison Mode - non-selected persons are left out by dashed black lines (- see text on Visual Mapping).<br /> <br /> ====Zooming and Panning====<br /> In the Comparison Mode the program allows for each split side (left and right) a separately adjustable zoom level and area by panning. A change of the zoom level is accomplished by the use of holding the 'Control'-key on the keyboard and turning the mouse wheel. Panning is accomplished by holding the left mouse button and moving the mouse in direction of desire.<br /> <br /> ====Split Screen Mode====<br /> The Comparison Mode splits the window into two separate sub-windows to allow for separately adjusting (by zooming and panning) the region of interest for each side (= lisa as well as bart) of the family tree.<br /> <br /> Note that without any character selected, the family relationships is not shown.<br /> In that case, moving with the mouse over a character causes the system to show the relationships relative to this character (e.g. Alberta Simpson is labeled as Pamelas daughter when the user moves the mouse over Pamelas picture, as shown in Figure 2).<br /> <br /> ====Dynamic Queries====<br /> There are several search queries the user can choose from - they are accessible in the Comparison Mode.<br /> <br /> One filter in the comparison mode allows the user for filtering with the help of regular expressions - this searches for matching strings in all data fields in the family tree and highlights the corresponding persons.<br /> <br /> More filters:<br /> <br /> - filter by gender<br /> <br /> - filter by Blood relationship (- blood related? Yes/ No.)<br /> <br /> - filter by time range (- see section 'Range Slider' below)<br /> <br /> ====Range Slider====<br /> The user can choose an arbitrary range of time to show the family tree only in the corresponding range.<br /> <br /> ====Details on Demand====<br /> On user demand the information of a person in the family tree is shown in a separate popup window. This window is divided into three different parts. One third shows the name, gender, date of birth and profession. The second one shows all mentionable events in the lifetime of the person - the last third of the window visualizes the 'satisfaction-over-time'-graph.<br /> <br /> As you can see, the 'satisfaction-over-time'-graph also includes various icone, representing the previous mentioned events. When the user moves the mouse over these icons, additional informations is shown.<br /> The system should include a set of predefined icons (e.g., school, career, prison) as well as a symbol for other events (e.g. internship in our graphic). If the user is not familiar with these icons and needs help, it is possible to display a legend via the help-symbol (?).<br /> <br /> ====Focus and Context====<br /> Usage of the Dynamic Queries causes the program to focus on the matching search results. The search results are visualized by adding a mask layer on top of the family tree, allowing only for the resulting persons to be shown clearly through the mask layer - the non-matching persons are overlaid by the dark but opaque layer.<br /> <br /> ===How are the users supported in their tasks?===<br /> A top priority for the team was to create a great experience for the user by making the controls as intuitive and easy to use as possible. Many of the Navigation Methods (left-clicking / zooming and panning) are commonly known from surfing the internet. Moreover an extensive help documentation is supplied with the family tree software package. <br /> <br /> ===What special features are there?===<br /> Dynamic query search with regular expression engine, range slider for time filtering, intuitive easy-to-use-interface, clear design (with priority on data-ink-ratio)<br /> <br /> ==References==<br /> <br /> &lt;references /&gt;<br /> <br /> <br /> -[Ball, 2004]: Robert Ball, Details on Demand vs. High Resolution, 2004.<br /> <br /> -[Shneiderman, 1996] Ben Shneiderman, 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, 1996.<br /> <br /> -[Card et al, 1999] Card, S.K., Mackinlay, J.D., and Shneiderman, B. (Eds.) Readings in Information Visualization: Using Vision to Think, pp. 1-34, Morgan Kaufmann Publishers, San Francisco, Califomia, 1999.</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=File:BaumVergleich.jpg&diff=24130 2010-01-27T22:24:29Z

<p>UE-InfoVis0910 0126013: New page: == Beschreibung == == Copyright status == == Source ==</p> <hr /> <div>== Beschreibung ==<br /> <br /> == Copyright status ==<br /> <br /> == Source ==</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2009/10_-_Gruppe_08_-_Aufgabe_4&diff=24129 2010-01-27T22:22:49Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Aufgabenstellung ==<br /> [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]<br /> === Zu erstellende Visualisierung ===<br /> -------------------------------<br /> * Stammbaum der Nachkommen von Lisa und Bart Simpson*<br /> <br /> ...Visualisierung der Nachkommen von Lisa Simpson sowie der Nachkommen von Bart Simpson. Dabei sollen zwei Stammbäume entstehen - einer von Bart und einer von Lisa - die dann miteinander verglichen werden können. Zuerst kommen Lisa und Bart, dann deren Kinder, ihre Enkel, etc. (mind 4 Generationen). Da es noch keine Nachkommen gibt, können diese frei erfunden werden.<br /> <br /> Die Visualisierung soll folgende Informationen darstellen:<br /> <br /> - Verwandtschaftsverhältnisse (zumindest Eltern-Kinder),<br /> <br /> - Unterscheidung zwischen Blutsverwandtschaft und angeheirateten Familienmitgliedern,<br /> <br /> - Geburts- und Todestag sowie Lebensdauer von allen Familienmitgliedern,<br /> <br /> - wichtige Ereignisse im Leben jedes Familienmitglieds (z.B., Anzeigen, Gefängnisaufenthalte, Schulzeit, Studienzeit, Nobelpreise, Arbeitslosigkeit etc.)<br /> <br /> - Zufriedenheit jedes Familienmitglieds (Skala: sehr niedrig - niedrig - mittel - hoch - sehr hoch); kann sich im Laufe des Lebens ändern.<br /> <br /> Die Visualisierung soll die interaktive Auseinandersetzung mit den Daten ermöglichen.<br /> Verpflichtend:<br /> Möglichkeiten zum besseren Vergleich von einzelnen Abschnitten der Stammbäume bzw. Vergleich von Ausschnitten aus Lisas und Barts Stammbäumen.<br /> + mind. 2 weitere Interaktionsmöglichkeiten (z.B., Details on Demand, Filteroptionen)<br /> <br /> Allgemein:<br /> <br /> - Die Daten sollen zur Analyse von Zusammenhängen zwischen Familienverhältnissen, wichtigen Ereignissen und Zufriedenheit visualisiert werden (die Anwendungsgebiets- und Zielgruppenanalyse kann kurz gehalten werden).<br /> <br /> - Die bisher erlernten Design-Prinzipien sollen umgesetzt werden z.B.: Optimierung der Data-ink ratio (keine Comics!), visuelle Attribute (Größe, Farbe, Position, etc.) sollen sinnvoll eingesetzt werden (Information darstellen).<br /> <br /> - Die Mockups sollten zumindest 1) die beiden Stammbäume im Überblick und 2) eine detaillierte Vergleichsansicht von 2 Teil-Stammbäumen wiedergeben.<br /> <br /> - Alle nicht angeführten Daten können frei erfunden werden.<br /> <br /> ------------------------------<br /> <br /> == Links ==<br /> <br /> * [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]<br /> <br /> * [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]<br /> <br /> *[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08|Gruppe 08]]<br /> <br /> ==Point A: Description of application area, data, target group and tasks==<br /> <br /> ===Application area and data===<br /> A family tree is a chart representing family relationships in a conventional tree structure. The tree shows the parents-children connection. The tree should show detail information of a person as well as important events and emotions (happiness). The family tree should visualize hierarchical structures. In our case we will add some additional information as hereditary diseases.<br /> <br /> ===Target group===<br /> The target audience of this visualization would be:<br /> <br /> - family members of the Simpsons<br /> <br /> - characters of the Simpsons-Universe<br /> <br /> - cast and crew of 'The Simpsons'-Television-Show<br /> <br /> No, seriously:<br /> <br /> - just folks who are interested - the family tree data is fictional anyway. Laymen, no prior knowledge needed.<br /> <br /> Target group for family trees are usually people, who would like to know more about specified family relationships. It serves as well for next family generations who would like to know more about their family members. The family tree is also very useful for medical matter because hereditary diseases are shown (epilepsy).In our case the target group is each person who would like to know more about The Simpsons characters.<br /> <br /> ===Goals===<br /> - The tree should be made very simple so everybody could be able to read the most important information about each person listed on the tree.<br /> <br /> - For the visualization of the data we will use miscellaneous visual attributes and high data-per-ink ratio. The goal is to keep the reader focused on the important information and give him maximum information about the persons and their relationships among each other on the tree. <br /> <br /> ==Point B: Concept==<br /> <br /> [[ Image:Gesamt2.jpg|Figure 1]]<br /> <br /> [[ Image:StammBaum.jpg|1000px|Figure 1]]<br /> <br /> [[ Image:Vergleich2.jpg|frame|Figure 2]]<br /> <br /> ===Type of Visualization===<br /> The family tree is visualized by the use of a hierarchical graph - in our case not to be mistaken for a tree since we have more than one higher-ranking node (= two parents) for each node.<br /> <br /> We wanted the root (Lisa and Bart) at the top of the visualisation to highlight that everything else (the offspring) follows unidirectional (-- in reality: time, in our visualisation: vertical axis).<br /> <br /> ===Visual mapping / Visual Attributes===<br /> <br /> ====Blood relationship -&gt; Annulus (around portrait)====<br /> Blue Annulus = existence of blood relationship<br /> <br /> Red Annulus = no existence of blood relationship<br /> <br /> ''Explanatory statement:'' Since the blood relationship to Lisa and Bart is a key information we decided to choose an Annulus around the portraits. In that manner it is fast to extract this particular information for the viewer.<br /> <br /> ====Marriage -&gt; dual wedding ring symbol (between two parents of a child)====<br /> dual wedding ring symbol = the parents are/were married with each other.<br /> <br /> ''Explanatory statement:''In many cultures two interlooped wedding rings are a symbol for marriage. &lt;ref name=&quot;ring&quot;&gt;Wikipedia.de: Ring(Schmuck). Retrieved at: 2010. [http://de.wikipedia.org/wiki/Ring_(Schmuck)#Ehering]&lt;/ref&gt;<br /> <br /> <br /> ====Relationship -&gt; Black persistent lines====<br /> Horizontal black persistent lines between persons indicate relationship based on partnership.<br /> <br /> Vertical black persistent lines between persons indicate relationship between parents and their child/children.<br /> <br /> <br /> ====Relationship -&gt; Black dashed lines====<br /> Horizontal black dashed lines in Comparison Mode indicate not shown siblings (due to eg. zoom level).<br /> <br /> Vertical black dashed lines in Comparison Mode indicate indirect parent-child-relationship - meaning one or more generations inbetween the dashed lines are left out.<br /> <br /> <br /> ===Interaction===<br /> <br /> ====Navigation====<br /> Navigation takes place via mouse controls. A modifier key on the keyboard is also used ('Control'-key). The program starts in the Overview mode showing the whole family tree.<br /> <br /> Mouse-hovering over a person brings up a popup window revealing all kinds of person-related information (name, gender, birth date, profession, events, satisfaction graph). Selecting an event item in this popup-window causes highlighting the corresponding time-section in the satisfaction graph.<br /> <br /> Selecting more than one person via 'Control'+Left-Mouse-Button-clicking several persons or drawing a selection frame around several persons (- via holding Left-Mouse-Button and moving the Mouse). Via 'Enter'-key on the keyboard the selected persons are shown in the Comparison Mode - non-selected persons are left out by dashed black lines (- see text on Visual Mapping).<br /> <br /> ====Zooming and Panning====<br /> In the Comparison Mode the program allows for each split side (left and right) a separately adjustable zoom level and area by panning. A change of the zoom level is accomplished by the use of holding the 'Control'-key on the keyboard and turning the mouse wheel. Panning is accomplished by holding the left mouse button and moving the mouse in direction of desire.<br /> <br /> ====Split Screen Mode====<br /> The Comparison Mode splits the window into two separate sub-windows to allow for separately adjusting (by zooming and panning) the region of interest for each side (= lisa as well as bart) of the family tree.<br /> <br /> Note that without any character selected, the family relationships is not shown.<br /> In that case, moving with the mouse over a character causes the system to show the relationships relative to this character (e.g. Alberta Simpson is labeled as Pamelas daughter when the user moves the mouse over Pamelas picture, as shown in Figure 2).<br /> <br /> ====Dynamic Queries====<br /> There are several search queries the user can choose from - they are accessible in the Comparison Mode.<br /> <br /> One filter in the comparison mode allows the user for filtering with the help of regular expressions - this searches for matching strings in all data fields in the family tree and highlights the corresponding persons.<br /> <br /> More filters:<br /> <br /> - filter by gender<br /> <br /> - filter by Blood relationship (- blood related? Yes/ No.)<br /> <br /> - filter by time range (- see section 'Range Slider' below)<br /> <br /> ====Range Slider====<br /> The user can choose an arbitrary range of time to show the family tree only in the corresponding range.<br /> <br /> ====Details on Demand====<br /> On user demand the information of a person in the family tree is shown in a separate popup window. This window is divided into three different parts. One third shows the name, gender, date of birth and profession. The second one shows all mentionable events in the lifetime of the person - the last third of the window visualizes the 'satisfaction-over-time'-graph.<br /> <br /> As you can see, the 'satisfaction-over-time'-graph also includes various icone, representing the previous mentioned events. When the user moves the mouse over these icons, additional informations is shown.<br /> The system should include a set of predefined icons (e.g., school, career, prison) as well as a symbol for other events (e.g. internship in our graphic). If the user is not familiar with these icons and needs help, it is possible to display a legend via the help-symbol (?).<br /> <br /> ====Focus and Context====<br /> Usage of the Dynamic Queries causes the program to focus on the matching search results. The search results are visualized by adding a mask layer on top of the family tree, allowing only for the resulting persons to be shown clearly through the mask layer - the non-matching persons are overlaid by the dark but opaque layer.<br /> <br /> ===How are the users supported in their tasks?===<br /> A top priority for the team was to create a great experience for the user by making the controls as intuitive and easy to use as possible. Many of the Navigation Methods (left-clicking / zooming and panning) are commonly known from surfing the internet. Moreover an extensive help documentation is supplied with the family tree software package. <br /> <br /> ===What special features are there?===<br /> Dynamic query search with regular expression engine, range slider for time filtering, intuitive easy-to-use-interface, clear design (with priority on data-ink-ratio)<br /> <br /> ==References==<br /> <br /> &lt;references /&gt;<br /> <br /> <br /> -[Ball, 2004]: Robert Ball, Details on Demand vs. High Resolution, 2004.<br /> <br /> -[Shneiderman, 1996] Ben Shneiderman, 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, 1996.<br /> <br /> -[Card et al, 1999] Card, S.K., Mackinlay, J.D., and Shneiderman, B. (Eds.) Readings in Information Visualization: Using Vision to Think, pp. 1-34, Morgan Kaufmann Publishers, San Francisco, Califomia, 1999.</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2009/10_-_Gruppe_08_-_Aufgabe_4&diff=24128 2010-01-27T22:21:08Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Aufgabenstellung ==<br /> [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]<br /> === Zu erstellende Visualisierung ===<br /> -------------------------------<br /> * Stammbaum der Nachkommen von Lisa und Bart Simpson*<br /> <br /> ...Visualisierung der Nachkommen von Lisa Simpson sowie der Nachkommen von Bart Simpson. Dabei sollen zwei Stammbäume entstehen - einer von Bart und einer von Lisa - die dann miteinander verglichen werden können. Zuerst kommen Lisa und Bart, dann deren Kinder, ihre Enkel, etc. (mind 4 Generationen). Da es noch keine Nachkommen gibt, können diese frei erfunden werden.<br /> <br /> Die Visualisierung soll folgende Informationen darstellen:<br /> <br /> - Verwandtschaftsverhältnisse (zumindest Eltern-Kinder),<br /> <br /> - Unterscheidung zwischen Blutsverwandtschaft und angeheirateten Familienmitgliedern,<br /> <br /> - Geburts- und Todestag sowie Lebensdauer von allen Familienmitgliedern,<br /> <br /> - wichtige Ereignisse im Leben jedes Familienmitglieds (z.B., Anzeigen, Gefängnisaufenthalte, Schulzeit, Studienzeit, Nobelpreise, Arbeitslosigkeit etc.)<br /> <br /> - Zufriedenheit jedes Familienmitglieds (Skala: sehr niedrig - niedrig - mittel - hoch - sehr hoch); kann sich im Laufe des Lebens ändern.<br /> <br /> Die Visualisierung soll die interaktive Auseinandersetzung mit den Daten ermöglichen.<br /> Verpflichtend:<br /> Möglichkeiten zum besseren Vergleich von einzelnen Abschnitten der Stammbäume bzw. Vergleich von Ausschnitten aus Lisas und Barts Stammbäumen.<br /> + mind. 2 weitere Interaktionsmöglichkeiten (z.B., Details on Demand, Filteroptionen)<br /> <br /> Allgemein:<br /> <br /> - Die Daten sollen zur Analyse von Zusammenhängen zwischen Familienverhältnissen, wichtigen Ereignissen und Zufriedenheit visualisiert werden (die Anwendungsgebiets- und Zielgruppenanalyse kann kurz gehalten werden).<br /> <br /> - Die bisher erlernten Design-Prinzipien sollen umgesetzt werden z.B.: Optimierung der Data-ink ratio (keine Comics!), visuelle Attribute (Größe, Farbe, Position, etc.) sollen sinnvoll eingesetzt werden (Information darstellen).<br /> <br /> - Die Mockups sollten zumindest 1) die beiden Stammbäume im Überblick und 2) eine detaillierte Vergleichsansicht von 2 Teil-Stammbäumen wiedergeben.<br /> <br /> - Alle nicht angeführten Daten können frei erfunden werden.<br /> <br /> ------------------------------<br /> <br /> == Links ==<br /> <br /> * [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]<br /> <br /> * [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]<br /> <br /> *[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08|Gruppe 08]]<br /> <br /> ==Point A: Description of application area, data, target group and tasks==<br /> <br /> ===Application area and data===<br /> A family tree is a chart representing family relationships in a conventional tree structure. The tree shows the parents-children connection. The tree should show detail information of a person as well as important events and emotions (happiness). The family tree should visualize hierarchical structures. In our case we will add some additional information as hereditary diseases.<br /> <br /> ===Target group===<br /> The target audience of this visualization would be:<br /> <br /> - family members of the Simpsons<br /> <br /> - characters of the Simpsons-Universe<br /> <br /> - cast and crew of 'The Simpsons'-Television-Show<br /> <br /> No, seriously:<br /> <br /> - just folks who are interested - the family tree data is fictional anyway. Laymen, no prior knowledge needed.<br /> <br /> Target group for family trees are usually people, who would like to know more about specified family relationships. It serves as well for next family generations who would like to know more about their family members. The family tree is also very useful for medical matter because hereditary diseases are shown (epilepsy).In our case the target group is each person who would like to know more about The Simpsons characters.<br /> <br /> ===Goals===<br /> - The tree should be made very simple so everybody could be able to read the most important information about each person listed on the tree.<br /> <br /> - For the visualization of the data we will use miscellaneous visual attributes and high data-per-ink ratio. The goal is to keep the reader focused on the important information and give him maximum information about the persons and their relationships among each other on the tree. <br /> <br /> ==Point B: Concept==<br /> <br /> [[ Image:Gesamt2.jpg|Figure 1]]<br /> <br /> [[ Image:StammBaum.jpg|Figure 1]]<br /> <br /> [[ Image:Vergleich2.jpg|frame|Figure 2]]<br /> <br /> ===Type of Visualization===<br /> The family tree is visualized by the use of a hierarchical graph - in our case not to be mistaken for a tree since we have more than one higher-ranking node (= two parents) for each node.<br /> <br /> We wanted the root (Lisa and Bart) at the top of the visualisation to highlight that everything else (the offspring) follows unidirectional (-- in reality: time, in our visualisation: vertical axis).<br /> <br /> ===Visual mapping / Visual Attributes===<br /> <br /> ====Blood relationship -&gt; Annulus (around portrait)====<br /> Blue Annulus = existence of blood relationship<br /> <br /> Red Annulus = no existence of blood relationship<br /> <br /> ''Explanatory statement:'' Since the blood relationship to Lisa and Bart is a key information we decided to choose an Annulus around the portraits. In that manner it is fast to extract this particular information for the viewer.<br /> <br /> ====Marriage -&gt; dual wedding ring symbol (between two parents of a child)====<br /> dual wedding ring symbol = the parents are/were married with each other.<br /> <br /> ''Explanatory statement:''In many cultures two interlooped wedding rings are a symbol for marriage. &lt;ref name=&quot;ring&quot;&gt;Wikipedia.de: Ring(Schmuck). Retrieved at: 2010. [http://de.wikipedia.org/wiki/Ring_(Schmuck)#Ehering]&lt;/ref&gt;<br /> <br /> <br /> ====Relationship -&gt; Black persistent lines====<br /> Horizontal black persistent lines between persons indicate relationship based on partnership.<br /> <br /> Vertical black persistent lines between persons indicate relationship between parents and their child/children.<br /> <br /> <br /> ====Relationship -&gt; Black dashed lines====<br /> Horizontal black dashed lines in Comparison Mode indicate not shown siblings (due to eg. zoom level).<br /> <br /> Vertical black dashed lines in Comparison Mode indicate indirect parent-child-relationship - meaning one or more generations inbetween the dashed lines are left out.<br /> <br /> <br /> ===Interaction===<br /> <br /> ====Navigation====<br /> Navigation takes place via mouse controls. A modifier key on the keyboard is also used ('Control'-key). The program starts in the Overview mode showing the whole family tree.<br /> <br /> Mouse-hovering over a person brings up a popup window revealing all kinds of person-related information (name, gender, birth date, profession, events, satisfaction graph). Selecting an event item in this popup-window causes highlighting the corresponding time-section in the satisfaction graph.<br /> <br /> Selecting more than one person via 'Control'+Left-Mouse-Button-clicking several persons or drawing a selection frame around several persons (- via holding Left-Mouse-Button and moving the Mouse). Via 'Enter'-key on the keyboard the selected persons are shown in the Comparison Mode - non-selected persons are left out by dashed black lines (- see text on Visual Mapping).<br /> <br /> ====Zooming and Panning====<br /> In the Comparison Mode the program allows for each split side (left and right) a separately adjustable zoom level and area by panning. A change of the zoom level is accomplished by the use of holding the 'Control'-key on the keyboard and turning the mouse wheel. Panning is accomplished by holding the left mouse button and moving the mouse in direction of desire.<br /> <br /> ====Split Screen Mode====<br /> The Comparison Mode splits the window into two separate sub-windows to allow for separately adjusting (by zooming and panning) the region of interest for each side (= lisa as well as bart) of the family tree.<br /> <br /> Note that without any character selected, the family relationships is not shown.<br /> In that case, moving with the mouse over a character causes the system to show the relationships relative to this character (e.g. Alberta Simpson is labeled as Pamelas daughter when the user moves the mouse over Pamelas picture, as shown in Figure 2).<br /> <br /> ====Dynamic Queries====<br /> There are several search queries the user can choose from - they are accessible in the Comparison Mode.<br /> <br /> One filter in the comparison mode allows the user for filtering with the help of regular expressions - this searches for matching strings in all data fields in the family tree and highlights the corresponding persons.<br /> <br /> More filters:<br /> <br /> - filter by gender<br /> <br /> - filter by Blood relationship (- blood related? Yes/ No.)<br /> <br /> - filter by time range (- see section 'Range Slider' below)<br /> <br /> ====Range Slider====<br /> The user can choose an arbitrary range of time to show the family tree only in the corresponding range.<br /> <br /> ====Details on Demand====<br /> On user demand the information of a person in the family tree is shown in a separate popup window. This window is divided into three different parts. One third shows the name, gender, date of birth and profession. The second one shows all mentionable events in the lifetime of the person - the last third of the window visualizes the 'satisfaction-over-time'-graph.<br /> <br /> As you can see, the 'satisfaction-over-time'-graph also includes various icone, representing the previous mentioned events. When the user moves the mouse over these icons, additional informations is shown.<br /> The system should include a set of predefined icons (e.g., school, career, prison) as well as a symbol for other events (e.g. internship in our graphic). If the user is not familiar with these icons and needs help, it is possible to display a legend via the help-symbol (?).<br /> <br /> ====Focus and Context====<br /> Usage of the Dynamic Queries causes the program to focus on the matching search results. The search results are visualized by adding a mask layer on top of the family tree, allowing only for the resulting persons to be shown clearly through the mask layer - the non-matching persons are overlaid by the dark but opaque layer.<br /> <br /> ===How are the users supported in their tasks?===<br /> A top priority for the team was to create a great experience for the user by making the controls as intuitive and easy to use as possible. Many of the Navigation Methods (left-clicking / zooming and panning) are commonly known from surfing the internet. Moreover an extensive help documentation is supplied with the family tree software package. <br /> <br /> ===What special features are there?===<br /> Dynamic query search with regular expression engine, range slider for time filtering, intuitive easy-to-use-interface, clear design (with priority on data-ink-ratio)<br /> <br /> ==References==<br /> <br /> &lt;references /&gt;<br /> <br /> <br /> -[Ball, 2004]: Robert Ball, Details on Demand vs. High Resolution, 2004.<br /> <br /> -[Shneiderman, 1996] Ben Shneiderman, 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, 1996.<br /> <br /> -[Card et al, 1999] Card, S.K., Mackinlay, J.D., and Shneiderman, B. (Eds.) Readings in Information Visualization: Using Vision to Think, pp. 1-34, Morgan Kaufmann Publishers, San Francisco, Califomia, 1999.</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=File:StammBaum.jpg&diff=24126 2010-01-27T22:19:03Z

<p>UE-InfoVis0910 0126013: New page: == Beschreibung == == Copyright status == == Source ==</p> <hr /> <div>== Beschreibung ==<br /> <br /> == Copyright status ==<br /> <br /> == Source ==</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2009/10_-_Gruppe_08_-_Aufgabe_2&diff=23647 2009-12-08T08:37:10Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Aufgabenstellung ==<br /> [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]<br /> === Zu beurteilende Tabelle ===<br /> [[Image:table2.gif]]<br /> <br /> === Point B : Critics on the given table ===<br /> ====1. White space:====<br /> This example shows horizontal white space between rows of data but no white space of vertikal data may cause difficulties for the reader of this table.<br /> <br /> ====2. Rules and grids:====<br /> As written in the lecture, the delineation of columns and rows is the least effective use of rules and grids. In our example are used thick grids and dots (intermittent lines) without any form what did not even separate the header from body nor any other data. There is a thick line between the body and the header but the problem is that the same thick lines are also used in the body what makes it look like group of data.That reduces the table’s effectiveness.<br /> <br /> ====3. Header:====<br /> In the header there is the same title written for each group of data what makes the table full of information and reduces the effectivness.There is also no need for unit´s name to be repeated for each data because it is the same name repeated all the time. <br /> <br /> ====4. Alignment:====<br /> Quantitative values in our table are center aligned.Because of the way numbers are written and read, aligning them to the center makes them difficult to interpret and decimels can be easily ignored.<br /> <br /> ====5. Number format:====<br /> A comma is not placed to the left of every three whole-number digits.<br /> <br /> ====6. Font:====<br /> In our table font is &quot;Bold&quot; what does not make the table legible.<br /> <br /> === Point C : Suggested revisions ===<br /> We developed two tables, one print version which is scaled to fit on a page and a second one which is basically designed for larger documents, e.g. look-up tables or electronic documents. The reason why we posted both of them is that we believe that the purpose and the environment of the table have influence on the design of the table.<br /> ==== Table 1 ====<br /> <br /> [[Image:Tabelle 1.jpg|550px]]<br /> <br /> ==== Table 2 ====<br /> <br /> [[Image:Infovis table2new.png|left|thumb|1000px|Tabelle 2]]<br /> <br /> <br /> ==== Ad Table 1 ====<br /> <br /> <br /> === Point D : Explanation of improvements ===<br /> =====1. White space:=====<br /> First thing we did was to delete already existing grids and rows and to replace them with white spaces horizontaly.We did that to make our table look more legible and to increase the table effectivness.<br /> <br /> =====2. Rules and grids=====<br /> We deleted all grids and rules except the header line.That is important for the reader to get the idea of the data he is reading.<br /> <br /> =====3. Header=====<br /> For better view we deleted all unit names that were repeated for each row and we left only one unit name that values for each one.<br /> We did the same thing with the column names and we left only one colum name &quot;Tk50-HTK&quot; written horizonatly and it is easiy to notice that it values for each subgroup.(E-195-1 etc.)<br /> <br /> =====4. Alignment=====<br /> Because numbers in our table represent quantitative values we aligned them to the<br /> right for better legibility.<br /> <br /> =====5. Number format=====<br /> For better legibility we changed number format and placed comma to the left of every three whole-number digits.<br /> <br /> =====6. Font=====<br /> We changed the font as well because BOLD makes the data less effective.We chose ariel font.<br /> <br /> =====7. Fill color=====<br /> Fill colors are less distracting to the eye as it scans across them.Because of that we chose grey grids accros horizontal rows.<br /> <br /> ==== Ad Table 2 ====<br /> =====1. White Space=====<br /> White space was used between each of the groups (E-195-/E-196-/E-197-).<br /> <br /> =====2. Rules and grids=====<br /> Most of the gridlines were dismissed. Only one gridline stayed remaining.<br /> <br /> =====3. Header=====<br /> The Header is now consisting of the chemical elements for better comparison of the relevant values in columns instead of in rows.<br /> <br /> =====4. Alignment=====<br /> Numbers are aligned on the right side. Mass numbers of the elements are aligned on the left and the element names (one row below) in the middle to make it look like the standard chemical notation of elements. <br /> <br /> =====5. Font=====<br /> Google Docs standard font.<br /> <br /> =====7. Fill color=====<br /> One fill color is used for the columns in order to help the eyes focus on them.<br /> <br /> =====8. Element Order=====<br /> The elements are now ordered according to their position in the periodic table rather than alphabetical.<br /> <br /> <br /> <br /> <br /> <br /> <br /> == Links ==<br /> <br /> <br /> * [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]<br /> <br /> * [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]<br /> <br /> *[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08|Gruppe 08]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2009/10_-_Gruppe_08_-_Aufgabe_2&diff=23582 2009-12-03T09:39:13Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Aufgabenstellung ==<br /> [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]<br /> === Zu beurteilende Tabelle ===<br /> [[Image:table2.gif]]<br /> <br /> === Point B : Critics on the given table ===<br /> ====1. White space:====<br /> This example shows horizontal white space between rows of data but no white space of vertikal data may cause difficulties for the reader of this table.<br /> <br /> ====2. Rules and grids:====<br /> As written in the lecture, the delineation of columns and rows is the least effective use of rules and grids. In our example are used thick grids and dots (intermittent lines) without any form what did not even separate the header from body nor any other data. There is a thick line between the body and the header but the problem is that the same thick lines are also used in the body what makes it look like group of data.That reduces the table’s effectiveness.<br /> <br /> ====3. Header:====<br /> In the header there is the same title written for each group of data what makes the table full of information and reduces the effectivness.There is also no need for unit´s name to be repeated for each data because it is the same name repeated all the time. <br /> <br /> ====4. Alignment:====<br /> Quantitative values in our table are center aligned.Because of the way numbers are written and read, aligning them to the center makes them difficult to interpret and decimels can be easily ignored.<br /> <br /> ====5. Number format:====<br /> A comma is not placed to the left of every three whole-number digits.<br /> <br /> ====6. Font:====<br /> In our table font is &quot;Bold&quot; what does not make the table legible.<br /> <br /> === Point C : Suggested revisions ===<br /> We developed two tables, one print version which is scaled to fit on a page and a second one which is basically designed for larger documents, e.g. look-up tables or electronic documents. The reason why we posted both of them is that we believe that the purpose and the environment of the table have influence on the design of the table.<br /> ==== Table 1 ====<br /> <br /> [[Image:Tabelle 1.jpg|550px]]<br /> <br /> ==== Table 2 ====<br /> <br /> [[Image:Infovis_table2.png]]<br /> <br /> === Point D : Explanation of improvements ===<br /> ==== Ad Table 1 ====<br /> =====1. White space:=====<br /> First thing we did was to delete already existing grids and rows and to replace them with white spaces horizontaly.We did that to make our table look more legible and to increase the table effectivness.<br /> <br /> =====2. Rules and grids=====<br /> We deleted all grids and rules except the header line.That is important for the reader to get the idea of the data he is reading.<br /> <br /> =====3. Header=====<br /> For better view we deleted all unit names that were repeated for each row and we left only one unit name that values for each one.<br /> We did the same thing with the column names and we left only one colum name &quot;Tk50-HTK&quot; written horizonatly and it is easiy to notice that it values for each subgroup.(E-195-1 etc.)<br /> <br /> =====4. Alignment=====<br /> Because numbers in our table represent quantitative values we aligned them to the<br /> right for better legibility.<br /> <br /> =====5. Number format=====<br /> For better legibility we changed number format and placed comma to the left of every three whole-number digits.<br /> <br /> =====6. Font=====<br /> We changed the font as well because BOLD makes the data less effective.We chose ariel font.<br /> <br /> =====7. Fill color=====<br /> Fill colors are less distracting to the eye as it scans across them.Because of that we chose grey grids accros horizontal rows.<br /> <br /> ==== Ad Table 2 ====<br /> =====1. White Space=====<br /> White space was used between each of the groups (E-195-/E-196-/E-197-).<br /> <br /> =====2. Rules and grids=====<br /> Most of the gridlines were dismissed. Only one gridline stayed remaining.<br /> <br /> =====3. Header=====<br /> The Header is now consisting of the chemical elements for better comparison of the relevant values in columns instead of in rows.<br /> <br /> =====4. Alignment=====<br /> Numbers are aligned on the right side. Mass numbers of the elements are aligned on the left and the element names (one row below) in the middle to make it look like the standard chemical notation of elements. <br /> <br /> =====5. Font=====<br /> Google Docs standard font.<br /> <br /> =====7. Fill color=====<br /> One fill color is used for the columns in order to help the eyes focus on them.<br /> <br /> =====8. Element Order=====<br /> The elements are now ordered according to their position in the periodic table rather than alphabetical.<br /> <br /> <br /> <br /> <br /> <br /> <br /> == Links ==<br /> <br /> <br /> * [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]<br /> <br /> * [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]<br /> <br /> *[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08|Gruppe 08]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2009/10_-_Gruppe_08_-_Aufgabe_2&diff=23581 2009-12-03T09:36:28Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Aufgabenstellung ==<br /> [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]<br /> === Zu beurteilende Tabelle ===<br /> [[Image:table2.gif]]<br /> <br /> === Point B : Critics on the given table ===<br /> ====1. White space:====<br /> This example shows horizontal white space between rows of data but no white space of vertikal data may cause difficulties for the reader of this table.<br /> <br /> ====2. Rules and grids:====<br /> As written in the lecture, the delineation of columns and rows is the least effective use of rules and grids. In our example are used thick grids and dots (intermittent lines) without any form what did not even separate the header from body nor any other data. There is a thick line between the body and the header but the problem is that the same thick lines are also used in the body what makes it look like group of data.That reduces the table’s effectiveness.<br /> <br /> ====3. Header:====<br /> In the header there is the same title written for each group of data what makes the table full of information and reduces the effectivness.There is also no need for unit´s name to be repeated for each data because it is the same name repeated all the time. <br /> <br /> ====4. Alignment:====<br /> Quantitative values in our table are center aligned.Because of the way numbers are written and read, aligning them to the center makes them difficult to interpret and decimels can be easily ignored.<br /> <br /> ====5. Number format:====<br /> A comma is not placed to the left of every three whole-number digits.<br /> <br /> ====6. Font:====<br /> In our table font is &quot;Bold&quot; what does not make the table legible.<br /> <br /> === Point C : Suggested revisions ===<br /> We developed two tables, one print version which is scaled to fit on a page and a second one which is basically designed for larger documents, e.g. look-up tables or electronic documents. The reason why we posted both of them is that we believe that the purpose and the environment of the table have influence on the design of the table.<br /> ==== Table 1 ====<br /> <br /> [[Image:Tabelle1.jpg|550px]]<br /> <br /> ==== Table 2 ====<br /> <br /> [[Image:Infovis_table2.png]]<br /> <br /> === Point D : Explanation of improvements ===<br /> ==== Ad Table 1 ====<br /> =====1. White space:=====<br /> First thing we did was to delete already existing grids and rows and to replace them with white spaces horizontaly.We did that to make our table look more legible and to increase the table effectivness.<br /> <br /> =====2. Rules and grids=====<br /> We deleted all grids and rules except the header line.That is important for the reader to get the idea of the data he is reading.<br /> <br /> =====3. Header=====<br /> For better view we deleted all unit names that were repeated for each row and we left only one unit name that values for each one.<br /> We did the same thing with the column names and we left only one colum name &quot;Tk50-HTK&quot; written horizonatly and it is easiy to notice that it values for each subgroup.(E-195-1 etc.)<br /> <br /> =====4. Alignment=====<br /> Because numbers in our table represent quantitative values we aligned them to the<br /> right for better legibility.<br /> <br /> =====5. Number format=====<br /> For better legibility we changed number format and placed comma to the left of every three whole-number digits.<br /> <br /> =====6. Font=====<br /> We changed the font as well because BOLD makes the data less effective.We chose ariel font.<br /> <br /> =====7. Fill color=====<br /> Fill colors are less distracting to the eye as it scans across them.Because of that we chose grey grids accros horizontal rows.<br /> <br /> ==== Ad Table 2 ====<br /> =====1. White Space=====<br /> White space was used between each of the groups (E-195-/E-196-/E-197-).<br /> <br /> =====2. Rules and grids=====<br /> Most of the gridlines were dismissed. Only one gridline stayed remaining.<br /> <br /> =====3. Header=====<br /> The Header is now consisting of the chemical elements for better comparison of the relevant values in columns instead of in rows.<br /> <br /> =====4. Alignment=====<br /> Numbers are aligned on the right side. Mass numbers of the elements are aligned on the left and the element names (one row below) in the middle to make it look like the standard chemical notation of elements. <br /> <br /> =====5. Font=====<br /> Google Docs standard font.<br /> <br /> =====7. Fill color=====<br /> One fill color is used for the columns in order to help the eyes focus on them.<br /> <br /> =====8. Element Order=====<br /> The elements are now ordered according to their position in the periodic table rather than alphabetical.<br /> <br /> <br /> <br /> <br /> <br /> <br /> == Links ==<br /> <br /> <br /> * [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]<br /> <br /> * [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]<br /> <br /> *[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08|Gruppe 08]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=File:Tabelle_1.jpg&diff=23580 2009-12-03T09:35:41Z

<p>UE-InfoVis0910 0126013: New page: == Beschreibung == == Copyright status == == Source ==</p> <hr /> <div>== Beschreibung ==<br /> <br /> == Copyright status ==<br /> <br /> == Source ==</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2009/10_-_Gruppe_08_-_Aufgabe_2&diff=23579 2009-12-03T09:34:47Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Aufgabenstellung ==<br /> [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]<br /> === Zu beurteilende Tabelle ===<br /> [[Image:table2.gif]]<br /> <br /> === Point B : Critics on the given table ===<br /> ====1. White space:====<br /> This example shows horizontal white space between rows of data but no white space of vertikal data may cause difficulties for the reader of this table.<br /> <br /> ====2. Rules and grids:====<br /> As written in the lecture, the delineation of columns and rows is the least effective use of rules and grids. In our example are used thick grids and dots (intermittent lines) without any form what did not even separate the header from body nor any other data. There is a thick line between the body and the header but the problem is that the same thick lines are also used in the body what makes it look like group of data.That reduces the table’s effectiveness.<br /> <br /> ====3. Header:====<br /> In the header there is the same title written for each group of data what makes the table full of information and reduces the effectivness.There is also no need for unit´s name to be repeated for each data because it is the same name repeated all the time. <br /> <br /> ====4. Alignment:====<br /> Quantitative values in our table are center aligned.Because of the way numbers are written and read, aligning them to the center makes them difficult to interpret and decimels can be easily ignored.<br /> <br /> ====5. Number format:====<br /> A comma is not placed to the left of every three whole-number digits.<br /> <br /> ====6. Font:====<br /> In our table font is &quot;Bold&quot; what does not make the table legible.<br /> <br /> === Point C : Suggested revisions ===<br /> We developed two tables, one print version which is scaled to fit on a page and a second one which is basically designed for larger documents, e.g. look-up tables or electronic documents. The reason why we posted both of them is that we believe that the purpose and the environment of the table have influence on the design of the table.<br /> ==== Table 1 ====<br /> [[Image:Informationsvisualisierung.jpg|550px]]<br /> <br /> <br /> ==== Table 2 ====<br /> <br /> [[Image:Infovis_table2.png]]<br /> <br /> === Point D : Explanation of improvements ===<br /> ==== Ad Table 1 ====<br /> =====1. White space:=====<br /> First thing we did was to delete already existing grids and rows and to replace them with white spaces horizontaly.We did that to make our table look more legible and to increase the table effectivness.<br /> <br /> =====2. Rules and grids=====<br /> We deleted all grids and rules except the header line.That is important for the reader to get the idea of the data he is reading.<br /> <br /> =====3. Header=====<br /> For better view we deleted all unit names that were repeated for each row and we left only one unit name that values for each one.<br /> We did the same thing with the column names and we left only one colum name &quot;Tk50-HTK&quot; written horizonatly and it is easiy to notice that it values for each subgroup.(E-195-1 etc.)<br /> <br /> =====4. Alignment=====<br /> Because numbers in our table represent quantitative values we aligned them to the<br /> right for better legibility.<br /> <br /> =====5. Number format=====<br /> For better legibility we changed number format and placed comma to the left of every three whole-number digits.<br /> <br /> =====6. Font=====<br /> We changed the font as well because BOLD makes the data less effective.We chose ariel font.<br /> <br /> =====7. Fill color=====<br /> Fill colors are less distracting to the eye as it scans across them.Because of that we chose grey grids accros horizontal rows.<br /> <br /> ==== Ad Table 2 ====<br /> =====1. White Space=====<br /> White space was used between each of the groups (E-195-/E-196-/E-197-).<br /> <br /> =====2. Rules and grids=====<br /> Most of the gridlines were dismissed. Only one gridline stayed remaining.<br /> <br /> =====3. Header=====<br /> The Header is now consisting of the chemical elements for better comparison of the relevant values in columns instead of in rows.<br /> <br /> =====4. Alignment=====<br /> Numbers are aligned on the right side. Mass numbers of the elements are aligned on the left and the element names (one row below) in the middle to make it look like the standard chemical notation of elements. <br /> <br /> =====5. Font=====<br /> Google Docs standard font.<br /> <br /> =====7. Fill color=====<br /> One fill color is used for the columns in order to help the eyes focus on them.<br /> <br /> =====8. Element Order=====<br /> The elements are now ordered according to their position in the periodic table rather than alphabetical.<br /> <br /> <br /> <br /> <br /> <br /> <br /> == Links ==<br /> <br /> <br /> * [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]<br /> <br /> * [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]<br /> <br /> *[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08|Gruppe 08]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=File:Informationsvisualisierung.jpg&diff=23376 2009-11-19T23:48:18Z

<p>UE-InfoVis0910 0126013: New page: == Beschreibung == == Copyright status == == Source ==</p> <hr /> <div>== Beschreibung ==<br /> <br /> == Copyright status ==<br /> <br /> == Source ==</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=Data-Ink_Ratio&diff=22861 2009-11-06T07:30:15Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Definitions ==<br /> <br /> The Data-Ink ratio is a concept introduced by Edward Tufte, the expert whose work has contributed significantly to designing effective data presentations. In his 1983 book, The Visual Display of Quantitative <br /> <br /> Data, he stated the goal: {{Quotation|Above all else show the data| Tufte, 1983}}<br /> <br /> &lt;br&gt;<br /> <br /> {{quotation|A large share of ink on a graphic should present data-information, the ink changing as the data change. Data-ink is the non-erasable core of a graphic, the non-redundant ink arranged in response to <br /> <br /> variation in the numbers represented.|Tufte, 1983}}<br /> <br /> <br /> &lt;br&gt;<br /> <br /> <br /> Tufte refers to data-ink as the non-erasable ink used for the presentation of data. If data-ink would be removed from the image, the graphic would lose the content. Non-Data-Ink is accordingly the ink that does <br /> <br /> not transport the information but it is used for scales, labels and edges. The data-ink ratio is the proportion of Ink that is used to present actual data compared to the total amount of ink (or pixels) used in <br /> <br /> the entire display. (Ratio of Data-Ink to non-Data-Ink). <br /> <br /> <br /> [[Image:DIR.jpg|thumb|600px|center]]<br /> <br /> <br /> <br /> <br /> Good graphics should include only data-Ink. Non-Data-Ink is everywhere where possible to be deleted. The reason for this is to avoid the attention of viewers of the data presentation to irrelevant elements.&lt;br&gt;<br /> The goal is to design a display with the highest possible data-ink ratio (that is, as close to the total of 1.0), without eliminating something that is necessary for effective communication.<br /> <br /> == Example ==<br /> <br /> This is an example of a graph with a low Data-Ink Ratio.<br /> <br /> [[Image:Dir1.png|thumb|Low Data-Ink Ratio|400px|center]]<br /> <br /> <br /> The border around the graph, the background color and the grid lines are all unnecessary data ink.<br /> <br /> &lt;br&gt;<br /> <br /> <br /> Now an example of a graph with a high Data-Ink Ratio<br /> <br /> [[Image:Dir2.png|thumb|High Data-Ink Ratio|400px|center]]<br /> <br /> We have deleted the border around the graph, the background color and the grid lines and drowned the attention to horizontal scales that are data-ink. There is nothing else to distract and the key features of the data stand out clearly.<br /> &lt;br&gt;<br /> <br /> == Critisicm on Tufte's principles ==<br /> Inbar, et al, evaluated in 2007 the people's acceptance of the minimalist approach to visualize information. Therefore he asked 87 students to rate their preference for two different graphs displaying identical information - a standard bar-graph and a minimalist version. Both versions were taken from [Tufte, 1983]. [Inbar, 2007]<br /> <br /> The results showed that the majority students did not like Tufte's minimalist design of bar-graphs - instead they seem to prefer &quot;chartjunk&quot;. [Inbar, 2007]<br /> <br /> <br /> <br /> == Quellen ==<br /> <br /> [Few, 2004] Stephen Few. Elegance Through Simplicity. Created at: October 16, 2004. Retrieved at: October 25, 2005. http://www.intelligententerprise.com/showArticle.jhtml?articleID=49400920.<br /> <br /> [Few, Edge 2009] Stephen Few, . Perceptual Edge Sometimes We Must Raise Our Voices, Visual Business Intelligence Newsletter Created at: January/February 2009. http://www.perceptualedge.com/articles/visual_business_intelligence/sometimes_we_must_raise_our_voices.pdf.<br /> <br /> [Tufte, 1983] Edward Tufte. ''The Visual Display of Quantitative Information''. http://campusphere.de/datensicht/files/EdwardR.Tufte.%20Tufte<br /> <br /> Pictures: http://www.tbray.org/ongoing/data-ink/di1, http://www.tbray.org/ongoing/data-ink/di5<br /> <br /> <br /> <br /> <br /> <br /> <br /> [[Category:Glossary]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=User_talk:UE-InfoVis0910_0126013&diff=22842 2009-11-05T23:28:08Z

<p>UE-InfoVis0910 0126013: Removing all content from page</p> <hr /> <div></div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=User_talk:UE-InfoVis0910_0126013&diff=22841 2009-11-05T23:27:26Z

<p>UE-InfoVis0910 0126013: New page: * Die Beschreibung wurde viel verändert (Altte war verwirrend geschrieben und hat weniger als oberflächig beschreibt worum es geht. War nicht ausreichend und auch nicht vollständig). [...</p> <hr /> <div>* Die Beschreibung wurde viel verändert (Altte war verwirrend geschrieben und hat weniger als oberflächig beschreibt worum es geht. War nicht ausreichend und auch nicht vollständig). [[User:UE-InfoVis0910 0426516|UE-InfoVis0910 0126013]]<br /> <br /> * Prägnante Definition ist eingefügt weil alte Text hat es überhaupt nicht gehabt [[User:UE-InfoVis0910 0426516|UE-InfoVis0910 0126013]]<br /> <br /> * Zitaten und „Critisicm on Tufte's principles“ sind gleich geblieben, sonst ist alles anders inhaltlich geändert [[User:UE-InfoVis0910 0426516|UE-InfoVis0910 0126013]]<br /> <br /> * Alte zwei Bilder sind gelöscht und neue zwei eingefügt (waren 2 Bilder von verschiedene Beispiele und mit solche zwei Bilder könnte nicht unterschied zwischen high/low Data-Ink Ratio schön erklärt werden, noch dazu die Quellen auf der Image-Site waren nicht angegeben) [[User:UE-InfoVis0910 0426516|UE-InfoVis0910 0126013]]<br /> <br /> * neue Quellen wurden hinzufügt [[User:UE-InfoVis0910 0426516|UE-InfoVis0910 0126013]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=Data-Ink_Ratio&diff=22840 2009-11-05T23:17:41Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Definitions ==<br /> <br /> The Data-Ink ratio is a concept introduced by Edward Tufte, the expert whose work has contributed significantly to designing effective data presentations. In his 1983 book, The Visual Display of Quantitative <br /> <br /> Data, he stated the goal: {{Quotation|Above all else show the data| Tufte, 1983}}<br /> <br /> &lt;br&gt;<br /> <br /> {{quotation|A large share of ink on a graphic should present data-information, the ink changing as the data change. Data-ink is the non-erasable core of a graphic, the non-redundant ink arranged in response to <br /> <br /> variation in the numbers represented.|Tufte, 1983}}<br /> <br /> <br /> &lt;br&gt;<br /> <br /> <br /> Tufte refers to data-ink as the non-erasable ink used for the presentation of data. If data-ink would be removed from the image, the graphic would lose the content. Non-Data-Ink is accordingly the ink that does <br /> <br /> not transport the information but it is used for scales, labels and edges. The data-ink ratio is the proportion of Ink that is used to present actual data compared to the total amount of ink (or pixels) used in <br /> <br /> the entire display. (Ratio of Data-Ink to non-Data-Ink). <br /> <br /> <br /> [[Image:DIR.jpg|thumb|400px|center]]<br /> <br /> <br /> <br /> <br /> Good graphics should include only data-Ink. Non-Data-Ink is everywhere where possible to be deleted. The reason for this is to avoid the attention of viewers of the data presentation to irrelevant elements.&lt;br&gt;<br /> The goal is to design a display with the highest possible data-ink ratio (that is, as close to the total of 1.0), without eliminating something that is necessary for effective communication.<br /> <br /> == Example ==<br /> <br /> This is an example of a graph with a low Data-Ink Ratio.<br /> <br /> [[Image:Dir1.png|thumb|Low Data-Ink Ratio|400px|center]]<br /> <br /> <br /> The border around the graph, the background color and the grid lines are all unnecessary data ink.<br /> <br /> &lt;br&gt;<br /> <br /> <br /> Now an example of a graph with a high Data-Ink Ratio<br /> <br /> [[Image:Dir2.png|thumb|High Data-Ink Ratio|400px|center]]<br /> <br /> We have deleted the border around the graph, the background color and the grid lines and drowned the attention to horizontal scales that are data-ink. There is nothing else to distract and the key features of the data stand out clearly.<br /> &lt;br&gt;<br /> <br /> == Critisicm on Tufte's principles ==<br /> Inbar, et al, evaluated in 2007 the people's acceptance of the minimalist approach to visualize information. Therefore he asked 87 students to rate their preference for two different graphs displaying identical information - a standard bar-graph and a minimalist version. Both versions were taken from [Tufte, 1983]. [Inbar, 2007]<br /> <br /> The results showed that the majority students did not like Tufte's minimalist design of bar-graphs - instead they seem to prefer &quot;chartjunk&quot;. [Inbar, 2007]<br /> <br /> <br /> <br /> == Quellen ==<br /> <br /> [Few, 2004] Stephen Few. Elegance Through Simplicity. Created at: October 16, 2004. Retrieved at: October 25, 2005. http://www.intelligententerprise.com/showArticle.jhtml?articleID=49400920.<br /> <br /> [Few, Edge 2009] Stephen Few, . Perceptual Edge Sometimes We Must Raise Our Voices, Visual Business Intelligence Newsletter Created at: January/February 2009. http://www.perceptualedge.com/articles/visual_business_intelligence/sometimes_we_must_raise_our_voices.pdf.<br /> <br /> [Tufte, 1983] Edward Tufte. ''The Visual Display of Quantitative Information''. http://campusphere.de/datensicht/files/EdwardR.Tufte.%20Tufte<br /> <br /> Pictures: http://www.tbray.org/ongoing/data-ink/di1, http://www.tbray.org/ongoing/data-ink/di5<br /> <br /> <br /> <br /> <br /> <br /> <br /> [[Category:Glossary]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=Data-Ink_Ratio&diff=22839 2009-11-05T23:16:36Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Definitions ==<br /> <br /> The Data-Ink ratio is a concept introduced by Edward Tufte, the expert whose work has contributed significantly to designing effective data presentations. In his 1983 book, The Visual Display of Quantitative <br /> <br /> Data, he stated the goal: {{Quotation|Above all else show the data| Tufte, 1983}}<br /> <br /> &lt;br&gt;<br /> <br /> {{quotation|A large share of ink on a graphic should present data-information, the ink changing as the data change. Data-ink is the non-erasable core of a graphic, the non-redundant ink arranged in response to <br /> <br /> variation in the numbers represented.|Tufte, 1983}}<br /> <br /> <br /> &lt;br&gt;<br /> <br /> <br /> Tufte refers to data-ink as the non-erasable ink used for the presentation of data. If data-ink would be removed from the image, the graphic would lose the content. Non-Data-Ink is accordingly the ink that does <br /> <br /> not transport the information but it is used for scales, labels and edges. The data-ink ratio is the proportion of Ink that is used to present actual data compared to the total amount of ink (or pixels) used in <br /> <br /> the entire display. (Ratio of Data-Ink to non-Data-Ink). <br /> <br /> <br /> [[Image:DIR.jpg|thumb|400px|center]]<br /> <br /> <br /> <br /> <br /> Good graphics should include only data-Ink. Non-Data-Ink is everywhere where possible to be deleted. The reason for this is to avoid the attention of viewers of the data presentation to irrelevant elements.&lt;br&gt;<br /> The goal is to design a display with the highest possible data-ink ratio (that is, as close to the total of 1.0), without eliminating something that is necessary for effective communication.<br /> <br /> == Example ==<br /> <br /> This is an example of a graph with a low Data-Ink Ratio.<br /> <br /> [[Image:Dir1.png|thumb|Low Data-Ink Ratio|400px|center]]<br /> <br /> <br /> The border around the graph, the background color and the grid lines are all unnecessary data ink.<br /> <br /> &lt;br&gt;<br /> <br /> <br /> Now an example of a graph with a high Data-Ink Ratio<br /> <br /> [[Image:Dir2.png|thumb|High Data-Ink Ratio|400px|center]]<br /> <br /> We have deleted the border around the graph, the background color and the grid lines and drowned the attention to horizontal scales that are data-ink. There is nothing else to distract and the key features of the data stand out clearly.<br /> &lt;br&gt;<br /> <br /> == Critisicm on Tufte's principles ==<br /> Inbar, et al, evaluated in 2007 the people's acceptance of the minimalist approach to visualize information. Therefore he asked 87 students to rate their preference for two different graphs displaying identical information - a standard bar-graph and a minimalist version. Both versions were taken from [Tufte, 1983]. [Inbar, 2007]<br /> <br /> The results showed that the majority students did not like Tufte's minimalist design of bar-graphs - instead they seem to prefer &quot;chartjunk&quot;. [Inbar, 2007]<br /> <br /> <br /> <br /> == Quellen ==<br /> <br /> [Few, 2004] Stephen Few. Elegance Through Simplicity. Created at: October 16, 2004. Retrieved at: October 25, 2005. http://www.intelligententerprise.com/showArticle.jhtml?articleID=49400920.<br /> <br /> [Few, Edge 2009] Stephen Few, . Perceptual Edge Sometimes We Must Raise Our Voices, Visual Business Intelligence Newsletter Created at: January/February 2009. http://www.perceptualedge.com/articles/visual_business_intelligence/sometimes_we_must_raise_our_voices.pdf.<br /> <br /> [Tufte, 1983] Edward Tufte. ''The Visual Display of Quantitative Information''. http://campusphere.de/datensicht/files/EdwardR.Tufte.%20Tufte<br /> <br /> Pictures: http://www.tbray.org/ongoing/data-ink/di1<br /> http://www.tbray.org/ongoing/data-ink/di5<br /> <br /> <br /> <br /> <br /> <br /> <br /> [[Category:Glossary]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=File:DIR.jpg&diff=22837 2009-11-05T23:15:42Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Beschreibung ==<br /> <br /> == Copyright status ==<br /> <br /> == Source ==<br /> <br /> self-made</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=File:DIR.jpg&diff=22836 2009-11-05T23:14:13Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Beschreibung ==<br /> <br /> == Copyright status ==<br /> <br /> == Source ==<br /> Selbst gemacht</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=File:Dir2.png&diff=22834 2009-11-05T23:12:55Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Beschreibung ==<br /> <br /> == Copyright status ==<br /> <br /> == Source ==<br /> http://www.tbray.org/ongoing/data-ink/di5</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=File:Dir1.png&diff=22833 2009-11-05T23:11:49Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Beschreibung ==<br /> <br /> == Copyright status ==<br /> <br /> == Source ==<br /> http://www.tbray.org/ongoing/data-ink/di1</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=Data-Ink_Ratio&diff=22829 2009-11-05T22:43:05Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Definitions ==<br /> <br /> The Data-Ink ratio is a concept introduced by Edward Tufte, the expert whose work has contributed significantly to designing effective data presentations. In his 1983 book, The Visual Display of Quantitative <br /> <br /> Data, he stated the goal: {{Quotation|Above all else show the data| Tufte, 1983}}<br /> <br /> &lt;br&gt;<br /> <br /> {{quotation|A large share of ink on a graphic should present data-information, the ink changing as the data change. Data-ink is the non-erasable core of a graphic, the non-redundant ink arranged in response to <br /> <br /> variation in the numbers represented.|Tufte, 1983}}<br /> <br /> <br /> &lt;br&gt;<br /> <br /> <br /> Tufte refers to data-ink as the non-erasable ink used for the presentation of data. If data-ink would be removed from the image, the graphic would lose the content. Non-Data-Ink is accordingly the ink that does <br /> <br /> not transport the information but it is used for scales, labels and edges. The data-ink ratio is the proportion of Ink that is used to present actual data compared to the total amount of ink (or pixels) used in <br /> <br /> the entire display. (Ratio of Data-Ink to non-Data-Ink). <br /> <br /> <br /> [[Image:DIR.jpg|thumb|400px|center]]<br /> <br /> <br /> <br /> <br /> Good graphics should include only data-Ink. Non-Data-Ink is everywhere where possible to be deleted. The reason for this is to avoid the attention of viewers of the data presentation to irrelevant elements.&lt;br&gt;<br /> The goal is to design a display with the highest possible data-ink ratio (that is, as close to the total of 1.0), without eliminating something that is necessary for effective communication.<br /> <br /> == Example ==<br /> <br /> This is an example of a graph with a low Data-Ink Ratio.<br /> <br /> [[Image:Dir1.png|thumb|Low Data-Ink Ratio|400px|center]]<br /> <br /> <br /> The border around the graph, the background color and the grid lines are all unnecessary data ink.<br /> <br /> &lt;br&gt;<br /> <br /> <br /> Now an example of a graph with a high Data-Ink Ratio<br /> <br /> [[Image:Dir2.png|thumb|High Data-Ink Ratio|400px|center]]<br /> <br /> We have deleted the border around the graph, the background color and the grid lines and drowned the attention to horizontal scales that are data-ink. There is nothing else to distract and the key features of the data stand out clearly.<br /> &lt;br&gt;<br /> <br /> == Critisicm on Tufte's principles ==<br /> Inbar, et al, evaluated in 2007 the people's acceptance of the minimalist approach to visualize information. Therefore he asked 87 students to rate their preference for two different graphs displaying identical information - a standard bar-graph and a minimalist version. Both versions were taken from [Tufte, 1983]. [Inbar, 2007]<br /> <br /> The results showed that the majority students did not like Tufte's minimalist design of bar-graphs - instead they seem to prefer &quot;chartjunk&quot;. [Inbar, 2007]<br /> <br /> <br /> <br /> == Quellen ==<br /> <br /> [Few, 2004] Stephen Few. Elegance Through Simplicity. Created at: October 16, 2004. Retrieved at: October 25, 2005. http://www.intelligententerprise.com/showArticle.jhtml?articleID=49400920.<br /> <br /> [Few, Edge 2009] Stephen Few, . Perceptual Edge Sometimes We Must Raise Our Voices, Visual Business Intelligence Newsletter Created at: January/February 2009. http://www.perceptualedge.com/articles/visual_business_intelligence/sometimes_we_must_raise_our_voices.pdf.<br /> <br /> [Tufte, 1983] Edward Tufte. ''The Visual Display of Quantitative Information''. http://campusphere.de/datensicht/files/EdwardR.Tufte.%20Tufte<br /> <br /> Pictures: http://www.tbray.org/ongoing/data-ink/di1<br /> <br /> <br /> <br /> <br /> <br /> <br /> [[Category:Glossary]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=Data-Ink_Ratio&diff=22828 2009-11-05T22:30:53Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Definitions ==<br /> <br /> The Data-Ink ratio is a concept introduced by Edward Tufte, the expert whose work has contributed significantly to designing effective data presentations. In his 1983 book, The Visual Display of Quantitative <br /> <br /> Data, he stated the goal: {{Quotation|Above all else show the data| Tufte, 1983}}<br /> <br /> &lt;br&gt;<br /> <br /> {{quotation|A large share of ink on a graphic should present data-information, the ink changing as the data change. Data-ink is the non-erasable core of a graphic, the non-redundant ink arranged in response to <br /> <br /> variation in the numbers represented.|Tufte, 1983}}<br /> <br /> <br /> &lt;br&gt;<br /> <br /> <br /> Tufte refers to data-ink as the non-erasable ink used for the presentation of data. If data-ink would be removed from the image, the graphic would lose the content. Non-Data-Ink is accordingly the ink that does <br /> <br /> not transport the information but it is used for scales, labels and edges. The data-ink ratio is the proportion of Ink that is used to present actual data compared to the total amount of ink (or pixels) used in <br /> <br /> the entire display. (Ratio of Data-Ink to non-Data-Ink). <br /> <br /> <br /> [[Image:DIR.jpg|thumb|400px|center]]<br /> <br /> <br /> <br /> <br /> Good graphics should include only data-Ink. Non-Data-Ink is everywhere where possible to be deleted. The reason for this is to avoid the attention of viewers of the data presentation to irrelevant elements.&lt;br&gt;<br /> The goal is to design a display with the highest possible data-ink ratio (that is, as close to the total of 1.0), without eliminating something that is necessary for effective communication.<br /> <br /> == Example ==<br /> <br /> This is an example of a graph with a low Data-Ink Ratio.<br /> <br /> [[Image:Dir1.png|thumb|Low Data-Ink Ratio|400px|center]]<br /> <br /> <br /> The border around the graph, the background color and the grid lines are all unnecessary data ink.<br /> <br /> &lt;br&gt;<br /> <br /> <br /> Now an example of a graph with a high Data-Ink Ratio<br /> <br /> [[Image:Dir2.png|thumb|High Data-Ink Ratio|400px|center]]<br /> <br /> We have deleted the border around the graph, the background color and the grid lines and drowned the attention to horizontal scales that are data-ink. There is nothing else to distract and the key features of the data stand out clearly.<br /> &lt;br&gt;<br /> <br /> == Critisicm on Tufte's principles ==<br /> Inbar, et al, evaluated in 2007 the people's acceptance of the minimalist approach to visualize information. Therefore he asked 87 students to rate their preference for two different graphs displaying identical information - a standard bar-graph and a minimalist version. Both versions were taken from [Tufte, 1983]. [Inbar, 2007]<br /> <br /> The results showed that the majority students did not like Tufte's minimalist design of bar-graphs - instead they seem to prefer &quot;chartjunk&quot;. [Inbar, 2007]<br /> <br /> <br /> <br /> == Bibliography ==<br /> <br /> [Hunt, 1997] Neville Hunt. Data Ink. Created at: 1997. Retrieved at: October 25, 2005. http://home.ched.coventry.ac.uk/Volume/vol0/dataink.htm|date=November 2009{{dead link}}.<br /> <br /> [Few, 2004] Stephen Few. Elegance Through Simplicity. Created at: October 16, 2004. Retrieved at: October 25, 2005. http://www.intelligententerprise.com/showArticle.jhtml?articleID=49400920.<br /> <br /> [Tufte, 1983] Edward Tufte. ''The Visual Display of Quantitative Information''. Graphics Press, Cheshire, 1983.<br /> <br /> [Inbar, 2007] Ohbad Inbar, Noam Tractinsky, Joachim Meyer. Minimalism in information visualization: attitudes towards maximizing the data-ink ratio. In ''ACM International Conference Proceeding Series; Vol. 250. Proceedings of the 14th European conference on Cognitive ergonomics: invent! explore!'', pages 185-188, London, United Kingdom, ACM, 2007<br /> <br /> <br /> <br /> <br /> [[Category:Glossary]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=Data-Ink_Ratio&diff=22827 2009-11-05T22:15:37Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Definitions ==<br /> <br /> The Data-Ink ratio is a concept introduced by Edward Tufte, the expert whose work has contributed significantly to designing effective data presentations. In his 1983 book, The Visual Display of Quantitative <br /> <br /> Data, he stated the goal: {{Quotation|Above all else show the data| Tufte, 1983}}<br /> <br /> &lt;br&gt;<br /> <br /> {{quotation|A large share of ink on a graphic should present data-information, the ink changing as the data change. Data-ink is the non-erasable core of a graphic, the non-redundant ink arranged in response to <br /> <br /> variation in the numbers represented.|Tufte, 1983}}<br /> <br /> <br /> &lt;br&gt;<br /> <br /> <br /> Tufte refers to data-ink as the non-erasable ink used for the presentation of data. If data-ink would be removed from the image, the graphic would lose the content. Non-Data-Ink is accordingly the ink that does <br /> <br /> not transport the information but it is used for scales, labels and edges. The data-ink ratio is the proportion of Ink that is used to present actual data compared to the total amount of ink (or pixels) used in <br /> <br /> the entire display. (Ratio of Data-Ink to non-Data-Ink). <br /> <br /> <br /> [[Image:DIR.jpg|thumb|400px|center]]<br /> <br /> <br /> <br /> <br /> Good graphics should include only data-Ink. Non-Data-Ink is everywhere where possible to be deleted. The reason for this is to avoid the attention of viewers of the data presentation to irrelevant elements.&lt;br&gt;<br /> The goal is to design a display with the highest possible data-ink ratio (that is, as close to the total of 1.0), without eliminating something that is necessary for effective communication.<br /> <br /> == Example ==<br /> <br /> First an example of a graph with a low Data-Ink Ratio<br /> <br /> [[Image:Dir1.png|thumb|Low Data-Ink Ratio|400px|center]]<br /> <br /> <br /> How much of the ink on this chart could be removed without loss of information?<br /> <br /> * The word &quot;Year&quot; is superflous<br /> * Only the first year needs to include the digits 19<br /> * Either the data labels or the vertical scale could be removed<br /> * The y-axis label is duplicated in the title<br /> * The bars need not be coloured<br /> <br /> &lt;br&gt;<br /> <br /> <br /> Now an example of a graph with a high Data-Ink Ratio<br /> <br /> [[Image:Dir2.png|thumb|High Data-Ink Ratio|400px|center]]<br /> <br /> This graph shows the revenue of three equally important service lines as it moves through the four quarters, but also the comparative performance of the three service lines in any one quarter.<br /> The three prominently displayed lines, without anything else to distract from them in the plot area of the graph, makes the key features of the data stand out clearly from the text data that surrounds them.<br /> <br /> == Critisicm on Tufte's principles ==<br /> Inbar, et al, evaluated in 2007 the people's acceptance of the minimalist approach to visualize information. Therefore he asked 87 students to rate their preference for two different graphs displaying identical information - a standard bar-graph and a minimalist version. Both versions were taken from [Tufte, 1983]. [Inbar, 2007]<br /> <br /> The results showed that the majority students did not like Tufte's minimalist design of bar-graphs - instead they seem to prefer &quot;chartjunk&quot;. [Inbar, 2007]<br /> <br /> <br /> <br /> == Bibliography ==<br /> <br /> [Hunt, 1997] Neville Hunt. Data Ink. Created at: 1997. Retrieved at: October 25, 2005. http://home.ched.coventry.ac.uk/Volume/vol0/dataink.htm|date=November 2009{{dead link}}.<br /> <br /> [Few, 2004] Stephen Few. Elegance Through Simplicity. Created at: October 16, 2004. Retrieved at: October 25, 2005. http://www.intelligententerprise.com/showArticle.jhtml?articleID=49400920.<br /> <br /> [Tufte, 1983] Edward Tufte. ''The Visual Display of Quantitative Information''. Graphics Press, Cheshire, 1983.<br /> <br /> [Inbar, 2007] Ohbad Inbar, Noam Tractinsky, Joachim Meyer. Minimalism in information visualization: attitudes towards maximizing the data-ink ratio. In ''ACM International Conference Proceeding Series; Vol. 250. Proceedings of the 14th European conference on Cognitive ergonomics: invent! explore!'', pages 185-188, London, United Kingdom, ACM, 2007<br /> <br /> <br /> <br /> <br /> [[Category:Glossary]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=File:Dir2.png&diff=22826 2009-11-05T22:11:59Z

<p>UE-InfoVis0910 0126013: New page: == Beschreibung == == Copyright status == == Source ==</p> <hr /> <div>== Beschreibung ==<br /> <br /> == Copyright status ==<br /> <br /> == Source ==</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=Data-Ink_Ratio&diff=22825 2009-11-05T22:11:37Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Definitions ==<br /> <br /> The Data-Ink ratio is a concept introduced by Edward Tufte, the expert whose work has contributed significantly to designing effective data presentations. In his 1983 book, The Visual Display of Quantitative <br /> <br /> Data, he stated the goal: {{Quotation|Above all else show the data| Tufte, 1983}}<br /> <br /> &lt;br&gt;<br /> <br /> {{quotation|A large share of ink on a graphic should present data-information, the ink changing as the data change. Data-ink is the non-erasable core of a graphic, the non-redundant ink arranged in response to <br /> <br /> variation in the numbers represented.|Tufte, 1983}}<br /> <br /> <br /> &lt;br&gt;<br /> <br /> <br /> Tufte refers to data-ink as the non-erasable ink used for the presentation of data. If data-ink would be removed from the image, the graphic would lose the content. Non-Data-Ink is accordingly the ink that does <br /> <br /> not transport the information but it is used for scales, labels and edges. The data-ink ratio is the proportion of Ink that is used to present actual data compared to the total amount of ink (or pixels) used in <br /> <br /> the entire display. (Ratio of Data-Ink to non-Data-Ink). <br /> <br /> <br /> [[Image:DIR.jpg|thumb|400px|center]]<br /> <br /> <br /> <br /> Good graphics should include only data-Ink. Non-Data-Ink is everywhere where possible to be deleted. The reason for this is to avoid the attention of viewers of the data presentation to irrelevant elements.&lt;br&gt;<br /> The goal is to design a display with the highest possible data-ink ratio (that is, as close to the total of 1.0), without eliminating something that is necessary for effective communication.<br /> <br /> == Example ==<br /> <br /> First an example of a graph with a low Data-Ink Ratio<br /> <br /> [[Image:Dir1.png|thumb|400px|center]]<br /> <br /> <br /> How much of the ink on this chart could be removed without loss of information?<br /> <br /> * The word &quot;Year&quot; is superflous<br /> * Only the first year needs to include the digits 19<br /> * Either the data labels or the vertical scale could be removed<br /> * The y-axis label is duplicated in the title<br /> * The bars need not be coloured<br /> <br /> &lt;br&gt;<br /> <br /> <br /> Now an example of a graph with a high Data-Ink Ratio<br /> <br /> [[Image:Dir2.png|thumb|400px|center]]<br /> <br /> This graph shows the revenue of three equally important service lines as it moves through the four quarters, but also the comparative performance of the three service lines in any one quarter.<br /> The three prominently displayed lines, without anything else to distract from them in the plot area of the graph, makes the key features of the data stand out clearly from the text data that surrounds them.<br /> <br /> == Critisicm on Tufte's principles ==<br /> Inbar, et al, evaluated in 2007 the people's acceptance of the minimalist approach to visualize information. Therefore he asked 87 students to rate their preference for two different graphs displaying identical information - a standard bar-graph and a minimalist version. Both versions were taken from [Tufte, 1983]. [Inbar, 2007]<br /> <br /> The results showed that the majority students did not like Tufte's minimalist design of bar-graphs - instead they seem to prefer &quot;chartjunk&quot;. [Inbar, 2007]<br /> <br /> <br /> <br /> == Bibliography ==<br /> <br /> [Hunt, 1997] Neville Hunt. Data Ink. Created at: 1997. Retrieved at: October 25, 2005. http://home.ched.coventry.ac.uk/Volume/vol0/dataink.htm|date=November 2009{{dead link}}.<br /> <br /> [Few, 2004] Stephen Few. Elegance Through Simplicity. Created at: October 16, 2004. Retrieved at: October 25, 2005. http://www.intelligententerprise.com/showArticle.jhtml?articleID=49400920.<br /> <br /> [Tufte, 1983] Edward Tufte. ''The Visual Display of Quantitative Information''. Graphics Press, Cheshire, 1983.<br /> <br /> [Inbar, 2007] Ohbad Inbar, Noam Tractinsky, Joachim Meyer. Minimalism in information visualization: attitudes towards maximizing the data-ink ratio. In ''ACM International Conference Proceeding Series; Vol. 250. Proceedings of the 14th European conference on Cognitive ergonomics: invent! explore!'', pages 185-188, London, United Kingdom, ACM, 2007<br /> <br /> <br /> <br /> <br /> [[Category:Glossary]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=Data-Ink_Ratio&diff=22824 2009-11-05T22:10:27Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Definitions ==<br /> <br /> The Data-Ink ratio is a concept introduced by Edward Tufte, the expert whose work has contributed significantly to designing effective data presentations. In his 1983 book, The Visual Display of Quantitative <br /> <br /> Data, he stated the goal: {{Quotation|Above all else show the data| Tufte, 1983}}<br /> <br /> &lt;br&gt;<br /> <br /> {{quotation|A large share of ink on a graphic should present data-information, the ink changing as the data change. Data-ink is the non-erasable core of a graphic, the non-redundant ink arranged in response to <br /> <br /> variation in the numbers represented.|Tufte, 1983}}<br /> <br /> <br /> &lt;br&gt;<br /> <br /> <br /> Tufte refers to data-ink as the non-erasable ink used for the presentation of data. If data-ink would be removed from the image, the graphic would lose the content. Non-Data-Ink is accordingly the ink that does <br /> <br /> not transport the information but it is used for scales, labels and edges. The data-ink ratio is the proportion of Ink that is used to present actual data compared to the total amount of ink (or pixels) used in <br /> <br /> the entire display. (Ratio of Data-Ink to non-Data-Ink). <br /> <br /> <br /> [[Image:DIR.jpg|thumb|400px|center]]<br /> <br /> <br /> <br /> Good graphics should include only data-Ink. Non-Data-Ink is everywhere where possible to be deleted. The reason for this is to avoid the attention of viewers of the data presentation to irrelevant elements.&lt;br&gt;<br /> The goal is to design a display with the highest possible data-ink ratio (that is, as close to the total of 1.0), without eliminating something that is necessary for effective communication.<br /> <br /> == Example ==<br /> <br /> First an example of a graph with a low Data-Ink Ratio<br /> <br /> [[Image:Dir1.png|thumb|400px|center]]<br /> [[Image:Dir1.png|thumb|Beschreibung]]<br /> <br /> How much of the ink on this chart could be removed without loss of information?<br /> <br /> * The word &quot;Year&quot; is superflous<br /> * Only the first year needs to include the digits 19<br /> * Either the data labels or the vertical scale could be removed<br /> * The y-axis label is duplicated in the title<br /> * The bars need not be coloured<br /> <br /> &lt;br&gt;<br /> <br /> <br /> Now an example of a graph with a high Data-Ink Ratio<br /> <br /> [[Image:DIR2.jpg|thumb|400px|center]]<br /> <br /> This graph shows the revenue of three equally important service lines as it moves through the four quarters, but also the comparative performance of the three service lines in any one quarter.<br /> The three prominently displayed lines, without anything else to distract from them in the plot area of the graph, makes the key features of the data stand out clearly from the text data that surrounds them.<br /> <br /> == Critisicm on Tufte's principles ==<br /> Inbar, et al, evaluated in 2007 the people's acceptance of the minimalist approach to visualize information. Therefore he asked 87 students to rate their preference for two different graphs displaying identical information - a standard bar-graph and a minimalist version. Both versions were taken from [Tufte, 1983]. [Inbar, 2007]<br /> <br /> The results showed that the majority students did not like Tufte's minimalist design of bar-graphs - instead they seem to prefer &quot;chartjunk&quot;. [Inbar, 2007]<br /> <br /> <br /> <br /> == Bibliography ==<br /> <br /> [Hunt, 1997] Neville Hunt. Data Ink. Created at: 1997. Retrieved at: October 25, 2005. http://home.ched.coventry.ac.uk/Volume/vol0/dataink.htm|date=November 2009{{dead link}}.<br /> <br /> [Few, 2004] Stephen Few. Elegance Through Simplicity. Created at: October 16, 2004. Retrieved at: October 25, 2005. http://www.intelligententerprise.com/showArticle.jhtml?articleID=49400920.<br /> <br /> [Tufte, 1983] Edward Tufte. ''The Visual Display of Quantitative Information''. Graphics Press, Cheshire, 1983.<br /> <br /> [Inbar, 2007] Ohbad Inbar, Noam Tractinsky, Joachim Meyer. Minimalism in information visualization: attitudes towards maximizing the data-ink ratio. In ''ACM International Conference Proceeding Series; Vol. 250. Proceedings of the 14th European conference on Cognitive ergonomics: invent! explore!'', pages 185-188, London, United Kingdom, ACM, 2007<br /> <br /> <br /> <br /> <br /> [[Category:Glossary]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=File:Dir1.png&diff=22823 2009-11-05T22:08:24Z

<p>UE-InfoVis0910 0126013: New page: == Beschreibung == == Copyright status == == Source ==</p> <hr /> <div>== Beschreibung ==<br /> <br /> == Copyright status ==<br /> <br /> == Source ==</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=Data-Ink_Ratio&diff=22822 2009-11-05T22:04:02Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Definitions ==<br /> <br /> The Data-Ink ratio is a concept introduced by Edward Tufte, the expert whose work has contributed significantly to designing effective data presentations. In his 1983 book, The Visual Display of Quantitative <br /> <br /> Data, he stated the goal: {{Quotation|Above all else show the data| Tufte, 1983}}<br /> <br /> &lt;br&gt;<br /> <br /> {{quotation|A large share of ink on a graphic should present data-information, the ink changing as the data change. Data-ink is the non-erasable core of a graphic, the non-redundant ink arranged in response to <br /> <br /> variation in the numbers represented.|Tufte, 1983}}<br /> <br /> <br /> &lt;br&gt;<br /> <br /> <br /> Tufte refers to data-ink as the non-erasable ink used for the presentation of data. If data-ink would be removed from the image, the graphic would lose the content. Non-Data-Ink is accordingly the ink that does <br /> <br /> not transport the information but it is used for scales, labels and edges. The data-ink ratio is the proportion of Ink that is used to present actual data compared to the total amount of ink (or pixels) used in <br /> <br /> the entire display. (Ratio of Data-Ink to non-Data-Ink). <br /> <br /> <br /> [[Image:DIR.jpg|thumb|400px|center]]<br /> <br /> <br /> <br /> Good graphics should include only data-Ink. Non-Data-Ink is everywhere where possible to be deleted. The reason for this is to avoid the attention of viewers of the data presentation to irrelevant elements.&lt;br&gt;<br /> The goal is to design a display with the highest possible data-ink ratio (that is, as close to the total of 1.0), without eliminating something that is necessary for effective communication.<br /> <br /> == Example ==<br /> <br /> First an example of a graph with a low Data-Ink Ratio<br /> <br /> [[Image:DIR.gif|thumb|400px|center]]<br /> <br /> How much of the ink on this chart could be removed without loss of information?<br /> <br /> * The word &quot;Year&quot; is superflous<br /> * Only the first year needs to include the digits 19<br /> * Either the data labels or the vertical scale could be removed<br /> * The y-axis label is duplicated in the title<br /> * The bars need not be coloured<br /> <br /> &lt;br&gt;<br /> <br /> <br /> Now an example of a graph with a high Data-Ink Ratio<br /> <br /> [[Image:DIR2.jpg|thumb|400px|center]]<br /> <br /> This graph shows the revenue of three equally important service lines as it moves through the four quarters, but also the comparative performance of the three service lines in any one quarter.<br /> The three prominently displayed lines, without anything else to distract from them in the plot area of the graph, makes the key features of the data stand out clearly from the text data that surrounds them.<br /> <br /> == Critisicm on Tufte's principles ==<br /> Inbar, et al, evaluated in 2007 the people's acceptance of the minimalist approach to visualize information. Therefore he asked 87 students to rate their preference for two different graphs displaying identical information - a standard bar-graph and a minimalist version. Both versions were taken from [Tufte, 1983]. [Inbar, 2007]<br /> <br /> The results showed that the majority students did not like Tufte's minimalist design of bar-graphs - instead they seem to prefer &quot;chartjunk&quot;. [Inbar, 2007]<br /> <br /> <br /> <br /> == Bibliography ==<br /> <br /> [Hunt, 1997] Neville Hunt. Data Ink. Created at: 1997. Retrieved at: October 25, 2005. http://home.ched.coventry.ac.uk/Volume/vol0/dataink.htm|date=November 2009{{dead link}}.<br /> <br /> [Few, 2004] Stephen Few. Elegance Through Simplicity. Created at: October 16, 2004. Retrieved at: October 25, 2005. http://www.intelligententerprise.com/showArticle.jhtml?articleID=49400920.<br /> <br /> [Tufte, 1983] Edward Tufte. ''The Visual Display of Quantitative Information''. Graphics Press, Cheshire, 1983.<br /> <br /> [Inbar, 2007] Ohbad Inbar, Noam Tractinsky, Joachim Meyer. Minimalism in information visualization: attitudes towards maximizing the data-ink ratio. In ''ACM International Conference Proceeding Series; Vol. 250. Proceedings of the 14th European conference on Cognitive ergonomics: invent! explore!'', pages 185-188, London, United Kingdom, ACM, 2007<br /> <br /> <br /> <br /> <br /> [[Category:Glossary]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=Data-Ink_Ratio&diff=22821 2009-11-05T21:58:27Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Definitions ==<br /> <br /> The Data-Ink ratio is a concept introduced by Edward Tufte, the expert whose work has contributed significantly to designing effective data presentations. In his 1983 book, The Visual Display of Quantitative <br /> <br /> Data, he stated the goal: {{Quotation|Above all else show the data| Tufte, 1983}}<br /> <br /> &lt;br&gt;<br /> <br /> {{quotation|A large share of ink on a graphic should present data-information, the ink changing as the data change. Data-ink is the non-erasable core of a graphic, the non-redundant ink arranged in response to <br /> <br /> variation in the numbers represented.|Tufte, 1983}}<br /> <br /> <br /> &lt;br&gt;<br /> <br /> <br /> Tufte refers to data-ink as the non-erasable ink used for the presentation of data. If data-ink would be removed from the image, the graphic would lose the content. Non-Data-Ink is accordingly the ink that does <br /> <br /> not transport the information but it is used for scales, labels and edges. The data-ink ratio is the proportion of Ink that is used to present actual data compared to the total amount of ink (or pixels) used in <br /> <br /> the entire display. (Ratio of Data-Ink to non-Data-Ink). <br /> <br /> <br /> [[Image:DIR.jpg|thumb|400px|center]]<br /> <br /> <br /> <br /> Good graphics should include only data-Ink. Non-Data-Ink is everywhere where possible to be deleted. The reason for this is to avoid the attention of viewers of the data presentation to irrelevant elements.<br /> The goal is to design a display with the highest possible data-ink ratio (that is, as close to the total of 1.0), without eliminating something that is necessary for effective communication.<br /> <br /> == Example ==<br /> <br /> First an example of a graph with a low Data-Ink Ratio<br /> <br /> [[Image:DIR.gif|thumb|400px|center]]<br /> <br /> How much of the ink on this chart could be removed without loss of information?<br /> <br /> * The word &quot;Year&quot; is superflous<br /> * Only the first year needs to include the digits 19<br /> * Either the data labels or the vertical scale could be removed<br /> * The y-axis label is duplicated in the title<br /> * The bars need not be coloured<br /> <br /> &lt;br&gt;<br /> <br /> <br /> Now an example of a graph with a high Data-Ink Ratio<br /> <br /> [[Image:DIR2.jpg|thumb|400px|center]]<br /> <br /> This graph shows the revenue of three equally important service lines as it moves through the four quarters, but also the comparative performance of the three service lines in any one quarter.<br /> The three prominently displayed lines, without anything else to distract from them in the plot area of the graph, makes the key features of the data stand out clearly from the text data that surrounds them.<br /> <br /> == Critisicm on Tufte's principles ==<br /> Inbar, et al, evaluated in 2007 the people's acceptance of the minimalist approach to visualize information. Therefore he asked 87 students to rate their preference for two different graphs displaying identical information - a standard bar-graph and a minimalist version. Both versions were taken from [Tufte, 1983]. [Inbar, 2007]<br /> <br /> The results showed that the majority students did not like Tufte's minimalist design of bar-graphs - instead they seem to prefer &quot;chartjunk&quot;. [Inbar, 2007]<br /> <br /> <br /> <br /> == Bibliography ==<br /> <br /> [Hunt, 1997] Neville Hunt. Data Ink. Created at: 1997. Retrieved at: October 25, 2005. http://home.ched.coventry.ac.uk/Volume/vol0/dataink.htm|date=November 2009{{dead link}}.<br /> <br /> [Few, 2004] Stephen Few. Elegance Through Simplicity. Created at: October 16, 2004. Retrieved at: October 25, 2005. http://www.intelligententerprise.com/showArticle.jhtml?articleID=49400920.<br /> <br /> [Tufte, 1983] Edward Tufte. ''The Visual Display of Quantitative Information''. Graphics Press, Cheshire, 1983.<br /> <br /> [Inbar, 2007] Ohbad Inbar, Noam Tractinsky, Joachim Meyer. Minimalism in information visualization: attitudes towards maximizing the data-ink ratio. In ''ACM International Conference Proceeding Series; Vol. 250. Proceedings of the 14th European conference on Cognitive ergonomics: invent! explore!'', pages 185-188, London, United Kingdom, ACM, 2007<br /> <br /> <br /> <br /> <br /> [[Category:Glossary]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=File:DIR.jpg&diff=22819 2009-11-05T21:56:17Z

<p>UE-InfoVis0910 0126013: New page: == Beschreibung == == Copyright status == == Source ==</p> <hr /> <div>== Beschreibung ==<br /> <br /> == Copyright status ==<br /> <br /> == Source ==</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=User:UE-InfoVis0910_0126013&diff=22437 2009-11-03T06:58:01Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>Name, Vorname: Martina Saric &lt;br&gt;<br /> <br /> Matrikelnummer: 0126013 &lt;br&gt;<br /> <br /> E-Mail: martina.pixmade@gmail.com &lt;br&gt;<br /> <br /> [[Image:Martina.JPG|thumb|left]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2009/10&diff=22436 2009-11-03T06:50:45Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>[[Image:Aigner03infovis ue.gif]] &lt;big&gt;WS 2009/10&lt;/big&gt;<br /> <br /> '''LVA Nr:''' 188.308 ([http://tuwis.tuwien.ac.at/lva/tuwien/188308 TUWIS++ Seite])<br /> <br /> '''LVA Homepage:''' http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/index.html<br /> <br /> '''Leitung:''' [[Gschwandtner, Theresia|Theresia Gschwandtner]] [gschwandtner (at) ifs.tuwien.ac.at]&lt;br&gt;<br /> '''Tutorin:''' [[User:Katharina-Anna Wendelin|Katharina-Anna Wendelin]] [e0425160 (at) student.tuwien.ac.at]<br /> <br /> <br /> == Gruppen ==<br /> &lt;!-- <br /> Gruppenlinks hier einfügen!<br /> Beispiel:<br /> *[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe XX|Gruppe XX]]<br /> &quot;XX&quot; durch Gruppennummer ersetzen!<br /> --&gt;<br /> <br /> [[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 02|Gruppe 02 (Feichtinger, Rezaei, Schindelka)]]<br /> <br /> [[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 03|Gruppe 03 (Lang, Hackl, Hasslacher)]]<br /> <br /> [[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 04|Gruppe 04 (Kaiser, Ehsani, Sverak)]]<br /> <br /> [[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 05|Gruppe 05 (Paizoni, Wuttej, Hudl)]]<br /> <br /> [[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 06|Gruppe 06 (Fried, Fritz, Hiller)]]<br /> <br /> [[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08|Gruppe 08 (Saric, Olea, Schwengerer)]]<br /> <br /> [[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 09|Gruppe 09 (Hubmann-Haidvogel, Kloibhofer, Riederer)]]<br /> <br /> [[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 10|Gruppe 10 (Kickinger, Ramsauer, Wittmann)]]<br /> <br /> [[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 11|Gruppe 11 (Gastecker, Hahn, Leeb)]]<br /> <br /> [[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 12|Gruppe 12 (Bauer, Eigner, Sakai)]]<br /> <br /> [[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 13|Gruppe 13 (Sadauskas, Scheikl, Burger)]]<br /> <br /> [[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 15|Gruppe 15 (Martin, Stix, Lenzhofer)]]<br /> <br /> == News / Bemerkungen ==<br /> <br /> Liebe TeilnehmerInnen! &lt;br&gt;<br /> Die vorläufige Bewertung der Aufgabe 0 ist nun auf eurer Gruppenseite <br /> (unter Aufgabe 0 - discussion page) abrufbar.<br /> Es besteht die Möglichkeit, euren aktuellen Punktestand (Maximum: 5 Punkte) <br /> bis einschließlich Fr., den 06. 11. 2009 23:59 zu verbessern. &lt;br&gt;&lt;br&gt;--[[User:Katharina-Anna Wendelin|Katharina-Anna Wendelin]] 11:42, 30 October 2009<br /> <br /> Liebe TeilnehmerInnen!&lt;br&gt;<br /> Die Links zu Aufgabe 1 (Auszubessernde InfoVis Begriffe) sind nun auf eurer Gruppenseite &lt;br&gt;unter &quot;Aufgabe 1&quot; zu finden.<br /> Achtung: die Aufgabenstellung hat sich im Vergleich zum Vorjahr geändert! &lt;br&gt;(siehe http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe1.html) &lt;br&gt; &lt;br&gt;-- [[User:Katharina-Anna Wendelin|Katharina-Anna Wendelin]] 21:18, 29 October 2009 (CEST)<br /> <br /> Liebe TeilnehmerInnen,&lt;br&gt;<br /> fügt bitte Gruppen mit nur einem oder zwei Mitgliedern selbstständig zusammen, <br /> z.B., Martin Schwengerer geht zur Gruppe 08 und Gruppe 12 verteilt sich auf Gruppe 01 und Gruppe 04.&lt;br&gt;<br /> Wie ihr euch umverteilt überlasse ich euch. Sollte das nicht funktionieren, bitte ich um <br /> Rückmeldung bis morgen, dann muss ich &quot;nachhelfen&quot; ;).&lt;br&gt; <br /> Vielen Dank!&lt;br&gt;<br /> -- [[Gschwandtner, Theresia|Theresia Gschwandtner]] 07:27, 29 October 2009 (CEST)<br /> <br /> Liebe TeilnehmerInnen,&lt;br&gt; <br /> aus Datenschutz-Gründen bitte ich euch eure Martrikelnummer<br /> nicht auf eurer InfoVis:Wiki Userseite anzugeben.&lt;br&gt; <br /> Vielen Dank!&lt;br&gt; <br /> -- [[Gschwandtner, Theresia|Theresia Gschwandtner]] 09:40, 27 October 2009 (CEST)<br /> <br /> Liebe TeilnehmerInnen!&lt;br&gt;<br /> Um diese Seite einheitlich zu gestalten (auch bezüglich der Vorjahre), schlage ich vor die Nachnamen <br /> der Gruppenmitglieder in Klammer neben der Gruppe anzugeben,&lt;br&gt; <br /> z.B.: Gruppe XX (Maier, Müller, Mustermann).&lt;br&gt;<br /> -- [[Gschwandtner, Theresia|Theresia Gschwandtner]] 10:05, 01 October 2009 (CEST)</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2009/10_-_Gruppe_08&diff=22435 2009-11-03T06:42:48Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>== Gruppenmitglieder ==<br /> [[User:UE-InfoVis0910_0426516|Olea, Christian]]&lt;br/&gt;<br /> [[User:UE-InfoVis0910_0126013|Saric, Martina]]&lt;br/&gt;<br /> [[User:UE-InfoVis0910_0625209|Schwengerer, Martin]]<br /> <br /> == Aufgaben ==<br /> [[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08 - Aufgabe 0|Aufgabe 0]]&lt;br/&gt;<br /> [[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08 - Aufgabe 1|Aufgabe 1]]&lt;br/&gt;<br /> [[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08 - Aufgabe 2|Aufgabe 2]]&lt;br/&gt;<br /> [[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08 - Aufgabe 3|Aufgabe 3]]&lt;br/&gt;<br /> [[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 08 - Aufgabe 4|Aufgabe 4]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=User:UE-InfoVis0910_0126013&diff=22434 2009-11-03T06:37:53Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>Name, Vorname: Martina Saric &lt;br&gt;<br /> <br /> Matrikelnummer: 0126013 &lt;br&gt;<br /> <br /> E-Mail: martina.pixmade@gmail.com &lt;br&gt;<br /> <br /> [[Image:Martina.JPG|thumb|Beschreibung]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=User:UE-InfoVis0910_0126013&diff=22433 2009-11-03T06:35:40Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>Name, Vorname: Martina Saric<br /> Matrikelnummer: 0126013<br /> E-Mail: martina.pixmade@gmail.com<br /> [[Image:Martina.JPG|thumb|Beschreibung]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=User:UE-InfoVis0910_0126013&diff=22432 2009-11-03T06:33:46Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>Martina Saric<br /> [[Image:Martina.JPG|thumb|Beschreibung]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=User:UE-InfoVis0910_0126013&diff=22431 2009-11-03T06:32:19Z

<p>UE-InfoVis0910 0126013: </p> <hr /> <div>Martina Saric<br /> [[Image:Martina.jpg]]</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=User:UE-InfoVis0910_0126013&diff=22430 2009-11-03T06:31:24Z

<p>UE-InfoVis0910 0126013: New page: Martina Saric</p> <hr /> <div>Martina Saric</div>

UE-InfoVis0910 0126013 https://infovis-wiki.net/w/index.php?title=File:Martina.JPG&diff=22429 2009-11-03T06:29:11Z

<p>UE-InfoVis0910 0126013: New page: == Summary == == Copyright status == == Source ==</p> <hr /> <div>== Summary ==<br /> <br /> == Copyright status ==<br /> <br /> == Source ==</div>

UE-InfoVis0910 0126013