Closed Jennit07 closed 1 year ago
In the
fill_geographies
function we listdatazone
within thecheck_variables_exist
but we don't actually use this anywhere in the script from what i can see. @Moohan Can you think of any reasons why we would needdatazone
before i remove this?
I think we used to take datazone
i.e. the datazone from the data mart which is attached to the episode, and if the postcode couldn't match a new datazone through the lookup (either postcode is invalid or missing), we'd use the original one. - The only situation this actually helps is when the postcode is missing/invalid but datazone isn't though, and I guess that's a very niche situation...
As long as we have the datazone2011
correctly named and no odd datazone
variable left over that should be fine!
As discussed on a call, i have renamed datazone
in the datamart and made use of this in the fill_geographies
function. PR open #744
I've sorted
hscp
on the branch738-sort-pc-lookup
and i thinkhbrescode
was done in #724 for the individual file. For datazone, i think this is an extra variable because it is taken from BOXI. We takedatazone2011
from the postcode lookup so i think we can dropdatazone
from this altogether.In the
fill_geographies
function we listdatazone
within thecheck_variables_exist
but we don't actually use this anywhere in the script from what i can see. @Moohan Can you think of any reasons why we would needdatazone
before i remove this? Thanks