InfoVis:Wiki - User contributions [en]

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 3

2011-01-17T21:05:30Z

UE-InfoVis1011 0402530:

==Introduction==
One of the Millenium Development Goals (MDG 7) is to halve, by 2015, the proportion of people without sustainable access to safe drinking-water and basic sanitation. Therefore the World Health Organization (WHO) and the United Nations Children's Fund (UNICEF) collected several data and published the intermediate results in 2010. Starting from this report and involving the collected data an interactive information visualization was designed and implemented using the JavaScript Framework Protovis (Referenz).

==Analysis of the data==
The data shows the temporal development of the access to safe drinking-water and basic sanitation. The data collection started in the year 1990 and was from then on upraised every 5 years. One exception is the last dataset which was collected in 1998, so the time difference is here only 3 years. The data was collected for every country separately with the possibility to build up dependencies by grouping the countries.
The basic structure of the data is as follows. Several nominal scales are linked to the two main categories water and sanitation. This nominal scales are improved, piped, other improved and unimproved for water and improved, shared, open defecation, other improvement and unimproved for sanitation. Moreover each of the above mentioned nominal scales can be split to two additional nominal scales, namely rural and urban. The values of the nominal scales contain absolute values as well as relative ones.

==Target Group analysis==
The visualization is focused on southeast asia. Thus it may be of interest for medical stuff in this region because it gives an overview of the development in improved water and sanitation progress. Combined with additional (medical) data conclusions about diseases caused by bad water or sanitation may be drawn. Moreover this visualization may be also of interest for the analysis of infrastructure development in this region.

==Used Visualization Techniques==

===Scatterplot===
Purpose : The Scatterplot displays the countries of the world according to the ratio of the supply with improved water and improved sanitation. The properties are discribed as follows:
*horizontal axis : proportion of population served with improved Sanitation
*vertical axis : proportion of polulation server with improved Water
*Dots : Countries of the World encoded by color and size
**Size == size of the Dots is oriented on the population of the Country(/1000) between a min and a max size for keeping up readability
**Color == Yellow for Countries in the Southeastern region & Blue for all other Countries of the World

===Indexchart===
*horizontal axis : Year (1990 - 2008)
*vertical axis : Percentage of shown data measured on the proportion of urban or rural population served with improved water or sanitation
*Lines : Trend of Developement between the data points of each year provivided by the WHO data; The used Colors represent the kind of data displayed in the following way
**Blue == improved Water supply
**Brown == improved Sanitation supply
*"Dots"(Symbols) : exact data of the year (related to the vertical axis);
The used Symbols represent the kind of data displayed in the following way
*"Cross" == Rural
*"Square" == Urban
*"Circle" == Total

===Map===
The Areas represent the proportion of population supplied with improved water encoded with color (changing data with chosen Year)
*Pink <= 50% of the total population supplied with improved water
*Lightgreen 50%-75% of the total population supplied with improved water
*Green 76-90% of the total population supplied with improved water
*Darkgreen 91-100% of the total population supplied with improved water
===Available forms of Interaction===

The forms of interaction available differ throughout the 3 plots

*Year-Slider : The year-slider allows the user to choose a certain year of interest modifying the displayed data in the scatterplot and the Map.
It also enables the user to execute a "play" function which iterates through the years, generating some sort of "animation" making
it possible to follow for the developement of the southeastern Asian in relation to the other countries of the world and so on.
*Scatterplot : "Mouseover" on displayed Dot shows the Countryname and the Population of that country
*Indexchart : "Mouseover" on the displayed "dots" shows the specific percentage value
*Map : "Mouseover" displays the Name of the Country
"Click" on a Country highlights the according Country"dot" in the scatterplot which stays highlighted and hence can be followed throughout the available years(also in slider "playmode")
also the clicked country's name gets displayed.

==External Links==
*Progress on sanitation and drinking-water - http://www.wssinfo.org/fileadmin/user_upload/resources/1278061137-JMP_report_2010_en.pdf
*Protovis - http://vis.stanford.edu/protovis/
==References==

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 3

2011-01-17T21:04:41Z

UE-InfoVis1011 0402530:

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 3

2011-01-17T20:45:21Z

UE-InfoVis1011 0402530:

==Introduction==
One of the Millenium Development Goals (MDG 7) is to halve, by 2015, the proportion of people without sustainable access to safe drinking-water and basic sanitation. Therefore the World Health Organization (WHO) and the United Nations Children's Fund (UNICEF) collected several data and published the intermediate results in 2010. Starting from this report and involving the collected data an interactive information visualization was designed and implemented using the JavaScript Framework Protovis (Referenz).

==Analysis of the data==
The data shows the temporal development of the access to safe drinking-water and basic sanitation. The data collection started in the year 1990 and was from then on upraised every 5 years. One exception is the last dataset which was collected in 1998, so the time difference is here only 3 years. The data was collected for every country separately with the possibility to build up dependencies by grouping the countries.
The basic structure of the data is as follows. Several nominal scales are linked to the two main categories water and sanitation. This nominal scales are improved, piped, other improved and unimproved for water and improved, shared, open defecation, other improvement and unimproved for sanitation. Moreover each of the above mentioned nominal scales can be split to two additional nominal scales, namely rural and urban. The values of the nominal scales contain absolute values as well as relative ones.

==Target Group analysis==
The visualization is focused on southeast asia. Thus it may be of interest for medical stuff in this region because it gives an overview of the development in improved water and sanitation progress. Combined with additional (medical) data conclusions about diseases caused by bad water or sanitation may be drawn. Moreover this visualization may be also of interest for the analysis of infrastructure development in this region.

==Used Visualization Techniques==

===Scatterplot===
*horizontal axis : proportion of population served with improved Sanitation
*vertical axis : proportion of polulation server with improved Water
*Dots : Countries of the World encoded by color and size
**Size == size of the Dots is oriented on the population of the Country(/1000) between a min and a max size for keeping up readability
**Color == Yellow for Countries in the Southeastern region & Blue for all other Countries of the World

===Indexchart===
*horizontal axis : Year (1990 - 2008)
*vertical axis : Percentage of shown data measured on the proportion of urban or rural population served with improved water or sanitation
*Lines : Trend of Developement between the data points of each year provivided by the WHO data; The used Colors represent the kind of data displayed in the following way
**Blue == improved Water supply
**Brown == improved Sanitation supply
*"Dots"(Symbols) : exact data of the year (related to the vertical axis);
The used Symbols represent the kind of data displayed in the following way
*"Cross" == Rural
*"Square" == Urban
*"Circle" == Total

===Map===
The Areas represent the proportion of population supplied with improved water encoded with color (changing data with chosen Year)
*Red <= 50% of the total population supplied with improved water
*Yellow 50% - 90% of the total population supplied with improved water
*Green > 90 of the total population supplied with improved water

===Available forms of Interaction===

The forms of interaction available differ throughout the 3 plots

*Year-Slider : The year-slider allows the user to choose a certain year of interest modifying the displayed data in the scatterplot and the Map.
It also enables the user to execute a "play" function which iterates through the years, generating some sort of "animation" making
it possible to follow for the developement of the southeastern Asian in relation to the other countries of the world and so on.
*Scatterplot : "Mouseover" on displayed Dot shows the Countryname and the Population of that country
*Indexchart : "Mouseover" on the displayed "dots" shows the specific percentage value
*Map : "Mouseover" displays the Name of the Country
"Click" on a Country highlights the according Country"dot" in the scatterplot which stays highlighted and hence can be followed throughout the available years(also in slider "playmode")
also the clicked country's name gets displayed.

==References==

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 3

2011-01-17T20:35:07Z

UE-InfoVis1011 0402530:

==Introduction==
One of the Millenium Development Goals (MDG 7) is to halve, by 2015, the proportion of people without sustainable access to safe drinking-water and basic sanitation. Therefore the World Health Organization (WHO) and the United Nations Children's Fund (UNICEF) collected several data and published the intermediate results in 2010. Starting from this report and involving the collected data an interactive information visualization was designed and implemented using the JavaScript Framework Protovis (Referenz).

==Analysis of the data==
The data shows the temporal development of the access to safe drinking-water and basic sanitation. The data collection started in the year 1990 and was from then on upraised every 5 years. One exception is the last dataset which was collected in 1998, so the time difference is here only 3 years. The data was collected for every country separately with the possibility to build up dependencies by grouping the countries.
The basic structure of the data is as follows. Several nominal scales are linked to the two main categories water and sanitation. This nominal scales are improved, piped, other improved and unimproved for water and improved, shared, open defecation, other improvement and unimproved for sanitation. Moreover each of the above mentioned nominal scales can be split to two additional nominal scales, namely rural and urban. The values of the nominal scales contain absolute values as well as relative ones.

==Target Group analysis==
The visualization is focused on southeast asia. Thus it may be of interest for medical stuff in this region because it gives an overview of the development in improved water and sanitation progress. Combined with additional (medical) data conclusions about diseases caused by bad water or sanitation may be drawn. Moreover this visualization may be also of interest for the analysis of infrastructure development in this region.

==Used Visualization Techniques==

===Scatterplot===
*horizontal axis : proportion of population served with improved Water
*vertical axis : proportion of polulation server with improved Sanitation
*Dots : Countries of the World encoded by color and size
**Size == size of the Dots is oriented on the population of the Country(/1000) between a min and a max size for keeping up readability
**Color == Yellow for Countries in the Southeastern region & Blue for all other Countries of the World

===Indexchart===
*horizontal axis : Year (1990 - 2008)
*vertical axis : Percentage of shown data measured on the proportion of urban or rural population served with improved water or sanitation
*Lines : Trend of Developement between the data points of each year provivided by the WHO data; The used Colors represent the kind of data displayed in the following way
**Blue == improved Water supply
**Brown == improved Sanitation supply
*"Dots"(Symbols) : exact data of the year (related to the vertical axis);
The used Symbols represent the kind of data displayed in the following way
*"Cross" == Rural
*"Square" == Urban
*"Circle" == Total

===Map===
The Areas represent the proportion of population supplied with improved water encoded with color (changing data with chosen Year)
*Red <= 50% of the total population supplied with improved water
*Yellow 50% - 90% of the total population supplied with improved water
*Green > 90 of the total population supplied with improved water

===Available forms of Interaction===

The forms of interaction available differ throughout the 3 plots

*Year-Slider : The year-slider allows the user to choose a certain year of interest modifying the displayed data in the scatterplot and the Map.
It also enables the user to execute a "play" function which iterates through the years, generating some sort of "animation" making
it possible to follow for the developement of the southeastern Asian in relation to the other countries of the world and so on.
*Scatterplot : "Mouseover" on displayed Dot shows the Countryname and the Population of that country
*Indexchart : "Mouseover" on the displayed "dots" shows the specific percentage value
*Map : "Mouseover" displays the Name of the Country
"Click" on a Country highlights the according Country"dot" in the scatterplot which stays highlighted and hence can be followed throughout the available years(also in slider "playmode")
also the clicked country's name gets displayed.

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 3

2011-01-17T20:34:05Z

UE-InfoVis1011 0402530:

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T21:15:43Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for the UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding to digital legends, the designers mostly rely on their subjective judgment and personal experience rather than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols.

'''Layout''' : As a legend uses space, it is important to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols must be consistent with the ones used in the map and to each other. They should also relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend should depend on the task at hand. On the one hand it can be useful to support the user with a legend even before the map is visible (e.g. bivariate legends, unfamiliar symbolism) but on the other hand a legend is less important when it is used only sporadically.

'''Dynamism''': Dynamism supports the interactive change of the above described categories.

'''Design and Process''': During the design process the legend should be handled like a map or a data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or can be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together and can be divided into three subthemes. The ''"no legend"'' approach hides symbols when precise identification is not needed or self-explanatory(also under the aspect of showing symbols only on demand in a dynamic environment). In the ''"map-section"'' the legend becomes a natural legend, taking into account a two-dimensional spatial mapping (Fig. 1). And finally the ''"map becomes legend"'' theme, which is designed as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content. Furthermore it provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes raises the question how to relate and navigate between those alternative symbol sets. To solve this problem alternative styles are displayed simultaneously and related using layout.

'''"The Relevant Legend"''' : Only the relevant information gets covered by the legend. As relevance changes over time and depends also on the data and the users, several variants can be derived from this concept. For example the legend may be changed according to community usage, task, knowledge, location or symbolism.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes ==

In order to demonstrate the possibilities along with the prepared guidelines four prototypes were developed. The objective of this task was to communicate the ideas behind the guidelines and to get feedback for further developments. After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes. The focus was directed at a specific data set (Strategi), and the general enhancement of the features of the prototypes was requested. Briefly, the following six prototpyes were developed:

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [Wood and Dykes, 2008] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Conclusion ==
The impact of this study was in general very positive. Many of the identified problems with on-screen map legends could be addressed. The impact evaluation made also clear that visual legends are much more advantageous than static legends. Moreover EDINA, the initiator of the study, regarded the work as “inspirational” and has secured funding for an additional project.

== References ==
[Dykes et al., 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

[Wood and Dykes, 2008] J. Wood and J. Dykes. Spatially ordered treemaps. ''IEEE Trans. Vis. Comp. Graphics'', 14(6):1348–1355, 2008

== External Links ==

*EDINA - http://edina.ac.uk/digimap/
*Map symbols - http://www.ordnancesurvey.co.uk/oswebsite/education/pdf/50KLegend-Eng.pdf
*Strategi - http://data.gov.uk/dataset/os-strategi

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T21:01:00Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for the UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding to digital legends, the designers mostly rely on their subjective judgment and personal experience rather than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols.

'''Layout''' : As a legend uses space, it is important to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols must be consistent with the ones used in the map and to each other. They should also relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend should depend on the task at hand. On the one hand it can be useful to support the user with a legend even before the map is visible (e.g. bivariate legends, unfamiliar symbolism) but on the other hand a legend is less important when it is used only sporadically.

'''Dynamism''': Dynamism supports the interactive change of the above described categories.

'''Design and Process''': During the design process the legend should be handled like a map or a data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or can be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together and can be divided into three subthemes. The ''"no legend"'' approach hides symbols when precise identification is not needed or self-explanatory(also under the aspect of showing symbols only on demand in a dynamic environment). In the ''"map-section"'' focus the legend becomes a natural legend, taking into account a two-dimensional spatial mapping (Fig. 1). And finally the ''"map becomes legend"'' theme, which is designed as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content. Furthermore it provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes raises the question how to relate and navigate between those alternative symbol sets. To solve this problem alternative styles are displayed simultaneously and related using layout.

'''"The Relevant Legend"''' : Only the relevant information gets covered by the legend. As relevance changes over time and depends also on the data and the users, several variants can be derived from this concept. For example the legend may be changed according to community usage, task, knowledge, location or symbolism.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes ==

In order to demonstrate the possibilities along with the prepared guidelines four prototypes were developed. The objective of this task was to communicate the ideas behind the guidelines and to get feedback for further developments. After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes. The focus was directed at a specific data set (Strategi), and the general enhancement of the features of the prototypes was requested. Briefly, the following six prototpyes were developed:

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [Wood and Dykes, 2008] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Conclusion ==
The impact of this study was in general very positive. Many of the identified problems with on-screen map legends could be addressed. The impact evaluation made also clear that visual legends are much more advantageous than static legends. Moreover EDINA, the initiator of the study, regarded the work as “inspirational” and has secured funding for an additional project.

== References ==
[Dykes et al., 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

[Wood and Dykes, 2008] J. Wood and J. Dykes. Spatially ordered treemaps. ''IEEE Trans. Vis. Comp. Graphics'', 14(6):1348–1355, 2008

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T20:50:42Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding to digital legends, the designers mostly rely on their subjective judgment and personal experience rather than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols.

'''Layout''' : As a legend uses space, it is important to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols must be consistent with the ones used in the map and to each other. They should also relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend should depend on the task at hand. On the one hand it can be useful to support the user with a legend even before the map is visible (e.g. bivariate legends, unfamiliar symbolism) but on the other hand a legend is less important when it is used only sporadically.

'''Dynamism''': Dynamism supports the interactive change of the above described categories.

'''Design and Process''': During the design process the legend should be handled like a map or a data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or can be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together and can be divided into three subthemes. The ''"no legend"'' approach hides symbols when precise identification is not needed or self-explanatory(also under the aspect of showing symbols only on demand in a dynamic environment). In the ''"map-section"'' focus the legend becomes a natural legend, taking into account a two-dimensional spatial mapping (Fig. 1). And finally the ''"map becomes legend"'' theme, which is designed as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content. Furthermore it provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes raises the question how to relate and navigate between those alternative symbol sets. To solve this problem alternative styles are displayed simultaneously and related using layout.

'''"The Relevant Legend"''' : Only the relevant information gets covered by the legend. As relevance changes over time and depends also on the data and the users, several variants can be derived from this concept. For example the legend may be changed according to community usage, task, knowledge, location or symbolism.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes ==

In order to demonstrate the possibilities along with the prepared guidelines four prototypes were developed. The objective of this task was to communicate the ideas behind the guidelines and to get feedback for further developments. After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes. The focus was directed at a specific data set (Strategi), and the general enhancement of the features of the prototypes was requested. Briefly, the following six prototpyes were developed:

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [Wood and Dykes, 2008] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Conclusion ==
The impact of this study was in general very positive. Many of the identified problems with on-screen map legends could be addressed. The impact evaluation made also clear that visual legends are much more advantageous than static legends. Moreover EDINA, the initiator of the study, regarded the work as “inspirational” and has secured funding for an additional project.

== References ==
[Dykes et al., 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

[Wood and Dykes, 2008] J. Wood and J. Dykes. Spatially ordered treemaps. ''IEEE Trans. Vis. Comp. Graphics'', 14(6):1348–1355, 2008

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T20:40:46Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding to digital legends, the designers mostly rely on their subjective judgment and personal experience rather than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols.

'''Layout''' : As a legend uses space, it is important to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols must be consistent with the ones used in the map and to each other. They should also relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend should depend on the task at hand. On the one hand it can be useful to support the user with a legend even before the map is visible (e.g. bivariate legends, unfamiliar symbolism) but on the other hand a legend is less important when it is used only sporadically.

'''Dynamism''': Dynamism supports the interactive change of the above described categories.

'''Design and Process''': During the design process the legend should be handled like a map or a data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or can be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together and can be divided into three subthemes. The ''"no legend"'' approach hides symbols when precise identification is not needed or self-explanatory(also under the aspect of showing symbols only on demand in a dynamic environment). In the ''"map-section"'' focus the legend becomes a natural legend, taking into account a two-dimensional spatial mapping (Fig. 1). And finally the ''"map becomes legend"'' theme, which is designed as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content. Furthermore it provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes raises the question how to relate and navigate between those alternative symbol sets. To solve this problem alternative styles are displayed simultaneously and related using layout.

'''"The Relevant Legend"''' : Only the relevant information gets covered by the legend. As relevance changes over time and depends also on the data and the users, several variants can be derived from this concept. For example the legend may be changed according to community usage, task, knowledge, location or symbolism.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes ==

In order to demonstrate the possibilities along with the prepared guidelines four prototypes were developed. The objective of this task was to communicate the ideas behind the guidelines and to get feedback for further developments. After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes. The focus was directed at a specific data set (Strategi), and the general enhancement of the features of the prototypes was requested. Briefly, the following six prototpyes were developed:

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [Wood and Dykes, 2008] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Conclusion ==
The impact of this study was in general very positive. Many of the identified problems with on-screen map legends could be addressed. The impact evaluation made also clear that visual legends are much more advantageous than static legends. Moreover EDINA, the initiator of the study, regarded the work as “inspirational” and has secured funding for an addition project.

== References ==
[Dykes et al., 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

[Wood and Dykes, 2008] J. Wood and J. Dykes. Spatially ordered treemaps. ''IEEE Trans. Vis. Comp. Graphics'', 14(6):1348–1355, 2008

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T20:04:51Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding to digital legends, the designers mostly rely on their subjective judgment and personal experience rather than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols.

'''Layout''' : As a legend uses space, it is important to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols must be consistent with the ones used in the map and to each other. They should also relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend should depend on the task at hand. On the one hand it can be useful to support the user with a legend even before the map is visible (e.g. bivariate legends, unfamiliar symbolism) but on the other hand a legend is less important when it is used only sporadically.

'''Dynamism''': Dynamism supports the interactive change of the above described categories.

'''Design and Process''': During the design process the legend should be handled like a map or a data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or can be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together and can be divided into three subthemes. The ''"no legend"'' approach hides symbols when precise identification is not needed or self-explanatory(also under the aspect of showing symbols only on demand in a dynamic environment). In the ''"map-section"'' focus the legend becomes a natural legend, taking into account a two-dimensional spatial mapping (Fig. 1). And finally the ''"map becomes legend"'' theme, which is designed as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content. Furthermore it provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes raises the question how to relate and navigate between those alternative symbol sets. To solve this problem alternative styles are displayed simultaneously and related using layout.

'''"The Relevant Legend"''' : Only the relevant information gets covered by the legend. As relevance changes over time and depends also on the data and the users, several variants can be derived from this concept. For example the legend may be changed according to community usage, task, knowledge, location or symbolism.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes ==

In order to demonstrate the possibilities along with the prepared guidelines four prototypes were developed. The objective of this task was to communicate the ideas behind the guidelines and to get feedback for further developments.

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [Wood and Dykes, 2008] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes including:

*a focus on the Strategi data set [Snyder, 1987];
*applying 2D layouts to the rich Strategi feature class hierarchy;
*enhancing prototypes with styles, layout options and more features for bi-directional interaction.

The team went to work and produced another 2, more constrained and functional prototypes.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

Additionally three different legend orderings were introduced.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Conclusion ==
The impact of this study was in general very positive. Many of the identified problems with on-screen map legends could be addressed. The impact evaluation made also clear that visual legends are much more advantageous than static legends. Moreover EDINA, the initiator of the study, regarded the work as “inspirational” and has secured funding for an addition project.

== References ==
[Dykes et al., 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

[Wood and Dykes, 2008] J. Wood and J. Dykes. Spatially ordered treemaps. ''IEEE Trans. Vis. Comp. Graphics'', 14(6):1348–1355, 2008

[Snyder, 1987] J. P. Snyder. Map Projections: A Working Manual Edition. 'USGS Professional Paper'. US Geological Survey, 1987

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T19:46:51Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding to digital legends, the designers mostly rely on their subjective judgment and personal experience rather than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols.

'''Layout''' : As a legend uses space, it is important to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols must be consistent with the ones used in the map and to each other. They should also relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend should depend on the task at hand. On the one hand it can be useful to support the user with a legend even before the map is visible (e.g. bivariate legends, unfamiliar symbolism) but on the other hand a legend is less important when it is used only sporadically.

'''Dynamism''': Dynamism supports the interactive change of the above described categories.

'''Design and Process''': During the design process the legend should be handled like a map or a data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or can be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together and can be divided into three subthemes. The ''"no legend"'' approach hides symbols when precise identification is not needed or self-explanatory(also under the aspect of showing symbols only on demand in a dynamic environment). In the ''"map-section"'' focus the legend becomes a natural legend, taking into account a two-dimensional spatial mapping (Fig. 1). And finally the ''"map becomes legend"'' theme, which is designed as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content. Furthermore it provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes raises the question how to relate and navigate between those alternative symbol sets. To solve this problem alternative styles are displayed simultaneously and related using layout.

'''"The Relevant Legend"''' : Only relevant information gets conveyed through the legend (e.g. things which are not on the map are not shown in the legend) . There are several variants derivable from the possibilities offered by this concept.
The ''"pop legend"'' influenced by community usage; ''"My Legend, my Map"'' influenced by group or individual requirements according to tasks at hand; ''"The Paint-Box Legend"'' utilizing the possibility to drag symbols from the legend onto the map, for example to identity regions with certain features; ''"The shopping Basket Legend"'', which enables the user to drop symbols from the map into the legend when needed.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes ==

In order to demonstrate the possibilities along with the prepared guidelines four prototypes were developed. The objective of this task was to communicate the ideas behind the guidelines and to get feedback for further developments.

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [62] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes including:

*a focus on the Strategi data set [45];
*applying 2D layouts to the rich Strategi feature class hierarchy;
*enhancing prototypes with styles, layout options and more features for bi-directional interaction.

The team went to work and produced another 2, more constrained and functional prototypes.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

Additionally three different legend orderings were introduced.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Conclusion ==
The impact of this study was in general very positive. Many of the identified problems with on-screen map legends could be addressed. The impact evaluation made also clear that visual legends are much more advantageous than static legends. Moreover EDINA, the initiator of the study, regarded the work as “inspirational” and has secured funding for an addition project.

== References ==
[Dykes et al. 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T19:45:34Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding to digital legends, the designers mostly rely on their subjective judgment and personal experience rather than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols.

'''Layout''' : As a legend uses space, it is important to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols must be consistent with the ones used in the map and to each other. They should also relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend should depend on the task at hand. On the one hand it can be useful to support the user with a legend even before the map is visible (e.g. bivariate legends, unfamiliar symbolism) but on the other hand a legend is less important when it is used only sporadically.

'''Dynamism''': Dynamism supports the interactive change of the above described categories.

'''Design and Process''': During the design process the legend should be handled like a map or a data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or can be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together and can be divided into three subthemes. The ''"no legend"'' approach hides symbols when precise identification is not needed or self-explanatory(also under the aspect of showing symbols only on demand in a dynamic environment). In the ''"map-section"'' focus the legend becomes a natural legend, taking into account a two-dimensional spatial mapping (Fig. 1). And finally the ''"map becomes legend"'' theme, which is designed as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content. Furthermore it provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes raises the question how to relate and navigate between those alternative symbol sets. To solve this problem alternative styles are displayed simultaneously and related using layout.

'''"The Relevant Legend"''' : Only relevant information gets conveyed through the legend (e.g. things which are not on the map are not shown in the legend) . There are several variants derivable from the possibilities offered by this concept.
The ''"pop legend"'' influenced by community usage; ''"My Legend, my Map"'' influenced by group or individual requirements according to tasks at hand; ''"The Paint-Box Legend"'' utilizing the possibility to drag symbols from the legend onto the map, for example to identity regions with certain features; ''"The shopping Basket Legend"'', which enables the user to drop symbols from the map into the legend when needed.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins, to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes ==

In order to demonstrate the possibilities along with the prepared guidelines four prototypes were developed. The objective of this task was to communicate the ideas behind the guidelines and to get feedback for further developments.

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [62] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes including:

*a focus on the Strategi data set [45];
*applying 2D layouts to the rich Strategi feature class hierarchy;
*enhancing prototypes with styles, layout options and more features for bi-directional interaction.

The team went to work and produced another 2, more constrained and functional prototypes.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

Additionally three different legend orderings were introduced.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Conclusion ==
The impact of this study was in general very positive. Many of the identified problems with on-screen map legends could be addressed. The impact evaluation made also clear that visual legends are much more advantageous than static legends. Moreover EDINA, the initiator of the study, regarded the work as “inspirational” and has secured funding for an addition project.

== References ==
[Dykes et al. 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T19:41:35Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding to digital legends, the designers mostly rely on their subjective judgment and personal experience rather than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols.

'''Layout''' : As a legend uses space, it is important to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols must be consistent with the ones used in the map and to each other. They should also relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend should depend on the task at hand. On the one hand it can be useful to support the user with a legend even before the map is visible (e.g. bivariate legends, unfamiliar symbolism) but on the other hand a legend is less important when it is used only sporadically.

'''Dynamism''': Dynamism supports the interactive change of the above described categories.

'''Design and Process''': During the design process the legend should be handled like a map or a data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or can be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together and can be divided into three subthemes. The ''"no legend"'' approach hides symbols when precise identification is not needed or self-explanatory(also under the aspect of showing symbols only on demand in a dynamic environment). In the ''"map-section"'' focus the legend becomes a natural legend, taking into account a two-dimensional spatial mapping (Fig. 1). And finally the ''"map becomes legend"'' theme, which is designed as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content. Furthermore it provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes, raises the question how to relate and navigate between those alternative symbol sets. Mapping those arrangements would be the problem to be solved by such a "legend of legends".

'''"The Relevant Legend"''' : Only relevant information gets conveyed through the legend (e.g. things which are not on the map are not shown in the legend) . There are several variants derivable from the possibilities offered by this concept.
The ''"pop legend"'' influenced by community usage; ''"My Legend, my Map"'' influenced by group or individual requirements according to tasks at hand; ''"The Paint-Box Legend"'' utilizing the possibility to drag symbols from the legend onto the map, for example to identity regions with certain features; ''"The shopping Basket Legend"'', which enables the user to drop symbols from the map into the legend when needed.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins, to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes ==

In order to demonstrate the possibilities along with the prepared guidelines four prototypes were developed. The objective of this task was to communicate the ideas behind the guidelines and to get feedback for further developments.

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [62] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes including:

*a focus on the Strategi data set [45];
*applying 2D layouts to the rich Strategi feature class hierarchy;
*enhancing prototypes with styles, layout options and more features for bi-directional interaction.

The team went to work and produced another 2, more constrained and functional prototypes.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

Additionally three different legend orderings were introduced.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Conclusion ==
The impact of this study was in general very positive. Many of the identified problems with on-screen map legends could be addressed. The impact evaluation made also clear that visual legends are much more advantageous than static legends. Moreover EDINA, the initiator of the study, regarded the work as “inspirational” and has secured funding for an addition project.

== References ==
[Dykes et al. 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T19:40:38Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding to digital legends, the designers mostly rely on their subjective judgment and personal experience rather than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols.

'''Layout''' : As a legend uses space, it is important to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols must be consistent with the ones used in the map and to each other. They should also relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend should depend on the task at hand. On the one hand it can be useful to support the user with a legend even before the map is visible (e.g. bivariate legends, unfamiliar symbolism) but on the other hand a legend is less important when it is used only sporadically.

'''Dynamism''': Dynamism supports the interactive change of the above described categories.

'''Design and Process''': During the design process the legend should be handled like a map or a data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or can be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together and can be divided into three subthemes. The ''"no legend"'' approach hides symbols when precise identification is not needed or self-explanatory(also under the aspect of showing symbols only on demand in a dynamic environment). In the ''"map-section"'' focus the legend becomes a natural legend, taking into account a two-dimensional spatial mapping (Fig. 1). And finally the ''"map becomes legend"'' theme, which is designed as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content. Furthermore it provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes, raises the question how to relate and navigate between those alternative symbol sets. Mapping those arrangements would be the problem to be solved by such a "legend of legends".

'''"The Relevant Legend"''' : Only relevant information gets conveyed through the legend (e.g. things which are not on the map are not shown in the legend) . There are several variants derivable from the possibilities offered by this concept.
The ''"pop legend"'' influenced by community usage; ''"My Legend, my Map"'' influenced by group or individual requirements according to tasks at hand; ''"The Paint-Box Legend"'' utilizing the possibility to drag symbols from the legend onto the map, for example to identity regions with certain features; ''"The shopping Basket Legend"'', which enables the user to drop symbols from the map into legend when needed.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins, to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes ==

In order to demonstrate the possibilities along with the prepared guidelines four prototypes were developed. The objective of this task was to communicate the ideas behind the guidelines and to get feedback for further developments.

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [62] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes including:

*a focus on the Strategi data set [45];
*applying 2D layouts to the rich Strategi feature class hierarchy;
*enhancing prototypes with styles, layout options and more features for bi-directional interaction.

The team went to work and produced another 2, more constrained and functional prototypes.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

Additionally three different legend orderings were introduced.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Conclusion ==
The impact of this study was in general very positive. Many of the identified problems with on-screen map legends could be addressed. The impact evaluation made also clear that visual legends are much more advantageous than static legends. Moreover EDINA, the initiator of the study, regarded the work as “inspirational” and has secured funding for an addition project.

== References ==
[Dykes et al. 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T17:36:58Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding to digital legends, the designers mostly rely on their subjective judgment and personal experience rather than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols.

'''Layout''' : As a legend uses space, it is important to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols must be consistent with the ones used in the map and to each other. They should also relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend should depend on the task at hand. On the one hand it can be useful to support the user with a legend even before the map is visible (e.g. bivariate legends, unfamiliar symbolism) but on the other hand a legend is less important when it is used only sporadically.

'''Dynamism''': Dynamism can be very convenient when dealing with change and alternative possibilities regarding design decisions and supports the interaction with the above described categories.

'''Design and Process''': During the design process the legend should be handled like a map or a data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or can be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together and can be divided into three subthemes. The ''"no legend"'' approach hides symbols when precise identification is not needed or self-explanatory(also under the aspect of showing symbols only on demand in a dynamic environment). In the ''"map-section"'' focus the legend becomes a natural legend, taking into account a two-dimensional spatial mapping (Fig. 1). And finally the ''"map becomes legend"'' theme, which is designed as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content. Furthermore it provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes, raises the question how to relate and navigate between those alternative symbol sets. Mapping those arrangements would be the problem to be solved by such a "legend of legends".

'''"The Relevant Legend"''' : Only relevant information gets conveyed through the legend (e.g. things which are not on the map are not shown in the legend) . There are several variants derivable from the possibilities offered by this concept.
The ''"pop legend"'' influenced by community usage; ''"My Legend, my Map"'' influenced by group or individual requirements according to tasks at hand; ''"The Paint-Box Legend"'' utilizing the possibility to drag symbols from the legend onto the map, for example to identity regions with certain features; ''"The shopping Basket Legend"'', which enables the user to drop symbols from the map into legend when needed.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins, to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes ==

In order to demonstrate the possibilities along with the prepared guidelines four prototypes were developed. The objective of this task was to communicate the ideas behind the guidelines and to get feedback for further developments.

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [62] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes including:

*a focus on the Strategi data set [45];
*applying 2D layouts to the rich Strategi feature class hierarchy;
*enhancing prototypes with styles, layout options and more features for bi-directional interaction.

The team went to work and produced another 2, more constrained and functional prototypes.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

Additionally three different legend orderings were introduced.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Conclusion ==
The impact of this study was in general very positive. Many of the identified problems with on-screen map legends could be addressed. The impact evaluation made also clear that visual legends are much more advantageous than static legends. Moreover EDINA, the initiator of the study, regarded the work as “inspirational” and has secured funding for an addition project.

== References ==
[Dykes et al. 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T17:33:42Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding to digital legends, the designers mostly rely on their subjective judgment and personal experience rather than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols.

'''Layout''' : As a legend uses space, it is important to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols must be consistent with the ones used in the map and to each other. They should also relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend should depend on the task at hand. On the one hand it can be useful to support the user with a legend even before the map is visible (e.g. bivariate legends, unfamiliar symbolism) but on the other hand a legend is less important when it is used only sporadically.

'''Dynamism''': Dynamism can be very convenient when dealing with change and alternative possibilities regarding design decisions. New options can be added, when used in combination with the categories above.

'''Design and Process''': During the design process the legend should be handled like a map or a data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together and can be divided into three subthemes. The ''"no legend"'' approach hides symbols when precise identification is not needed or self-explanatory(also under the aspect of showing symbols only on demand in a dynamic environment). In the ''"map-section"'' focus the legend becomes a natural legend, taking into account a two-dimensional spatial mapping (Fig. 1). And finally the ''"map becomes legend"'' theme, which is designed as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content. Furthermore it provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes, raises the question how to relate and navigate between those alternative symbol sets. Mapping those arrangements would be the problem to be solved by such a "legend of legends".

'''"The Relevant Legend"''' : Only relevant information gets conveyed through the legend (e.g. things which are not on the map are not shown in the legend) . There are several variants derivable from the possibilities offered by this concept.
The ''"pop legend"'' influenced by community usage; ''"My Legend, my Map"'' influenced by group or individual requirements according to tasks at hand; ''"The Paint-Box Legend"'' utilizing the possibility to drag symbols from the legend onto the map, for example to identity regions with certain features; ''"The shopping Basket Legend"'', which enables the user to drop symbols from the map into legend when needed.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins, to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes ==

In order to demonstrate the possibilities along with the prepared guidelines four prototypes were developed. The objective of this task was to communicate the ideas behind the guidelines and to get feedback for further developments.

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [62] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes including:

*a focus on the Strategi data set [45];
*applying 2D layouts to the rich Strategi feature class hierarchy;
*enhancing prototypes with styles, layout options and more features for bi-directional interaction.

The team went to work and produced another 2, more constrained and functional prototypes.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

Additionally three different legend orderings were introduced.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Conclusion ==
The impact of this study was in general very positive. Many of the identified problems with on-screen map legends could be addressed. The impact evaluation made also clear that visual legends are much more advantageous than static legends. Moreover EDINA, the initiator of the study, regarded the work as “inspirational” and has secured funding for an addition project.

== References ==
[Dykes et al. 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T17:11:02Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding to digital legends, the designers mostly rely on their subjective judgment and personal experience rather than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols.

'''Layout''' : As a legend uses space, it is important to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols must be consistent with the ones used in the map and to each other. Also they should relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend should depend on the task at hand. On the one hand it can be useful to support the user with a legend even before the map is visible (e.g. bivariate legends, unfamiliar symbolism) but on the other hand a legend is less important when it is used only sporadically.

'''Dynamism''': Dynamism can be very convenient when dealing with change and alternative possibilities regarding design decisions. New options can be added, when used in combination with the categories above.

'''Design and Process''': During the design process the legend should be handled like a map or a data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together and can be divided into three subthemes. The ''"no legend"'' approach hides symbols when precise identification is not needed or self-explanatory(also under the aspect of showing symbols only on demand in a dynamic environment). In the ''"map-section"'' focus the legend becomes a natural legend, taking into account a two-dimensional spatial mapping (Fig. 1). And finally the ''"map becomes legend"'' theme, which is designed as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content. Furthermore it provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes, raises the question how to relate and navigate between those alternative symbol sets. Mapping those arrangements would be the problem to be solved by such a "legend of legends".

'''"The Relevant Legend"''' : Only relevant information gets conveyed through the legend (e.g. things which are not on the map are not shown in the legend) . There are several variants derivable from the possibilities offered by this concept.
The ''"pop legend"'' influenced by community usage; ''"My Legend, my Map"'' influenced by group or individual requirements according to tasks at hand; ''"The Paint-Box Legend"'' utilizing the possibility to drag symbols from the legend onto the map, for example to identity regions with certain features; ''"The shopping Basket Legend"'', which enables the user to drop symbols from the map into legend when needed.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins, to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes ==

In order to demonstrate the possibilities along with the prepared guidelines four prototypes were developed. The objective of this task was to communicate the ideas behind the guidelines and to get feedback for further developments.

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [62] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes including:

*a focus on the Strategi data set [45];
*applying 2D layouts to the rich Strategi feature class hierarchy;
*enhancing prototypes with styles, layout options and more features for bi-directional interaction.

The team went to work and produced another 2, more constrained and functional prototypes.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

Additionally three different legend orderings were introduced.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Conclusion ==
The impact of this study was in general very positive. Many of the identified problems with on-screen map legends could be addressed. The impact evaluation made also clear that visual legends are much more advantageous than static legends. Moreover EDINA, the initiator of the study, regarded the work as “inspirational” and has secured funding for an addition project.

== References ==
[Dykes et al. 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T17:03:39Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding to digital legends, the designers mostly rely on their subjective judgment and personal experience rather than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols.

'''Layout''' : As a legend uses space, it is important to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols must be consistent with the ones used in the map and to each other. Also they should relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend should depend on the task at hand. On the one hand it can be useful to support the user with a legend even before the map is visible (e.g. bivariate legends, unfamiliar symbolism) but on the other hand it can be of lesser need when it’s expected that the legend is used less frequently.

'''Dynamism''': Dynamism can be very convenient when dealing with change and alternative possibilities regarding design decisions. New options can be added, when used in combination with the categories above.

'''Design and Process''': During the design process the legend should be handled like a map or a data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together and can be divided into three subthemes. The ''"no legend"'' approach hides symbols when precise identification is not needed or self-explanatory(also under the aspect of showing symbols only on demand in a dynamic environment). In the ''"map-section"'' focus the legend becomes a natural legend, taking into account a two-dimensional spatial mapping (Fig. 1). And finally the ''"map becomes legend"'' theme, which is designed as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content. Furthermore it provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes, raises the question how to relate and navigate between those alternative symbol sets. Mapping those arrangements would be the problem to be solved by such a "legend of legends".

'''"The Relevant Legend"''' : Only relevant information gets conveyed through the legend (e.g. things which are not on the map are not shown in the legend) . There are several variants derivable from the possibilities offered by this concept.
The ''"pop legend"'' influenced by community usage; ''"My Legend, my Map"'' influenced by group or individual requirements according to tasks at hand; ''"The Paint-Box Legend"'' utilizing the possibility to drag symbols from the legend onto the map, for example to identity regions with certain features; ''"The shopping Basket Legend"'', which enables the user to drop symbols from the map into legend when needed.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins, to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes ==

In order to demonstrate the possibilities along with the prepared guidelines four prototypes were developed. The objective of this task was to communicate the ideas behind the guidelines and to get feedback for further developments.

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [62] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes including:

*a focus on the Strategi data set [45];
*applying 2D layouts to the rich Strategi feature class hierarchy;
*enhancing prototypes with styles, layout options and more features for bi-directional interaction.

The team went to work and produced another 2, more constrained and functional prototypes.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

Additionally three different legend orderings were introduced.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Conclusion ==
The impact of this study was in general very positive. Many of the identified problems with on-screen map legends could be addressed. The impact evaluation made also clear that visual legends are much more advantageous than static legends. Moreover EDINA, the initiator of the study, regarded the work as “inspirational” and has secured funding for an addition project.

== References ==
[Dykes et al. 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T17:00:11Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding to digital legends, the designers mostly rely on their subjective judgment and personal experience rather than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols.

'''Layout''' : As a legend uses space, it is important to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols must be consistent with the ones used in the map and to each other. Also they should relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend, should be depended on the task at hand. On the one hand it can be useful to support the user with a legend even before the map is visible (e.g. bivariate legends, unfamiliar symbolism) but on the other hand it can be of lesser need when it’s expected that the legend is used less frequently.

'''Dynamism''': Dynamism can be very convenient when dealing with change and alternative possibilities regarding design decisions. New options can be added, when used in combination with the categories above.

'''Design and Process''': During the design process the legend should be handled like a map or a data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together and can be divided into three subthemes. The ''"no legend"'' approach hides symbols when precise identification is not needed or self-explanatory(also under the aspect of showing symbols only on demand in a dynamic environment). In the ''"map-section"'' focus the legend becomes a natural legend, taking into account a two-dimensional spatial mapping (Fig. 1). And finally the ''"map becomes legend"'' theme, which is designed as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content. Furthermore it provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes, raises the question how to relate and navigate between those alternative symbol sets. Mapping those arrangements would be the problem to be solved by such a "legend of legends".

'''"The Relevant Legend"''' : Only relevant information gets conveyed through the legend (e.g. things which are not on the map are not shown in the legend) . There are several variants derivable from the possibilities offered by this concept.
The ''"pop legend"'' influenced by community usage; ''"My Legend, my Map"'' influenced by group or individual requirements according to tasks at hand; ''"The Paint-Box Legend"'' utilizing the possibility to drag symbols from the legend onto the map, for example to identity regions with certain features; ''"The shopping Basket Legend"'', which enables the user to drop symbols from the map into legend when needed.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins, to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes ==

In order to demonstrate the possibilities along with the prepared guidelines four prototypes were developed. The objective of this task was to communicate the ideas behind the guidelines and to get feedback for further developments.

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [62] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes including:

*a focus on the Strategi data set [45];
*applying 2D layouts to the rich Strategi feature class hierarchy;
*enhancing prototypes with styles, layout options and more features for bi-directional interaction.

The team went to work and produced another 2, more constrained and functional prototypes.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

Additionally three different legend orderings were introduced.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Conclusion ==
The impact of this study was in general very positive. Many of the identified problems with on-screen map legends could be addressed. The impact evaluation made also clear that visual legends are much more advantageous than static legends. Moreover EDINA, the initiator of the study, regarded the work as “inspirational” and has secured funding for an addition project.

== References ==
[Dykes et al. 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T16:57:09Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding to digital legends, the designers mostly rely on their subjective judgment and personal experience rather than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols.

'''Layout''' : As a legend uses space, it is of important matter to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols must be consistent with the ones used in the map and to each other. Also they should relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend, should be depended on the task at hand. On the one hand it can be useful to support the user with a legend even before the map is visible (e.g. bivariate legends, unfamiliar symbolism) but on the other hand it can be of lesser need when it’s expected that the legend is used less frequently.

'''Dynamism''': Dynamism can be very convenient when dealing with change and alternative possibilities regarding design decisions. New options can be added, when used in combination with the categories above.

'''Design and Process''': During the design process the legend should be handled like a map or a data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together and can be divided into three subthemes. The ''"no legend"'' approach hides symbols when precise identification is not needed or self-explanatory(also under the aspect of showing symbols only on demand in a dynamic environment). In the ''"map-section"'' focus the legend becomes a natural legend, taking into account a two-dimensional spatial mapping (Fig. 1). And finally the ''"map becomes legend"'' theme, which is designed as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content. Furthermore it provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes, raises the question how to relate and navigate between those alternative symbol sets. Mapping those arrangements would be the problem to be solved by such a "legend of legends".

'''"The Relevant Legend"''' : Only relevant information gets conveyed through the legend (e.g. things which are not on the map are not shown in the legend) . There are several variants derivable from the possibilities offered by this concept.
The ''"pop legend"'' influenced by community usage; ''"My Legend, my Map"'' influenced by group or individual requirements according to tasks at hand; ''"The Paint-Box Legend"'' utilizing the possibility to drag symbols from the legend onto the map, for example to identity regions with certain features; ''"The shopping Basket Legend"'', which enables the user to drop symbols from the map into legend when needed.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins, to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes ==

In order to demonstrate the possibilities along with the prepared guidelines four prototypes were developed. The objective of this task was to communicate the ideas behind the guidelines and to get feedback for further developments.

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [62] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes including:

*a focus on the Strategi data set [45];
*applying 2D layouts to the rich Strategi feature class hierarchy;
*enhancing prototypes with styles, layout options and more features for bi-directional interaction.

The team went to work and produced another 2, more constrained and functional prototypes.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

Additionally three different legend orderings were introduced.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Conclusion ==
The impact of this study was in general very positive. Many of the identified problems with on-screen map legends could be addressed. The impact evaluation made also clear that visual legends are much more advantageous than static legends. Moreover EDINA, the initiator of the study, regarded the work as “inspirational” and has secured funding for an addition project.

== References ==
[Dykes et al. 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T16:52:05Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding digital legends, the designers mostly rely rather on their subjective judgment and personal experience, than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols.

'''Layout''' : As a legend uses space, it is of important matter to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols must be consistent with the ones used in the map and to each other. Also they should relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend, should be depended on the task at hand. On the one hand it can be useful to support the user with a legend even before the map is visible (e.g. bivariate legends, unfamiliar symbolism) but on the other hand it can be of lesser need when it’s expected that the legend is used less frequently.

'''Dynamism''': Dynamism can be very convenient when dealing with change and alternative possibilities regarding design decisions. New options can be added, when used in combination with the categories above.

'''Design and Process''': During the design process the legend should be handled like a map or a data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together and can be divided into three subthemes. The ''"no legend"'' approach hides symbols when precise identification is not needed or self-explanatory(also under the aspect of showing symbols only on demand in a dynamic environment). In the ''"map-section"'' focus the legend becomes a natural legend, taking into account a two-dimensional spatial mapping (Fig. 1). And finally the ''"map becomes legend"'' theme, which is designed as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content. Furthermore it provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes, raises the question how to relate and navigate between those alternative symbol sets. Mapping those arrangements would be the problem to be solved by such a "legend of legends".

'''"The Relevant Legend"''' : Only relevant information gets conveyed through the legend (e.g. things which are not on the map are not shown in the legend) . There are several variants derivable from the possibilities offered by this concept.
The ''"pop legend"'' influenced by community usage; ''"My Legend, my Map"'' influenced by group or individual requirements according to tasks at hand; ''"The Paint-Box Legend"'' utilizing the possibility to drag symbols from the legend onto the map, for example to identity regions with certain features; ''"The shopping Basket Legend"'', which enables the user to drop symbols from the map into legend when needed.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins, to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes ==

In order to demonstrate the possibilities along with the prepared guidelines four prototypes were developed. The objective of this task was to communicate the ideas behind the guidelines and to get feedback for further developments.

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [62] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes including:

*a focus on the Strategi data set [45];
*applying 2D layouts to the rich Strategi feature class hierarchy;
*enhancing prototypes with styles, layout options and more features for bi-directional interaction.

The team went to work and produced another 2, more constrained and functional prototypes.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

Additionally three different legend orderings were introduced.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Conclusion ==
The impact of this study was in general very positive. Many of the identified problems with on-screen map legends could be addressed. The impact evaluation made also clear that visual legends are much more advantageous than static legends. Moreover EDINA, the initiator of the study, regarded the work as “inspirational” and has secured funding for an addition project.

== References ==
[Dykes et al. 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

Teaching talk:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T16:34:12Z

UE-InfoVis1011 0402530:

Ich habe den Text etwas überarbeitet und die Fehler, die mir aufgefallen sind, entfernt. Da es mir zu mühsam ist, alle Änderungen konkret hier im Wiki aufzulisten, schicke ich eine Email aus, wo alle Änderungen markiert sind.

@Content: Bei "Digital Prototypes: Focussed Development" ist beim punkt : " a focus on the Strategi data set; " und bei "In the case of this paper a 2D spatial treemap" eine [referenz] ausm paper drinnen. ich schätz mal das is nicht absicht. Ich besser mal die (") kleinigkeit aus. beim -> T"he Legend as Statistical Graphic – Hierarchy". aus -- [[User:UE-InfoVis1011 0051804|UE-InfoVis1011 0051804]] 16:24, 17 November 2010 (CET)

@Bild: Ich bin mir da nicht ganz sicher. bei der fig.3 ist im paper extra ein copyright angeführt das ich als urheber angegeben hab beim upload. Rein referenziell glaub ich, dass man sowieso nur auf das paper referenzieren muss (bakkarbeitsmäßig) und nicht auf die "quelle der quelle". Aber inwiefern sich das referenz- und urhebertechnisch in einer Wiki von anderen arbeiten bzw. papers unterscheidet in bezug auf fairuse/copyright is halt die frage. -- [[User:UE-InfoVis1011 0051804|UE-InfoVis1011 0051804]] 16:15, 17 November 2010 (CET)

@Bild: Dürfen wir die Bilder überhaupt verwenden? Wegen Copyright und so, oder fällt das unter fair use?

@Bild: Die referenzen hab ich beim upload selbst angegeben . source inkl. "fig.3" bzw. copyright, welches im text unter der abbildung im paper ist. Aber ich habs jetzt nochmal in der bildbeschriftung eingefügt für alle fälle.
-- [[User:UE-InfoVis1011 0051804|UE-InfoVis1011 0051804]] 21:10, 16 November 2010 (CET)

Bild: das sollte auch referenziert werden

Euer Artikel:

Rethinking Map Legends with Visualization
Jason Dykes, Jo Wood, Aidan Slingsby
IEEE Transactions on Visualization and Computer Graphics (TVCG)
November/December 2010 (vol. 16 no. 6):890-899, 2010.

[http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=5613425 http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=5613425] (Zugriff im TU Netzwerk)

-- [[Gschwandtner, Theresia|Theresia Gschwandtner]] 07:49, 08 November 2010 (CEST)

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T16:30:42Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding digital legends, the designers mostly rely rather on their subjective judgment and personal experience, than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols

'''Layout''' : As a legend uses space, it is of important matter to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols must be consistent with the ones used in the map and to each other. Also they should relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend, should be depended on the task at hand. On the one hand it can be useful to support the user with a legend even before the map is visible (e.g. bivariate legends, unfamiliar symbolism) but on the other hand it can be of lesser need when it’s expected that the legend is used less frequently.

'''Dynamism''': Dynamism comes in hand when dealing with change and alternative possibilities regarding design decisions. New options can be added, when used in combination with the categories above.

'''Design and Process''': During the design process the legend should be handled like a map or a data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together and can be divided into three subthemes. The ''"no legend"'' approach hides symbols when precise identification is not needed or self-explanatory(also under the aspect of showing symbols only on demand in a dynamic environment). In the ''"map-section"'' focus the legend becomes a natural legend, taking into account a two-dimensional spatial mapping (Fig. 1). And finally the ''"map becomes legend"'' theme, which is designed as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content. Furthermore it provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes, raises the question how to relate and navigate between those alternative symbol sets. Mapping those arrangements would be the problem to be solved by such a "legend of legends".

'''"The Relevant Legend"''' : Only relevant information gets conveyed through the legend (e.g. things which are not on the map are not shown in the legend) . There are several variants derivable from the possibilities offered by this concept.
The ''"pop legend"'' influenced by community usage; ''"My Legend, my Map"'' influenced by group or individual requirements according to tasks at hand; ''"The Paint-Box Legend"'' utilizing the possibility to drag symbols from the legend onto the map, for example to identity regions with certain features; ''"The shopping Basket Legend"'', which enables the user to drop symbols from the map into legend when needed.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins, to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes ==

In order to demonstrate the possibilities along with the prepared guidelines four prototypes were developed. The objective of this task was to communicate the ideas behind the guidelines and to get feedback for further developments.

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [62] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes including:

*a focus on the Strategi data set [45];
*applying 2D layouts to the rich Strategi feature class hierarchy;
*enhancing prototypes with styles, layout options and more features for bi-directional interaction.

The team went to work and produced another 2, more constrained and functional prototypes.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

Additionally three different legend orderings were introduced.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Conclusion ==
The impact of this study was in general very positive. Many of the identified problems with on-screen map legends could be addressed. The impact evaluation made also clear that visual legends are much more advantageous than static legends. Moreover EDINA, the initiator of the study, regarded the work as “inspirational” and has secured funding for an addition project.

== References ==
[Dykes et al. 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T16:29:29Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding digital legends, the designers mostly rely rather on their subjective judgment and personal experience, than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols

'''Layout''' : As a legend uses space, it is of important matter to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols must be consistent with the ones used in the map and to each other. Also they should relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend, should be depended on the task at hand. On the one hand it can be useful to support the user with a legend even before the map is visible (e.g. bivariate legends, unfamiliar symbolism) but on the other hand it can be of lesser need when it’s expected that the legend is used less frequently.

'''Dynamism''': Dynamism comes in hand when dealing with change and alternative possibilities regarding design decisions. New options can be added, when used in combination with the categories above.

'''Design and Process''': During the design process the legend should be handled like a map or a data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together and can be divided into three subthemes. The ''"no legend"'' approach hides symbols when precise identification is not needed or self-explanatory(also under the aspect of showing symbols only on demand in a dynamic environment). In the ''"map-section"'' focus the legend becomes a natural legend, taking into account a two-dimensional spatial mapping (Fig. 1). And finally the ''"map becomes legend"'' theme, which is designed as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content. Furthermore it provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes, raises the question how to relate and navigate between those alternative symbol sets. Mapping those arrangements would be the problem to be solved by such a "legend of legends".

'''"The Relevant Legend"''' : Only relevant information gets conveyed through the legend (e.g. things which are not on the map are not shown in the legend) . There are several variants derivable from the possibilities offered by this concept.
The ''"pop legend"'' influenced by community usage; ''"My Legend, my Map"'' influenced by group or individual requirements according to tasks at hand; ''"The Paint-Box Legend"'' utilizing the possibility to drag symbols from the legend onto the map, for example to identity regions with certain features; ''"The shopping Basket Legend"'', which enables the user to drop symbols from the map into legend when needed.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins, to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes ==

In order to demonstrate the possibilities along with the prepared guidelines four prototypes were developed. The objective of this task was to communicate the ideas behind the guidelines and to get feedback for further developments.

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [62] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes including:

*a focus on the Strategi data set [45];
*applying 2D layouts to the rich Strategi feature class hierarchy;
*enhancing prototypes with styles, layout options and more features for bi-directional interaction.

The team went to work and produced another 2, more constrained and functional prototypes.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

Additionally three different legend orderings were introduced.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Conclusion ==
The impact of this study was in general very positive. Many of the identified problems with on-screen map legends could be addressed. The impact evaluation made clear that visual legends are much more advantageous than static legends. Moreover EDINA, the initiator of the study, regarded the work as “inspirational” and has secured funding for an addition project.

== References ==
[Dykes et al. 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T16:26:41Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding digital legends, the designers mostly rely rather on their subjective judgment and personal experience, than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols

'''Layout''' : As a legend uses space, it is of important matter to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols must be consistent with the ones used in the map and to each other. Also they should relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend, should be depended on the task at hand. On the one hand it can be useful to support the user with a legend even before the map is visible (e.g. bivariate legends, unfamiliar symbolism) but on the other hand it can be of lesser need when it’s expected that the legend is used less frequently.

'''Dynamism''': Dynamism comes in hand when dealing with change and alternative possibilities regarding design decisions. New options can be added, when used in combination with the categories above.

'''Design and Process''': During the design process the legend should be handled like a map or a data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together and can be divided into three subthemes. The ''"no legend"'' approach hides symbols when precise identification is not needed or self-explanatory(also under the aspect of showing symbols only on demand in a dynamic environment). In the ''"map-section"'' focus the legend becomes a natural legend, taking into account a two-dimensional spatial mapping (Fig. 1). And finally the ''"map becomes legend"'' theme, which is designed as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content. Furthermore it provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes, raises the question how to relate and navigate between those alternative symbol sets. Mapping those arrangements would be the problem to be solved by such a "legend of legends".

'''"The Relevant Legend"''' : Only relevant information gets conveyed through the legend (e.g. things which are not on the map are not shown in the legend) . There are several variants derivable from the possibilities offered by this concept.
The ''"pop legend"'' influenced by community usage; ''"My Legend, my Map"'' influenced by group or individual requirements according to tasks at hand; ''"The Paint-Box Legend"'' utilizing the possibility to drag symbols from the legend onto the map, for example to identity regions with certain features; ''"The shopping Basket Legend"'', which enables the user to drop symbols from the map into legend when needed.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins, to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes: Imagination Exercise ==

Section 5 and 6 of the paper describe the implementation of the previously discussed themes and ideas. They first developed 4 prototypes.

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [62] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

== Digital Prototypes: Focussed Development ==

After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes including:

*a focus on the Strategi data set [45];
*applying 2D layouts to the rich Strategi feature class hierarchy;
*enhancing prototypes with styles, layout options and more features for bi-directional interaction.

The team went to work and produced another 2, more constrained and functional prototypes.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

Additionally three different legend orderings were introduced.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Impact ==

The impact, which is discussed in section 7 of the paper, was in general very positive.

'''"Current Problems and Successes'''" : The team could address many of the identified problems. Most design intention could be achieved. Only the legend/map display ratio in favor of the map, created no impact and therefore remains an ongoing priority.

'''"Aspirations'''" : The team received a good response on achieving aspirations. Because it was not a high-priority target the issue of text-based search was not addressed. Aesthetics was also a key point.

'''"Tasks and Functionality'''" : The impact evaluation made clear, that visual legends are much more advantageous than static legends. Evaluators furthermore commented that visual legends can give map a more professional look.

'''"Other Reactions'''" : EDINA regarded the work as “inspirational” and has secured funding for an additional project.

== References ==
[Dykes et al. 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T16:22:07Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding digital legends, the designers mostly rely rather on their subjective judgment and personal experience, than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols

'''Layout''' : As a legend uses space, it is of important matter to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols must be consistent with the ones used in the map and to each other. Also they should relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend, should be depended on the task at hand. On the one hand it can be useful to support the user with a legend even before the map is visible (e.g. bivariate legends, unfamiliar symbolism) but on the other hand it can be of lesser need when it’s expected that the legend is used less frequently.

'''Dynamism''': Dynamism comes in hand when dealing with change and alternative possibilities regarding design decisions. New options can be added, when used in combination with the categories above.

'''Design and Process''': During the design process the legend should be handled like a map or a data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together, this concept can be divided into three subthemes. The ''"no legend"'' approach - hiding symbols when precise identification is not needed or self-explanatory ones (also under the aspect of showing symbols only on demand in a dynamic environment); the ''"map-section"'' focus (Fig.1) - under which the legend becomes a natural legend, taking into account a two-dimensional spatial mapping; and furthermore the ''"map becomes legend"'' theme - which is implemented as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content. Furthermore it provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes, raises the question how to relate and navigate between those alternative symbol sets. Mapping those arrangements would be the problem to be solved by such a "legend of legends".

'''"The Relevant Legend"''' : Relevance of selection is the key motivation of this approach. Only relevant information gets conveyed through the legend (e.g. things which are not on the map are not shown in the legend) . There are several variants derivable from the possibilities offered by this concept.
The ''"pop legend"'' influenced by community usage; ''"My Legend, my Map"'' influenced by group or individual requirements according to tasks at hand; ''"The Paint-Box Legend"'' utilizing the possibility to drag symbols from the legend onto the map, for example to identity regions with certain features; ''"The shopping Basket Legend"'', which enables the user to drop symbols from the map into legend when needed.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins, to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes: Imagination Exercise ==

Section 5 and 6 of the paper describe the implementation of the previously discussed themes and ideas. They first developed 4 prototypes.

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [62] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

== Digital Prototypes: Focussed Development ==

After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes including:

*a focus on the Strategi data set [45];
*applying 2D layouts to the rich Strategi feature class hierarchy;
*enhancing prototypes with styles, layout options and more features for bi-directional interaction.

The team went to work and produced another 2, more constrained and functional prototypes.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

Additionally three different legend orderings were introduced.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Impact ==

The impact, which is discussed in section 7 of the paper, was in general very positive.

'''"Current Problems and Successes'''" : The team could address many of the identified problems. Most design intention could be achieved. Only the legend/map display ratio in favor of the map, created no impact and therefore remains an ongoing priority.

'''"Aspirations'''" : The team received a good response on achieving aspirations. Because it was not a high-priority target the issue of text-based search was not addressed. Aesthetics was also a key point.

'''"Tasks and Functionality'''" : The impact evaluation made clear, that visual legends are much more advantageous than static legends. Evaluators furthermore commented that visual legends can give map a more professional look.

'''"Other Reactions'''" : EDINA regarded the work as “inspirational” and has secured funding for an additional project.

== References ==
[Dykes et al. 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-17T16:19:00Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualization techniques.

== Introduction ==
Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined. All the work was done in cooperation with EDINA who provide digital mapping services for UK.

== Legend Design ==
Due to a lack of generalized, objective guidelines regarding digital legends, the designers mostly rely rather on their subjective judgment and personal experience, than on objective principles. Guidance for the design of digital legends in literature is often surprisingly conservative, hence
broad guidelines for design considerations were developed, based on extensive research on different kind of resources. These guidelines are oriented on the following categories:

'''Selection''' : To uphold the cognitive focus and avoid dividing the attention of the user between map and legend, only relevant information should be shown, i.e. unknown or not self explanatory symbols

'''Layout''' : As legend uses space, it is of important matter to arrange its elements in a meaningful way. The representation structure should follow a visual logic. The most effective legends are those, which are reflecting relationships among data.

'''Symbols''' : The way features are represented by symbols, must be consistent with the ones used in the map and to each other. Also they should relate to the mapped phenomenon they represent and fulfill expectations arising within a social and cultural context.

'''Position''': When, where or how a user is encountering a legend, should be depended on the task at hand. For example, while it can be of use to support the user with a legend even before the map is visible in some cases (e.g. bivariate legends, unfamiliar symbolism), it can be of lesser need when it's expected that the legend is used less frequently.

'''Dynamism''': Dynamism comes in handy when dealing with change and alternative possibilities regarding design decisions. New options can be added, when used in combination with the categories above.

'''Design and Process''': During the design process the legend should be handled like map or data graphic. The legend should be seen as spatial information visualization, to which aesthetic and relational qualities apply.

== Legend Themes ==

To provide support in the process of software development and to frame ideas, legend-themes were created. Those themes describe perspectives on the legend utilizing the guidelines, in accordance with the defined problem domain. The themes can be used alone or be combined with each other.
[[Image:The_Map_is_Legend.jpg | 400px | thumb | '''Figure 1 ''' : ''The Map is the Legend - Map Section [Dykes et al. 2010] - (Ordnance Survey. OS Landranger (1:50,000 scale) map symbols. 2002.)'']]
'''"The Map is Legend"''' : This concept fuses the roles of map and legend together, this concept can be divided into three subthemes. The ''"no legend"'' approach - hiding symbols when precise identification is not needed or self-explanatory ones (also under the aspect of showing symbols only on demand in a dynamic environment); the ''"map-section"'' focus (Fig.1) - under which the legend becomes a natural legend, taking into account a two-dimensional spatial mapping; and furthermore the ''"map becomes legend"'' theme - which is implemented as a dynamic map, allowing transformation between legend elements and the according spatial map allocation.

'''"The Legend as Statistical Graphic"''' : In this case the legend acts as an statistical overview of the current selection, reflecting a summary of map content and furthermore provides the basis for exploring the map in a query-like manner.

'''"A Legend of Legends"''' : The possibility of having different styles of symbol schemes, raises the question how to relate and navigate between those alternative symbol sets. Mapping those arrangements would be the problem to be solved by such a "legend of legends".

'''"The Relevant Legend"''' : Relevance of selection is the key motivation of this approach. Only relevant information gets conveyed through the legend (e.g. things which are not on the map are not shown in the legend) . There are several variants derivable from the possibilities offered by this concept.
The ''"pop legend"'' influenced by community usage; ''"My Legend, my Map"'' influenced by group or individual requirements according to tasks at hand; ''"The Paint-Box Legend"'' utilizing the possibility to drag symbols from the legend onto the map, for example to identity regions with certain features; ''"The shopping Basket Legend"'', which enables the user to drop symbols from the map into legend when needed.

'''"The Source independent Legend"''' : The characteristics of how the items are being grouped are not related to the sources the described data comes from. Yet the symbols should give information of their origins, to make the sources of related data distinguishable.

'''"The Ground Truth Legend"''' : In this case, the symbolism used depends on local community based decisions. Relevance between map and legend gets augmented by community customized imagery .

== Digital Prototypes: Imagination Exercise ==

Section 5 and 6 of the paper describe the implementation of the previously discussed themes and ideas. They first developed 4 prototypes.

'''"The Map is the Legend'''" : In this prototype the 1D legend can be transformed into a 2D map, which can furthermore be transformed into a 2D legend.

'''"The Legend as Statistical Graphic – Bar Chart'''" : The legend in this prototype consists of bar charts, which represent the summery of the features (e.g. Building Area, Road Or Track Area, …) of the current map view. The program also supports bidirectional interactions for selection and highlighting between the map and the legend.

'''"The Legend as Statistical Graphic – Matrix'''" : This prototype supports the exploration of co-occurring features. For this purpose two feature classes can be assigned to the two axes of this 2D legend. The resulting matrix describes the degree of co-occurrence of these features in the current part of the map.

'''"The Legend as Statistical Graphic – Hierarchy'''" : Prototype 4 explores the idea of using a hierarchical legend for data that is hierarchical in nature. In the case of this paper a 2D spatial treemap [62] is used for the depiction of the national bedrock geology classification. The prototype supports bi-directional interactions between the map and the legend.

== Digital Prototypes: Focussed Development ==

After the development of the first four prototypes a second round of discussion with EDINA followed. After some consideration time, EDINA issued priorities for the next round of prototypes including:

*a focus on the Strategi data set [45];
*applying 2D layouts to the rich Strategi feature class hierarchy;
*enhancing prototypes with styles, layout options and more features for bi-directional interaction.

The team went to work and produced another 2, more constrained and functional prototypes.

'''"The Map is the Legend – Strategi'''" : Here “The Map is the Legend” theme is applied to Strategi. Because of the significant amount of features, there were some new design issues. The screen space didn’t suffice to harbor the whole legend, in the case of a large font and a number of features selected.

Additionally three different legend orderings were introduced.

'''"The Legend as Statistical Graphic – Strategi'''" : In this prototype the legend reflects the hierarchical structure of the strategi dataset (point, line, area). The total occurrences of the statistical data values are encoded in the size of the symbol (national) and in the color (local).

== Impact ==

The impact, which is discussed in section 7 of the paper, was in general very positive.

'''"Current Problems and Successes'''" : The team could address many of the identified problems. Most design intention could be achieved. Only the legend/map display ratio in favor of the map, created no impact and therefore remains an ongoing priority.

'''"Aspirations'''" : The team received a good response on achieving aspirations. Because it was not a high-priority target the issue of text-based search was not addressed. Aesthetics was also a key point.

'''"Tasks and Functionality'''" : The impact evaluation made clear, that visual legends are much more advantageous than static legends. Evaluators furthermore commented that visual legends can give map a more professional look.

'''"Other Reactions'''" : EDINA regarded the work as “inspirational” and has secured funding for an additional project.

== References ==
[Dykes et al. 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

Teaching talk:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-16T18:49:00Z

UE-InfoVis1011 0402530:

Bild: das sollte auch referenziert werden

Euer Artikel:

Rethinking Map Legends with Visualization
Jason Dykes, Jo Wood, Aidan Slingsby
IEEE Transactions on Visualization and Computer Graphics (TVCG)
November/December 2010 (vol. 16 no. 6):890-899, 2010.

[http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=5613425 http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=5613425] (Zugriff im TU Netzwerk)

-- [[Gschwandtner, Theresia|Theresia Gschwandtner]] 07:49, 08 November 2010 (CEST)

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-16T10:48:07Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

The following article is a summary of [Dykes et al. 2010], where the design of map legends is combined with visualition techniques. Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities. In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined.

== References ==
[Dykes et al. 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-16T10:37:04Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities.
In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined.

== References ==
[Dykes et al. 2010] Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2

2010-11-16T10:35:34Z

UE-InfoVis1011 0402530:

= Rethinking Map Legends with Visualization =

Maps are cartographic projections from the 3 dimensional Earth’s surface to a 2 dimensional plane. Due to the loss of information caused by this transformation legends are used in order to make the maps easily accessible. But many of the information designs used in maps were developed for a static context whereas map legends in a dynamic environment offer new possibilities.
In order to develop new guidelines for legend design current problems and successes with on-screen maps were identified. Based on these results aspirations, tasks and functionality of digimap legends were determined.

== References ==
[Dykes et al. 2010]Jason Dykes, Jo Wood, Aidan Slingsby. Rethinking Map Legends with Visualization.''IEEE Transactions on Visualization and Computer Graphics'', 16(6): 890 - 899 , November/December 2010

Teaching:TUW - UE InfoVis WS 2010/11

2010-11-04T12:25:39Z

UE-InfoVis1011 0402530:

[[Image:Aigner03infovis ue.gif]] <big>WS 2010/11</big>

'''LVA Nr:''' 188.308 ([https://tiss.tuwien.ac.at/course/courseDetails.xhtml?courseNr=188308&semester=2010W TISS Seite])

'''LVA Homepage:''' http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws10/index.html

'''Leitung:''' [[Aigner, Wolfgang|Wolfgang Aigner]] [aigner (at) ifs.tuwien.ac.at] 
:: [[Gschwandtner, Theresia|Theresia Gschwandtner]] [gschwandtner (at) ifs.tuwien.ac.at] 

== Gruppen ==

*[[Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 01|Gruppe 01 (Emrich, Kraxner, Schneider)]]
*[[Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 03|Gruppe 03 (Leichtfried, Chwistek, Kastner)]]
*[[Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 05|Gruppe 05 (Alili, Bachhuber, Marschik)]]
*[[Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06|Gruppe 06 (Fikar, Posset, Nezveda)]]

== News / Bemerkungen ==
Liebe Studierende, 
die Grafiken für Aufgabe 1 (Workshop) sind [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws10/infovis_ue_aufgabe1.html online]. 
-- [[User:Iwolf|Wolfgang Aigner]] 11:46, 28 October 2010 (CEST)

Liebe TeilnehmerInnen! 
Die Aufgabe 0 habt ihr erfolgreich abgeschlossen (die Punkte findet ihr auf der jeweiligen Talk Seite zu eurer Gruppenseite). 
Bitte füllt die Gruppen auf, damit wir in 3er Gruppen weiterarbeiten können. Ich schlage vor:
Michael Kraxner zu Gruppe 1,
Philipp Kastner zu Gruppe 3 und
Matej Nezveda zu Gruppe 6.
Falls ihr euch intern einigt wer wohin wechselt ist uns das auch recht. 
Die zu verbessernden Grafiken für Aufgabe 1 findet ihr auf der LVA Homepage: http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws10/infovis_ue_aufgabe1.html. 
-- [[Gschwandtner, Theresia|Theresia Gschwandtner]] 12:39, 27 October 2010 (CEST)

Liebe TeilnehmerInnen! 
Um diese Seite einheitlich zu gestalten (auch bezüglich der Vorjahre), schlage ich vor die Nachnamen
der Gruppenmitglieder in Klammer neben der Gruppe anzugeben, 
z.B.: Gruppe XX (Maier, Müller, Mustermann). 
-- [[Gschwandtner, Theresia|Theresia Gschwandtner]] 10:34, 08 October 2010 (CEST)

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06

2010-11-04T12:24:47Z

UE-InfoVis1011 0402530:

''Gruppenseite zur Übung [[Teaching:TUW_-_UE_InfoVis_WS_2010/11 | Infovis]]''

== Gruppenmitglieder ==

*[[User:UE-InfoVis1011_0051804 | Fikar, Peter]]
*[[User:UE-InfoVis1011_0325435 | Posset, Jorit]]
*[[User:UE-InfoVis1011_0402530 | Nezveda, Matej]]

== Aufgaben ==
*[[Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 0|Aufgabe 0]]
**''Referenz : '' [[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws10/infovis_ue_aufgabe0.html Angabe 0]]
*[[Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 1|Aufgabe 1]]
**''Referenz : '' [[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws10/infovis_ue_aufgabe1.html Angabe 1]]
*[[Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 2|Aufgabe 2]]
**''Referenz : '' [[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws10/infovis_ue_aufgabe2.html Angabe 2]]
*[[Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06 - Aufgabe 3|Aufgabe 3]]
**''Referenz : '' [[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws10/infovis_ue_aufgabe3.html Angabe 3]]

User:UE-InfoVis1011 0402530

2010-10-25T15:17:02Z

UE-InfoVis1011 0402530:

[[Image:InfoVis 2010 0402530.jpg|alt=Matej Nezveda|120px]]

== Profile ==
*'''Name:''' Matej Nezveda
*'''Location:''' Amstetten, Lower Austria
*'''Contact:''' e0402530 (at) student.tuwien.ac.at

== Course ==
*[http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2010/11 InfoVis Wiki]
*[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws10/index.html InfoVis LVA-Homepage]

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 07

2010-10-25T15:12:59Z

UE-InfoVis1011 0402530:

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 07

== Gruppenmitglieder ==
*[[User:UE-InfoVis1011_0402530 | Nezveda, Matej]]

== Aufgaben ==
*[[Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 07 - Aufgabe 0|Aufgabe 0]]
*[[Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 07 - Aufgabe 1|Aufgabe 1]]
*[[Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 07 - Aufgabe 2|Aufgabe 2]]
*[[Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 07 - Aufgabe 3|Aufgabe 3]]

Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 07

2010-10-25T15:07:43Z

UE-InfoVis1011 0402530: New page: == Gruppenmitglieder == * Nezveda, Matej

== Gruppenmitglieder ==
*[[User:UE-InfoVis1011_0402530 | Nezveda, Matej]]

Teaching:TUW - UE InfoVis WS 2010/11

2010-10-25T15:05:32Z

UE-InfoVis1011 0402530:

[[Image:Aigner03infovis ue.gif]] <big>WS 2010/11</big>

'''LVA Nr:''' 188.308 ([https://tiss.tuwien.ac.at/course/courseDetails.xhtml?courseNr=188308&semester=2010W TISS Seite])

'''LVA Homepage:''' http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws10/index.html

'''Leitung:''' [[Aigner, Wolfgang|Wolfgang Aigner]] [aigner (at) ifs.tuwien.ac.at] 
:: [[Gschwandtner, Theresia|Theresia Gschwandtner]] [gschwandtner (at) ifs.tuwien.ac.at] 

== Gruppen ==

*[[Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 01|Gruppe 01 (Emrich, Schneider, ???)]]
*[[Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 02|Gruppe 02 (Kraxner, ???, ???)]]
*[[Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 03|Gruppe 03 (Leichtfried, Chwistek, ???)]]
*[[Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 04|Gruppe 04 (Kastner, ???, ???)]]
*[[Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 05|Gruppe 05 (Alili, Bachhuber, Marschik)]]
*[[Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 06|Gruppe 06 (Fikar, Posset, ???)]]
*[[Teaching:TUW - UE InfoVis WS 2010/11 - Gruppe 07|Gruppe 07 (Nezveda, ???, ???)]]

== News / Bemerkungen ==

Liebe TeilnehmerInnen! 
Um diese Seite einheitlich zu gestalten (auch bezüglich der Vorjahre), schlage ich vor die Nachnamen
der Gruppenmitglieder in Klammer neben der Gruppe anzugeben, 
z.B.: Gruppe XX (Maier, Müller, Mustermann). 
-- [[Gschwandtner, Theresia|Theresia Gschwandtner]] 10:34, 08 October 2010 (CEST)

User:UE-InfoVis1011 0402530

2010-10-25T14:56:36Z

UE-InfoVis1011 0402530:

User:UE-InfoVis1011 0402530

2010-10-25T14:49:44Z

UE-InfoVis1011 0402530: New page: 120px

[[Image:InfoVis 2010 0402530.jpg|alt=Matej Nezveda|120px]]

File:InfoVis 2010 0402530.jpg

2010-10-25T14:43:45Z

UE-InfoVis1011 0402530: New page: == Summary == == Copyright status == == Source ==