Hi - given email convo (Daniel, KCGIS and me) on 4/18 regarding zip code shapefile - the preferred column in our zip code shapefiles (e.g. "zip-shore-kc-clip" but maybe the others too, from here \dphcifs\APDE-CDIP\Shapefiles\ZIP ) is meaningless and in fact misleading. Therefore, can we delete it, and replace it with some 'main city' determination calculated from the zip-to-hra crosswalks?
I did an ad hoc 'main city' determination for my RGV DB in this manner --> if at least 70% of a zip code (population) corresponds to one HRA - that HRA name becomes the 'main city'. If not, then the main city = the concatenation of the top 2 HRAs. (e.g. 30% seattle and 22% shoreline gets label "Seattle/ Shoreline"). I guess you could be really simple and assign the main city to the the very first one too.
This would make zip code shapefiles immensely useful in that we can attach city labels for better understanding of program staff.
Hi - given email convo (Daniel, KCGIS and me) on 4/18 regarding zip code shapefile - the preferred column in our zip code shapefiles (e.g. "zip-shore-kc-clip" but maybe the others too, from here \dphcifs\APDE-CDIP\Shapefiles\ZIP ) is meaningless and in fact misleading. Therefore, can we delete it, and replace it with some 'main city' determination calculated from the zip-to-hra crosswalks?
I did an ad hoc 'main city' determination for my RGV DB in this manner --> if at least 70% of a zip code (population) corresponds to one HRA - that HRA name becomes the 'main city'. If not, then the main city = the concatenation of the top 2 HRAs. (e.g. 30% seattle and 22% shoreline gets label "Seattle/ Shoreline"). I guess you could be really simple and assign the main city to the the very first one too.
This would make zip code shapefiles immensely useful in that we can attach city labels for better understanding of program staff.
THANK YOU!