Represent's federal, provincial and territorial boundary sets originally had names like 'Federal electoral districts'. However, these jurisdictions modify their boundaries following formal processes at regular intervals. In order to have permanent and unambiguous names, Represent is transitioning towards adding suffixes like (2013 Representation Order), (Representation Act, 2005), (2015 Redistribution), etc. to the name.
The suffixes are based on each jurisdiction's most common way of referring to the boundary modification.
The boundary sets aren't being renamed immediately to avoid disrupting API users who have hardcoded the current names.
Instead, whenever the boundaries change, we take that opportunity to add suffixes to all boundary
sets for that jurisdiction.
Steps:
[ ] Open the old set's definition.py file, like boundaries/ocd-division/country-ca/2013/definition.py
[ ] The appropriate suffix to the name is staged as a comment in the file
For some, we only found long references to commissions like Electoral Boundaries Commission or Electoral Divisions Boundaries Commission, so we simply used the year like (2010) instead of something like (2008 Redistribution)
[x] Add a singular parameter to the definition, like singular='Federal electoral district',
This change is staged
[ ] Commit and push your changes
[ ] Update the old set, like fab alpheus update_boundaries:args="-d data/shapefiles/public/boundaries/ocd-division/country:ca/2013"
[ ] In the Django admin, delete the old set with the old name, like 'Federal electoral districts'
Note that with municipal boundaries, we only ever use the most recent boundaries, because it's hard to track the formal processes, and it would be a lot of work to maintain even if we could track those processes.
jpmckinney
commented
7 months ago
Represent's federal, provincial and territorial boundary sets originally had names like 'Federal electoral districts'. However, these jurisdictions modify their boundaries following formal processes at regular intervals. In order to have permanent and unambiguous names, Represent is transitioning towards adding suffixes like
(2013 Representation Order),(Representation Act, 2005),(2015 Redistribution), etc. to the name.The suffixes are based on each jurisdiction's most common way of referring to the boundary modification.
The boundary sets aren't being renamed immediately to avoid disrupting API users who have hardcoded the current names.
Instead, whenever the boundaries change, we take that opportunity to add suffixes to all boundary sets for that jurisdiction.
Steps:
definition.pyfile, likeboundaries/ocd-division/country-ca/2013/definition.pyElectoral Boundaries CommissionorElectoral Divisions Boundaries Commission, so we simply used the year like(2010)instead of something like(2008 Redistribution)singularparameter to the definition, likesingular='Federal electoral district',fab alpheus update_boundaries:args="-d data/shapefiles/public/boundaries/ocd-division/country:ca/2013"Transitioned:
2022(first election after new boundaries)Note that with municipal boundaries, we only ever use the most recent boundaries, because it's hard to track the formal processes, and it would be a lot of work to maintain even if we could track those processes.