<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>ネットワーク on Visualizing.JP</title>
        <link>https://visualizing.jp/en/tags/%E3%83%8D%E3%83%83%E3%83%88%E3%83%AF%E3%83%BC%E3%82%AF/</link>
        <description>Recent content in ネットワーク on Visualizing.JP</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en-US</language>
        <copyright>Yuichi Yazaki</copyright>
        <lastBuildDate>Mon, 03 Aug 2020 00:00:00 +0900</lastBuildDate><atom:link href="https://visualizing.jp/en/tags/%E3%83%8D%E3%83%83%E3%83%88%E3%83%AF%E3%83%BC%E3%82%AF/index.xml" rel="self" type="application/rss+xml" /><item>
        <title>Examples of Alluvial Diagrams</title>
        <link>https://visualizing.jp/en/alluvial-diagrams-example/</link>
        <pubDate>Mon, 03 Aug 2020 00:00:00 +0900</pubDate>
        
        <guid>https://visualizing.jp/en/alluvial-diagrams-example/</guid>
        <description>&lt;img src="https://visualizing.jp/alluvial-diagrams-example/images/image-24.png" alt="Featured image of post Examples of Alluvial Diagrams" /&gt;&lt;p&gt;This article collects examples related to Examples of Alluvial Diagrams. It is useful for comparing how the same visualization idea changes across topics, datasets, and publication contexts.&lt;/p&gt;
&lt;p&gt;The examples show how a visualization technique can be adapted to different subjects and audiences.&lt;/p&gt;
&lt;h2 id=&#34;what-to-look-for&#34;&gt;What to Look For
&lt;/h2&gt;&lt;p&gt;When reading these examples, compare the data structure, the visual encoding, and the intended reading task. Similar chart types can communicate very different messages depending on annotation, ordering, scale, and color.&lt;/p&gt;
&lt;h2 id=&#34;design-notes&#34;&gt;Design Notes
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;Compare the examples by asking what task each design supports.&lt;/li&gt;
&lt;li&gt;Look for differences in scale, annotation, color, and layout.&lt;/li&gt;
&lt;li&gt;Notice whether the design emphasizes overview, comparison, storytelling, or exploration.&lt;/li&gt;
&lt;li&gt;Use the examples as references, not as fixed templates.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary
&lt;/h2&gt;&lt;p&gt;These examples are best read as a design reference. They show not only what the technique can express, but also where layout, labeling, and editorial framing determine whether the result is readable.&lt;/p&gt;</description>
        </item>
        <item>
        <title>Examples of Sankey Diagrams</title>
        <link>https://visualizing.jp/en/sankey-diagram-example/</link>
        <pubDate>Sun, 02 Aug 2020 00:00:00 +0900</pubDate>
        
        <guid>https://visualizing.jp/en/sankey-diagram-example/</guid>
        <description>&lt;img src="https://visualizing.jp/sankey-diagram-example/images/image-13.png" alt="Featured image of post Examples of Sankey Diagrams" /&gt;&lt;p&gt;This article collects examples related to Examples of Sankey Diagrams. It is useful for comparing how the same visualization idea changes across topics, datasets, and publication contexts.&lt;/p&gt;
&lt;p&gt;The examples show how a visualization technique can be adapted to different subjects and audiences.&lt;/p&gt;
&lt;h2 id=&#34;what-to-look-for&#34;&gt;What to Look For
&lt;/h2&gt;&lt;p&gt;When reading these examples, compare the data structure, the visual encoding, and the intended reading task. Similar chart types can communicate very different messages depending on annotation, ordering, scale, and color.&lt;/p&gt;
&lt;h2 id=&#34;design-notes&#34;&gt;Design Notes
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;Compare the examples by asking what task each design supports.&lt;/li&gt;
&lt;li&gt;Look for differences in scale, annotation, color, and layout.&lt;/li&gt;
&lt;li&gt;Notice whether the design emphasizes overview, comparison, storytelling, or exploration.&lt;/li&gt;
&lt;li&gt;Use the examples as references, not as fixed templates.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary
&lt;/h2&gt;&lt;p&gt;These examples are best read as a design reference. They show not only what the technique can express, but also where layout, labeling, and editorial framing determine whether the result is readable.&lt;/p&gt;</description>
        </item>
        <item>
        <title>Sankey Diagram</title>
        <link>https://visualizing.jp/en/sankey-diagram/</link>
        <pubDate>Sun, 02 Aug 2020 00:00:00 +0900</pubDate>
        
        <guid>https://visualizing.jp/en/sankey-diagram/</guid>
        <description>&lt;img src="https://visualizing.jp/sankey-diagram/images/image-13.png" alt="Featured image of post Sankey Diagram" /&gt;&lt;p&gt;A Sankey diagram represents flows between nodes with bands whose widths are proportional to quantity.&lt;/p&gt;
&lt;p&gt;The focus is on how the visual form supports comparison, pattern recognition, and explanation.&lt;/p&gt;
&lt;h2 id=&#34;how-to-read-it&#34;&gt;How to Read It
&lt;/h2&gt;&lt;p&gt;Start by identifying the data units, the visual encodings, and the direction of comparison. Then read the overall pattern before moving to individual values. This helps separate the main structure from small local variation.&lt;/p&gt;
&lt;h2 id=&#34;when-to-use-it&#34;&gt;When to Use It
&lt;/h2&gt;&lt;p&gt;Use this approach when the audience needs to understand a relationship that would be hard to see in a table. It is most effective when the chart type matches the question: comparison, distribution, hierarchy, flow, geography, or change over time.&lt;/p&gt;
&lt;h2 id=&#34;design-notes&#34;&gt;Design Notes
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;Clarify what each visual channel represents before interpreting the graphic.&lt;/li&gt;
&lt;li&gt;Use labels, legends, and units so readers can distinguish pattern from measurement.&lt;/li&gt;
&lt;li&gt;Choose the method only when its visual structure matches the analytical question.&lt;/li&gt;
&lt;li&gt;Avoid unnecessary decoration that makes comparison harder.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary
&lt;/h2&gt;&lt;p&gt;Sankey Diagram is useful when its structure fits the data and the reading task. As with any visualization method, the key is to make the encoding explicit and avoid asking the form to do more than it can support.&lt;/p&gt;</description>
        </item>
        <item>
        <title>Visualizing Friend Connections on Facebook</title>
        <link>https://visualizing.jp/en/friendship-facebook/</link>
        <pubDate>Tue, 19 May 2020 00:00:00 +0900</pubDate>
        
        <guid>https://visualizing.jp/en/friendship-facebook/</guid>
        <description>&lt;img src="https://visualizing.jp/friendship-facebook/images/163413_479288597199_8388607_n.png" alt="Featured image of post Visualizing Friend Connections on Facebook" /&gt;&lt;p&gt;This article examines Visualizing Friend Connections on Facebook as a case study in data visualization, information design, or visual culture.&lt;/p&gt;
&lt;p&gt;The article is useful as a case study in how data, design choices, and context shape interpretation.&lt;/p&gt;
&lt;h2 id=&#34;what-it-shows&#34;&gt;What It Shows
&lt;/h2&gt;&lt;p&gt;The main point is not only the finished visual form, but also the reasoning behind it: what was selected, emphasized, simplified, or compared. Those decisions determine what readers can notice.&lt;/p&gt;
&lt;h2 id=&#34;design-and-context-notes&#34;&gt;Design and Context Notes
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;Identify the data, audience, and communication goal behind the work.&lt;/li&gt;
&lt;li&gt;Notice how visual form, annotation, and context shape interpretation.&lt;/li&gt;
&lt;li&gt;Distinguish the core idea from details that belong to a specific medium or moment.&lt;/li&gt;
&lt;li&gt;Treat the example as a prompt for design judgment rather than a universal rule.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary
&lt;/h2&gt;&lt;p&gt;Visualizing Friend Connections on Facebook shows how visualization works as both analysis and communication. Reading it carefully means looking at the data, the visual encoding, and the cultural or practical context around the work.&lt;/p&gt;</description>
        </item>
        
    </channel>
</rss>
