<div dir="ltr"><div dir="ltr">One solution would be to have a field that calculates percentage of funds distributed. That way the choropleth uses the same range for the percentages but they update each week. You could then have a scale bar that displays the overall percentage of funds distributed, and show what percentage is distributed to each county, sort of how they do with fundraisers.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Dec 3, 2020 at 12:00 PM <<a href="mailto:gis_info-request@omls.oregon.gov">gis_info-request@omls.oregon.gov</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send gis_info mailing list submissions to<br>
<a href="mailto:gis_info@omls.oregon.gov" target="_blank">gis_info@omls.oregon.gov</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://omls.oregon.gov/mailman/listinfo/gis_info" rel="noreferrer" target="_blank">https://omls.oregon.gov/mailman/listinfo/gis_info</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:gis_info-request@omls.oregon.gov" target="_blank">gis_info-request@omls.oregon.gov</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:gis_info-owner@omls.oregon.gov" target="_blank">gis_info-owner@omls.oregon.gov</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of gis_info digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: FW: Looking for advice on making an updating choropleth<br>
(Darrell Fuhriman)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 3 Dec 2020 09:49:18 -0800<br>
From: Darrell Fuhriman <<a href="mailto:darrell@garnix.org" target="_blank">darrell@garnix.org</a>><br>
To: "=?utf-8?Q?gis=5Finfo=<a href="http://40omls.oregon.gov?=" rel="noreferrer" target="_blank">40omls.oregon.gov?=</a>"<br>
<<a href="mailto:gis_info@omls.oregon.gov" target="_blank">gis_info@omls.oregon.gov</a>>, SMITH Cy * DAS <<a href="mailto:Cy.SMITH@oregon.gov" target="_blank">Cy.SMITH@oregon.gov</a>><br>
Cc: JOHNSON Nathan * DCBS <<a href="mailto:Nathan.Johnson@oregon.gov" target="_blank">Nathan.Johnson@oregon.gov</a>>, VARGAS Antonio<br>
R * DCBS <<a href="mailto:Antonio.R.Vargas@oregon.gov" target="_blank">Antonio.R.Vargas@oregon.gov</a>><br>
Subject: Re: [gis_info] FW: Looking for advice on making an updating<br>
choropleth<br>
Message-ID: <ce87f62e-f518-4e8c-a923-2de34120d4bc@Spark><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I don?t think there are perfect solutions to this problem, just less bad ones. The reality is if you?re looking at an exponential growth situation, this is bound to happen. This was exactly the problem that led to the argument a few weeks back about Georgia and its COVID case maps changing the scale ? people thought they were being misled.<br>
<br>
With the surge in COVID cases, the NYT recently had to change the scale on its maps, and they had a big caveat to that effect when they did.<br>
<br>
I think that?s probably the least bad solution: update it the scale, but only occasionally. Make sure there?s a note?right next to the legend?that explains when and why the scale has changed. You could do it on an as-needed basis (but build yourself some headroom so it?s not happening weekly), or on a schedule, like quarterly or annually.<br>
<br>
It?s probably also helpful to use a system where the bins are consistent, like a linear scale, and you?re just changing the top end of the scale. In other words avoid Jenks, which could just compound the confusion if someone is looking back at past maps, IMO.<br>
<br>
Darrell<br>
On Dec 3, 2020, 09:29 -0800, SMITH Cy * DAS via gis_info <<a href="mailto:gis_info@omls.oregon.gov" target="_blank">gis_info@omls.oregon.gov</a>>, wrote:<br>
> Hi folks, we have a question about making good choropleth maps.? See below.<br>
><br>
> cy<br>
><br>
> <image001.png><br>
> Cy Smith, GISP<br>
> Enterprise Information Services<br>
> Data Governance and Transparency|Geospatial Enterprise Office<br>
> (503)378-6066, <a href="http://gis.oregon.gov" rel="noreferrer" target="_blank">http://gis.oregon.gov</a><br>
> ?Ensuring user-friendly, reliable and secure state technology systems that serve Oregonians.?<br>
><br>
><br>
> From: VARGAS Antonio R * DCBS <<a href="mailto:Antonio.R.Vargas@oregon.gov" target="_blank">Antonio.R.Vargas@oregon.gov</a>><br>
> Sent: Thursday, December 3, 2020 9:19 AM<br>
> To: SMITH Cy * DAS <<a href="mailto:Cy.SMITH@oregon.gov" target="_blank">Cy.SMITH@oregon.gov</a>>; TANNER Joshua * DAS <<a href="mailto:Joshua.TANNER@oregon.gov" target="_blank">Joshua.TANNER@oregon.gov</a>><br>
> Cc: JOHNSON Nathan * DCBS <<a href="mailto:Nathan.Johnson@oregon.gov" target="_blank">Nathan.Johnson@oregon.gov</a>><br>
> Subject: Looking for advice on making an updating choropleth<br>
><br>
> Hello,<br>
><br>
> I was wondering if you or someone on your team could provide some advice or a reference to best practices that might help with a project.<br>
><br>
> I?ve been asked to make a choropleth to illustrate dollar amounts going to each Oregon county to illustrate the progress of a program. The issue I?m having is that leadership would like to update the choropleth with new data each week, and I?m not sure how to choose the color scale to accommodate that.<br>
><br>
> By the end of its lifespan, the dollar amounts will be roughly an order of magnitude higher than at the start. So, when I choose a color scale with enough room at the high end to account for this in the future, basically every county in today?s map is assigned the lowest colors on the scale. One idea we had was to use a continuous color scale, though the colors still end up very similar.<br>
><br>
> On the other hand, if I were to update the color scale each time the data is updated, so that the data fills the whole color range each time, I expect that the colors assigned to each county wouldn?t change much over time. I guess the map would look wholly the same each data update, just with the legend assigning different dollar amounts to each color.<br>
><br>
> Any advice would be much appreciated.<br>
><br>
> Kind regards,<br>
><br>
> Antonio<br>
><br>
> -----<br>
><br>
> Antonio R. Vargas<br>
> Research Analyst<br>
> Division of Financial Regulation<br>
> Oregon Dept. of Consumer and Business Services<br>
> Office: 971.345.1106<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://omls.oregon.gov/pipermail/gis_info/attachments/20201203/4bb9bb29/attachment-0001.html" rel="noreferrer" target="_blank">https://omls.oregon.gov/pipermail/gis_info/attachments/20201203/4bb9bb29/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
gis_info mailing list<br>
<a href="mailto:gis_info@omls.oregon.gov" target="_blank">gis_info@omls.oregon.gov</a><br>
<a href="https://omls.oregon.gov/mailman/listinfo/gis_info" rel="noreferrer" target="_blank">https://omls.oregon.gov/mailman/listinfo/gis_info</a><br>
<br>
<br>
------------------------------<br>
<br>
End of gis_info Digest, Vol 214, Issue 3<br>
****************************************<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><p style="color:rgb(0,0,0);line-height:21px;font-style:italic;letter-spacing:1px;margin:0px;padding:0px"><font size="1" face="garamond, serif"><b>Twenty years from now you will be more disappointed by the things that you didn't do than by the ones you did do. So throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore. Dream. Discover.</b></font></p><h2 style="color:rgb(0,0,0);padding-top:0px;font-style:italic;letter-spacing:1px;line-height:10px"><font size="1" face="garamond, serif">- Mark Twain</font></h2></div></div></div>