You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current loc_table in ramptools uses a branching approach that starts at the health facility and then pulls in the parents to those health facilities. This results in some subcounties, which don't have health facilities, not included in this version of loc_table. This becomes problematic when trying to link with shapefiles or calculate overall statistics for a district (population, subcounty count, etc.)
Therefore, will replace with a version created from a "top-down" approach, in which the children of each region is pulled. Austin pulled this on 08MAY2024.
The text was updated successfully, but these errors were encountered:
I merged if with the bottom_up approach (also pulled in May) to get a combined file. Script for this is in my Scratch folder in Box. loc_table_merge_May2024_version
This combines the bottom up loc_table pulled on 240508_location_hierarchy with the top-down location table pulled 240524_location_hierarchy.
The current
loc_table
in ramptools uses a branching approach that starts at the health facility and then pulls in the parents to those health facilities. This results in some subcounties, which don't have health facilities, not included in this version ofloc_table
. This becomes problematic when trying to link with shapefiles or calculate overall statistics for a district (population, subcounty count, etc.)Therefore, will replace with a version created from a "top-down" approach, in which the children of each region is pulled. Austin pulled this on 08MAY2024.
The text was updated successfully, but these errors were encountered: