You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
The AP serves special elections alongside regular results, and typically the only indicators of specialness are in the text fields racetype, seatname, and description.
I've confirmed with AP Support that the 2018 general-election data will use these fields like so:
racetype will be "Special General"
seatname will be "a year … either the year the term for that seat began or when it was to end - we are still working that out"
2016 general special elections had similar content; for example, the special House races:
id,racetype,racetypeid,description,seatname
12979-polid-53401-state-HI-1,Special General,G,2014 - Unexpired Term,1-Unexpired Term
18848-polid-54203-state-KY-1,Special General,G,2014 - Unexpired Term,1-Unexpired Term
40288-polid-49768-state-PA-1,Special General,G,Replace Fattah,2-Unexpired Term
Obviously, we'd have to get further confirmations from the AP before we just assume string parsing like racetype ILIKE '%special%' AS is_special_election would produce an accurate new column. But I think that it'd be a valuable addition to the schema, surfacing/structuring a meaningful piece of information that is useful in data pipelines and graphics, but isn't explicitly structured by the AP.
The Elex CSV schema already has an is_ballot_measure column, which is an analogous "calculated field." This seems to suggest that an is_special_election flag would fit as well.
The text was updated successfully, but these errors were encountered:
For the two 2018 US Senate races (officeid=S) in question), in MN and MS, the racetype will NOT be Special General as we do need to set the national flag/needs to be figured into the national trend table, but there will be differentiated by a seatname which depicts the starting year of the term (seatname will be 2014 for both races). The “regular” MN and MS US Senate races will not have a seatname.
So, racetype ILIKE '%special%' AS is_special_election isn't even going to do the trick for November 2018, much less into the future. Good to know, but frustrating!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The AP serves special elections alongside regular results, and typically the only indicators of specialness are in the text fields
racetype
,seatname
, anddescription
.I've confirmed with AP Support that the 2018 general-election data will use these fields like so:
racetype
will be"Special General"
seatname
will be "a year … either the year the term for that seat began or when it was to end - we are still working that out"2016 general special elections had similar content; for example, the special House races:
Obviously, we'd have to get further confirmations from the AP before we just assume string parsing like
racetype ILIKE '%special%' AS is_special_election
would produce an accurate new column. But I think that it'd be a valuable addition to the schema, surfacing/structuring a meaningful piece of information that is useful in data pipelines and graphics, but isn't explicitly structured by the AP.The Elex CSV schema already has an
is_ballot_measure
column, which is an analogous "calculated field." This seems to suggest that anis_special_election
flag would fit as well.The text was updated successfully, but these errors were encountered: