Skip to content

Bespoke/forres and lossiemouth#170

Draft
Moohan wants to merge 66 commits intomainfrom
bespoke/forres_and_lossiemouth
Draft

Bespoke/forres and lossiemouth#170
Moohan wants to merge 66 commits intomainfrom
bespoke/forres_and_lossiemouth

Conversation

@Moohan
Copy link
Copy Markdown
Member

@Moohan Moohan commented Feb 20, 2025

This PR is being kept as a draft for reference. See the 'files changed' for how the bespoke profiles differ from the 'main' profiles. Note that this branch / PR should be kept up to date with the changes in the 'main' profiles, this can be done using the 'update' button at the bottom of the PR conversation page (this page).

It might also be useful to see comparisons to other bespoke profiles, to ensure we're being consistent and using all the learning from each time we do them.

Moohan and others added 30 commits May 14, 2024 08:23
This function aggregates the data from IZ level to the new 'locality' boundaries, it tries to properly recompute the CI when the values are available.
This will return the Moray specific lookup
This will likely need doing for other data too...
Some are already loaded with `library(tidyverse)`
…alth-Scotland/list-localities-profiles into bespoke/forres_and_lossiemouth
This will inevitably be left on the drive occupying space and these files also had patient-level data, which isn't ideal!
@Moohan Moohan added the custom profile Relating to a custom boudary request label Jun 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

custom profile Relating to a custom boudary request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants