Proposed features/polling station
|Status:||Draft (under way)|
|Proposed by:||Harry Wood|
|Applies to:||node area|
|Definition:||A place where you can vote in government elections|
A place where you can vote in government elections
Important information. The government should provide it of course, but we should also have it tagged somehow.
Polling stations are only valid for a particular election, although their location may be relatively constant in reality.
Note that amenity=polling_station has been used, however there is a problem with this because a building will typically have some other primary purpose e.g. amenity=community_centre. polling_station=yes was suggested as a better tag, following advice from James Rutter (Surrey Heath Borough Council) I am proposing polling_station=year. For Local Authorities, "polling stations are only 'valid' for a particular election" and "can differ between local and gen elections...often stations may be temporary eg a carpark." example photo of temporary polling station
Mapping a polling station
Tag the primary purpose of the building, then add polling_station=2010 to indicate that it also functions as a polling station for this current election. If the building has no other primary purpose, then add the tag amenity=polling_station too.
Changing locations over time
In theory polling stations change location from one election to another, but in practice they stay in the same place quite a lot.
Polling stations locations should only be kept in the database if they are expected to be used in a forthcoming election. What this means is ideally we map polling stations of a forthcoming election. If we don't know them (e.g. when an election is 5 years away) then it's fine to map locations as they were used in the last election, since we can reasonably expect most of these to stay in the same place. Any polling station location which we know to no longer be in use for forthcoming elections, should be removed (or moved to its new location) Obviously in the run up to an election we would expect to know more, and to be able to map these things more accurately. Putting the year as the tag value will help us keep track of this process.
The result will hopefully be a logical usable set of "current" polling station locations, without any overly-complicated attempt to map historical 4th dimensional data.
Propose we use something like election=local and election=general ?
polling_station:ref=nnn - polling station reference number (ref is too general and may already be used on the same object for another purpose)
A relation could also be used to define the area covered by a polling station (a test case is available in Orange, France) :
- polling_station : node or way of the polling station itself
- outer : ways defining the area covered
|Used on these elements|
|Tools for this tag|
In France, the polling stations are rather stable data : they are written on the polling card (carte d'électeur), so they are valid for at least several years and several pollings. So, for us, I think amenity=polling_station is better than polling_station=YEAR. Gall 14:21, 11 December 2011 (UTC) Moreover, there are sometimes big buildings (like sport centers) which shelter several polling stations. So, in this case, each polling station should be a node inside the building, roughly centered on the ballot box. Gall 14:21, 11 December 2011 (UTC)
You're right, in France polling station do not change (its exeption when it change), but also there is a polling station identifier (a number related to the city), perhaps can we add a ref=1 for example and also an indicator to the city where the polling_station is attached... Something like :
- polling_station:city=city name
--15:48, 11 December 2011 (UTC)Padorange 15:48, 11 December 2011 (UTC)
- Well they don't change much in the UK either, but I guess the point was that they change location enough that it's needs re-checking for each election (if we're aiming for a usefully accurate mappable dataset), and the year tagging scheme would allow us to do that. I realised there was an incomplete sentence above. I think I meant to write "If the building has no other primary purpose, then add the tag amenity=polling_station too." (so I've added that now) Obviously that applies too if the node has no other primary purpose, if you're mapping the node inside the building. I wasn't anticipating that level of hyper detail. Certainly there's usually three or four desks inside a community centre, which might be mapped as separate polling stations I suppose.... although the layout of these desks probably changes quite a lot -- Harry Wood (talk) 11:00, 24 September 2013 (UTC)
In Germany a polling station ("Wahllokal") has a number (Wahlkreis-Nummer), which can be tagged as ref=101. I recommend to combine it with address keys add:city=* etc. . Mehrere Wahlkreise in einem Gebäude können mit Semikolon getrennt werden ( ref=101;102;103).
- polling_station=yes (to define a voctation place)
- polling_station:zone=* (electoral zone. It has the formact SS-XXXX, where SS is the id number of the state, and XXXX is the id number of electoral zone. The list of electoral zone can be found in .
- polling_station:sections=* The id sections of the ballot boxes instaled in the polling station. One or more values separated by commas.
- polling_station:voters=* Number of voters in the polling station
- polling_station:update=yyyy/mm/dd (last verification date of above data)