InfoVis:Wiki - User contributions [en]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 4

2008-02-29T19:15:00Z

UE-InfoVis0708 0527260:

== Aufgabenstellung ==

Aufgabe ist das Design einer interaktiven Visualisierungsapplikation zur Darstellung und Exploration (des zeitlichen Verlaufs) von Laborwerten einer Blutuntersuchung. BenutzerInnen, Einsatzzweck, Tasks, etc. sollen von Euch selbst festgelegt und beschrieben werden.

[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]

=== Beispiele für derartige Datensätze ===

[[Image:20061115_blutuntersuchung.jpg]]

[[Image:20070920_blutuntersuchung.jpg]]

== Description of the application area, the dataset, the users and the duties ==
=== Description of the application area and of the given dataset ===
 Application area analysis – Routine medical blood test in hospitals. 
'''Specifics:'''
*the given data implements a small and a big blood count
*the most important data fields are labelled through a * (these data is outside of the normal reference area)

=== Target group analysis ===
 After we confer with some doctors and nurses, we know that it wouldn’t make sense to visualize the whole blood count. The doctors are satisfied with the actual situation (blood counts in a table in which the important data is signed through a *), because of the easy handling and the well arranged data. Therefore we want to do a special visualisation for nurses, which show them the important data which they need to take care of the state of their patients. Nurses have to look at variations in the blood count. 

An example of use would be patients at the intensive care. They need routine blood counts during their sheltering at the hospital. 

It would definitely draw a distinction if the visualisation would be made for a nurse or a doctor. Nurses didn’t mind about the whole dataset, they only have to look up variations. Only the doctors need the detailed blood count. 

'''Specifics:''' 
*Nurses even know all medical terms but they don’t need the whole information of the blood count. The variances are enough.
=== Dataset analysis ===
 '''Description of the data type of the dataset''' 
The measured blood count values are ordinal and continuous. The values of blood counts could change with each measurement.The reference values are ordinal and discrete, because the reference areas are a fixed medical demand. 
 '''Description of the data structure of the dataset''' 
The dataset is multidimensional and temporal. But over the time you could draw conclusions from the collected blood counts, so the values get dependent over time.

At the first look the dataset values seem to be independent of each other. There could even be varying measured values in different blood counts. But it is possible to group some dataset values for special applications. For example it could be in the doctor's interest to group the values, which belong to a certain organ or which indicate certain a diseases.

=== Aim of the visualization ===
 Nurses can easily look up variations of the blood count through the visualisation. For example could a variation of the blood values cause a drastically situation for people keeping a comatose. 
Therefore it is important to visualize the data out of the reference range. This could be a solution for the following question: 
*Is the actual status of the patient better or worse? 

----

== Concept ==
=== Types of Visualization ===
 
*For each patient an own pie-chart with extensions
*The label above the pie-cart is the patient name
*The number of the pie slices is equal to the sum of the most important data labelled through a * 

A label inside of the pie-chart gives you information about the examination and the result of it. If the dataset of the blood count diversify after a new examination, the specific pie slices will be labelled spatial or though colouring. Therefore the visualisation of the pie will be maximized through volume expansion coloured in red or green. Inside this new bigger pie-chart it is possible to look up the percentage-wise values of the comparison between the last two examinations. 

The centre of the pie-chart is visualized through a calendar sheet and the time of the examination. Per mouse click on the calendar sheet it is possible to get an overview about the last ten examination results. If there are more examination results you can click on the button ”add earlier blood counts” to upgrade the existing list.

=== Visual Mapping ===
 
*For each through a * marked value, we will create an own pie slice labelled by the actual examination value.
*All slices have the same size. We focus our diagram on the results of the variations of the examinations and not on the specific values.
*Each examination name (for example, hdl cholesterol, choli,...) has a unique colour. So it would be possible to relate them easily.
*The date of examination will be visualized intuitive through a calendar sheet.
*Positive variations (the examination value fit back into the reference area) are marked in green colour / Negative variations are marked red.

=== Techniques ===

In our approach we use an icon-based technique to display the blood counts. Icons are well fitted for multivariate data sets and to reduce the huge amount of data. It is also easy to show data changes with them.

=== Interaction possibilities ===
[[Image:patientSoftware1_low.jpg|thumb|180px|Pic.1 GUI of the PatientSoftware]]

[[Image:patientSoftware2_low.jpg|thumb|180px|Pic.2 Detailview of one patient]]

[[Image:patientSoftware3_low.jpg|thumb|180px|Pic.3 Functionality of the software]]

[[Image:patientSoftware4_low.jpg|thumb|180px|Pic.4 Bloodcount of one patient]]

 ''' Interaction with the system ''' 
 Overall View: 
*In the overall view every patient is symbolized by a mini pie chart
*Double clicking the mini pie chart takes you to the detail view of the respective patient
*The overall view is underlayed with a grey layer to show its inactive and the detail view is shown above it in form of a big pie chart
*A click on the gray underlayed background takes you back from the detail view to the overall view
*There exists a search field, with which you can search after patient names
*A measured value beyond the reference range is symbolized by a red blinking mini pie chart. The mini pie chart blinks till it got investigated in the detail view
 Detail view: 
*Clicking the calendar symbol shows you a list with the last ten blood counts. individual blood counts are distinguishable by the means of ther creation date. if there are more than ten blood counts, the extra entry 'add earlier blodd counts' will be shown. clicking this entry opens a new window containing all the blood counts. the user can choose one ore more blood counts which will be added in the list.
*By clicking the '+add' button new analyzed values are added in the pie chart
*By clicking the '-rem' button a previously shown value can be removed from the pie chart
*By clicking the 'blood count' button, the full blood count in standardized table form is shown
*By moving the mouse cursor over pie piece the reference range is shown as toll tip

 '''Aim of interactions''' 
 

*The overall view shows only the most important data and enables through that an easy handling.
*For more detailed information it is possible to change into the detail view or to call up the blood count function (the blood count as a classical table).
*Red blinking pie charts in the overall view signal that the values of the patient get worth. The nurse is able to apply necessary steps.
*It is possible to add or remove special blood count values to make an individual pie chart for each patient.
*The function of the calendar allows calling up old blood counts. So the nurses have the possibility to compare actual and old blood counts without any administration effort.

=== Support for the user ===
 
*Assuming that the blood counts stored digitally we visualize only the important data (marked through *) of the blood counts but it is possible to add more examination values if it is needed.
*Variations between the different examination values are inserted/updated automatically.
*Negative variations are highlighted trough a red blinking light.
*The calendar sheet offers you the possibility to look up older examination results.
*Through a mouse click on the button “blood count” it is possible to switch to the original blood count view.

=== Specifics ===
 There is not only the detailed view, and the pie-chart view you could also open the overall view which shows you the pie – diagrams of the whole station in hospital. So it is possible for the nurses to get a general overview of the worse red marked values. Additionally will new worse examination data blink red, until the nurse has opened the pie-chart view.

=== Advantages and Disadvantages ===
 
*We only visualize the most important data for the nurses. Even so it is possible to check out the whole information easily.
*It is easily possible to watch out special examination values trough adding or removing of special examination values to the pie-chart view.
*The new red blinking data, advert the nurses to look up the new information.
*A Disadvantage for doctors could be that you can’t see the whole blood count on the first glance.

=== Expansion Possiblities ===
 To combine the software of the hospital with our blood count software would offer some extension possibilities. For example it would be possible to show the whole patient information by one click or the nurse could directly inform a doctor if some values exploded.

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06|Gruppe 06]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 4

2008-02-29T11:24:27Z

UE-InfoVis0708 0527260:

== Aufgabenstellung ==

Aufgabe ist das Design einer interaktiven Visualisierungsapplikation zur Darstellung und Exploration (des zeitlichen Verlaufs) von Laborwerten einer Blutuntersuchung. BenutzerInnen, Einsatzzweck, Tasks, etc. sollen von Euch selbst festgelegt und beschrieben werden.

[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]

=== Beispiele für derartige Datensätze ===

[[Image:20061115_blutuntersuchung.jpg]]

[[Image:20070920_blutuntersuchung.jpg]]

== Description of the application area, the dataset, the users and the duties ==
=== Description of the application area and of the given dataset ===
 Application area analysis – Routine medical blood test in hospitals. 
'''Specifics:'''
*the given data implements a small and a big blood count
*the most important data fields are labelled through a * (these data is outside of the normal reference area)

=== Target group analysis ===
 After we confer with some doctors and nurses, we know that it wouldn’t make sense to visualize the whole blood count. The doctors are satisfied with the actual situation (blood counts in a table in which the important data is signed through a *), because of the easy handling and the well arranged data. Therefore we want to do a special visualisation for nurses, which show them the important data which they need to take care of the state of their patients. Nurses have to look at variations in the blood count. 

An example of use would be patients at the intensive care. They need routine blood counts during their sheltering at the hospital. 

It would definitely draw a distinction if the visualisation would be made for a nurse or a doctor. Nurses didn’t mind about the whole dataset, they only have to look up variations. Only the doctors need the detailed blood count. 

'''Specifics:''' 
*Nurses even know all medical terms but they don’t need the whole information of the blood count. The variances are enough.
=== Dataset analysis ===
 '''Description of the data type of the dataset''' 
The measured blood count values are ordinal and continuous. The values of blood counts could change with each measurement.The reference values are ordinal and discrete, because the reference areas are a fixed medical demand. 
 '''Description of the data structure of the dataset''' 
The dataset is multidimensional and temporal. But over the time you could draw conclusions from the collected blood counts, so the values get dependent over time.

At the first look the dataset values seem to be independent of each other. There could even be varying measured values in different blood counts. But it is possible to group some dataset values for special applications. For example it could be in the doctor's interest to group the values, which belong to a certain organ or which indicate certain diseases.

=== Aim of the visualization ===
 Nurses can easily look up variations of the blood count through the visualisation. For example could a variation of the blood values cause a drastically situation for people keeping a comatose. 
Therefore it is important to visualize the data out of the reference range. This could be a solution for the following question: 
*Is the actual status of the patient better or worse? 

----

== Concept ==
=== Types of Visualization ===
 
*For each patient an own pie-chart with extensions
*The label above the pie-cart is the patient name
*The number of the pie slices is equal to the sum of the most important data labelled through a * 

A label inside of the pie-chart gives you information about the examination and the result of it. If the dataset of the blood count diversify after a new examination, the specific pie slices will be labelled spatial or though colouring. Therefore the visualisation of the pie will be maximized through volume expansion coloured in red or green. Inside this new bigger pie-chart it is possible to look up the percentage-wise values of the comparison between the last two examinations. 

The centre of the pie-chart is visualized through a calendar sheet and the time of the examination. Per mouse click on the calendar sheet it is possible to get an overview about the last ten examination results. If there are more examination results you can click on the button ”add earlier blood counts” to upgrade the existing list.

=== Visual Mapping ===
 
*For each through a * marked value, we will create an own pie slice labelled by the actual examination value.
*All slices have the same size. We focus our diagram on the results of the variations of the examinations and not on the specific values.
*Each examination name (for example, hdl cholesterol, choli,...) has a unique colour. So it would be possible to relate them easily.
*The date of examination will be visualized intuitive through a calendar sheet.
*Positive variations (the examination value fit back into the reference area) are marked in green colour / Negative variations are marked red.

=== Techniques ===

In our approach we use an icon-based technique to display the blood counts. Icons are well fitted for multivariate data sets and to reduce the huge amount of data. It is also easy to show data changes with them.

=== Interaction possibilities ===
[[Image:patientSoftware1_low.jpg|thumb|180px|Pic.1 GUI of the PatientSoftware]]

[[Image:patientSoftware2_low.jpg|thumb|180px|Pic.2 Detailview of one patient]]

[[Image:patientSoftware3_low.jpg|thumb|180px|Pic.3 Functionality of the software]]

[[Image:patientSoftware4_low.jpg|thumb|180px|Pic.4 Bloodcount of one patient]]

 ''' Interaction with the system ''' 
 Overall View: 
*In the overall view every patient is symbolized by a mini pie chart
*Double clicking the mini pie chart takes you to the detail view of the respective patient
*The overall view is underlayed with a grey layer to show its inactive and the detail view is shown above it in form of a big pie chart
*A click on the gray underlayed background takes you back from the detail view to the overall view
*There exists a search field, with which you can search after patient names
*A measured value beyond the reference range is symbolized by a red blinking mini pie chart. The mini pie chart blinks till it got investigated in the detail view
 Detail view: 
*Clicking the calendar symbol shows you a list with the last ten blood counts. individual blood counts are distinguishable by the means of ther creation date. if there are more than ten blood counts, the extra entry 'add earlier blodd counts' will be shown. clicking this entry opens a new window containing all the blood counts. the user can choose one ore more blood counts which will be added in the list.
*By clicking the '+add' button new analyzed values are added in the pie chart
*By clicking the '-rem' button a previously shown value can be removed from the pie chart
*By clicking the 'blood count' button, the full blood count in standardized table form is shown
*By moving the mouse cursor over pie piece the reference range is shown as toll tip

 '''Aim of interactions''' 
 

*The overall view shows only the most important data and enables through that an easy handling.
*For more detailed information it is possible to change into the detail view or to call up the blood count function (the blood count as a classical table).
*Red blinking pie charts in the overall view signal that the values of the patient get worth. The nurse is able to apply necessary steps.
*It is possible to add or remove special blood count values to make an individual pie chart for each patient.
*The function of the calendar allows calling up old blood counts. So the nurses have the possibility to compare actual and old blood counts without any administration effort.

=== Support for the user ===
 
*Assuming that the blood counts stored digitally we visualize only the important data (marked through *) of the blood counts but it is possible to add more examination values if it is needed.
*Variations between the different examination values are inserted/updated automatically.
*Negative variations are highlighted trough a red blinking light.
*The calendar sheet offers you the possibility to look up older examination results.
*Through a mouse click on the button “blood count” it is possible to switch to the original blood count view.

=== Specifics ===
 There is not only the detailed view, and the pie-chart view you could also open the overall view which shows you the pie – diagrams of the whole station in hospital. So it is possible for the nurses to get a general overview of the worse red marked values. Additionally will new worse examination data blink red, until the nurse has opened the pie-chart view.

=== Advantages and Disadvantages ===
 
*We only visualize the most important data for the nurses. Even so it is possible to check out the whole information easily.
*It is easily possible to watch out special examination values trough adding or removing of special examination values to the pie-chart view.
*The new red blinking data, advert the nurses to look up the new information.
*A Disadvantage for doctors could be that you can’t see the whole blood count on the first glance.

=== Expansion Possiblities ===
 To combine the software of the hospital with our blood count software would offer some extension possibilities. For example it would be possible to show the whole patient information by one click or the nurse could directly inform a doctor if some values exploded.

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06|Gruppe 06]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 3

2008-01-13T19:32:52Z

UE-InfoVis0708 0527260:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 3

2008-01-13T19:03:36Z

UE-InfoVis0708 0527260:

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 3

2008-01-13T18:20:29Z

UE-InfoVis0708 0527260:

Teaching talk:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 3

2008-01-13T18:20:14Z

UE-InfoVis0708 0527260:

== Bewertung ==

'''Punkte: 13 von 25'''

'''Begründung:'''

siehe Kommentare (kursiv) bei [[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 3|Aufgabe 3]]

=== Critics ===

''Was meint ihr damit konkret? Präzisieren.'' 
''Wenn ihr mit Titel "Private Kredite & öffentliche Schulden in der Bundesrepublik Deutschland" meint; das ist meine Beschriftung der Abbildung im Wiki. Es gibt definitiv keinen Titel hier.'' 
''Da der Zeitpunkt der Erhebung der Daten nicht angegeben ist (was der Fall sein sollte), kann nicht eindeutig gesagt werden, ob Schätzung sich auf alle Balken, oder nur auf den 1997er bezieht. Ich würde aber auf Grund der Position auf letzteres tippen.'' 
''Es gibt eigentlich gar keine Zeitleiste im Sinne einer Zeitachse.'' 
''Sonstiges:'' 
''- Die "Balken" für Private Kredite und öffentliche Schulden sind in Form und Gestaltung unterschiedlich.'' 
''- 3D Effekte erschweren die Lesbarkeit.'' 
''- Zusätzlich erschwerend ist, dass ein Teil der Balken nach oben und ein Teil nach unten zeigt, obwohl kein Vegleich positiver mit negativer Werte dargestellt wird.'' 
''- Die vertikale Schrift ist schlecht lesbar und wäre wenn möglich zu vermeiden.'' 
''- unnötiges Beiwerk (Schiffs- oder Hafen-Metapher)'' 
''- schlechte Farbwahl (geringer Kontrast zu Hintergrund)'' 
''- Farbverläufe in den Balken erschweren Lesbarkeit'' 

=== Declaration of improvements ===

''Ihr habt hier die fehlenden Balken durch lineare Interpolation eingefügt. Das sollte vermieden werden, denn das geht schon in Richtung Datenmanipulation (vor allem, weil ihr auch noch exakte numerische Werte dazuschreibt. 
''Es könnte nämlich auch sein, dass etwa die Schulden von einem Jahr auf das andere sprunghaft steigen und das würde dann in Wahrheit ein völlig anderes Bild ergeben. 

''Es sollte auch vermieden werden, Balken überlappend zu zeichnen (bis auf einen Ausnahmefall - vgl. S. Few), sondern nebeneinander.'' 

''Die Farbwahl wäre auch zu hinterfragen (das dunkle Rot ist gesättigter (scheint wichtiger zu sein) als das dunkle Blau).'' 

''Vertikale Schrift, auch für Quellenangabe, sollte - wenn möglich - vermieden werden.'' 

'''''Ihr habt die Möglichkeit, die angegebenen Dinge noch bis einschließlich 15.01.2008 zu verbessern - dann wird natürlich eure Punkteanzahl aufgewertet!'''''

-- [[User:ASchratt|Alexander Schratt]] 17:19, 20 December 2007 (CEST)

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 3

2008-01-13T18:10:58Z

UE-InfoVis0708 0527260:

== Poor Graphic ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe3.html Beschreibung der Aufgabe 3]

[[Image:Kredite_Schulden.jpg]]

Private Kredite & öffentliche Schulden in der Bundesrepublik Deutschland

== Critics ==

*It is the goal to maximize the data ink ratio and to reduce the non – data ink. In our example there is definitely too much non – data ink and even unnecessary data ink. For example the waves of credits, the balustrade, the people or the cores and the rest of the ship and harbor metapher.

*Visual means to highlight data is split into two possibilities. You could visual data as greater or you could use contrasting visual data. But in our example the trying of highlight any data is failing.

''Was meint ihr damit konkret? Präzisieren.''

*The Label – what it is, when it is and who produced it, should stand in the title of the graphic. In our example there is no title, so there is no explaining of the coherence between private credits and public debts.

''Wenn ihr mit Titel "Private Kredite & öffentliche Schulden in der Bundesrepublik Deutschland" meint; das ist meine Beschriftung der Abbildung im Wiki. Es gibt definitiv keinen Titel hier.''

*The headlines and the explaining notes have a bad position. For example the note: “Schätzung”, is definitely on the wrong position.

''Da der Zeitpunkt der Erhebung der Daten nicht angegeben ist (was der Fall sein sollte), kann nicht eindeutig gesagt werden, ob Schätzung sich auf alle Balken, oder nur auf den 1997er bezieht. Ich würde aber auf Grund der Position auf letzteres tippen.''

*If it was the intension of the graphics' creator to compare the values, its hard to do so, because the values are from different years.

''Es gibt eigentlich gar keine Zeitleiste im Sinne einer Zeitachse.''

*The 'Private Kredite'-bars and the 'öffentliche Schulden'-bars differ in form and design.

*Because of the 3D effects, its harder to read the graphic.

*The readability is additionally hindered by the bars, which go in opposite directions, although there is no comparison between positiv and negative values.

*The color gradient in the bars further decrease the readability of the graphic.

*The vertical aligned source text is hard to read and should be aligned horizontal.

*Because the chosen color for the bars has little contrast compared to the background (the bars are not highlighted enough), the reader has to search for the important information.

''Sonstiges:'' 
''- Die "Balken" für Private Kredite und öffentliche Schulden sind in Form und Gestaltung unterschiedlich.'' 
''- 3D Effekte erschweren die Lesbarkeit.'' 
''- Zusätzlich erschwerend ist, dass ein Teil der Balken nach oben und ein Teil nach unten zeigt, obwohl kein Vegleich positiver mit negativer Werte dargestellt wird.'' 
''- Die vertikale Schrift ist schlecht lesbar und wäre wenn möglich zu vermeiden.'' 
''- unnötiges Beiwerk (Schiffs- oder Hafen-Metapher)'' 
''- schlechte Farbwahl (geringer Kontrast zu Hintergrund)'' 
''- Farbverläufe in den Balken erschweren Lesbarkeit'' 

== Redesign ==

[[Image:Kredite_Schulden_verbessert.jpg]]

== Declaration of improvements ==

*A significant label with a short declaration, the period of data collection and from whom it is.

*The next step is to reduce the non – data ink, remove unnecessary data ink and emphasize the most important data ink. So we remove all the non – data ink like the balustrade and the people. To emphasize the most important data ink it will be necessary to replace the representations of the waves and the cores through simplicity like bars.

*We separate the two sections (credits and debts) with a colour separation. The spatial separation was not really clearly arranged. Further more we defined a declaration of the colours in the legend, to avoid the problem with the misplaced data.

*For a better comparison we would need more data. There should be collected data from the same years or at least the same bench marks. It is not possible to compare apples and oranges.

''Ihr habt hier die fehlenden Balken durch lineare Interpolation eingefügt. Das sollte vermieden werden, denn das geht schon in Richtung Datenmanipulation (vor allem, weil ihr auch noch exakte numerische Werte dazuschreibt. 
''Es könnte nämlich auch sein, dass etwa die Schulden von einem Jahr auf das andere sprunghaft steigen und das würde dann in Wahrheit ein völlig anderes Bild ergeben. 

''Es sollte auch vermieden werden, Balken überlappend zu zeichnen (bis auf einen Ausnahmefall - vgl. S. Few), sondern nebeneinander.'' 

''Die Farbwahl wäre auch zu hinterfragen (das dunkle Rot ist gesättigter (scheint wichtiger zu sein) als das dunkle Blau).'' 

''Vertikale Schrift, auch für Quellenangabe, sollte - wenn möglich - vermieden werden.'' 

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06|Gruppe 06]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 3

2008-01-13T17:57:49Z

UE-InfoVis0708 0527260:

== Poor Graphic ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe3.html Beschreibung der Aufgabe 3]

[[Image:Kredite_Schulden.jpg]]

Private Kredite & öffentliche Schulden in der Bundesrepublik Deutschland

== Critics ==

*It is the goal to maximize the data ink ratio and to reduce the non – data ink. In our example there is definitely too much non – data ink and even unnecessary data ink. For example the waves of credits, the balustrade, the people or the cores and the rest of the ship and harbor metapher.

*Visual means to highlight data is split into two possibilities. You could visual data as greater or you could use contrasting visual data. But in our example the trying of highlight any data is failing.

''Was meint ihr damit konkret? Präzisieren.''

*The Label – what it is, when it is and who produced it, should stand in the title of the graphic. In our example there is no title, so there is no explaining of the coherence between private credits and public debts.

''Wenn ihr mit Titel "Private Kredite & öffentliche Schulden in der Bundesrepublik Deutschland" meint; das ist meine Beschriftung der Abbildung im Wiki. Es gibt definitiv keinen Titel hier.''

*The headlines and the explaining notes have a bad position. For example the note: “Schätzung”, is definitely on the wrong position.

''Da der Zeitpunkt der Erhebung der Daten nicht angegeben ist (was der Fall sein sollte), kann nicht eindeutig gesagt werden, ob Schätzung sich auf alle Balken, oder nur auf den 1997er bezieht. Ich würde aber auf Grund der Position auf letzteres tippen.''

*If it was the intension of the graphics' creator to compare the values, its hard to do so, because the values are from different years.

''Es gibt eigentlich gar keine Zeitleiste im Sinne einer Zeitachse.''

*The 'Private Kredite'-bars and the 'öffentliche Schulden'-bars differ in form and design.

*Because of the 3D effects, its harder to read the graphic.

*The readability is additionally hindered by the bars, which go in opposite directions, although there is no comparison between positiv and negative values.

*The color gradient in the bars further decrease the readability of the graphic.

*The vertical aligned source text is hard to read and should be aligned horizontal.

*Because the chosen color for the bars has little contrast compared to the background (the bars are not highlighted enough), the reader has to search for the important information.

''Sonstiges:'' 
''- Die "Balken" für Private Kredite und öffentliche Schulden sind in Form und Gestaltung unterschiedlich.'' 
''- 3D Effekte erschweren die Lesbarkeit.'' 
''- Zusätzlich erschwerend ist, dass ein Teil der Balken nach oben und ein Teil nach unten zeigt, obwohl kein Vegleich positiver mit negativer Werte dargestellt wird.'' 
''- Die vertikale Schrift ist schlecht lesbar und wäre wenn möglich zu vermeiden.'' 
''- unnötiges Beiwerk (Schiffs- oder Hafen-Metapher)'' 
''- schlechte Farbwahl (geringer Kontrast zu Hintergrund)'' 
''- Farbverläufe in den Balken erschweren Lesbarkeit'' 

== Redesign ==

[[Image:Kredite_Schulden_verbessert.jpg]]

== Declaration of improvements ==

*A significant label with a short declaration, the period of data collection and from whom it is.

*The next step is to reduce the non – data ink, remove unnecessary data ink and emphasize the most important data ink. So we remove all the non – data ink like the balustrade and the people. To emphasize the most important data ink it will be necessary to replace the representations of the waves and the cores through simplicity like bars.

*We separate the two sections (credits and debts) with a colour separation. The spatial separation was not really clearly arranged. Further more we defined a declaration of the colours in the legend, to avoid the problem with the misplaced data.

*For a better comparison we would need more data. There should be collected data from the same years or at least the same bench marks. It is not possible to compare apples and oranges. We create a solution for this problem. There for we calculate some more values (estimated values) to compare the same years and the same data. To get a better impression we have highlighted the original values with a brighter colour, because it would stand out more than a lighter or less saturated colour.

''Ihr habt hier die fehlenden Balken durch lineare Interpolation eingefügt. Das sollte vermieden werden, denn das geht schon in Richtung Datenmanipulation (vor allem, weil ihr auch noch exakte numerische Werte dazuschreibt. 
''Es könnte nämlich auch sein, dass etwa die Schulden von einem Jahr auf das andere sprunghaft steigen und das würde dann in Wahrheit ein völlig anderes Bild ergeben. 

''Es sollte auch vermieden werden, Balken überlappend zu zeichnen (bis auf einen Ausnahmefall - vgl. S. Few), sondern nebeneinander.'' 

''Die Farbwahl wäre auch zu hinterfragen (das dunkle Rot ist gesättigter (scheint wichtiger zu sein) als das dunkle Blau).'' 

''Vertikale Schrift, auch für Quellenangabe, sollte - wenn möglich - vermieden werden.'' 

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06|Gruppe 06]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 3

2008-01-13T17:54:57Z

UE-InfoVis0708 0527260:

== Poor Graphic ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe3.html Beschreibung der Aufgabe 3]

[[Image:Kredite_Schulden.jpg]]

Private Kredite & öffentliche Schulden in der Bundesrepublik Deutschland

== Critics ==

*It is the goal to maximize the data ink ratio and to reduce the non – data ink. In our example there is definitely too much non – data ink and even unnecessary data ink. For example the waves of credits, the balustrade, the people or the cores and the rest of the ship and harbor metapher.

*Visual means to highlight data is split into two possibilities. You could visual data as greater or you could use contrasting visual data. But in our example the trying of highlight any data is failing.

''Was meint ihr damit konkret? Präzisieren.''

*The Label – what it is, when it is and who produced it, should stand in the title of the graphic. In our example there is no title, so there is no explaining of the coherence between private credits and public debts.

''Wenn ihr mit Titel "Private Kredite & öffentliche Schulden in der Bundesrepublik Deutschland" meint; das ist meine Beschriftung der Abbildung im Wiki. Es gibt definitiv keinen Titel hier.''

*The headlines and the explaining notes have a bad position. For example the note: “Schätzung”, is definitely on the wrong position.

''Da der Zeitpunkt der Erhebung der Daten nicht angegeben ist (was der Fall sein sollte), kann nicht eindeutig gesagt werden, ob Schätzung sich auf alle Balken, oder nur auf den 1997er bezieht. Ich würde aber auf Grund der Position auf letzteres tippen.''

*It is hard to compare the data because of the values in different years. If it was the intension of the graphics' creator to compare the values, its hard to do so, because the values are from different years.

''Es gibt eigentlich gar keine Zeitleiste im Sinne einer Zeitachse.''

*The 'Private Kredite'-bars and the 'öffentliche Schulden'-bars differ in form and design.

*Because of the 3D effects, its harder to read the graphic.

*The readability is additionally hindered by the bars, which go in opposite directions, although there is no comparison between positiv and negative values.

*The color gradient in the bars further decrease the readability of the graphic.

*The vertical aligned source text is hard to read and should be aligned horizontal.

*Because the chosen color for the bars has little contrast compared to the background (the bars are not highlighted enough), the reader has to search for the important information.

''Sonstiges:'' 
''- Die "Balken" für Private Kredite und öffentliche Schulden sind in Form und Gestaltung unterschiedlich.'' 
''- 3D Effekte erschweren die Lesbarkeit.'' 
''- Zusätzlich erschwerend ist, dass ein Teil der Balken nach oben und ein Teil nach unten zeigt, obwohl kein Vegleich positiver mit negativer Werte dargestellt wird.'' 
''- Die vertikale Schrift ist schlecht lesbar und wäre wenn möglich zu vermeiden.'' 
''- unnötiges Beiwerk (Schiffs- oder Hafen-Metapher)'' 
''- schlechte Farbwahl (geringer Kontrast zu Hintergrund)'' 
''- Farbverläufe in den Balken erschweren Lesbarkeit'' 

== Redesign ==

[[Image:Kredite_Schulden_verbessert.jpg]]

== Declaration of improvements ==

*A significant label with a short declaration, the period of data collection and from whom it is.

*The next step is to reduce the non – data ink, remove unnecessary data ink and emphasize the most important data ink. So we remove all the non – data ink like the balustrade and the people. To emphasize the most important data ink it will be necessary to replace the representations of the waves and the cores through simplicity like bars.

*We separate the two sections (credits and debts) with a colour separation. The spatial separation was not really clearly arranged. Further more we defined a declaration of the colours in the legend, to avoid the problem with the misplaced data.

*For a better comparison we would need more data. There should be collected data from the same years or at least the same bench marks. It is not possible to compare apples and oranges. We create a solution for this problem. There for we calculate some more values (estimated values) to compare the same years and the same data. To get a better impression we have highlighted the original values with a brighter colour, because it would stand out more than a lighter or less saturated colour.

''Ihr habt hier die fehlenden Balken durch lineare Interpolation eingefügt. Das sollte vermieden werden, denn das geht schon in Richtung Datenmanipulation (vor allem, weil ihr auch noch exakte numerische Werte dazuschreibt. 
''Es könnte nämlich auch sein, dass etwa die Schulden von einem Jahr auf das andere sprunghaft steigen und das würde dann in Wahrheit ein völlig anderes Bild ergeben. 

''Es sollte auch vermieden werden, Balken überlappend zu zeichnen (bis auf einen Ausnahmefall - vgl. S. Few), sondern nebeneinander.'' 

''Die Farbwahl wäre auch zu hinterfragen (das dunkle Rot ist gesättigter (scheint wichtiger zu sein) als das dunkle Blau).'' 

''Vertikale Schrift, auch für Quellenangabe, sollte - wenn möglich - vermieden werden.'' 

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06|Gruppe 06]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 3

2008-01-13T17:33:45Z

UE-InfoVis0708 0527260:

== Poor Graphic ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe3.html Beschreibung der Aufgabe 3]

[[Image:Kredite_Schulden.jpg]]

Private Kredite & öffentliche Schulden in der Bundesrepublik Deutschland

== Critics ==

*It is the goal to maximize the data ink ratio and to reduce the non – data ink. In our example there is definitely too much non – data ink and even unnecessary data ink. For example the waves of credits, the balustrade, the people or the cores and the rest of the ship and harbor metapher.

*Visual means to highlight data is split into two possibilities. You could visual data as greater or you could use contrasting visual data. But in our example the trying of highlight any data is failing.

''Was meint ihr damit konkret? Präzisieren.''

*The Label – what it is, when it is and who produced it, should stand in the title of the graphic. In our example there is no title, so there is no explaining of the coherence between private credits and public debts.

''Wenn ihr mit Titel "Private Kredite & öffentliche Schulden in der Bundesrepublik Deutschland" meint; das ist meine Beschriftung der Abbildung im Wiki. Es gibt definitiv keinen Titel hier.''

*The headlines and the explaining notes have a bad position. For example the note: “Schätzung”, is definitely on the wrong position.

''Da der Zeitpunkt der Erhebung der Daten nicht angegeben ist (was der Fall sein sollte), kann nicht eindeutig gesagt werden, ob Schätzung sich auf alle Balken, oder nur auf den 1997er bezieht. Ich würde aber auf Grund der Position auf letzteres tippen.''

*It is hard to compare the data because of the values in different years. The timeline is not complete.

''Es gibt eigentlich gar keine Zeitleiste im Sinne einer Zeitachse.''

*The 'Private Kredite'-bars and the 'öffentliche Schulden'-bars differ in form and design.

*Because of the 3D effects, its harder to read the graphic.

*The readability is additionally hindered by the bars, which go in opposite directions, although there is no comparison between positiv and negative values.

*The color gradient in the bars further decrease the readability of the graphic.

*The vertical aligned source text is hard to read and should be aligned horizontal.

*Because the chosen color for the bars has little contrast compared to the background (the bars are not highlighted enough), the reader has to search for the important information.

''Sonstiges:'' 
''- Die "Balken" für Private Kredite und öffentliche Schulden sind in Form und Gestaltung unterschiedlich.'' 
''- 3D Effekte erschweren die Lesbarkeit.'' 
''- Zusätzlich erschwerend ist, dass ein Teil der Balken nach oben und ein Teil nach unten zeigt, obwohl kein Vegleich positiver mit negativer Werte dargestellt wird.'' 
''- Die vertikale Schrift ist schlecht lesbar und wäre wenn möglich zu vermeiden.'' 
''- unnötiges Beiwerk (Schiffs- oder Hafen-Metapher)'' 
''- schlechte Farbwahl (geringer Kontrast zu Hintergrund)'' 
''- Farbverläufe in den Balken erschweren Lesbarkeit'' 

== Redesign ==

[[Image:Kredite_Schulden_verbessert.jpg]]

== Declaration of improvements ==

*A significant label with a short declaration, the period of data collection and from whom it is.

*The next step is to reduce the non – data ink, remove unnecessary data ink and emphasize the most important data ink. So we remove all the non – data ink like the balustrade and the people. To emphasize the most important data ink it will be necessary to replace the representations of the waves and the cores through simplicity like bars.

*We separate the two sections (credits and debts) with a colour separation. The spatial separation was not really clearly arranged. Further more we defined a declaration of the colours in the legend, to avoid the problem with the misplaced data.

*For a better comparison we would need more data. There should be collected data from the same years or at least the same bench marks. It is not possible to compare apples and oranges. We create a solution for this problem. There for we calculate some more values (estimated values) to compare the same years and the same data. To get a better impression we have highlighted the original values with a brighter colour, because it would stand out more than a lighter or less saturated colour.

''Ihr habt hier die fehlenden Balken durch lineare Interpolation eingefügt. Das sollte vermieden werden, denn das geht schon in Richtung Datenmanipulation (vor allem, weil ihr auch noch exakte numerische Werte dazuschreibt. 
''Es könnte nämlich auch sein, dass etwa die Schulden von einem Jahr auf das andere sprunghaft steigen und das würde dann in Wahrheit ein völlig anderes Bild ergeben. 

''Es sollte auch vermieden werden, Balken überlappend zu zeichnen (bis auf einen Ausnahmefall - vgl. S. Few), sondern nebeneinander.'' 

''Die Farbwahl wäre auch zu hinterfragen (das dunkle Rot ist gesättigter (scheint wichtiger zu sein) als das dunkle Blau).'' 

''Vertikale Schrift, auch für Quellenangabe, sollte - wenn möglich - vermieden werden.'' 

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06|Gruppe 06]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 3

2008-01-13T17:27:49Z

UE-InfoVis0708 0527260:

== Poor Graphic ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe3.html Beschreibung der Aufgabe 3]

[[Image:Kredite_Schulden.jpg]]

Private Kredite & öffentliche Schulden in der Bundesrepublik Deutschland

== Critics ==

*It is the goal to maximize the data ink ratio and to reduce the non – data ink. In our example there is definitely too much non – data ink and even unnecessary data ink. For example the waves of credits, the balustrade, the people or the cores and the rest of the ship and harbor metapher.

*Visual means to highlight data is split into two possibilities. You could visual data as greater or you could use contrasting visual data. But in our example the trying of highlight any data is failing.

''Was meint ihr damit konkret? Präzisieren.''

*The Label – what it is, when it is and who produced it, should stand in the title of the graphic. In our example there is no title, so there is no explaining of the coherence between private credits and public debts.

''Wenn ihr mit Titel "Private Kredite & öffentliche Schulden in der Bundesrepublik Deutschland" meint; das ist meine Beschriftung der Abbildung im Wiki. Es gibt definitiv keinen Titel hier.''

*The headlines and the explaining notes have a bad position. For example the note: “Schätzung”, is definitely on the wrong position. It gives you the impression that it is only guilty for this core.

''Da der Zeitpunkt der Erhebung der Daten nicht angegeben ist (was der Fall sein sollte), kann nicht eindeutig gesagt werden, ob Schätzung sich auf alle Balken, oder nur auf den 1997er bezieht. Ich würde aber auf Grund der Position auf letzteres tippen.''

*It is hard to compare the data because of the values in different years. The timeline is not complete.

''Es gibt eigentlich gar keine Zeitleiste im Sinne einer Zeitachse.''

*The 'Private Kredite'-bars and the 'öffentliche Schulden'-bars differ in form and design.

*Because of the 3D effects, its harder to read the graphic.

*The readability is additionally hindered by the bars, which go in opposite directions, although there is no comparison between positiv and negative values.

*The color gradient in the bars further decrease the readability of the graphic.

*The vertical aligned source text is hard to read and should be aligned horizontal.

*Because the chosen color for the bars has little contrast compared to the background (the bars are not highlighted enough), the reader has to search for the important information.

''Sonstiges:'' 
''- Die "Balken" für Private Kredite und öffentliche Schulden sind in Form und Gestaltung unterschiedlich.'' 
''- 3D Effekte erschweren die Lesbarkeit.'' 
''- Zusätzlich erschwerend ist, dass ein Teil der Balken nach oben und ein Teil nach unten zeigt, obwohl kein Vegleich positiver mit negativer Werte dargestellt wird.'' 
''- Die vertikale Schrift ist schlecht lesbar und wäre wenn möglich zu vermeiden.'' 
''- unnötiges Beiwerk (Schiffs- oder Hafen-Metapher)'' 
''- schlechte Farbwahl (geringer Kontrast zu Hintergrund)'' 
''- Farbverläufe in den Balken erschweren Lesbarkeit'' 

== Redesign ==

[[Image:Kredite_Schulden_verbessert.jpg]]

== Declaration of improvements ==

*A significant label with a short declaration, the period of data collection and from whom it is.

*The next step is to reduce the non – data ink, remove unnecessary data ink and emphasize the most important data ink. So we remove all the non – data ink like the balustrade and the people. To emphasize the most important data ink it will be necessary to replace the representations of the waves and the cores through simplicity like bars.

*We separate the two sections (credits and debts) with a colour separation. The spatial separation was not really clearly arranged. Further more we defined a declaration of the colours in the legend, to avoid the problem with the misplaced data.

*For a better comparison we would need more data. There should be collected data from the same years or at least the same bench marks. It is not possible to compare apples and oranges. We create a solution for this problem. There for we calculate some more values (estimated values) to compare the same years and the same data. To get a better impression we have highlighted the original values with a brighter colour, because it would stand out more than a lighter or less saturated colour.

''Ihr habt hier die fehlenden Balken durch lineare Interpolation eingefügt. Das sollte vermieden werden, denn das geht schon in Richtung Datenmanipulation (vor allem, weil ihr auch noch exakte numerische Werte dazuschreibt. 
''Es könnte nämlich auch sein, dass etwa die Schulden von einem Jahr auf das andere sprunghaft steigen und das würde dann in Wahrheit ein völlig anderes Bild ergeben. 

''Es sollte auch vermieden werden, Balken überlappend zu zeichnen (bis auf einen Ausnahmefall - vgl. S. Few), sondern nebeneinander.'' 

''Die Farbwahl wäre auch zu hinterfragen (das dunkle Rot ist gesättigter (scheint wichtiger zu sein) als das dunkle Blau).'' 

''Vertikale Schrift, auch für Quellenangabe, sollte - wenn möglich - vermieden werden.'' 

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06|Gruppe 06]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 3

2008-01-13T17:18:55Z

UE-InfoVis0708 0527260:

== Poor Graphic ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe3.html Beschreibung der Aufgabe 3]

[[Image:Kredite_Schulden.jpg]]

Private Kredite & öffentliche Schulden in der Bundesrepublik Deutschland

== Critics ==

*It is the goal to maximize the data ink ratio and to reduce the non – data ink. In our example there is definitely too much non – data ink and even unnecessary data ink. For example the waves of credits, the balustrade, the people or the cores and the rest of the ship and harbor metapher.

*Visual means to highlight data is split into two possibilities. You could visual data as greater or you could use contrasting visual data. But in our example the trying of highlight any data is failing.

''Was meint ihr damit konkret? Präzisieren.''

*The Label – what it is, when it is and who produced it, should stand in the title of the graphic. In our example there is something like a title but very small at the end of the graphic. Even more there is no explaining of the coherence between private credits and public debts.

''Wenn ihr mit Titel "Private Kredite & öffentliche Schulden in der Bundesrepublik Deutschland" meint; das ist meine Beschriftung der Abbildung im Wiki. Es gibt definitiv keinen Titel hier.''

*The headlines and the explaining notes have a bad position. For example the note: “Schätzung”, is definitely on the wrong position. It gives you the impression that it is only guilty for this core.

''Da der Zeitpunkt der Erhebung der Daten nicht angegeben ist (was der Fall sein sollte), kann nicht eindeutig gesagt werden, ob Schätzung sich auf alle Balken, oder nur auf den 1997er bezieht. Ich würde aber auf Grund der Position auf letzteres tippen.''

*It is hard to compare the data because of the values in different years. The timeline is not complete.

''Es gibt eigentlich gar keine Zeitleiste im Sinne einer Zeitachse.''

*The 'Private Kredite'-bars and the 'öffentliche Schulden'-bars differ in form and design.

*Because of the 3D effects, its harder to read the graphic.

*The readability is additionally hindered by the bars, which go in opposite directions, although there is no comparison between positiv and negative values.

*The color gradient in the bars further decrease the readability of the graphic.

*The vertical aligned source text is hard to read and should be aligned horizontal.

*Because the chosen color for the bars has little contrast compared to the background (the bars are not highlighted enough), the reader has to search for the important information.

''Sonstiges:'' 
''- Die "Balken" für Private Kredite und öffentliche Schulden sind in Form und Gestaltung unterschiedlich.'' 
''- 3D Effekte erschweren die Lesbarkeit.'' 
''- Zusätzlich erschwerend ist, dass ein Teil der Balken nach oben und ein Teil nach unten zeigt, obwohl kein Vegleich positiver mit negativer Werte dargestellt wird.'' 
''- Die vertikale Schrift ist schlecht lesbar und wäre wenn möglich zu vermeiden.'' 
''- unnötiges Beiwerk (Schiffs- oder Hafen-Metapher)'' 
''- schlechte Farbwahl (geringer Kontrast zu Hintergrund)'' 
''- Farbverläufe in den Balken erschweren Lesbarkeit'' 

== Redesign ==

[[Image:Kredite_Schulden_verbessert.jpg]]

== Declaration of improvements ==

*A significant label with a short declaration, the period of data collection and from whom it is.

*The next step is to reduce the non – data ink, remove unnecessary data ink and emphasize the most important data ink. So we remove all the non – data ink like the balustrade and the people. To emphasize the most important data ink it will be necessary to replace the representations of the waves and the cores through simplicity like bars.

*We separate the two sections (credits and debts) with a colour separation. The spatial separation was not really clearly arranged. Further more we defined a declaration of the colours in the legend, to avoid the problem with the misplaced data.

*For a better comparison we would need more data. There should be collected data from the same years or at least the same bench marks. It is not possible to compare apples and oranges. We create a solution for this problem. There for we calculate some more values (estimated values) to compare the same years and the same data. To get a better impression we have highlighted the original values with a brighter colour, because it would stand out more than a lighter or less saturated colour.

''Ihr habt hier die fehlenden Balken durch lineare Interpolation eingefügt. Das sollte vermieden werden, denn das geht schon in Richtung Datenmanipulation (vor allem, weil ihr auch noch exakte numerische Werte dazuschreibt. 
''Es könnte nämlich auch sein, dass etwa die Schulden von einem Jahr auf das andere sprunghaft steigen und das würde dann in Wahrheit ein völlig anderes Bild ergeben. 

''Es sollte auch vermieden werden, Balken überlappend zu zeichnen (bis auf einen Ausnahmefall - vgl. S. Few), sondern nebeneinander.'' 

''Die Farbwahl wäre auch zu hinterfragen (das dunkle Rot ist gesättigter (scheint wichtiger zu sein) als das dunkle Blau).'' 

''Vertikale Schrift, auch für Quellenangabe, sollte - wenn möglich - vermieden werden.'' 

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06|Gruppe 06]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 3

2008-01-13T17:04:27Z

UE-InfoVis0708 0527260:

== Poor Graphic ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe3.html Beschreibung der Aufgabe 3]

[[Image:Kredite_Schulden.jpg]]

Private Kredite & öffentliche Schulden in der Bundesrepublik Deutschland

== Critics ==

*It is the goal to maximize the data ink ratio and to reduce the non – data ink. In our example there is definitely too much non – data ink and even unnecessary data ink. For example the waves of credits, the balustrade, the people or the cores and the rest of the ship and harbor metapher.

*Visual means to highlight data is split into two possibilities. You could visual data as greater or you could use contrasting visual data. But in our example the trying of highlight any data is failing.

''Was meint ihr damit konkret? Präzisieren.''

*The Label – what it is, when it is and who produced it, should stand in the title of the graphic. In our example there is something like a title but very small at the end of the graphic. Even more there is no explaining of the coherence between private credits and public debts.

''Wenn ihr mit Titel "Private Kredite & öffentliche Schulden in der Bundesrepublik Deutschland" meint; das ist meine Beschriftung der Abbildung im Wiki. Es gibt definitiv keinen Titel hier.''

*The headlines and the explaining notes have a bad position. For example the note: “Schätzung”, is definitely on the wrong position. It gives you the impression that it is only guilty for this core.

''Da der Zeitpunkt der Erhebung der Daten nicht angegeben ist (was der Fall sein sollte), kann nicht eindeutig gesagt werden, ob Schätzung sich auf alle Balken, oder nur auf den 1997er bezieht. Ich würde aber auf Grund der Position auf letzteres tippen.''

*It is hard to compare the data because of the values in different years. The timeline is not complete.

''Es gibt eigentlich gar keine Zeitleiste im Sinne einer Zeitachse.''

*The 'Private Kredite'-bars and the 'öffentliche Schulden'-bars differ in form and design.

*Because of the 3D effects, its harder to read the graphic.

*The readability is additionally hindered by the bars, which go in opposite directions, although there is no comparison between positiv and negative values.

*The color gradient in the bars further decrease the readability of the graphic.

*The vertical aligned source text is hard to read and should be aligned horizontal.

''Sonstiges:'' 
''- Die "Balken" für Private Kredite und öffentliche Schulden sind in Form und Gestaltung unterschiedlich.'' 
''- 3D Effekte erschweren die Lesbarkeit.'' 
''- Zusätzlich erschwerend ist, dass ein Teil der Balken nach oben und ein Teil nach unten zeigt, obwohl kein Vegleich positiver mit negativer Werte dargestellt wird.'' 
''- Die vertikale Schrift ist schlecht lesbar und wäre wenn möglich zu vermeiden.'' 
''- unnötiges Beiwerk (Schiffs- oder Hafen-Metapher)'' 
''- schlechte Farbwahl (geringer Kontrast zu Hintergrund)'' 
''- Farbverläufe in den Balken erschweren Lesbarkeit'' 

== Redesign ==

[[Image:Kredite_Schulden_verbessert.jpg]]

== Declaration of improvements ==

*A significant label with a short declaration, the period of data collection and from whom it is.

*The next step is to reduce the non – data ink, remove unnecessary data ink and emphasize the most important data ink. So we remove all the non – data ink like the balustrade and the people. To emphasize the most important data ink it will be necessary to replace the representations of the waves and the cores through simplicity like bars.

*We separate the two sections (credits and debts) with a colour separation. The spatial separation was not really clearly arranged. Further more we defined a declaration of the colours in the legend, to avoid the problem with the misplaced data.

*For a better comparison we would need more data. There should be collected data from the same years or at least the same bench marks. It is not possible to compare apples and oranges. We create a solution for this problem. There for we calculate some more values (estimated values) to compare the same years and the same data. To get a better impression we have highlighted the original values with a brighter colour, because it would stand out more than a lighter or less saturated colour.

''Ihr habt hier die fehlenden Balken durch lineare Interpolation eingefügt. Das sollte vermieden werden, denn das geht schon in Richtung Datenmanipulation (vor allem, weil ihr auch noch exakte numerische Werte dazuschreibt. 
''Es könnte nämlich auch sein, dass etwa die Schulden von einem Jahr auf das andere sprunghaft steigen und das würde dann in Wahrheit ein völlig anderes Bild ergeben. 

''Es sollte auch vermieden werden, Balken überlappend zu zeichnen (bis auf einen Ausnahmefall - vgl. S. Few), sondern nebeneinander.'' 

''Die Farbwahl wäre auch zu hinterfragen (das dunkle Rot ist gesättigter (scheint wichtiger zu sein) als das dunkle Blau).'' 

''Vertikale Schrift, auch für Quellenangabe, sollte - wenn möglich - vermieden werden.'' 

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06|Gruppe 06]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 4

2008-01-02T17:47:09Z

UE-InfoVis0708 0527260:

== Aufgabenstellung ==

Aufgabe ist das Design einer interaktiven Visualisierungsapplikation zur Darstellung und Exploration (des zeitlichen Verlaufs) von Laborwerten einer Blutuntersuchung. BenutzerInnen, Einsatzzweck, Tasks, etc. sollen von Euch selbst festgelegt und beschrieben werden.

[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]

=== Beispiele für derartige Datensätze ===

[[Image:20061115_blutuntersuchung.jpg]]

[[Image:20070920_blutuntersuchung.jpg]]

== Description of the application area, the dataset, the users and the duties ==
=== Description of the application area and of the given dataset ===
 Application area analysis – Routine medical blood test in hospitals. 
'''Specifics:'''
*the given data implements a small and a big blood count
*the most important data fields are labelled through a * (these data is outside of the normal reference area)

=== Target group analysis ===
 After we confer with some doctors and nurses, we know that it wouldn’t make sense to visualize the whole blood count. The doctors are satisfied with the actual situation (blood counts in a table in which the important data is signed through a *), because of the easy handling and the well arranged data. Therefore we want to do a special visualisation for nurses, which show them the important data which they need to take care of the state of their patients. Nurses have to look at variations in the blood count. 

An example of use would be patients at the intensive care. They need routine blood counts during their sheltering at the hospital. 

It would definitely draw a distinction if the visualisation would be made for a nurse or a doctor. Nurses didn’t mind about the whole dataset, they only have to look up variations. Only the doctors need the detailed blood count. 

'''Specifics:''' 
*Nurses even know all medical terms but they don’t need the whole information of the blood count. The variances are enough.
=== Dataset analysis ===
 '''Description of the data type of the dataset''' 
The measured blood count values are ordinal and continuous. The values of blood counts could change with each measurement.The reference values are ordinal and discrete, because the reference areas are a fixed medical demand. 
 '''Description of the data structure of the dataset''' 
The dataset is multidimensional and temporal. The values of one data set are independent of each other. The measured data of blood counts could even be different. But over the time you could draw conclusions from the collected blood counts. So the values get dependent over time.

=== Aim of the visualization ===
 Nurses can easily look up variations of the blood count through the visualisation. For example could a variation of the blood values cause a drastically situation for people keeping a comatose. 
Therefore it is important to visualize the data out of the reference range. This could be a solution for the following question: 
*Is the actual status of the patient better or worse? 

----

== Concept ==
=== Types of Visualization ===
 
*For each patient an own pie-chart with extensions
*The label above the pie-cart is the patient name
*The number of the pie slices is equal to the sum of the most important data labelled through a * 

A label inside of the pie-chart gives you information about the examination and the result of it. If the dataset of the blood count diversify after a new examination, the specific pie slices will be labelled spatial or though colouring. Therefore the visualisation of the pie will be maximized through volume expansion coloured in red or green. Inside this new bigger pie-chart it is possible to look up the percentage-wise values of the comparison between the last two examinations. 

The centre of the pie-chart is visualized through a calendar sheet and the time of the examination. Per mouse click on the calendar sheet it is possible to get an overview about the last ten examination results. If there are more examination results you can click on the button ”add earlier blood counts” to upgrade the existing list.

=== Visual Mapping ===
 
*For each through a * marked value, we will create an own pie slice labelled by the actual examination value.
*All slices have the same size. We focus our diagram on the results of the variations of the examinations and not on the specific values.
*Each examination name (for example, hdl cholesterol, choli,...) has a unique colour. So it would be possible to relate them easily.
*The date of examination will be visualized intuitive through a calendar sheet.
*Positive variations (the examination value fit back into the reference area) are marked in green colour / Negative variations are marked red.

=== Techniques ===

In our approach we use an icon-based technique to display the blood counts. Icons are well fitted for multivariate data sets and to reduce the huge amount of data. It is also easy to show data changes with them.

=== Interaction possibilities ===

 ''' Interaction with the system ''' 
 Overall View: 
*In the overall view every patient is symbolized by a mini pie chart
*Double clicking the mini pie chart takes you to the detail view of the respective patient
*The overall view is underlayed with a grey layer to show its inactive and the detail view is shown above it in form of a big pie chart
*A click on the gray underlayed background takes you back from the detail view to the overall view
*There exists a search field, with which you can search after patient names
*A measured value beyond the reference range is symbolized by a red blinking mini pie chart. The mini pie chart blinks till it got investigated in the detail view
 Detail view: 
*Clicking the calendar symbol shows you a list with the last ten blood counts. individual blood counts are distinguishable by the means of ther creation date. if there are more than ten blood counts, the extra entry 'add earlier blodd counts' will be shown. clicking this entry opens a new window containing all the blood counts. the user can choose one ore more blood counts which will be added in the list.
*By clicking the '+add' button new analyzed values are added in the pie chart
*By clicking the '-rem' button a previously shown value can be removed from the pie chart
*By clicking the 'blood count' button, the full blood count in standardized table form is shown
*By moving the mouse cursor over pie piece the reference range is shown as toll tip

 '''Aim of interactions''' 
 

*The overall view shows only the most important data and enables through that an easy handling.
*For more detailed information it is possible to change into the detail view or to call up the blood count function (the blood count as a classical table).
*Red blinking pie charts in the overall view signal that the values of the patient get worth. The nurse is able to apply necessary steps.
*It is possible to add or remove special blood count values to make an individual pie chart for each patient.
*The function of the calendar allows calling up old blood counts. So the nurses have the possibility to compare actual and old blood counts without any administration effort.

=== Mockup(s) ===

=== Support for the user ===
 
*Assuming that the blood counts stored digitally we visualize only the important data (marked through *) of the blood counts but it is possible to add more examination values if it is needed.
*Variations between the different examination values are inserted/updated automatically.
*Negative variations are highlighted trough a red blinking light.
*The calendar sheet offers you the possibility to look up older examination results.
*Through a mouse click on the button “blood count” it is possible to switch to the original blood count view.

=== Specifics ===
 There is not only the detailed view, and the pie-chart view you could also open the overall view which shows you the pie – diagrams of the whole station in hospital. So it is possible for the nurses to get a general overview of the worse red marked values. Additionally will new worse examination data blink red, until the nurse has opened the pie-chart view.

=== Advantages and Disadvantages ===
 
*We only visualize the most important data for the nurses. Even so it is possible to check out the whole information easily.
*It is easily possible to watch out special examination values trough adding or removing of special examination values to the pie-chart view.
*The new red blinking data, advert the nurses to look up the new information.
*A Disadvantage for doctors could be that you can’t see the whole blood count on the first glance.

=== Expansion Possiblities ===
 To combine the software of the hospital with our blood count software would offer some extension possibilities. For example it would be possible to show the whole patient information by one click or the nurse could directly inform a doctor if some values exploded.

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06|Gruppe 06]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 1 - Thematic Map

2007-12-02T23:01:19Z

UE-InfoVis0708 0527260:

=== Defintion ===
{{Definition|'''Thematic Maps''' give information about spatial pattern of one ore more specific data themes for standard geographic areas.

For example:

* Physical phenomena like climate
* Human characteristics
* Population density
* Health issues like cholera
* Economy
* Traffic
}}

=== History & Development ===
[[Image:halley.gif|150px|thumb|right|Wind trade map by Halley]]
[[Image:300px-Snow-cholera-map-1.jpg|150px|thumb|right|Thematic map by Snow]]
The term 'thematic map' was introduced first by the german Nikolaus Kreutzburg on a cartography meeting in 1952. Before that, people used other, non-correct terms for these maps.

The 'Nubian Goldmine' map (ancient world ) could already be labeld as a thematic map, however in a sense thematic maps existed since the 16th/17th century. For Example, Edmond Halley (1686) created a map, which included the information of the direction of trade winds in the Atlantic Ocean.

Another famous example of an early thematic map was created by John Snow in 1855 and specifies the cholera progression in a specific area.

=== Use of Thematic Maps ===
Important aims of Thematic Maps:

# Thematic Maps provide specific information about particular locations
# They include general information of spatial patterns
# They open the possibility to compare patterns on one or two different maps

Further it is important for the cartographers to be careful to portray the data on the map so that it will be easy for the audience to use and understand. But they have even to notice the spatial accuracy, the aesthetics, human visual perception, the presentation format and the audience. The audience is very important because a political scientist will have other interest than a biologist scientist.

Even the marks and symbols a cartographer uses to represent data are relevant.
Next step for displaying data is to collect data sets. Therefore you have to differ between univariate, bivariate and multivariate mapping.

Univariate mapping means to deal with one subject like cancer rates or the rainfall of a year. In comparison the bivariate mapping deals with two subjects like the population density in relation to the textile manufacturing. Multivariate mapping means only to deal with more than two subjects.

In following domains for example, thematic maps are used: administation, scheduling, environment, education, science, public relations, transport & tourismn, documentation, national defense, or mass media.

=== Methods ===
[[Image:g156.gif|right|thumb|120px|Choropleth]] [[Image:map100km.png|right|thumb|120px|Proportional]] [[Image:Isopleth_map.jpg|right|thumb|120px|Isolines]] [[Image:tower_maps_large.gif|right|thumb|120px|Dot]] [[Image:zoom2_lowres.jpg|right|thumb|120px|Dasymetric]]
The most important methods for designing a thematic map are:

* Choropleth
* Proportional Symbol
* Isolines
* Dot
* Dasymetric

==== Choropleth ====

Choropleth maps are the most common thematic maps. A choropleth map displays statistical data, which is colored or patterned accordingly to their distribution. Therefor it is necessary to collect the data of equal areas which are as small as possible. Like a grid with e.g. 1km² elements.
This provides an easy way to demonstrate how data is shared across a geographic area, e.g. population density. Typically they are used after elections to show the spreading of the votes. (In these examples administrative borders are used instead of raster variants) 
 
==== Proportional Symbol ====

Proportional Symbols maps represent data associated with point locations. Interpretations of statistics represented by these maps are simple to understand. The Proportional Symbols vary in size from place to place on a map in proportion to the quantities they represents.

==== Isolines ====

An Isoline map uses contour lines to join points where a function has a same particular value and thus show valleys and hills, and the steepness of slopes. Contour lines are curved or straight lines on a map describing the intersection of a real or hypothetical surface with one or more horizontal planes.

==== Dot ====

These maps use dots to show the presence of a feature or occurrence and display a spatial pattern. A dot is not necessarily required to represent a single unit and may indicate any number of entities.

==== Dasymetric ====

''Dasymetric maps'' utilize areal symbols to spatially classify volumetric data. However, although boundaries are displayed on dasymetric maps, these geographic units may span multiple theme values.

=== References ===

[Ross] Zev Ross, ZevRoss Spatial Analysis. Retrieved at: November 8, 2007. http://www.zevross.com/special/history/halley.gif. 

[Answers.com] John Snow. Retrieved at: November 8, 2007. http://www.answers.com/topic/john-snow-physician 

[bbc.co.uk] BBC – Education Scotland – Standard Grade Bitesize. Retrieved at: November 8, 2007. http://www.bbc.co.uk/scotland/education/bitesize/standard/geography/population/distribution_density_rev3.shtml 

[forums.nbn.org.uk] Joint Nature Conservation Committee. Retrieved at: November 8, 2007. http://forums.nbn.org.uk/recreport/index.php?id=5 

[www.volcano.si.edu] Global Volcanism Program. Retrieved at: November 8, 2007. http://www.volcano.si.edu/world/volcano.cfm?vnum=0804-04=&volpage=var 

[Dodge] Martin Dodge, An Atlas of Cyberspaces. Retrieved at: November 8, 2007.
http://www.cybergeography.org/atlas/tower_maps_large.gif 

[www.usgs.gov] Population Density of the San Francisco Bay Area. Retrieved at: November 8, 2007.
http://geography.wr.usgs.gov/science/dasymetric/images/zoom2_lowres.jpg 

[en.wikipdedia.org] Thematic map. Retrieved at: November 8, 2007. http://en.wikipedia.org/wiki/Thematic_map 

[Dr. Michael P. Peterson] THEMATIC MAPS. University of Nebraska at Omaha. Retrieved at: November 8, 2007. http://maps.unomaha.edu/Peterson/carta/Notes/THEMMAP.html 

[www.gigawiz.com] Thematic Maps and Map Projection Utilities. Retrieved at: November 8, 2007. http://www.gigawiz.com/thematic.html 

[Jeffrey J Hemphill] Proportional Symbol Maps with ArcGIS. Retrieved at: November 8, 2007. http://www.geog.ucsb.edu/~jeff/gis/proportional_symbols.html 

[Scott Freundschuh] Course Map Design. UNIVERSITY OF MINNESOTA DULUTH. Retrieved at: November 8, 2007.http://www.d.umn.edu/geog/cartfolder/HTML%20Pages/Map-Types.htm 

[Michelle Halsell] Nubian Gold. Education Development Center, Inc. Retrieved at: December 2,2007. http://www.dignubia.org/maps/timeline/bce-1450.htm

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 1 - Thematic Map

2007-12-02T22:52:28Z

UE-InfoVis0708 0527260:

=== Defintion ===
{{Definition|'''Thematic Maps''' give information about spatial pattern of one ore more specific data themes for standard geographic areas.

For example:

* Physical phenomena like climate
* Human characteristics
* Population density
* Health issues like cholera
* Economy
* Traffic
}}

=== History & Development ===
[[Image:halley.gif|150px|thumb|right|Wind trade map by Halley]]
[[Image:300px-Snow-cholera-map-1.jpg|150px|thumb|right|Thematic map by Snow]]
The term 'thematic map' was introduced first by the german Nikolaus Kreutzburg on a cartography meeting in 1952. Before that, people used other, non-correct terms for these maps.

In a sense thematic maps existed already in the 16th/17th century, although the 'Nubian Goldmine' map (ancient world ) could already be labeld as one. For Example, Edmond Halley (1686) created a map, which included the information of the direction of trade winds in the Atlantic Ocean.

Another famous example of an early thematic map was created by John Snow in 1855 and specifies the cholera progression in a specific area.

=== Use of Thematic Maps ===
Important aims of Thematic Maps:

# Thematic Maps provide specific information about particular locations
# They include general information of spatial patterns
# They open the possibility to compare patterns on one or two different maps

Further it is important for the cartographers to be careful to portray the data on the map so that it will be easy for the audience to use and understand. But they have even to notice the spatial accuracy, the aesthetics, human visual perception, the presentation format and the audience. The audience is very important because a political scientist will have other interest than a biologist scientist.

Even the marks and symbols a cartographer uses to represent data are relevant.
Next step for displaying data is to collect data sets. Therefore you have to differ between univariate, bivariate and multivariate mapping.

Univariate mapping means to deal with one subject like cancer rates or the rainfall of a year. In comparison the bivariate mapping deals with two subjects like the population density in relation to the textile manufacturing. Multivariate mapping means only to deal with more than two subjects.

In following domains for example, thematic maps are used: administation, scheduling, environment, education, science, public relations, transport & tourismn, documentation, national defense, or mass media.

=== Methods ===
[[Image:g156.gif|right|thumb|120px|Choropleth]] [[Image:map100km.png|right|thumb|120px|Proportional]] [[Image:Isopleth_map.jpg|right|thumb|120px|Isolines]] [[Image:tower_maps_large.gif|right|thumb|120px|Dot]] [[Image:zoom2_lowres.jpg|right|thumb|120px|Dasymetric]]
The most important methods for designing a thematic map are:

* Choropleth
* Proportional Symbol
* Isolines
* Dot
* Dasymetric

==== Choropleth ====

Choropleth maps are the most common thematic maps. A choropleth map displays statistical data, which is colored or patterned accordingly to their distribution. Therefor it is necessary to collect the data of equal areas which are as small as possible. Like a grid with e.g. 1km² elements.
This provides an easy way to demonstrate how data is shared across a geographic area, e.g. population density. Typically they are used after elections to show the spreading of the votes. (In these examples administrative borders are used instead of raster variants) 
 
==== Proportional Symbol ====

Proportional Symbols maps represent data associated with point locations. Interpretations of statistics represented by these maps are simple to understand. The Proportional Symbols vary in size from place to place on a map in proportion to the quantities they represents.

==== Isolines ====

An Isoline map uses contour lines to join points where a function has a same particular value and thus show valleys and hills, and the steepness of slopes. Contour lines are curved or straight lines on a map describing the intersection of a real or hypothetical surface with one or more horizontal planes.

==== Dot ====

These maps use dots to show the presence of a feature or occurrence and display a spatial pattern. A dot is not necessarily required to represent a single unit and may indicate any number of entities.

==== Dasymetric ====

''Dasymetric maps'' utilize areal symbols to spatially classify volumetric data. However, although boundaries are displayed on dasymetric maps, these geographic units may span multiple theme values.

=== References ===

[Ross] Zev Ross, ZevRoss Spatial Analysis. Retrieved at: November 8, 2007. http://www.zevross.com/special/history/halley.gif. 

[Answers.com] John Snow. Retrieved at: November 8, 2007. http://www.answers.com/topic/john-snow-physician 

[bbc.co.uk] BBC – Education Scotland – Standard Grade Bitesize. Retrieved at: November 8, 2007. http://www.bbc.co.uk/scotland/education/bitesize/standard/geography/population/distribution_density_rev3.shtml 

[forums.nbn.org.uk] Joint Nature Conservation Committee. Retrieved at: November 8, 2007. http://forums.nbn.org.uk/recreport/index.php?id=5 

[www.volcano.si.edu] Global Volcanism Program. Retrieved at: November 8, 2007. http://www.volcano.si.edu/world/volcano.cfm?vnum=0804-04=&volpage=var 

[Dodge] Martin Dodge, An Atlas of Cyberspaces. Retrieved at: November 8, 2007.
http://www.cybergeography.org/atlas/tower_maps_large.gif 

[www.usgs.gov] Population Density of the San Francisco Bay Area. Retrieved at: November 8, 2007.
http://geography.wr.usgs.gov/science/dasymetric/images/zoom2_lowres.jpg 

[en.wikipdedia.org] Thematic map. Retrieved at: November 8, 2007. http://en.wikipedia.org/wiki/Thematic_map 

[Dr. Michael P. Peterson] THEMATIC MAPS. University of Nebraska at Omaha. Retrieved at: November 8, 2007. http://maps.unomaha.edu/Peterson/carta/Notes/THEMMAP.html 

[www.gigawiz.com] Thematic Maps and Map Projection Utilities. Retrieved at: November 8, 2007. http://www.gigawiz.com/thematic.html 

[Jeffrey J Hemphill] Proportional Symbol Maps with ArcGIS. Retrieved at: November 8, 2007. http://www.geog.ucsb.edu/~jeff/gis/proportional_symbols.html 

[Scott Freundschuh] Course Map Design. UNIVERSITY OF MINNESOTA DULUTH. Retrieved at: November 8, 2007.http://www.d.umn.edu/geog/cartfolder/HTML%20Pages/Map-Types.htm 

[Michelle Halsell] Nubian Gold. Education Development Center, Inc. Retrieved at: December 2,2007. http://www.dignubia.org/maps/timeline/bce-1450.htm

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 1 - Thematic Map

2007-12-02T19:09:14Z

UE-InfoVis0708 0527260:

=== Defintion ===
{{Definition|'''Thematic Maps''' give information about spatial pattern of one ore more specific data themes for standard geographic areas.

For example:

* Physical phenomena like climate
* Human characteristics
* Population density
* Health issues like cholera
* Economy
* Traffic
}}

=== History & Development ===
[[Image:halley.gif|150px|thumb|right|Wind trade map by Halley]]
[[Image:300px-Snow-cholera-map-1.jpg|150px|thumb|right|Thematic map by Snow]]
The term 'thematic map' was introduced first by the german Nikolaus Kreutzburg on a cartography meeting in 1952. Before 1952 people used other, non-correct labels for these maps.

In a wider sense thematic maps existed already in the 16th/17th century. For Example, Edmond Halley (1686) created a map, which included the information of the direction of trade winds in the Atlantic Ocean.

Another famous example of an early thematic map was created by John Snow in 1855 and specifies the cholera progression in a specific area.

=== Use of Thematic Maps ===
Important aims of Thematic Maps:

# Thematic Maps provide specific information about particular locations
# They include general information of spatial patterns
# They open the possibility to compare patterns on one or two different maps

Further it is important for the cartographers to be careful to portray the data on the map so that it will be easy for the audience to use and understand. But they have even to notice the spatial accuracy, the aesthetics, human visual perception, the presentation format and the audience. The audience is very important because a political scientist will have other interest than a biologist scientist.

Even the marks and symbols a cartographer uses to represent data are relevant.
Next step for displaying data is to collect data sets. Therefore you have to differ between univariate, bivariate and multivariate mapping.

Univariate mapping means to deal with one subject like cancer rates or the rainfall of a year. In comparison the bivariate mapping deals with two subjects like the population density in relation to the textile manufacturing. Multivariate mapping means only to deal with more than two subjects.

In following domains for example, thematic maps are used: administation, scheduling, environment, education, science, public relations, transport & tourismn, documentation, national defense, or mass media.

=== Methods ===
[[Image:g156.gif|right|thumb|120px|Choropleth]] [[Image:map100km.png|right|thumb|120px|Proportional]] [[Image:Isopleth_map.jpg|right|thumb|120px|Isolines]] [[Image:tower_maps_large.gif|right|thumb|120px|Dot]] [[Image:zoom2_lowres.jpg|right|thumb|120px|Dasymetric]]
The most important methods for designing a thematic map are:

* Choropleth
* Proportional Symbol
* Isolines
* Dot
* Dasymetric

==== Choropleth ====

Choropleth maps are the most common thematic maps. A choropleth map displays statistical data, which is colored or patterned accordingly to their distribution. Therefor it is necessary to collect the data of equal areas which are as small as possible. Like a grid with e.g. 1km² elements.
This provides an easy way to demonstrate how data is shared across a geographic area, e.g. population density. Typically they are used after elections to show the spreading of the votes. (In these examples administrative borders are used instead of raster variants) 
 
==== Proportional Symbol ====

Proportional Symbols maps represent data associated with point locations. Interpretations of statistics represented by these maps are simple to understand. The Proportional Symbols vary in size from place to place on a map in proportion to the quantities they represents.

==== Isolines ====

An Isoline map uses contour lines to join points where a function has a same particular value and thus show valleys and hills, and the steepness of slopes. Contour lines are curved or straight lines on a map describing the intersection of a real or hypothetical surface with one or more horizontal planes.

==== Dot ====

These maps use dots to show the presence of a feature or occurrence and display a spatial pattern. A dot is not necessarily required to represent a single unit and may indicate any number of entities.

==== Dasymetric ====

''Dasymetric maps'' utilize areal symbols to spatially classify volumetric data. However, although boundaries are displayed on dasymetric maps, these geographic units may span multiple theme values.

=== References ===

[Ross] Zev Ross, ZevRoss Spatial Analysis. Retrieved at: November 8, 2007. http://www.zevross.com/special/history/halley.gif. 

[Answers.com] John Snow. Retrieved at: November 8, 2007. http://www.answers.com/topic/john-snow-physician 

[bbc.co.uk] BBC – Education Scotland – Standard Grade Bitesize. Retrieved at: November 8, 2007. http://www.bbc.co.uk/scotland/education/bitesize/standard/geography/population/distribution_density_rev3.shtml 

[forums.nbn.org.uk] Joint Nature Conservation Committee. Retrieved at: November 8, 2007. http://forums.nbn.org.uk/recreport/index.php?id=5 

[www.volcano.si.edu] Global Volcanism Program. Retrieved at: November 8, 2007. http://www.volcano.si.edu/world/volcano.cfm?vnum=0804-04=&volpage=var 

[Dodge] Martin Dodge, An Atlas of Cyberspaces. Retrieved at: November 8, 2007.
http://www.cybergeography.org/atlas/tower_maps_large.gif 

[www.usgs.gov] Population Density of the San Francisco Bay Area. Retrieved at: November 8, 2007.
http://geography.wr.usgs.gov/science/dasymetric/images/zoom2_lowres.jpg 

[en.wikipdedia.org] Thematic map. Retrieved at: November 8, 2007. http://en.wikipedia.org/wiki/Thematic_map 

[Dr. Michael P. Peterson] THEMATIC MAPS. University of Nebraska at Omaha. Retrieved at: November 8, 2007. http://maps.unomaha.edu/Peterson/carta/Notes/THEMMAP.html 

[www.gigawiz.com] Thematic Maps and Map Projection Utilities. Retrieved at: November 8, 2007. http://www.gigawiz.com/thematic.html 

[Jeffrey J Hemphill] Proportional Symbol Maps with ArcGIS. Retrieved at: November 8, 2007. http://www.geog.ucsb.edu/~jeff/gis/proportional_symbols.html 

[Scott Freundschuh] Course Map Design. UNIVERSITY OF MINNESOTA DULUTH. Retrieved at: November 8, 2007.http://www.d.umn.edu/geog/cartfolder/HTML%20Pages/Map-Types.htm

File:Zoom2 lowres.jpg

2007-11-27T19:32:22Z

UE-InfoVis0708 0527260:

== Description ==
Dasymetric example
== Copyright status ==

== Source ==
[www.usgs.gov] Population Density of the San Francisco Bay Area. Retrieved at: November 8, 2007. http://geography.wr.usgs.gov/science/dasymetric/images/zoom2_lowres.jpg

File:Tower maps large.gif

2007-11-27T19:31:42Z

UE-InfoVis0708 0527260:

== Description ==
Dot example
== Copyright status ==

== Source ==
[Dodge] Martin Dodge, An Atlas of Cyberspaces. Retrieved at: November 8, 2007. http://www.cybergeography.org/atlas/tower_maps_large.gif

File:Isopleth map.jpg

2007-11-27T19:31:06Z

UE-InfoVis0708 0527260:

== Description ==
Example Isopleth map
== Copyright status ==

== Source ==
[www.volcano.si.edu] Global Volcanism Program. Retrieved at: November 8, 2007. http://www.volcano.si.edu/world/volcano.cfm?vnum=0804-04=&volpage=var

File:Map100km.png

2007-11-27T19:30:09Z

UE-InfoVis0708 0527260:

== Description ==
Proportional Symbol example
== Copyright status ==

== Source ==
[forums.nbn.org.uk] Joint Nature Conservation Committee. Retrieved at: November 8, 2007. http://forums.nbn.org.uk/recreport/index.php?id=5

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 1 - Thematic Map

2007-11-27T19:29:23Z

UE-InfoVis0708 0527260:

=== Defintion ===
{{Definition|'''Thematic Maps''' give information about spatial pattern of one ore more specific data themes for standard geographic areas.

For example:

* Physical phenomena like climate
* Human characteristics
* Population density
* Health issues like cholera
* Economy
* Traffic

General maps show you where you can find something on this world but a thematic map tells you the story about.
}}

=== History & Development ===
[[Image:halley.gif|150px|thumb|right|First map by Halley]]
[[Image:300px-Snow-cholera-map-1.jpg|150px|thumb|right|Thematic map by Snow]]
The first map was created by Edmond Halley (1686). This map includes the information of the direction of trade winds in the Atlantic Ocean.

The most famous example of an early thematic map was created by John Snow in 1855 and specifies the cholera progression in a specific area.

=== Use of Thematic Maps ===
Important aims of Thematic Maps:

# Thematic Maps provide specific information about particular locations
# They include general information of spatial patterns
# They open the possibility to compare patterns on one or two different maps

Further it is important for the cartographers to be careful to portray the data on the map so that it will be easy for the audience to use and understand. But they have even to notice the spatial accuracy, the aesthetics, human visual perception, the presentation format and the audience. The audience is very important because a political scientist will have other interest than a biologist scientist.

Even the marks and symbols a cartographer uses to represent data are relevant.
Next step for displaying data is to collect data sets. Therefore you have to differ between univariate, bivariate and multivariate mapping.

Univariate mapping means to deal with one subject like cancer rates or the rainfall of a year. In comparison the bivariate mapping deals with two subjects like the population density in relation to the textile manufacturing. Multivariate mapping means only to deal with more than two subjects.

=== Methods ===
[[Image:g156.gif|right|thumb|120px|Choropleth]] [[Image:map100km.png|right|thumb|120px|Proportional]] [[Image:Isopleth_map.jpg|right|thumb|120px|Isarithmic]] [[Image:tower_maps_large.gif|right|thumb|120px|Dot]] [[Image:zoom2_lowres.jpg|right|thumb|120px|Dasymetric]]
The most important methods for designing a thematic map are:

* Choropleth
* Proportional Symbol
* Isolines
* Dot
* Dasymetric

==== Choropleth ====

Choropleth maps are the most common thematic maps. A choropleth map displays statistical data, which is colored or patterned accordingly to their distribution. It provides an easy way to demonstrate how data is shared across a geographic area, e.g. population density. Typically they are used after elections to show the spreading of the votes. 
 
==== Proportional Symbol ====

Proportional Symbols maps represent data associated with point locations. Interpretations of statistics represented by these maps are simple to understand. The Proportional Symbols vary in size from place to place on a map in proportion to the quantities they represents.

==== Isarithmic ====

An Isarithmic map uses contour lines to join points where a function has a same particular value and thus show valleys and hills, and the steepness of slopes. Contour lines are curved or straight lines on a map describing the intersection of a real or hypothetical surface with one or more horizontal planes.

==== Dot ====

These maps use dots to show the presence of a feature or occurrence and display a spatial pattern. A dot is not necessarily required to represent a single unit and may indicate any number of entities.

==== Dasymetric ====

''Dasymetric maps'' utilize areal symbols to spatially classify volumetric data. However, although boundaries are displayed on dasymetric maps, these geographic units may span multiple theme values.

=== References ===

[Ross] Zev Ross, ZevRoss Spatial Analysis. Retrieved at: November 8, 2007. http://www.zevross.com/special/history/halley.gif. 

[Answers.com] John Snow. Retrieved at: November 8, 2007. http://www.answers.com/topic/john-snow-physician 

[bbc.co.uk] BBC – Education Scotland – Standard Grade Bitesize. Retrieved at: November 8, 2007. http://www.bbc.co.uk/scotland/education/bitesize/standard/geography/population/distribution_density_rev3.shtml 

[forums.nbn.org.uk] Joint Nature Conservation Committee. Retrieved at: November 8, 2007. http://forums.nbn.org.uk/recreport/index.php?id=5 

[www.volcano.si.edu] Global Volcanism Program. Retrieved at: November 8, 2007. http://www.volcano.si.edu/world/volcano.cfm?vnum=0804-04=&volpage=var 

[Dodge] Martin Dodge, An Atlas of Cyberspaces. Retrieved at: November 8, 2007.
http://www.cybergeography.org/atlas/tower_maps_large.gif 

[www.usgs.gov] Population Density of the San Francisco Bay Area. Retrieved at: November 8, 2007.
http://geography.wr.usgs.gov/science/dasymetric/images/zoom2_lowres.jpg 

[en.wikipdedia.org] Thematic map. Retrieved at: November 8, 2007. http://en.wikipedia.org/wiki/Thematic_map 

[Dr. Michael P. Peterson] THEMATIC MAPS. University of Nebraska at Omaha. Retrieved at: November 8, 2007. http://maps.unomaha.edu/Peterson/carta/Notes/THEMMAP.html 

[www.gigawiz.com] Thematic Maps and Map Projection Utilities. Retrieved at: November 8, 2007. http://www.gigawiz.com/thematic.html 

[Jeffrey J Hemphill] Proportional Symbol Maps with ArcGIS. Retrieved at: November 8, 2007. http://www.geog.ucsb.edu/~jeff/gis/proportional_symbols.html 

[Scott Freundschuh] Course Map Design. UNIVERSITY OF MINNESOTA DULUTH. Retrieved at: November 8, 2007.http://www.d.umn.edu/geog/cartfolder/HTML%20Pages/Map-Types.htm

File:G156.gif

2007-11-27T19:28:30Z

UE-InfoVis0708 0527260:

== Description ==
Choropleth example
== Copyright status ==

== Source ==
[bbc.co.uk] BBC – Education Scotland – Standard Grade Bitesize. Retrieved at: November 8, 2007. http://www.bbc.co.uk/scotland/education/bitesize/standard/img/geography/population/g156.gif

File:300px-Snow-cholera-map-1.jpg

2007-11-27T19:24:18Z

UE-InfoVis0708 0527260:

== Description ==
Thematic map created by John Snow in 1855.
== Copyright status ==

== Source ==
[Answers.com] John Snow. Retrieved at: November 8, 2007. http://www.answers.com/topic/snow-cholera-map-1-jpg

File:300px-Snow-cholera-map-1.jpg

2007-11-27T19:23:11Z

UE-InfoVis0708 0527260:

File:Halley.gif

2007-11-27T19:21:32Z

UE-InfoVis0708 0527260:

== Description ==
The first map created by Edmond Halley including the information of the direction of trade winds in the Atlantic Ocean.
== Copyright status ==

== Source ==
[Ross] Zev Ross, ZevRoss Spatial Analysis. Retrieved at: November 8, 2007. http://www.zevross.com/special/history/halley.gif.

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 1 - Thematic Map

2007-11-27T19:19:25Z

UE-InfoVis0708 0527260:

=== Defintion ===
{{Definition|'''Thematic Maps''' give information about spatial pattern of one ore more specific data themes for standard geographic areas.

For example:

* Physical phenomena like climate
* Human characteristics
* Population density
* Health issues like cholera
* Economy
* Traffic

General maps show you where you can find something on this world but a thematic map tells you the story about.
}}

=== History & Development ===
[[Image:halley.gif|150px|thumb|right|First map by Halley]]
[[Image:300px-Snow-cholera-map-1.jpg|150px|thumb|right|Thematic map by Snow]]
The first map was created by Edmond Halley (1686). This map includes the information of the direction of trade winds in the Atlantic Ocean.

The most famous example of an early thematic map was created by John Snow in 1855 and specifies the cholera progression in a specific area.

=== Use of Thematic Maps ===
Important aims of Thematic Maps:

# Thematic Maps provide specific information about particular locations
# They include general information of spatial patterns
# They open the possibility to compare patterns on one or two different maps

Further it is important for the cartographers to be careful to portray the data on the map so that it will be easy for the audience to use and understand. But they have even to notice the spatial accuracy, the aesthetics, human visual perception, the presentation format and the audience. The audience is very important because a political scientist will have other interest than a biologist scientist.

Even the marks and symbols a cartographer uses to represent data are relevant.
Next step for displaying data is to collect data sets. Therefore you have to differ between univariate, bivariate and multivariate mapping.

Univariate mapping means to deal with one subject like cancer rates or the rainfall of a year. In comparison the bivariate mapping deals with two subjects like the population density in relation to the textile manufacturing. Multivariate mapping means only to deal with more than two subjects.

=== Methods ===
[[Image:g156.gif|right|thumb|120px|Choropleth]] [[Image:map100km.png|right|thumb|120px|Proportional]] [[Image:Isopleth_map.jpg|right|thumb|120px|Isarithmic]] [[Image:tower_maps_large.gif|right|thumb|120px|Dot]] [[Image:zoom2_lowres.jpg|right|thumb|120px|Dasymetric]]
The most important methods for designing a thematic map are:

* Choropleth
* Proportional Symbol
* Isolines
* Dot
* Dasymetric

==== Choropleth ====

Choropleth maps are the most common thematic maps. A choropleth map displays statistical data, which is colored or patterned accordingly to their distribution. It provides an easy way to demonstrate how data is shared across a geographic area, e.g. population density. Typically they are used after elections to show the spreading of the votes. 
 
==== Proportional Symbol ====

Proportional Symbols maps represent data associated with point locations. Interpretations of statistics represented by these maps are simple to understand. The Proportional Symbols vary in size from place to place on a map in proportion to the quantities they represents.

==== Isarithmic ====

An Isarithmic map uses contour lines to join points where a function has a same particular value and thus show valleys and hills, and the steepness of slopes. Contour lines are curved or straight lines on a map describing the intersection of a real or hypothetical surface with one or more horizontal planes.

==== Dot ====

These maps use dots to show the presence of a feature or occurrence and display a spatial pattern. A dot is not necessarily required to represent a single unit and may indicate any number of entities.

==== Dasymetric ====

''Dasymetric maps'' utilize areal symbols to spatially classify volumetric data. However, although boundaries are displayed on dasymetric maps, these geographic units may span multiple theme values.

=== References ===

[Ross] Zev Ross, ZevRoss Spatial Analysis. Retrieved at: November 8, 2007. http://www.zevross.com/special/history/halley.gif. 

[Answers.com] John Snow. Retrieved at: November 8, 2007. http://www.answers.com/topic/john-snow-physician 

[bbc.co.uk] BBC – Education Scotland – Standard Grade Bitesize. Retrieved at: November 8, 2007. http://www.bbc.co.uk/home/d/ 

[forums.nbn.org.uk] Joint Nature Conservation Committee. Retrieved at: November 8, 2007. http://forums.nbn.org.uk/recreport/index.php?id=5 

[www.volcano.si.edu] Global Volcanism Program. Retrieved at: November 8, 2007. http://www.volcano.si.edu/world/volcano.cfm?vnum=0804-04=&volpage=var 

[Dodge] Martin Dodge, An Atlas of Cyberspaces. Retrieved at: November 8, 2007.
http://www.cybergeography.org/atlas/tower_maps_large.gif 

[www.usgs.gov] Population Density of the San Francisco Bay Area. Retrieved at: November 8, 2007.
http://geography.wr.usgs.gov/science/dasymetric/images/zoom2_lowres.jpg 

[en.wikipdedia.org] Thematic map. Retrieved at: November 8, 2007. http://en.wikipedia.org/wiki/Thematic_map 

[Dr. Michael P. Peterson] THEMATIC MAPS. University of Nebraska at Omaha. Retrieved at: November 8, 2007. http://maps.unomaha.edu/Peterson/carta/Notes/THEMMAP.html 

[www.gigawiz.com] Thematic Maps and Map Projection Utilities. Retrieved at: November 8, 2007. http://www.gigawiz.com/thematic.html 

[Jeffrey J Hemphill] Proportional Symbol Maps with ArcGIS. Retrieved at: November 8, 2007. http://www.geog.ucsb.edu/~jeff/gis/proportional_symbols.html 

[Scott Freundschuh] Course Map Design. UNIVERSITY OF MINNESOTA DULUTH. Retrieved at: November 8, 2007.http://www.d.umn.edu/geog/cartfolder/HTML%20Pages/Map-Types.htm

File:LOD5.jpg

2007-11-27T19:11:35Z

UE-InfoVis0708 0527260:

== Description ==
Hierarchical LOD
== Copyright status ==

== Source ==
[Reddy, 2007] Martin Reddy. Run-Time Management for LOD. Pixar Animation Studios. Retrieved at: November 8, 2007. http://lodbook.com/course/2003/Reddy_RunTime.ppt

File:LOD4.jpg

2007-11-27T19:10:50Z

UE-InfoVis0708 0527260:

== Description ==
View Dependent LOD
== Copyright status ==

== Source ==
[Reddy, 2007] Martin Reddy. Run-Time Management for LOD. Pixar Animation Studios. Retrieved at: November 8, 2007. http://lodbook.com/course/2003/Reddy_RunTime.ppt

File:LOD2.jpg

2007-11-27T19:09:55Z

UE-InfoVis0708 0527260:

== Description ==
Maximum detail of an object for close-ups and a minimum of detail for very far away objects.
== Copyright status ==

== Source ==
[Luebke, 2002] David Luebke. Course Real-Time Rendering. University of Virginia. Created at: September 26, 2002. Retrieved at: November 8, 2007. http://www.cs.virginia.edu/~gfx/Courses/2004/RealTime/lecture06.LOD1.ppt.

File:LOD1.jpg

2007-11-27T19:08:57Z

UE-InfoVis0708 0527260:

== Description ==
Maximum to minimum LOD
== Copyright status ==

== Source ==
[Luebke, 2002] David Luebke. Course Real-Time Rendering. University of Virginia. Created at: September 26, 2002. Retrieved at: November 8, 2007. http://www.cs.virginia.edu/~gfx/Courses/2004/RealTime/lecture06.LOD1.ppt.

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 1 - Level of Detail

2007-11-27T18:55:29Z

UE-InfoVis0708 0527260:

=== Definition ===
{{Definition|The basic idea of '''Level of Detail''' is to decrease the complexity of an object or model, so that less information has to be saved.}}

=== Overview ===
The starting point is a high resolution object. But not all of the information is important from each view or distant! The solution is to simplify these small or distant objects as much as possible. This process will even be called Level of Detail or LOD. For that the object is divided into a grid of polygons, which will be reduced step by step. 

{{Quotation|For example, a dodecahedron looks like a sphere from a sufficiently large distance and thus can be used to model it so long as it is viewed from that or a greater distance. However, if it must ever be viewed more closely, it will look like a dodecahedron. One solution to this is simply to define it with the most detail that will ever be necessary. However, then it might have far more detail than is needed to represent it at large distances, and in a complex environment with many such objects, there would be too many polygons (or other geometric primitives) for the visible surface algorithms to efficiently handle.|[http://design.osu.edu/carlson/history/PDFs/clark-vis-surface.pdf]}}

=== Parts ===
LOD is not such an easy one man process. In fact of this we will now subdivide the frameworks into four important parts: 
* Discrete LOD
* Continuous LOD
* View Dependent LOD
* Hierarchical LOD

==== The Discrete LOD (DLOD) ====
[[Image:LOD1.jpg|thumb|180px|Pic.1 Maximum to minimum LOD]][[Image:LOD2.jpg|thumb|180px|Pic.2 Closeups & far away objects]]
The Discrete LOD is the traditional version. The concept is to provide some different models to represent an object. Therefore it is possible to use external algorithm (normally non trivial). The idea is to divide these models in several parts, dependent on the needed Level of Detail (picture 1).

Like we have already described in the example above, it is important to think about how much information really is needed. Maximum detail of an object for close-ups and a minimum of detail for very far away objects (picture 2).

An Advantage of DLOD is that it is the simplest programming model and the run-time rendering needs only to combine the several models of the Level of Details. But there is even an unfortunately disadvantage, because sometimes are DLOD not adequate for drastic simplification. Large objects need to be subdivided and the small objects must be combined. This implementation would be very difficult even when not impossible with discrete algorithms.

==== Continous LOD ====
The discrete LOD is more or less the prototype of the Continuous LOD. It is a continuous spectrum of LODs. That means that one picture includes the information, necessary for more levels of details. These are measured by an algorithm. So it is possible to extract the best model for the actual viewpoint in real time.

===== Example: =====
[[Image:LOD3.jpg|left|200px|Example: Continious LOD]]

Level of Detail 1: red points 
Level of Detail 2: red + blue points 
Level of Detail 3: red + blue + green points 
Level of Detail 4: red + blue + green + black points 

==== View Dependent LOD ====
[[Image:LOD4.jpg|right|150px|Example: View Dependent LOD]]
The View Dependent LOD uses the current view parameters to find the best resolution for the current view.

For example you have a robot which travels through the environment. It is only useful to show a high resolution version from things the robot is gazing at. Like the focus of the human eyes.

==== Hierarchical LOD ====

Hierarchical LOD uses the several models of the Discrete LOD and combines them to a group in a hierarchy. So it is possible to extract the important points of a whole environment.
===== Example: =====
[[Image:LOD5.jpg|right|250px|Example: Hierachical LOD]]
In a computer-game it is usual to zoom into the environment. Therefore it is the best solution to have some different resolutions and to morph between them. In this example you see three LODs, the first one at a very low resolution and the third one with the highest resolution mostly outgoing from the original object.

=== References ===

[1] [Clark, 197] James H. Clark. Hierarchical Geometric Models for Visible Surface Algorithms. In Proceedings of the Third Annual Conference on Computer Graphics, Interactive Techniques, and Image Processing, pages 547-554, July 14-16, 1976. Communications October 1976 of Volume 19 the ACM Number 10. 

[Luebke, 2002] David Luebke. Course Real-Time Rendering. University of Virginia. Created at: September 26, 2002. Retrieved at: November 8, 2007. http://www.cs.virginia.edu/~gfx/Courses/2004/RealTime/lecture06.LOD1.ppt. 

[Fischer, 2007] Matthias Fischer. Vorlesung Algorithmen in der Computergrafik SS 2007 Universität Paderborn. Retrieved at: November 8, 2007. http://wwwhni.uni-paderborn.de/fileadmin/hni_alg/lehre/SS2007/AlgoCG/algoCG_LODPM.ppt 

[Reddy, 2007] Martin Reddy. Run-Time Management for LOD. Pixar Animation Studios. Retrieved at: November 8, 2007. http://lodbook.com/course/2003/Reddy_RunTime.ppt 

[en.wikipedia.org] Level of Detail. Retrieved at: November 8, 2007. http://en.wikipedia.org/wiki/Level_of_detail 

[de.wikipedia.org] Level of Detail. Retrieved at: November 8, 2007. http://de.wikipedia.org/wiki/Level_of_Detail 

[DGL Wiki ] Level of Detail. Delphi-OpenGL-Community. Retrieved at: November 8, 2007.
http://wiki.delphigl.com/index.php/LOD 

[Deussen, 2002] Oliver Deussen. Level-of-Detail. Vorlesung Computergraphik II. TU Dresden. Retrieved at: November 8, 2007. http://web.inf.tu-dresden.de/ST2/cg/pdf_daten/Informatik/HS/cg2/ss02/lod_script.pdf 

[Southern and Gain] R. Southern and J. Gain. Creation and Control of Real-time Continuous Level of Detail on Programmable Graphics Hardware. Collaborative Visual Computing Laboratory University of Cape Town, South Africa. Retrieved at: November 8, 2007. http://www.cl.cam.ac.uk/~rs416/papers/southern01_CGF.pdf 

[Birkholz] Hermann Birkholz. Texturing of Continuous LOD Meshes with the Hierarchical Texture Atlas. University of Rostock, Germany. Retrieved at: November 8, 2007.http://wwwicg.informatik.uni-rostock.de/~hb01/doc/Texturing%20of%20Continuous%20LOD%20Meshes%20with%20the%20Hierarchical%20Texture.pdf

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 1 - Level of Detail

2007-11-27T18:38:14Z

UE-InfoVis0708 0527260:

=== Definition ===
The basic idea of ''Level of Detail'' is to decrease the complexity of an object or model, so that less information has to be saved. 

=== Overview ===
The starting point is a high resolution object. But not all of the information is important from each view or distant! The solution is to simplify these small or distant objects as much as possible. This process will even be called Level of Detail or LOD. For that the object is divided into a grid of polygons, which will be reduced step by step. 

{{Quotation|For example, a dodecahedron looks like a sphere from a sufficiently large distance and thus can be used to model it so long as it is viewed from that or a greater distance. However, if it must ever be viewed more closely, it will look like a dodecahedron. One solution to this is simply to define it with the most detail that will ever be necessary. However, then it might have far more detail than is needed to represent it at large distances, and in a complex environment with many such objects, there would be too many polygons (or other geometric primitives) for the visible surface algorithms to efficiently handle.|[http://design.osu.edu/carlson/history/PDFs/clark-vis-surface.pdf]}}

=== Parts ===
LOD is not such an easy one man process. In fact of this we will now subdivide the frameworks into four important parts: 
* Discrete LOD
* Continuous LOD
* View Dependent LOD
* Hierarchical LOD

==== The Discrete LOD (DLOD) ====
[[Image:LOD1.jpg|thumb|180px|Pic.1 Maximum to minimum LOD]][[Image:LOD2.jpg|thumb|180px|Pic.2 Closeups & far away objects]]
The Discrete LOD is the traditional version. The concept is to provide some different models to represent an object. Therefore it is possible to use external algorithm (normally non trivial). The idea is to divide these models in several parts, dependent on the needed Level of Detail (picture 1).

Like we have already described in the example above, it is important to think about how much information really is needed. Maximum detail of an object for close-ups and a minimum of detail for very far away objects (picture 2).

An Advantage of DLOD is that it is the simplest programming model and the run-time rendering needs only to combine the several models of the Level of Details. But there is even an unfortunately disadvantage, because sometimes are DLOD not adequate for drastic simplification. Large objects need to be subdivided and the small objects must be combined. This implementation would be very difficult even when not impossible with discrete algorithms.

==== Continous LOD ====
The discrete LOD is more or less the prototype of the Continuous LOD. It is a continuous spectrum of LODs. That means that one picture includes the information, necessary for more levels of details. These are measured by an algorithm. So it is possible to extract the best model for the actual viewpoint in real time.

===== Example: =====
[[Image:LOD3.jpg|left|200px|Example: Continious LOD]]

Level of Detail 1: red points 
Level of Detail 2: red + blue points 
Level of Detail 3: red + blue + green points 
Level of Detail 4: red + blue + green + black points 

==== View Dependent LOD ====
[[Image:LOD4.jpg|right|150px|Example: View Dependent LOD]]
The View Dependent LOD uses the current view parameters to find the best resolution for the current view.

For example you have a robot which travels through the environment. It is only useful to show a high resolution version from things the robot is gazing at. Like the focus of the human eyes.

==== Hierarchical LOD ====

Hierarchical LOD uses the several models of the Discrete LOD and combines them to a group in a hierarchy. So it is possible to extract the important points of a whole environment.
===== Example: =====
[[Image:LOD5.jpg|right|250px|Example: Hierachical LOD]]
In a computer-game it is usual to zoom into the environment. Therefore it is the best solution to have some different resolutions and to morph between them. In this example you see three LODs, the first one at a very low resolution and the third one with the highest resolution mostly outgoing from the original object.

=== References ===

[1] [Clark, 197] James H. Clark. Hierarchical Geometric Models for Visible Surface Algorithms. In Proceedings of the Third Annual Conference on Computer Graphics, Interactive Techniques, and Image Processing, pages 547-554, July 14-16, 1976. Communications October 1976 of Volume 19 the ACM Number 10. 

[Luebke, 2002] David Luebke. Course Real-Time Rendering. University of Virginia. Created at: September 26, 2002. Retrieved at: November 8, 2007. http://www.cs.virginia.edu/~gfx/Courses/2004/RealTime/lecture06.LOD1.ppt. 

[Fischer, 2007] Matthias Fischer. Vorlesung Algorithmen in der Computergrafik SS 2007 Universität Paderborn. Retrieved at: November 8, 2007. http://wwwhni.uni-paderborn.de/fileadmin/hni_alg/lehre/SS2007/AlgoCG/algoCG_LODPM.ppt 

[Reddy, 2007] Martin Reddy. Run-Time Management for LOD. Pixar Animation Studios. Retrieved at: November 8, 2007. http://lodbook.com/course/2003/Reddy_RunTime.ppt 

[en.wikipedia.org] Level of Detail. Retrieved at: November 8, 2007. http://en.wikipedia.org/wiki/Level_of_detail 

[de.wikipedia.org] Level of Detail. Retrieved at: November 8, 2007. http://de.wikipedia.org/wiki/Level_of_Detail 

[DGL Wiki ] Level of Detail. Delphi-OpenGL-Community. Retrieved at: November 8, 2007.
http://wiki.delphigl.com/index.php/LOD 

[Deussen, 2002] Oliver Deussen. Level-of-Detail. Vorlesung Computergraphik II. TU Dresden. Retrieved at: November 8, 2007. http://web.inf.tu-dresden.de/ST2/cg/pdf_daten/Informatik/HS/cg2/ss02/lod_script.pdf 

[Southern and Gain] R. Southern and J. Gain. Creation and Control of Real-time Continuous Level of Detail on Programmable Graphics Hardware. Collaborative Visual Computing Laboratory University of Cape Town, South Africa. Retrieved at: November 8, 2007. http://www.cl.cam.ac.uk/~rs416/papers/southern01_CGF.pdf 

[Birkholz] Hermann Birkholz. Texturing of Continuous LOD Meshes with the Hierarchical Texture Atlas. University of Rostock, Germany. Retrieved at: November 8, 2007.http://wwwicg.informatik.uni-rostock.de/~hb01/doc/Texturing%20of%20Continuous%20LOD%20Meshes%20with%20the%20Hierarchical%20Texture.pdf

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 2

2007-11-23T16:03:56Z

UE-InfoVis0708 0527260:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]

=== Zu beurteilende Tabelle ===

[[Image:few_performance_summary.jpg]]

== Critics ==

*White space should be used instead of girds to delineate rows and columns. Grids break up the data, while white space makes it easier scanning across a single row or column. Optionally subtle horizontal fill shades could be used to delineate the rows from each other.
*In the given table the (at least for us) most important information, the actual bookings, are placed in the last columns.
*The order of the given table is wrong. Quantitative values which should be compared should be placed close to each other and quantitative values which are derived form other values should be placed just to the right of the column from which they are derived. The order of the columns should be rearranged to: 
:{| border=1
|Sales Rep
|Quota
|Actual Bookings
|Variance to Quota
|% of Quota
|Forecast
|}

*Choosing ‘Sales Rep’ for the row header is a good decision, because it has the most subdivisions and arranging them across the columns would exceed the page width. Additionally the reader has all relevant information about one sales rep. in a single row. The sales rep. are also alphabetically ordered, which makes it easy to find a particular one.
*The column header ‘Sales Rep’ should be aligned to the left, as this alignment works best with text. The rest of the column headers should be aligned to the right, as right alignment works best with numbers. This will help to improve scanning the columns.
*The column headers fill shade is a good method to delineate the table header from the rest of the table, although it could be slightly more subtle. Also a ruler could be used instead of a fill shade.
*Each percentage values in the column ‘% of Quota’ should have a percentage sign to the right.
*The table has no summarizing values, only the sum of each column seems reasonable. The column summaries should be delineated from the rest of the table the same way as the column headers.

== Improved Table ==

== Declaration of improvements ==

*White space instead of grids makes it a lot easier for the reader to track across the rows.
*The (for us) most important information of the actual bookings were placed as second column, so the reader doesn’t need to scan the whole row. In addition the column was highlighted with a subtle shade to get the readers attention.
*With the changed order the reader can easily compare the quota with the actual bookings. The columns ‘Variance to Quota’ and ‘% of Quota’ are also next to the column ‘Actual Bookings”, from which they are derived, which makes it easier to analyze them.
*With the changed alignment of the column headers, it’s easer for the reader to scan the columns.
*The percentage sign was added to each value in the ’% of Quota’ column.
*Instead of fill shades rulers were used to separate headers and footers.
*Total column sums were added to provide the reader with further information.

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06|Gruppe 06]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 2

2007-11-23T15:45:08Z

UE-InfoVis0708 0527260:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]

=== Zu beurteilende Tabelle ===

[[Image:few_performance_summary.jpg]]

== Critics ==

*White space should be used instead of girds to delineate rows and columns. Grids break up the data, while white space makes it easier scanning across a single row or column. Optionally subtle horizontal fill shades could be used to delineate the rows from each other.
*In the given table the (at least for us) most important information, the actual bookings, are placed in the last columns.
*The order of the given table is wrong. Quantitative values which should be compared should be placed close to each other and quantitative values which are derived form other values should be placed just to the right of the column from which they are derived.
The order of the columns should be rearranged to:
{| border=1
|Sales Rep
|Quota
|Actual Bookings
|Variance to Quota
|% of Quota
|Forecast
|} 

*Choosing ‘Sales Rep’ for the row header is a good decision, because it has the most subdivisions and arranging them across the columns would exceed the page width. Additionally the reader has all relevant information about one sales rep. in a single row. The sales rep. are also alphabetically ordered, which makes it easy to find a particular one.
*The column header ‘Sales Rep’ should be aligned to the left, as this alignment works best with text. The rest of the column headers should be aligned to the right, as right alignment works best with numbers. This will help to improve scanning the columns.
*The column headers fill shade is a good method to delineate the table header from the rest of the table, although it could be slightly more subtle. Also a ruler could be used instead of a fill shade.
*Each percentage values in the column ‘% of Quota’ should have a percentage sign to the right.
*The table has no summarizing values, only the sum of each column seems reasonable. The column summaries should be delineated from the rest of the table the same way as the column headers.

== Improved Table ==

== Declaration of improvements ==

*White space instead of grids makes it a lot easier for the reader to track across the rows.
*The (for us) most important information of the actual bookings were placed as second column, so the reader doesn’t need to scan the whole row. In addition the column was highlighted with a subtle shade to get the readers attention.
*With the changed order the reader can easily compare the quota with the actual bookings. The columns ‘Variance to Quota’ and ‘% of Quota’ are also next to the column ‘Actual Bookings”, from which they are derived, which makes it easier to analyze them.
*With the changed alignment of the column headers, it’s easer for the reader to scan the columns.
*The percentage sign was added to each value in the ’% of Quota’ column.
*Instead of fill shades rulers were used to separate headers and footers.
*Total column sums were added to provide the reader with further information.

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06|Gruppe 06]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 2

2007-11-23T15:42:12Z

UE-InfoVis0708 0527260:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]

=== Zu beurteilende Tabelle ===

[[Image:few_performance_summary.jpg]]

== Critics ==

*White space should be used instead of girds to delineate rows and columns. Grids break up the data, while white space makes it easier scanning across a single row or column. Optionally subtle horizontal fill shades could be used to delineate the rows from each other.
*In the given table the (at least for us) most important information, the actual bookings, are placed in the last columns.
*The order of the given table is wrong. Quantitative values which should be compared should be placed close to each other and quantitative values which are derived form other values should be placed just to the right of the column from which they are derived.
The order of the columns should be rearranged to:
{| border=1
|Sales Rep
|Quota
|Actual Bookings
|Variance to Quota
|% of Quota
|Forecast
|} 

*Choosing ‘Sales Rep’ for the row header is a good decision, because it has the most subdivisions and arranging them across the columns would exceed the page width. Additionally the reader has all relevant information about one sales rep. in a single row. The sales rep. are also alphabetically ordered, which makes it easy to find a particular one.
*The column header ‘Sales Rep’ should be aligned to the left, as this alignment works best with text. The rest of the column headers should be aligned to the right, as right alignment works best with numbers. This will help to improve scanning the columns.
*The column headers fill shade is a good method to delineate the table header from the rest of the table, although it could be slightly more subtle. Also a ruler could be used instead of a fill shade.
*Each percentage values in the column ‘% of Quota’ should have a percentage sign to the right.
*The table has no summarizing values, only the sum of each column seems reasonable. The column summaries should be delineated from the rest of the table the same way as the column headers.

== Improved Table ==

== Declaration of improvements ==

*White space instead of grids makes it a lot easier for the reader to track across the rows.
*The (for us) most important information of the actual bookings were placed as second column, so the reader doesn’t need to scan the whole row. In addition the column was highlighted with a subtle shade to get the readers attention.
*With the changed order the reader can easily compare the quota with the actual bookings. The columns ‘Variance to Quota’ and ‘% of Quota’ are also next to the column ‘Actual Bookings”, from which they are derived, which makes it easier to analyze them.
*With the changed alignment of the column headers, it’s easer for the reader to scan the columns.
*The percentage sign was added to each value in the’% of Quota’ column

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06|Gruppe 06]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 2

2007-11-23T15:35:59Z

UE-InfoVis0708 0527260:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]

=== Zu beurteilende Tabelle ===

[[Image:few_performance_summary.jpg]]

== Critics ==

*White space should be used instead of girds to delineate rows and columns. Grids break up the data, while white space makes it easier scanning across a single row or column. Optionally subtle horizontal fill shades could be used to delineate the rows from each other.
*In the given table the (at least for us) most important information, the actual bookings, are placed in the last columns.
*The order of the given table is wrong. Quantitative values which should be compared should be placed close to each other and quantitative values which are derived form other values should be placed just to the right of the column from which they are derived.
The order of the columns should be rearranged to:
{| border=1
|Sales Rep
|Quota
|Actual Bookings
|Variance to Quota
|% of Quota
|Forecast
|} 

*Choosing ‘Sales Rep’ for the row header is a good decision, because it has the most subdivisions and arranging them across the columns would exceed the page width. Additionally the reader has all relevant information about one sales rep. in a single row. The sales rep. are also alphabetically ordered, which makes it easy to find a particular one.
*The column header ‘Sales Rep’ should be aligned to the left, as this alignment works best with text. The rest of the column headers should be aligned to the right, as right alignment works best with numbers. This will help to improve scanning the columns.
*The column headers fill shade is a good method to delineate the table header from the rest of the table, although it could be slightly more subtle. Also a ruler could be used instead of a fill shade.
*Each percentage values in the column ‘% of Quota’ should have a percentage sign to the right.
*The table has no summarizing values, only the sum of each column seems reasonable. The column summaries should be delineated from the rest of the table the same way as the column headers.

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2007/08|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06|Gruppe 06]]

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 1 - Level of Detail

2007-11-09T20:56:18Z

UE-InfoVis0708 0527260:

=== Defintion ===
The basic idea of ''Level of Detail'' is to decrease the complexity of an object or model, so that less information has to be saved. 

=== Overview ===
The starting point is a high resolution object. But not all of the information is important from each view or distant! The solution is to simplify these small or distant objects as much as possible. This process will even be called Level of Detail or LOD. For that the object is divided into a grid of rectangles, which will be reduced step by step. 

{{Quotation|For example, a dodecahedron looks like a sphere from a sufficiently large distance and thus can be used to model it so long as it is viewed from that or a greater distance. However, if it must ever be viewed more closely, it will look like a dodecahedron. One solution to this is simply to define it with the most detail that will ever be necessary. However, then it might have far more detail than is needed to represent it at large distances, and in a complex environment with many such objects, there would be too many polygons (or other geometric primitives) for the visible surface algorithms to efficiently handle.|[http://design.osu.edu/carlson/history/PDFs/clark-vis-surface.pdf]}}

=== Parts ===
LOD is not such an easy one man process. In fact of this we will now subdivide the frameworks into four important parts: 
* Discrete LOD
* Continuous LOD
* View Dependent LOD
* Hierarchical LOD

==== The Discrete LOD (DLOD) ====
[[Image:LOD1.jpg|thumb|180px|Pic.1 Maximum to minimum LOD]][[Image:LOD2.jpg|thumb|180px|Pic.2 Closeups & far away objects]]
The Discrete LOD is the traditional version. The concept is to provide some different models to represent an object. Therefore it is possible to use external algorithm (normally non trivial). The idea is to divide these models in several parts, dependent on the needed Level of Detail (picture 1).

Like we have already described in the example above, it is important to think about how much information really is needed. Maximum detail of an object for close-ups and a minimum of detail for very far away objects (picture 2).

An Advantage of DLOD is that it is the simplest programming model and the run-time rendering needs only to combine the several models of the Level of Details. But there is even an unfortunately disadvantage, because sometimes are DLOD not adequate for drastic simplification. Large objects need to be subdivided and the small objects must be combined. This implementation would be very difficult even when not impossible with discrete algorithms.

==== Continous LOD ====
The discrete LOD is more or less the prototype of the Continuous LOD. It is a continuous spectrum of LODs. That means that one picture includes the information, necessary for more levels of details. These are measured by an algorithm. So it is possible to extract the best model for the actual viewpoint in real time.

===== Example: =====
[[Image:LOD3.jpg|left|200px|Example: Continious LOD]]

Level of Detail 1: red points 
Level of Detail 2: red + blue points 
Level of Detail 3: red + blue + green points 
Level of Detail 4: red + blue + green + black points 

==== View Dependent LOD ====
[[Image:LOD4.jpg|right|150px|Example: View Dependent LOD]]
The View Dependent LOD uses the current view parameters to find the best resolution for the current view.

For example you have a robot which travels through the environment. It is only useful to show a high resolution version from things the robot is gazing at. Like the focus of the human eyes.

==== Hierarchical LOD ====

Hierarchical LOD uses the several models of the Discrete LOD and combines them to a group in a hierarchy. So it is possible to extract the important points of a whole environment.
===== Example: =====
[[Image:LOD5.jpg|right|250px|Example: Hierachical LOD]]
In a computer-game it is usual to zoom into the environment. Therefore it is the best solution to have some different resolutions and to morph between them. In this example you see three LODs, the first one at a very low resolution and the third one with the highest resolution mostly outgoing from the original object.

=== References ===

[1] [Clark, 197] James H. Clark. Hierarchical Geometric Models for Visible Surface Algorithms. In Proceedings of the Third Annual Conference on Computer Graphics, Interactive Techniques, and Image Processing, pages 547-554, July 14-16, 1976. Communications October 1976 of Volume 19 the ACM Number 10. 

[Luebke, 2002] David Luebke. Course Real-Time Rendering. University of Virginia. Created at: September 26, 2002. Retrieved at: November 8, 2007. http://www.cs.virginia.edu/~gfx/Courses/2004/RealTime/lecture06.LOD1.ppt. 

[Fischer, 2007] Matthias Fischer. Vorlesung Algorithmen in der Computergrafik SS 2007 Universität Paderborn. Retrieved at: November 8, 2007. http://wwwhni.uni-paderborn.de/fileadmin/hni_alg/lehre/SS2007/AlgoCG/algoCG_LODPM.ppt 

[Reddy, 2007] Martin Reddy. Run-Time Management for LOD. Pixar Animation Studios. Retrieved at: November 8, 2007. http://lodbook.com/course/2003/Reddy_RunTime.ppt 

[en.wikipedia.org] Level of Detail. Retrieved at: November 8, 2007. http://en.wikipedia.org/wiki/Level_of_detail 

[de.wikipedia.org] Level of Detail. Retrieved at: November 8, 2007. http://de.wikipedia.org/wiki/Level_of_Detail 

[DGL Wiki ] Level of Detail. Delphi-OpenGL-Community. Retrieved at: November 8, 2007.
http://wiki.delphigl.com/index.php/LOD 

[Deussen, 2002] Oliver Deussen. Level-of-Detail. Vorlesung Computergraphik II. TU Dresden. Retrieved at: November 8, 2007. http://web.inf.tu-dresden.de/ST2/cg/pdf_daten/Informatik/HS/cg2/ss02/lod_script.pdf 

[Southern and Gain] R. Southern and J. Gain. Creation and Control of Real-time Continuous Level of Detail on Programmable Graphics Hardware. Collaborative Visual Computing Laboratory University of Cape Town, South Africa. Retrieved at: November 8, 2007. http://www.cl.cam.ac.uk/~rs416/papers/southern01_CGF.pdf 

[Birkholz] Hermann Birkholz. Texturing of Continuous LOD Meshes with the Hierarchical Texture Atlas. University of Rostock, Germany. Retrieved at: November 8, 2007.http://wwwicg.informatik.uni-rostock.de/~hb01/doc/Texturing%20of%20Continuous%20LOD%20Meshes%20with%20the%20Hierarchical%20Texture.pdf

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 1 - Thematic Map

2007-11-09T20:34:08Z

UE-InfoVis0708 0527260:

=== Defintion ===
Thematic Maps give information about spatial pattern of one ore more specific data themes for standard geographic areas.

For example:

* Physical phenomena like climate
* Human characteristics
* Population density
* Health issues like cholera

General maps show you where you can find something on this world but a thematic map tells you the story about.

=== History & Development ===
[[Image:halley.gif|150px|thumb|right|First map by Halley]]
[[Image:300px-Snow-cholera-map-1.jpg|150px|thumb|right|Thematic map by Snow]]
The first map was created by Edmond Halley (1686). This map includes the information of the direction of trade winds in the Atlantic Ocean.

The most famous example of an early thematic map was created by John Snow in 1855 and specifies the cholera progression in a specific area.

=== Use of Thematic Maps ===
Important aims of Thematic Maps:

# Thematic Maps provide specific information about particular locations
# They include general information of spatial patterns
# They open the possibility to compare patterns on one or two different maps

Further it is important for the cartographers to be careful to portray the data on the map so that it will be easy for the audience to use and understand. But they have even to notice the spatial accuracy, the aesthetics, human visual perception, the presentation format and the audience. The audience is very important because a political scientist will have other interest than a biologist scientist.

Even the marks and symbols a cartographer uses to represent data are relevant.
Next step for displaying data is to collect data sets. Therefore you have to differ between univariate, bivariate and multivariate mapping.

Univariate mapping means to deal with one subject like cancer rates or the rainfall of a year. In comparison the bivariate mapping deals with two subjects like the population density in relation to the textile manufacturing. Multivariate mapping means only to deal with more than two subjects.

=== Methods ===
[[Image:g156.gif|right|thumb|120px|Choropleth]] [[Image:map100km.png|right|thumb|120px|Proportional]] [[Image:Isopleth_map.jpg|right|thumb|120px|Isarithmic]] [[Image:tower_maps_large.gif|right|thumb|120px|Dot]] [[Image:zoom2_lowres.jpg|right|thumb|120px|Dasymetric]]
The most important methods for designing a thematic map are:

* Choropleth
* Proportional Symbol
* Isarithmic
* Dot
* Dasymetric

==== Choropleth ====

Choropleth maps are the most common thematic maps. A choropleth map displays statistical data, which is colored or patterned accordingly to their distribution. It provides an easy way to demonstrate how data is shared across a geographic area, e.g. population density. Typically they are used after elections to show the spreading of the votes. 
 
==== Proportional Symbol ====

Proportional Symbols maps represent data associated with point locations. Interpretations of statistics represented by these maps are simple to understand. The Proportional Symbols vary in size from place to place on a map in proportion to the quantities they represents.

==== Isarithmic ====

An Isarithmic map uses contour lines to join points where a function has a same particular value and thus show valleys and hills, and the steepness of slopes. Contour lines are curved or straight lines on a map describing the intersection of a real or hypothetical surface with one or more horizontal planes.

==== Dot ====

These maps use dots to show the presence of a feature or occurrence and display a spatial pattern. A dot is not necessarily required to represent a single unit and may indicate any number of entities.

==== Dasymetric ====

''Dasymetric maps'' utilize areal symbols to spatially classify volumetric data. However, although boundaries are displayed on dasymetric maps, these geographic units may span multiple theme values.

=== References ===

[Ross] Zev Ross, ZevRoss Spatial Analysis. Retrieved at: November 8, 2007. http://www.zevross.com/special/history/halley.gif. 

[Answers.com] John Snow. Retrieved at: November 8, 2007. http://www.answers.com/topic/john-snow-physician 

[bbc.co.uk] BBC – Education Scotland – Standard Grade Bitesize. Retrieved at: November 8, 2007. http://www.bbc.co.uk/home/d/ 

[forums.nbn.org.uk] Joint Nature Conservation Committee. Retrieved at: November 8, 2007. http://forums.nbn.org.uk/recreport/index.php?id=5 

[www.volcano.si.edu] Global Volcanism Program. Retrieved at: November 8, 2007. http://www.volcano.si.edu/world/volcano.cfm?vnum=0804-04=&volpage=var 

[Dodge] Martin Dodge, An Atlas of Cyberspaces. Retrieved at: November 8, 2007.
http://www.cybergeography.org/atlas/tower_maps_large.gif 

[www.usgs.gov] Population Density of the San Francisco Bay Area. Retrieved at: November 8, 2007.
http://geography.wr.usgs.gov/science/dasymetric/images/zoom2_lowres.jpg 

[en.wikipdedia.org] Thematic map. Retrieved at: November 8, 2007. http://en.wikipedia.org/wiki/Thematic_map 

[Dr. Michael P. Peterson] THEMATIC MAPS. University of Nebraska at Omaha. Retrieved at: November 8, 2007. http://maps.unomaha.edu/Peterson/carta/Notes/THEMMAP.html 

[www.gigawiz.com] Thematic Maps and Map Projection Utilities. Retrieved at: November 8, 2007. http://www.gigawiz.com/thematic.html 

[Jeffrey J Hemphill] Proportional Symbol Maps with ArcGIS. Retrieved at: November 8, 2007. http://www.geog.ucsb.edu/~jeff/gis/proportional_symbols.html 

[Scott Freundschuh] Course Map Design. UNIVERSITY OF MINNESOTA DULUTH. Retrieved at: November 8, 2007.http://www.d.umn.edu/geog/cartfolder/HTML%20Pages/Map-Types.htm

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 1 - Level of Detail

2007-11-09T19:17:38Z

UE-InfoVis0708 0527260:

=== Defintion ===
The basic idea of ''Level of Detail'' is to decrease the complexity of an object or model, so that less information has to be saved. 

=== Overview ===
The starting point is a high resolution object. But not all of the information is important from each view or distant! The solution is to simplify these small or distant objects as much as possible. This process will even be called Level of Detail or LOD. For that the object is divided into a grid of rectangles, which will be reduced step by step. 

{{Quotation|For example, a dodecahedron looks like a sphere from a sufficiently large distance and thus can be used to model it so long as it is viewed from that or a greater distance. However, if it must ever be viewed more closely, it will look like a dodecahedron. One solution to this is simply to define it with the most detail that will ever be necessary. However, then it might have far more detail than is needed to represent it at large distances, and in a complex environment with many such objects, there would be too many polygons (or other geometric primitives) for the visible surface algorithms to efficiently handle.|[http://design.osu.edu/carlson/history/PDFs/clark-vis-surface.pdf]}}

=== Parts ===
LOD is not such an easy one man process. In fact of this we will now subdivide the frameworks into four important parts: 
* Discrete LOD
* Continuous LOD
* View Dependent LOD
* Hierarchical LOD

==== The Discrete LOD (DLOD) ====
The Discrete LOD is the traditional version. The concept is to provide some different models to represent an object. Therefore it is possible to use external algorithm (normally non trivial). The idea is to divide these models in several parts, dependent on the needed Level of Detail (picture 1).

[[Image:LOD1.jpg|thumb|300px|Pic.1 Maximum to minimum LOD]][[Image:LOD2.jpg|thumb|168px|Pic.2 Closeups & far away objects]]

Like we have already described in the example above, it is important to think about how much information really is needed. Maximum detail of an object for close-ups and a minimum of detail for very far away objects (picture 2).

An Advantage of DLOD is that it is the simplest programming model and the run-time rendering needs only to combine the several models of the Level of Details. But there is even an unfortunately disadvantage, because sometimes are DLOD not adequate for drastic simplification. Large objects need to be subdivided and the small objects must be combined. This implementation would be very difficult even when not impossible with discrete algorithms.

==== Continous LOD ====
The discrete LOD is more or less the prototype of the Continuous LOD. It is a continuous spectrum of LODs. That means that one picture includes the information, necessary for more levels of details. These are measured by an algorithm. So it is possible to extract the best model for the actual viewpoint in real time.

===== Example: =====
[[Image:LOD3.jpg|left|thumb|200px|Example: Continious LOD]]

Level of Detail 1: red points 
Level of Detail 2: red + blue points 
Level of Detail 3: red + blue + green points 
Level of Detail 4: red + blue + green + black points 

==== View Dependent LOD ====
[[Image:LOD4.jpg|right|thumb|150px|Example: View Dependent LOD]]
The View Dependent LOD uses the current view parameters to find the best resolution for the current view.

For example you have a robot which travels through the environment. It is only useful to show a high resolution version from things the robot is gazing at. Like the focus of the human eyes.

==== Hierarchical LOD ====

Hierarchical LOD uses the several models of the Discrete LOD and combines them to a group in a hierarchy. So it is possible to extract the important points of a whole environment.
===== Example: =====
[[Image:LOD5.jpg|right|thumb|250px|Example: Hierachical LOD]]
In a computer-game it is usual to zoom into the environment. Therefore it is the best solution to have some different resolutions and to morph between them. In this example you see three LODs, the first one at a very low resolution and the third one with the highest resolution mostly outgoing from the original object.

=== References ===

[1] [Clark, 197] James H. Clark. Hierarchical Geometric Models for Visible Surface Algorithms. In Proceedings of the Third Annual Conference on Computer Graphics, Interactive Techniques, and Image Processing, pages 547-554, July 14-16, 1976. Communications October 1976 of Volume 19 the ACM Number 10. 

[Luebke, 2002] David Luebke. Course Real-Time Rendering. University of Virginia. Created at: September 26, 2002. Retrieved at: November 8, 2007. http://www.cs.virginia.edu/~gfx/Courses/2004/RealTime/lecture06.LOD1.ppt. 

[Fischer, 2007] Matthias Fischer. Vorlesung Algorithmen in der Computergrafik SS 2007 Universität Paderborn. Retrieved at: November 8, 2007. http://wwwhni.uni-paderborn.de/fileadmin/hni_alg/lehre/SS2007/AlgoCG/algoCG_LODPM.ppt 

[Reddy, 2007] Martin Reddy. Run-Time Management for LOD. Pixar Animation Studios. Retrieved at: November 8, 2007. http://lodbook.com/course/2003/Reddy_RunTime.ppt

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 1 - Level of Detail

2007-11-09T19:11:57Z

UE-InfoVis0708 0527260:

=== Defintion ===
The basic idea of ''Level of Detail'' is to decrease the complexity of an object or model, so that less information has to be saved. 

=== Overview ===
The starting point is a high resolution object. But not all of the information is important from each view or distant! The solution is to simplify these small or distant objects as much as possible. This process will even be called Level of Detail or LOD. For that the object is divided into a grid of rectangles, which will be reduced step by step. 

{{Quotation|For example, a dodecahedron looks like a sphere from a sufficiently large distance and thus can be used to model it so long as it is viewed from that or a greater distance. However, if it must ever be viewed more closely, it will look like a dodecahedron. One solution to this is simply to define it with the most detail that will ever be necessary. However, then it might have far more detail than is needed to represent it at large distances, and in a complex environment with many such objects, there would be too many polygons (or other geometric primitives) for the visible surface algorithms to efficiently handle.|[http://design.osu.edu/carlson/history/PDFs/clark-vis-surface.pdf]}}

=== Parts ===
LOD is not such an easy one man process. In fact of this we will now subdivide the frameworks into four important parts: 
* Discrete LOD
* Continuous LOD
* View Dependent LOD
* Hierarchical LOD

==== The Discrete LOD (DLOD) ====
The Discrete LOD is the traditional version. The concept is to provide some different models to represent an object. Therefore it is possible to use external algorithm (normally non trivial). The idea is to divide these models in several parts, dependent on the needed Level of Detail (picture 1).

[[Image:LOD1.jpg|thumb|300px|Pic.1 Maximum to minimum LOD]][[Image:LOD2.jpg|thumb|168px|Pic.2 Closeups & far away objects]]

Like we have already described in the example above, it is important to think about how much information really is needed. Maximum detail of an object for close-ups and a minimum of detail for very far away objects (picture 2).

An Advantage of DLOD is that it is the simplest programming model and the run-time rendering needs only to combine the several models of the Level of Details. But there is even an unfortunately disadvantage, because sometimes are DLOD not adequate for drastic simplification. Large objects need to be subdivided and the small objects must be combined. This implementation would be very difficult even when not impossible with discrete algorithms.

==== Continous LOD ====
The discrete LOD is more or less the prototype of the Continuous LOD. It is a continuous spectrum of LODs. That means that one picture includes the information, necessary for more levels of details. These are measured by an algorithm. So it is possible to extract the best model for the actual viewpoint in real time.

===== Example: =====
[[Image:LOD3.jpg|left|thumb|200px|Example: Continious LOD]]

Level of Detail 1: red points 
Level of Detail 2: red + blue points 
Level of Detail 3: red + blue + green points 
Level of Detail 4: red + blue + green + black points 

==== View Dependent LOD ====
[[Image:LOD4.jpg|right|thumb|150px|Example: View Dependent LOD]]
The View Dependent LOD uses the current view parameters to find the best resolution for the current view.

For example you have a robot which travels through the environment. It is only useful to show a high resolution version from things the robot is gazing at. Like the focus of the human eyes.

==== Hierarchical LOD ====

Hierarchical LOD uses the several models of the Discrete LOD and combines them to a group in a hierarchy. So it is possible to extract the important points of a whole environment.
===== Example: =====
[[Image:LOD5.jpg|right|thumb|250px|Example: Hierachical LOD]]
In a computer-game it is usual to zoom into the environment. Therefore it is the best solution to have some different resolutions and to morph between them. In this example you see three LODs, the first one at a very low resolution and the third one with the highest resolution mostly outgoing from the original object.

=== References ===

[1] [Clark, 197] James H. Clark. Hierarchical Geometric Models for Visible Surface Algorithms. In Proceedings of the Third Annual Conference on Computer Graphics, Interactive Techniques, and Image Processing, pages 547-554, July 14-16, 1976. Communications October 1976 of Volume 19 the ACM Number 10. 

[Luebke, 2002] David Luebke. Course Real-Time Rendering University of Virginia. Created at: September 26, 2002. Retrieved at: November 8, 2007. http://www.cs.virginia.edu/~gfx/Courses/2004/RealTime/lecture06.LOD1.ppt. 

[Fischer, 2007] Matthias Fischer. Vorlesung Algorithmen in der Computergrafik SS 2007 Universität Paderborn. Retrieved at: November 8, 2007. http://wwwhni.uni-paderborn.de/fileadmin/hni_alg/lehre/SS2007/AlgoCG/algoCG_LODPM.ppt 

[Reddy, 2007] Martin Reddy. Run-Time Management for LOD. Pixar Animation Studios. Retrieved at: November 8, 2007. http://lodbook.com/course/2003/Reddy_RunTime.ppt

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 1 - Level of Detail

2007-11-09T18:38:38Z

UE-InfoVis0708 0527260:

=== Defintion ===
The basic idea of ''Level of Detail'' is to decrease the complexity of an object or model, so that less information has to be saved. 

=== Overview ===
The starting point is a high resolution object. But not all of the information is important from each view or distant! The solution is to simplify these small or distant objects as much as possible. This process will even be called Level of Detail or LOD. For that the object is divided into a grid of rectangles, which will be reduced step by step. 

{{Quotation|For example, a dodecahedron looks like a sphere from a sufficiently large distance and thus can be used to model it so long as it is viewed from that or a greater distance. However, if it must ever be viewed more closely, it will look like a dodecahedron. One solution to this is simply to define it with the most detail that will ever be necessary. However, then it might have far more detail than is needed to represent it at large distances, and in a complex environment with many such objects, there would be too many polygons (or other geometric primitives) for the visible surface algorithms to efficiently handle.|[http://design.osu.edu/carlson/history/PDFs/clark-vis-surface.pdf]}}

=== Parts ===
LOD is not such an easy one man process. In fact of this we will now subdivide the frameworks into four important parts: 
* Discrete LOD
* Continuous LOD
* View Dependent LOD
* Hierarchical LOD

==== The Discrete LOD (DLOD) ====
The Discrete LOD is the traditional version. The concept is to provide some different models to represent an object. Therefore it is possible to use external algorithm (normally non trivial). The idea is to divide these models in several parts, dependent on the needed Level of Detail (picture 1).

[[Image:LOD1.jpg|thumb|300px|Pic.1 Maximum to minimum LOD]][[Image:LOD2.jpg|thumb|168px|Pic.2 Closeups & far away objects]]

Like we have already described in the example above, it is important to think about how much information really is needed. Maximum detail of an object for close-ups and a minimum of detail for very far away objects (picture 2).

An Advantage of DLOD is that it is the simplest programming model and the run-time rendering needs only to combine the several models of the Level of Details. But there is even an unfortunately disadvantage, because sometimes are DLOD not adequate for drastic simplification. Large objects need to be subdivided and the small objects must be combined. This implementation would be very difficult even when not impossible with discrete algorithms.

==== Continous LOD ====
The discrete LOD is more or less the prototype of the Continuous LOD. It is a continuous spectrum of LODs. That means that one picture includes the information, necessary for more levels of details. These are measured by an algorithm. So it is possible to extract the best model for the actual viewpoint in real time.

===== Example: =====
[[Image:LOD3.jpg|left|thumb|200px|Example: Continious LOD]]

Level of Detail 1: red points 
Level of Detail 2: red + blue points 
Level of Detail 3: red + blue + green points 
Level of Detail 4: red + blue + green + black points 

==== View Dependent LOD ====
[[Image:LOD4.jpg|right|thumb|150px|Example: View Dependent LOD]]
The View Dependent LOD uses the current view parameters to find the best resolution for the current view.

For example you have a robot which travels through the environment. It is only useful to show a high resolution version from things the robot is gazing at. Like the focus of the human eyes.

==== Hierarchical LOD ====

Hierarchical LOD uses the several models of the Discrete LOD and combines them to a group in a hierarchy. So it is possible to extract the important points of a whole environment.
===== Example: =====
[[Image:LOD5.jpg|right|thumb|250px|Example: Hierachical LOD]]
In a computer-game it is usual to zoom into the environment. Therefore it is the best solution to have some different resolutions and to morph between them. In this example you see three LODs, the first one at a very low resolution and the third one with the highest resolution mostly outgoing from the original object.

=== References ===

[1] [Clark, 197] James H. Clark. Hierarchical Geometric Models for Visible Surface Algorithms. In Proceedings of the Third Annual Conference on Computer Graphics, Interactive Techniques, and Image Processing, pages 547-554, July 14-16, 1976. Communications October 1976 of Volume 19 the ACM Number 10. 

[Luebke, 2002] David Luebke, Course Real-Time Rendering. University of Virginia. Created at: September 26, 2002. Retrieved at: November 8, 2007. http://www.cs.virginia.edu/~gfx/Courses/2004/RealTime/lecture06.LOD1.ppt.

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 1 - Level of Detail

2007-11-09T18:24:10Z

UE-InfoVis0708 0527260:

=== Defintion ===
The basic idea of ''Level of Detail'' is to decrease the complexity of an object or model, so that less information has to be saved. 

=== Overview ===
The starting point is a high resolution object. But not all of the information is important from each view or distant! The solution is to simplify these small or distant objects as much as possible. This process will even be called Level of Detail or LOD. For that the object is divided into a grid of rectangles, which will be reduced step by step. 

{{Quotation|For example, a dodecahedron looks like a sphere from a sufficiently large distance and thus can be used to model it so long as it is viewed from that or a greater distance. However, if it must ever be viewed more closely, it will look like a dodecahedron. One solution to this is simply to define it with the most detail that will ever be necessary. However, then it might have far more detail than is needed to represent it at large distances, and in a complex environment with many such objects, there would be too many polygons (or other geometric primitives) for the visible surface algorithms to efficiently handle.|[http://design.osu.edu/carlson/history/PDFs/clark-vis-surface.pdf]}}

=== Parts ===
LOD is not such an easy one man process. In fact of this we will now subdivide the frameworks into four important parts: 
* Discrete LOD
* Continuous LOD
* View Dependent LOD
* Hierarchical LOD

==== The Discrete LOD (DLOD) ====
The Discrete LOD is the traditional version. The concept is to provide some different models to represent an object. Therefore it is possible to use external algorithm (normally non trivial). The idea is to divide these models in several parts, dependent on the needed Level of Detail (picture 1).

[[Image:LOD1.jpg|300px|Maximum to minimum LOD]][[Image:LOD2.jpg|168px|Closeups & far away objects]]

Like we have already described in the example above, it is important to think about how much information really is needed. Maximum detail of an object for close-ups and a minimum of detail for very far away objects (picture 2).

An Advantage of DLOD is that it is the simplest programming model and the run-time rendering needs only to combine the several models of the Level of Details. But there is even an unfortunately disadvantage, because sometimes are DLOD not adequate for drastic simplification. Large objects need to be subdivided and the small objects must be combined. This implementation would be very difficult even when not impossible with discrete algorithms.

==== Continous LOD ====
The discrete LOD is more or less the prototype of the Continuous LOD. It is a continuous spectrum of LODs. That means that one picture includes the information, necessary for more levels of details. These are measured by an algorithm. So it is possible to extract the best model for the actual viewpoint in real time.

===== Example: =====
[[Image:LOD3.jpg|left|200px|Example: Continious LOD]]

Level of Detail 1: red points 
Level of Detail 2: red + blue points 
Level of Detail 3: red + blue + green points 
Level of Detail 4: red + blue + green + black points 

==== View Dependent LOD ====
[[Image:LOD4.jpg|right|thumb|150px|Example: View Dependent LOD]]
The View Dependent LOD uses the current view parameters to find the best resolution for the current view.

For example you have a robot which travels through the environment. It is only useful to show a high resolution version from things the robot is gazing at. Like the focus of the human eyes.

==== Hierarchical LOD ====

Hierarchical LOD uses the several models of the Discrete LOD and combines them to a group in a hierarchy. So it is possible to extract the important points of a whole environment.
===== Example: =====
[[Image:LOD5.jpg|right|thumb|250px|Example: Hierachical LOD]]
In a computer-game it is usual to zoom into the environment. Therefore it is the best solution to have some different resolutions and to morph between them. In this example you see three LODs, the first one at a very low resolution and the third one with the highest resolution mostly outgoing from the original object.

=== References ===

[1] [Clark, 197] James H. Clark. Hierarchical Geometric Models for Visible Surface Algorithms. In Proceedings of the Third Annual Conference on Computer Graphics, Interactive Techniques, and Image Processing, pages 547-554, July 14-16, 1976. Communications October 1976 of Volume 19 the ACM Number 10.

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 1 - Thematic Map

2007-11-09T17:47:34Z

UE-InfoVis0708 0527260:

File:Isarithmic map.png

2007-11-09T17:43:57Z

UE-InfoVis0708 0527260: Isarithmic map, welche den Luftdruck zeigt

== Beschreibung ==
Isarithmic map, welche den Luftdruck zeigt
== Copyright status ==

== Source ==
Wikipedia

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06 - Aufgabe 1 - Thematic Map

2007-11-09T16:49:12Z

UE-InfoVis0708 0527260:

User:UE-InfoVis0708 0527260

2007-10-29T10:38:20Z

UE-InfoVis0708 0527260:

[[Image:me02.jpg|right|thumb]]
{|
|''Name:''||'''Alexander Kraicsich'''
|-
|''Matrikelnummer:''||'''0527260'''
|-
|''Studienkennzahl:''||'''532- Medieninformatik'''
|-
|''E-mail:''||'''e0527260 at student.tuwien.ac.at'''
|} 
Zurück zu [[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06|Gruppe 06 Übersicht]]

File:Me02.jpg

2007-10-29T10:36:07Z

UE-InfoVis0708 0527260: New page: == Beschreibung == == Copyright status == Alexander Kraicsich == Source ==

== Beschreibung ==

== Copyright status ==
Alexander Kraicsich
== Source ==

File:Me01.jpg

2007-10-29T10:28:43Z

UE-InfoVis0708 0527260: New page: == Beschreibung == == Copyright status == Alexander Kraicsich == Source ==

== Beschreibung ==

== Copyright status ==
Alexander Kraicsich
== Source ==

User:UE-InfoVis0708 0525566

2007-10-26T10:18:01Z

UE-InfoVis0708 0527260:

[[Image:Studi2.jpg|right|thumb|pic]] 
{|
|''Nachname:''||'''Sagmeister'''
|-
|''Vorname:''||'''Clemens'''
|-
|''Matrikelnummer:''||'''0525566'''
|-
|''Studienkennzahl:''||'''532 - Medieninformatik'''
|-
|''E-mail Adresse:''||'''e0525566 at student.tuwien.ac.at'''
|} 
Zurück zu [[Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 06|Gruppe 06 Übersicht]]