<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Qgis on Visualizing.JP</title>
        <link>https://visualizing.jp/en/tags/qgis/</link>
        <description>Recent content in Qgis on Visualizing.JP</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en-US</language>
        <copyright>Yuichi Yazaki</copyright>
        <lastBuildDate>Thu, 27 Feb 2020 00:00:00 +0900</lastBuildDate><atom:link href="https://visualizing.jp/en/tags/qgis/index.xml" rel="self" type="application/rss+xml" /><item>
        <title>Classification in QGIS</title>
        <link>https://visualizing.jp/en/qgis-classification/</link>
        <pubDate>Thu, 27 Feb 2020 00:00:00 +0900</pubDate>
        
        <guid>https://visualizing.jp/en/qgis-classification/</guid>
        <description>&lt;img src="https://visualizing.jp/qgis-classification/images/qgis_jenks.png" alt="Featured image of post Classification in QGIS" /&gt;&lt;p&gt;This article introduces Classification in QGIS from a practical data visualization workflow perspective.&lt;/p&gt;
&lt;p&gt;The emphasis is on how the tool, format, or workflow fits into practical visualization work.&lt;/p&gt;
&lt;h2 id=&#34;practical-context&#34;&gt;Practical Context
&lt;/h2&gt;&lt;p&gt;A tool or format matters because it changes what can be produced, repeated, shared, or maintained. The important question is not only whether it works once, but whether it supports a reliable workflow with clear inputs and outputs.&lt;/p&gt;
&lt;h2 id=&#34;workflow-notes&#34;&gt;Workflow Notes
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;Check the data format and assumptions before adopting the workflow.&lt;/li&gt;
&lt;li&gt;Separate one-time setup issues from repeatable production steps.&lt;/li&gt;
&lt;li&gt;Document version, data source, and conversion settings when reproducibility matters.&lt;/li&gt;
&lt;li&gt;Prefer simple outputs first, then add interaction or styling after the data is correct.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary
&lt;/h2&gt;&lt;p&gt;Classification in QGIS is relevant as part of the broader craft of preparing, transforming, and publishing data. The value comes from understanding both the technical mechanism and the communication task it supports.&lt;/p&gt;</description>
        </item>
        <item>
        <title>Jenks Natural Breaks in Map Classification</title>
        <link>https://visualizing.jp/en/classification-jenks/</link>
        <pubDate>Thu, 27 Feb 2020 00:00:00 +0900</pubDate>
        
        <guid>https://visualizing.jp/en/classification-jenks/</guid>
        <description>&lt;img src="https://visualizing.jp/classification-jenks/images/qgis_jenks.png" alt="Featured image of post Jenks Natural Breaks in Map Classification" /&gt;&lt;p&gt;This article examines Jenks Natural Breaks in Map Classification 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;Jenks Natural Breaks in Map Classification 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>
        <item>
        <title>When fTools and GDALTools Are Missing in QGIS</title>
        <link>https://visualizing.jp/en/qgis-processing/</link>
        <pubDate>Sun, 23 Feb 2020 00:00:00 +0900</pubDate>
        
        <guid>https://visualizing.jp/en/qgis-processing/</guid>
        <description>&lt;img src="https://visualizing.jp/qgis-processing/images/qgis_processing.png" alt="Featured image of post When fTools and GDALTools Are Missing in QGIS" /&gt;&lt;p&gt;This article introduces When fTools and GDALTools Are Missing in QGIS from a practical data visualization workflow perspective.&lt;/p&gt;
&lt;p&gt;The emphasis is on how the tool, format, or workflow fits into practical visualization work.&lt;/p&gt;
&lt;h2 id=&#34;practical-context&#34;&gt;Practical Context
&lt;/h2&gt;&lt;p&gt;A tool or format matters because it changes what can be produced, repeated, shared, or maintained. The important question is not only whether it works once, but whether it supports a reliable workflow with clear inputs and outputs.&lt;/p&gt;
&lt;h2 id=&#34;workflow-notes&#34;&gt;Workflow Notes
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;Check the data format and assumptions before adopting the workflow.&lt;/li&gt;
&lt;li&gt;Separate one-time setup issues from repeatable production steps.&lt;/li&gt;
&lt;li&gt;Document version, data source, and conversion settings when reproducibility matters.&lt;/li&gt;
&lt;li&gt;Prefer simple outputs first, then add interaction or styling after the data is correct.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary
&lt;/h2&gt;&lt;p&gt;When fTools and GDALTools Are Missing in QGIS is relevant as part of the broader craft of preparing, transforming, and publishing data. The value comes from understanding both the technical mechanism and the communication task it supports.&lt;/p&gt;</description>
        </item>
        <item>
        <title>Generating TopoJSON from a Shapefile</title>
        <link>https://visualizing.jp/en/shapefile-to-topojson/</link>
        <pubDate>Sun, 18 May 2014 00:00:00 +0900</pubDate>
        
        <guid>https://visualizing.jp/en/shapefile-to-topojson/</guid>
        <description>&lt;img src="https://visualizing.jp/shapefile-to-topojson/images/fi_Shape2Topo.png" alt="Featured image of post Generating TopoJSON from a Shapefile" /&gt;&lt;p&gt;This article introduces Generating TopoJSON from a Shapefile from a practical data visualization workflow perspective.&lt;/p&gt;
&lt;p&gt;The emphasis is on how the tool, format, or workflow fits into practical visualization work.&lt;/p&gt;
&lt;h2 id=&#34;practical-context&#34;&gt;Practical Context
&lt;/h2&gt;&lt;p&gt;A tool or format matters because it changes what can be produced, repeated, shared, or maintained. The important question is not only whether it works once, but whether it supports a reliable workflow with clear inputs and outputs.&lt;/p&gt;
&lt;h2 id=&#34;workflow-notes&#34;&gt;Workflow Notes
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;Check the data format and assumptions before adopting the workflow.&lt;/li&gt;
&lt;li&gt;Separate one-time setup issues from repeatable production steps.&lt;/li&gt;
&lt;li&gt;Document version, data source, and conversion settings when reproducibility matters.&lt;/li&gt;
&lt;li&gt;Prefer simple outputs first, then add interaction or styling after the data is correct.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary
&lt;/h2&gt;&lt;p&gt;Generating TopoJSON from a Shapefile is relevant as part of the broader craft of preparing, transforming, and publishing data. The value comes from understanding both the technical mechanism and the communication task it supports.&lt;/p&gt;</description>
        </item>
        
    </channel>
</rss>
