Graphical Representation: Maps (Just the Quotes)

"Two important characteristics of maps should be noticed. A map is not the territory it represents, but, if correct, it has a similar structure to the territory, which accounts for its usefulness. If the map could be ideally correct, it would include, in a reduced scale, the map of the map; the map of the map, of the map [...]" (Alfred Korzybski, "Science and Sanity: An Introduction to Non-Aristotelian Systems and General Semantics", 1933)

"The first of the principles governing symbols is this: The symbol is NOT the thing symbolized; the word is NOT the thing; the map is NOT the territory it stands for." (Samuel I Hayakawa, "Language in Thought and Action", 1949)

"A fundamental value in the scientific outlook is concern with the best available map of reality. The scientist will always seek a description of events which enables him to predict most by assuming least. He thus already prefers a particular form of behavior. If moralities are systems of preferences, here is at least one point at which science cannot be said to be completely without preferences. Science prefers good maps." (Anatol Rapoport, "Science and the goals of man: a study in semantic orientation", 1950)

"No map contains all the information about the territory it represents. [...] Furthermore, the scale of the map makes a big difference. The smaller the scale the less features will be shown." (Anatol Rapoport, "Science and the goals of man: a study in semantic orientation", 1950)

"Good design looks right. It is simple (clear and uncomplicated). Good design is also elegant, and does not look contrived. A map should be aesthetically pleasing, thought provoking, and communicative."  (Arthur H Robinson, "Elements of Cartography", 1953)

"The design process involves a series of operations. In map design, it is convenient to break this sequence into three stages. In the first stage, you draw heavily on imagination and creativity. You think of various graphic possibilities, consider alternative ways." (Arthur H Robinson, "Elements of Cartography", 1953)

"The types of graphics used in operating a business fall into three main categories: diagrams, maps, and charts. Diagrams, such as organization diagrams, flow diagrams, and networks, are usually intended to graphically portray how an activity should be, or is being, accomplished, and who is responsible for that accomplishment. Maps such as route maps, location maps, and density maps, illustrate where an activity is, or should be, taking place, and what exists there. [...] Charts such as line charts, column charts, and surface charts, are normally constructed to show the businessman how much and when. Charts have the ability to graphically display the past, present, and anticipated future of an activity. They can be plotted so as to indicate the current direction that is being followed in relationship to what should be followed. They can indicate problems and potential problems, hopefully in time for constructive corrective action to be taken." (Robert D Carlsen & Donald L Vest, "Encyclopedia of Business Charts", 1977)

"Maps containing marks that indicate a variety of features at specific locations are easy to produce and often revealing for the reader. You can use dots, numbers, and shapes, with or without keys. The basic map must always be simple and devoid of unnecessary detail. There should be no ambiguity about what happens where." (Bruce Robertson, "How to Draw Charts & Diagrams", 1988)

"Maps used as charts do not need fine cartographic detail. Their purpose is to express ideas, explain relationships, or store data for consultation. Keep your maps simple. Edit out irrelevant detail. Without distortion, try to present the facts as the main feature of your map, which should serve only as a springboard for the idea you're trying to put across." (Bruce Robertson, "How to Draw Charts & Diagrams", 1988)

"The prevailing style of management must undergo transformation. A system cannot understand itself. The transformation requires a view from outside. The aim [...] is to provide an outside view - a lens - that I call a system of profound knowledge. It provides a map of theory by which to understand the organizations that we work in." (Dr. W. Edwards Deming, "The New Economics for Industry, Government, Education", 1994)

"Maps, due to their melding of scientific and artistic approaches, always involve complex interaction between the denotative and the connotative meanings of signs they contain." (Alan MacEachren, "How Maps Work: Representation, Visualization, and Design", 1995)

"The fact that map is a fuzzy and radial, rather than a precisely defined, category is important because what a viewer interprets a display to be will influence her expectations about the display and how she interacts with it." (Alan MacEachren, "How Maps Work: Representation, Visualization, and Design", 1995)

"The representational nature of maps, however, is often ignored - what we see when looking at a map is not the word, but an abstract representation that we find convenient to use in place of the world. When we build these abstract representations we are not revealing knowledge as much as are creating it." (Alan MacEachren, "How Maps Work: Representation, Visualization, and Design", 1995)

"Understanding how maps work and why maps work (or do not work) as representations in their own right and as prompts to further representations, and what it means for a map to work, are critical issues as we embark on a visual information age." (Alan MacEachren, "How Maps Work: Representation, Visualization, and Design", 1995)

"Eliciting and mapping the participant's mental models, while necessary, is far from sufficient [...] the result of the elicitation and mapping process is never more than a set of causal attributions, initial hypotheses about the structure of a system, which must then be tested. Simulation is the only practical way to test these models. The complexity of the cognitive maps produced in an elicitation workshop vastly exceeds our capacity to understand their implications. Qualitative maps are simply too ambiguous and too difficult to simulate mentally to provide much useful information on the adequacy of the model structure or guidance about the future development of the system or the effects of policies." (John D Sterman, "Learning in and about complex systems", Systems Thinking Vol. 3 2003)

"A road plan can show the exact location, elevation, and dimensions of any part of the structure. The map corresponds to the structure, but it's not the same as the structure. Software, on the other hand, is just a codification of the behaviors that the programmers and users want to take place. The map is the same as the structure. […] This means that software can only be described accurately at the level of individual instructions. […] A map or a blueprint for a piece of software must greatly simplify the representation in order to be comprehensible. But by doing so, it becomes inaccurate and ultimately incorrect. This is an important realization: any architecture, design, or diagram we create for software is essentially inadequate. If we represent every detail, then we're merely duplicating the software in another form, and we're wasting our time and effort." (George Stepanek, "Software Project Secrets: Why Software Projects Fail", 2005) 

"A map does not just chart, it unlocks and formulates meaning; it forms bridges between here and there, between disparate ideas that we did not know were previously connected." (Reif Larsen, "The Selected Works of T S Spivet", 2009)

"Graphics, charts, and maps aren’t just tools to be seen, but to be read and scrutinized. The first goal of an infographic is not to be beautiful just for the sake of eye appeal, but, above all, to be understandable first, and beautiful after that; or to be beautiful thanks to its exquisite functionality." (Alberto Cairo, "The Functional Art", 2011)

"The utility of mapping as a form of data visualization isn’t in accuracy or precision, but rather the map’s capacity to help us make and organize hypothesis about the world of ideas and things. hypothesis-making through the map isn’t strictly inductive or deductive, although it can use the thought process of either, but it is often based on general observations." (Winifred E Newman, "Data Visualization for Design Thinking: Applied Mapping", 2017)

"Maps also have the disadvantage that they consume the most powerful encoding channels in the visualization toolbox - position and size - on an aspect that is held constant. This leaves less effective encoding channels like color for showing the dimension of interest." (Danyel Fisher & Miriah Meyer, "Making Data Visual", 2018)

More quotes on 'Maps' on "The Web of Knowledge".