<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Ggplot2 on The Final Artefact</title><link>https://www.thefinalartefact.xyz/tags/ggplot2/</link><description>Recent content in Ggplot2 on The Final Artefact</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Sat, 28 Mar 2015 00:00:00 +0000</lastBuildDate><atom:link href="https://www.thefinalartefact.xyz/tags/ggplot2/index.xml" rel="self" type="application/rss+xml"/><item><title>Managing rows in the ggplot legend</title><link>https://www.thefinalartefact.xyz/post/managing-rows-in-the-ggplot-legend/</link><pubDate>Sat, 28 Mar 2015 00:00:00 +0000</pubDate><guid>https://www.thefinalartefact.xyz/post/managing-rows-in-the-ggplot-legend/</guid><description>&lt;p&gt;After developing the Shiny App sourcing live labour market data from NOMIS. I wanted to accommodate a convenient way of managing rows in the legend. In particular, I wanted to account for the situation where end-user may select a number of geographies that will only conveniently fit into two or more rows. After transposing the data to long format, guessing the number of elements in the legend is relatively simple as it will correspond to the number of unique geographies passed via the subset command.&lt;/p&gt;</description></item></channel></rss>