This document describes XML messages that are used for local council election events that use the first-past-the-post (FPTP) system. The nomination and results coverage is focused on each party standing and the seats they have won out of the seats being offered up for election, at the entire council level rather than individual wards. The messages do not supply individual named nominations.
For local council elections, the following types of data are available in XML:
All message types are specified by a set of W3C schema files, downloadable from here.
Councils participating in an election belong to a single given type from the following set:
The type of each council is set accordingly for the election, such that a mixture of all types maybe in use
Also, a council may be offering all, half or a third of its seats for election. The results messages provide the total and offered seats in these cases. If the council is subject to a boundary change this will be indicated, and a different number of seats will be offered than before.
When the PA is conducting local election tests, the same election entity is used as on the night. Therefore the paIdattributes for the election id, in all the XML, will be the same as on the night. The same can be said for council and party ids.
However local election test files will always start with a “Local_Test_” prefix, whilst live data files simply have a “Local_” prefix.
To prepare your systems for elections, first use the nominations files from our FTP server. There is a nominations file for each council, giving the details of the council, and all the parties standing for election.
Nominations files follow the following format:
If the election is data is from a test the filename format is:
Occasionally corrections to nominations come to light before or during the results operation. In such a case, a revised nominations file for the affected constituency will automatically be made available, with the same filename.
The nominations for a council are provided in a message with an LocalElectionNominations root element, adhering to the LocalNominations.xsd
Here is an example of a nominations message for Amber Valley from the 2015 Council elections, with the filename Local_nominations_Amber_Valley.xml:
Notes on the above example:
Results messages are sent as soon as the number of seats won by each nominated party is known, and summarise the structure of the council after these changes. Most importantly they reveal which party has held or gained control.
Live results messages for local councils follow the following filename pattern:
Whereas test messages follow the pattern:
The revision number in the filename is incremented whenever a correction is made to the result, and starts from 1.
A result for a council uses a LocalElectionResult root element and adheres to the LocalResult.xsd
Here is an example of a result message from the 2015 Councils Election, using the filenameLocal_result_Amber_Valley_1.xml:
The results message repeats some of the information seen in the nominations message, but uses a new structure to convey the seats won by each party and new structure of the council. If there have been corrections to the result, the revision attribute in the root element will be incremented.
Notes on this message:
At regular intervals a State of parties (SOP) message is generated, that summarises the council control gained, held and lost by the parties and the changes in seat totals. Each SOP message is generated for the number of results in so far, which is indicated by the SOP filename and within the message.
The SOP message may be generated for all councils (National), or just for councils in England, Scotland or Wales. The use of these types of regional SOP depends on the councils taking part in the election.
SOP messages for all councils follow the following filename pattern, where the ‘results total’ is the number of results so far, for all councils or a region:
Regional SOP messages follow a similar pattern, with the region of England, Scotland or Wales added e.g.
Whereas for a test the file format will be:
A SOP message uses the LocalStateOfParties root element and adheres to the LocalStateOfParties.xsd
Here is an example of a SOP message from the 2015 local council election, using the filename Local_SOP_279.xml:
Notes on this message:
The XML message feed contains an enhancement which is not available in the other feed formats, namely unique ID numbers for each election, council and party. These can be relied upon to match data from nominations messages to results messages, and to uniquely identify different entities within a message. They cannot be used to match entities between elections though. Elections, councils and parties will have different PA ids between different elections.
However where the same parties are standing across different elections they are likely to have the same full name and abbreviation. Likewise, councils will have the same names unless changes have been necessary.