In general, when somebody asks to download their TRC data as a CSV, it’s often the wrong thing. Once you’ve exported to a CSV, you lose out on the benefits of TRC, including our mobile canvassing apps. It also causes problems like a) how do you keep the downloaded CSV in current with changes; b) how do ensure data collected from that CSV gets uploaded back to your account? And usually there’s a better way to accomplish their scenario…
Note that while Android and iOS release versions are coordinated, not every version is released on both platforms. Generally, the Android builds are a bit more frequent, due to the higher market penetration and the fact that I personally test it in the field daily.
Here is a quick summary of the changes introduced with each release:
July 24, 2:30 AM: Full rollout. (Promoted from beta 1.4.2)
– Restored WebVew hosted in NavigationPage for login
– Added Log In menu command
– Updated to pre-release Xamarin.Forms (fixed issue #2393)
July 20, 11:22 PM: Full rollout. (Promoted from beta 1.4.1)
– New menu item to Share sheet with other users
– Added transfer token for Plug-ins button to bypass Web client login
– Switched to using App Center errors to report exception handling
– Switch to CarouselView from Andrei Misiukevich to work around Issue #2637
– Swiping in CarouselView will now wrap around
– Fixed delay in bringing up Settings panel
– Sort by distance is now updated live as position changes
July 7, 5:10 PM: Full rollout. (Promoted from beta 1.3.6)
– Pins now update color and opacity with incremental sync of voter records
Jul 3, 11:33 PM: Full rollout. (Promoted from beta 1.3.5)
– Manual upload to cloud now syncs changes in all sheets, not just current one.
– Alert now displayed when manual upload is unsuccessful.
– Fixed closest household button
– Handled phone number formatting overflow
– Streamlined conversion for string types
– Switched to chat keyboard for comments
– Refined voter detail panel
Jul 1, 9:05 PM: Full rollout. (Promoted from beta 1.3.3)
– App name change to Canvasser, with new adaptive icon
– Back button from main page navigates to parent sheet
– Added Plug-in button in SheetDetailPage
– Added detail section on VoterDetailPage for custom columns
– Preserves last visible region for each sheet
– Fixes missing map pins after extended load
– Updated logic for dimming households (visited or all members dimmed)
– Filtered voters now show as dimmed
– Added automatic sync after connectivity is restored or successful login
– Exception handling for failed OpenSheet (e.g. loss of permission)
– Fixed household member list opacity update
– Updated target URL for Learn More button in About
– Simplification of WebView-based login/logout, with new icon
Apr 24, 8:33 PM: Full rollout. (Promoted from beta 1.2.2)
– Reverting to CarouselPage to try to work around infrequent crash from ObjectDisposedException
– Maintains sorted order of household members when switching to voter detail page
Apr 19, 8:37 PM: Full rollout.
– Added SearchBar on List tab
– Added male and female avatars
– Fixed icon color update
– Sorts household members by age
– Possible fix for System.ObjectDisposedException
Apr 16, 8:30 AM: Full rollout.
– New buttons on voter detail page to dial phone number and send email
– Auto formatting of phone number (US only)
– Preferred virtual keyboard variants for phone number and email entry
– Upgrade to ProGuard 6.0.2 bytecode optimization
Apr 12, 4:57 PM: Full rollout. (Promoted from beta 1.1.3)
– Sync changes when app sent to background
– Scroll corresponding list item into view when pin selected on map
– Added completion percentage to the sheet Info page
– Fixed off-by-one bug when applying missed changes from other users
Apr 6, 10:20 PM: Full rollout.
– Rolled back to Xamarin Forms v220.127.116.110555 to work around WebView login bug
Apr 6, 3:28 PM: Full rollout.
– Clears WebView cache after logout so that previous user’s cookies aren’t still present
– Fixes performance issues with CarouselPage by switching to CarouselView, which supports UI virtualization
– Fixes a crash when location services goes unexpectedly offline
– Fixed crash caused on some configurations by CarouselView linker error
Apr 3, 3:02 PM: Full rollout. (Promoted from beta 1.1)
– Swipe left or right in household or voter detail panels for next & previous
– My location button in household detail view to quickly index to closest address
– New default sorting of households is by address
– Exception handling for failed DateTime parsing
While your individual vote is private, the aggregate vote of from your precinct (ie, neighborhood) is public. Campaigns often look at these precincts level results to answer questions like “How did the President do in my district?” and “How did this Initiative correlate with that candidate?”.
Merging precinct results from different races together to get these insights can be valuable – but only if the merge is done correctly! But what happens when you need to merge precinct results across different years and the precinct boundaries have changed? This is particularly significant when comparing precinct results from 2010 (before redistricting).
Here are several examples of precinct changes, going from an old (dotted blue line) to a new (solid red line) boundary.
- Rename – The precinct gets renamed from “A” to “X”, but covers the same area.
- Split – The precinct gets split into 2 smaller precincts. “A” gets split into “X” and “Y”
- Merge – Two smaller precincts get merged into a larger precinct. “A” and “B” get merged into “X”
- Combination – a combination of the above, representing a potentially arbitrarily complex transformation.
Your precinct may even have kept the same name but still significantly changed boundaries! A precinct from 2010 and another from 2018 could have the same name, but refer to totally different voters or neighborhoods.
So naively, if you just measure results from old and new precincts, you could get a complete mixup.
We measured how much WA state 2018 precincts had changed since 2018 (before redistricting). We call this the “decay rate” (see VRDB decay rate).
Each point on the chart below represents how “intact” a 2010 precinct is compared to the same precinct name in 2018. Precincts that are 100% intact are stable and haven’t changed – those results can be merged safely by name. This chart shows the portion of precincts that stayed the same vs. changed.
In fact, it turns out over a third of the precincts were totally intact from 2010. But half were completely different! Merging precincts from that half could give completely random results. What’s interesting is how clustered the results were: over 80% of precincts are either nearly unchanged or completely changed. So this is a highly localized phenomena: some areas may not see it at all (and hence not even realize it exists), whereas other areas may be heavily impacted.
What can we do?
The good news is that once we recognize this, we can actually do geo spatial comparisons to map the old precincts into the new ones. This creates a transform that lets us compare precinct results across different boundaries.
This article describes a best-practice for campaigns in using data for targeting voters and how you can achieve that with TRC.
The flow here is to start with getting initial public data from the county auditor, merge in microtargeting information, choose the targets, canvass, and iterate on the model.
Conceptually, we can think of data like a giant spreadsheet (CSV file). Each row is a voter, and columns are information about that voter. We’ll walk through the different phases with a small sample of 8 records, but TRC can help you do this with your entire district of 80,000 records
In previous posts we’ve looked at how our political system has become increasingly polarized, with our analysis of voting records showing that many self-styled moderates and independents are exhibiting much more partisan behavior when voting on the House or Senate floor. Having served for a few years now on a PDC open data advisory group, I realized that the same type of analysis could be done for organizational donors. Despite this being public data, not many people in Washington state know who the biggest political donors are, much less who they support.
So, are many of these “non-partisan” or “bi-partisan” organizational donors more partisan than they let on?
We can figure this out, and the methodology is pretty simple. The PDC Open Data Portal publishes all contributions to candidates and political committees back to 2008. For this first analysis, we looked at donations to partisan legislative and statewide candidates from businesses, unions and political action committees. The partisanship score for each donor is the difference in percentage of donations by party, giving each a range from 100 (exclusively Republican) to -100 (exclusively Democrat).
Most of the effort here is involved with the fuzzy matching algorithm, since candidates are very inconsistent on how they report the names of these organizations to the PDC. I use a trigram matching method, which isn’t perfect…but it does pretty well. Currently, contributions are grouped under the same donor if 80% or more of the trigrams match, but this is adjustable.
Here are the results:
If you visit WhipStat.com, you’ll now find an interactive and animated version of our organizational donor partisan analysis that allows you to filter by jurisdiction type and date range.
If you’d like to do further analysis, feel free to hit the Download button for a tab-delimited table of the charted data. Note that for now we don’t display or download the complete donor dataset, as that includes over 8,000 organizations.
A few things become apparent when reviewing the results:
- Some of the biggest legislative donors give heavily to candidates from both parties.
- About 6% more is given to Democrats than Republicans in legislative races, but that increases to 28% when looking at statewide races.
Up next: We’ll take a close look at hard money vs. soft money contributions.
“Gerrymandering” is manipulating political boundaries to favor a party. Wikipedia has an excellent summary and examples of the concept:
We’ll take a purely data-driven approach to measure if Washington State’s legislative districts are gerrymandered. While there is no absolute mathematical definition for gerrymandering – and therefore no definitive test – there are good objective statistical tests to measure anomalies.
This article focuses on applying these approaches to the legislative boundaries in WA state.
- First, we’ll look at the actual election results and see if there’s anything suspicious on the surface.
- Then we’ll run a standard statistical test – the McGhee test developed at the University of Chicago.
- And then we’ll run some generic algorithms to produce actually gerrymandered maps and compare to actual results.
To simplify nomenclature throughout this analysis, we’ll provide summary from the GOP perspective. The results can all be directly flipped to switch to the Democrat perspective. (IE, almost always, a x% GOP result means a (100-x)% Democrat result).
To simplify nomenclature, we’ll look at results from the GOP There’s no definitive criteria for creating district boundaries. Districts must be contiguous and similar in population. However, even these criteria are tricky. For example, a district boundary is set for 10 years, so as population grows and shifts over time, districts’ populations may shift. Districts can’t be simple shapes like hexagons because they may need to account for geographic boundaries or roads.
Here is a map of legislative boundaries. Since districts are population based (and not based on square-miles), one can see the districts are more concentrated in dense population centers.
 Looking at actual election results
WA has 49 legislative districts, and each district has 2 house members and 1 senate member.
As of the last statewide legislative election in Nov ‘16, in the senate, the GOP / Democrat split was 24-25. In the house, the GOP/ Democrats split was 48- 50. Roughly 90% of the 49 districts have all three members from the same party, indicating that individual districts carry a definitive partisan bias. But when tallying up all the legislative races, the overall split is almost evenly divided between parties in both the house and senate caucus.
Here’s how the GOP results in the legislative caucuses compares to their 2016 statewide results between a Democrat and Republican candidate. [ Source: WA Secretary of State] :
|GOP Candidate||Percent Vote|
|2016 Secretary of State (Wyman)||54.74%|
|2016 GOP House||48.98%|
|2016 GOP Senate||48.98%|
|2012, Governor (McKenna)||48.50%|
|2016 Auditor (Miloscia)||47.69%|
|2016 Public Lands (McLaughlin)||46.84%|
|2016 Governor (Bryant)||45.61%|
|2016 Lt. Governor (McClendon)||45.61%|
|2016 Insurance Commissioner (Schrock)||41.66%|
|2016 Senate (Vance)||40.99%|
|2016 President (Trump)||38.07%|
So clearly the Republicans have done a better job in the legislature than at most statewide races. Only Kim Wyman has outperformed the caucuses.
Some may suggest gerrymandering as the only way that the Republican caucuses could outperform statewide races. But a statewide race requires a single candidate to appeal to all 49 districts. Whereas legislative districts have a different candidate per district, allowing each candidate to vary to “fit the district”.
The real test of boundaries is to focus on a single partisan candidate and compare what percent of legislative districts they’d “win” to their statewide percentage. For example, Trump got 38.07% of the statewide vote. He also won 19 / 49 legislative districts, which is 38.78% – nearly the same ratio that he had statewide. That is a strong indicator that the districts aren’t gerrymandered.
We can see the results from other partisan statewide candidates:
|GOP Candidate||% of Statewide vote||% of Districts won|
|2016 Secretary of State (Wyman)||54.74%||78%|
|2016 Auditor (Miloscia)||47.69%||53%|
|2016 Public Lands (McLaughlin)||46.84%||47%|
|2016 Governor (Bryant)||45.61%||47%|
|2016 Lt. Governor (McClendon)||45.61%||45%|
|2016 President (Trump)||38.07%||39%|
|2016 Insurance Commissioner (Schrock)||41.66%||33%|
|2016 Senate (Vance)||40.99%||27%|
This analysis is looking at a broad range of races across a 15% spread. If the districts were actually gerrymandered, we’d expect that GOP candidates consistently performed better (or from the Democrat’s perspective, worse) in ‘% of district won’ than by ‘% of statewide vote’. But they do not. There’s an almost linear correlation between these results (R2=.83). Candidates that won more statewide votes also won more individual districts. Some GOP candidates benefit from the legislative boundaries, some performed worse.
 Bring out the math – running the statistical tests
The mathematical test we’ll run is the McGhee test, developed by Eric McGhee from University of Chicago. “Wired” explains “In that paper, they proposed a simple measure of partisan symmetry, called the “efficiency gap,” which tries to capture just what it is that gerrymandering does. At its core, gerrymandering is about wasting your opponent’s votes: packing them where they aren’t needed and spreading them where they can’t win.”
The test defines a “wasted vote” as any vote that does not directly contribute to a victory. If you win a district, any vote past 50% is considered wasted (it wasn’t necessary to win); if you lose a district, all of the votes were wasted. Practically, this means:
- Unless you win a district with exactly 50%+ 1 votes, there are at least some “wasted” votes.
- large blowout victories and 49.9% “close calls” produce the most “wasted” votes.
It then defines an “efficiency gap” as the (difference in each party’s wasted vote divided by the total vote). There is no definitive threshold for the efficiency gap that defines gerrymandering, but McGhee calculated the average efficiency gap in 2012 was 6%, and the egregious gerrymandering examples have are over 10%.
We apply the McGhee test on the 2016 presidential race across the legislative districts using election data from the Secretary of State:
|GOP Candidate||Percent Vote||Egap|
|2016 Secretary of State (Wyman)||54.74%||-16.3%|
|2016 Auditor (Miloscia)||47.69%||-6.3%|
|2016 Public Lands (McLaughlin)||46.84%||-2.1%|
|2016 Lt. Governor (McClendon)||45.61%||-2.2%|
|2016 Governor (Bryant)||45.61%||-4.5%|
|2016 Insurance Commissioner (Schrock)||41.66%||2.6%|
|2016 Senate (Vance)||40.99%||6.8%|
|2016 President (Trump)||38.07%||-3.7%|
The average gap from this spectrum of WA races is 3.2%, well below the national average. So our statistical test suggest that the districts are not gerrymandered.
 What would gerrymandering look like?
A final approach we take is to work backwards: we can deliberately produce gerrymandered maps and compare them to the actual map.
Here, we use a genetic algorithm, which starts with an initial configuration and then mutates it over a series of iterations as it “evolves” towards a goal. Mutations must preserve certain rules like contiguous boundaries. In this case, the goal was to maximize the number of GOP legislative victories, where victories where calculated using a Monte Carlo simulation driven by previous election turnout results from record poor GOP years. We used election results that initially gave GOP only 21 of the 49 districts – simulating a “worst case scenario” for GOP that put them near their historical lows. After series of genetic mutations, the final result was a map with 26 of 49 GOP wins – a pickup of 5 seats. The chart here shows the evolution progressing along the top.
However, we notice that the boundaries here definitely look suspicious. They’re clearly warped and have unnatural borders designed to carve out an advantage.
What this also shows is that truly gerrymandered results could produce a significant GOP advantage – even in a year with record poor Republican voter turnout.
- The legislative results are within proximity of the statewide governor results. And when measured across a wide range of candidates, there is no consistent advantage from district boundaries over a pure statewide vote.
- The house and senate GOP caucus performances do perform exceptionally well – particularly compared to the statewide performance of most GOP candidates. But this appears to be more due to the caucuses picking candidates to fit their district rather than gerrymandering.
- If we deliberately create theoretical gerrymandered districts via computer simulation, the potential GOP advantage would be significantly higher than what we witness.
In the absence of any contradicting evidence, we would conclude that WA state’s legislative boundaries are fairly drawn and not gerrymandered.
The special election for the 45th district senate seat is Nov 7th 2017, just a few days away. Here are some statistics based on the ballot returns reported by the Secretary of State.
The district is about 92,000 voters. Overall turnout as of Nov 4th is 21.3%. This is the highest turnout for an election district over 30,000 voters.
King County turnout overall is 15.4%. For comparison to other off-year legislative elections, Teri Hickel’s ’15 special election was 35%.
There has been significant new voter registration in the district since Andy Hill’s ’14 election victory. Here is a breakdown registration date:
|% of district||… registered since…|
|2%||Since ’17 Primary|
|6%||Within last year|
|21%||Since Nov ’14|
It’s a predominantly Democrat district. In ‘14 and ’16 house races, Democrat’s average victory in LD 45 has been around 58%. The district also voted over a 2:1 for Hillary Clinton over Donald Trump. Kim Wyman and Andy Hill are the only Republicans to have won this district.
The SOS does not report on the actual ballot results until election night, but we can use the Voter-Science party id database  to see how results are looking prior to election day.
Here is a heat map of Democrat turnout (left) vs. GOP turnout (right) in the 45th :
Of Voters identified as GOP, 28% have voted. Of voters identified as Democrats, 23% have voted. Of voters identified as Independents, only 14% have voted. So while the democrats may have raw volume of numbers, the GOP has driven higher turnout amongst their base.
 The Voter-Science party ID database has a party ID for 87% of the individuals in the 45th district and has accurately predicted all 45th races within 98.5% accuracy since 2015.