spatial_zip_to_hra20_pop: Spatial crosswalk between ZIP codes and 2020 HRAs

spatial_zip_to_hra20_popR Documentation

Spatial crosswalk between ZIP codes and 2020 HRAs

Description

There is one row between each ZIP and HRA that shares population.

Usage

spatial_zip_to_hra20_pop

Format

A data.table with 233 rows and 11 variables:

ZIP: ZIP code,

hra20_id: HRA numeric id,

s2t_fraction: Percent of the population in ZIP that is also in hra20_id,

isect_amount: # of people who live in the intersection of ZIP and hra20_id,

tcoverage_amount: Population of the hra20_id in any ZIP code,

target_amount: Total number of people within the HRA (including areas not covered by ZIPs),

hra_name: Name of the HRA,

source_id: ZIP,

target_id: hra20_id,

method: method to produce intersections,

creation_date: Date file created

Details

The are based on the point pop approach in spatagg::create_xwalk and broadly follow that file structure.

Note: ZIP codes are not completely nested within King County. As such, end users may want to further process this file to handle edge effects


PHSKC-APDE/rads.data documentation built on Jan. 25, 2025, 12:25 a.m.