Prog\Updates\Num_units_all.sas currently creates summary files with annual counts of single family, condo, and cooperative units from the RealProp.Parcel_base file. This task is to update the program to use the residential unit counts in the Mar.Address_points_view file, which should provide more accurate unit counts as well as allow us to add multifamily rental units to the summary files.
The goal is to produce new versions of the Mar.Num_units_* data sets by adding a variable for counts of multifamily rental units to this part of the Num_units_all.sas code, as well as replace the existing sf, condo, and coop counts with MAR-based counts.
if ui_proptype = '10' then units_sf = 1;
else if ui_proptype = '11' then units_condo = 1;
units_coop = no_units;
units_sf_condo = sum( units_sf, units_condo, 0 );
units_owner = sum( units_sf, units_condo, units_coop, 0 );
...
The rest of the Num_units_all.sas program can then summarize the rental unit counts along with the existing ones.
The address-to-parcel file (Mar.Address_ssl_xref) should be used to connect the Parcel_base and Address_points_view data sets. Note that the relationship between addresses and parcels is "many to many," so some work is need to figure out the best way to add the unit count variable (active_res_occupancy_count) to the parcel data and avoid duplicating unit counts. A procedure like this may be the way to go.
- Reduce Mar.Address_ssl_xref to one entry per address_id.
- Aggregate file created in 1. by SSL, summing active_res_occupancy_count.
- Merge file 2. with RealProp.Parcel_base to add unit counts. (These data can then be used in Num_units_all.sas.)
The best way to do 1. may be, where an address is matched to multiple parcels, to pick the parcel that is active (i.e., in Parcel_base, in_last_ownerpt=1). If more than one active parcel matches, then perhaps pick the most recent one (i.e., has highest value of ownerpt_extractdat_first). But, it's possible that we may need to match on some of the older parcels to get accurate historical unit counts. So, we need to experiment and check the results.
@lhendey @rpitingolo, It would be good if this issue could be done as part of the large unit study, but it would also be useful for the ODCA study.
Prog\Updates\Num_units_all.sas currently creates summary files with annual counts of single family, condo, and cooperative units from the RealProp.Parcel_base file. This task is to update the program to use the residential unit counts in the Mar.Address_points_view file, which should provide more accurate unit counts as well as allow us to add multifamily rental units to the summary files.
The goal is to produce new versions of the Mar.Num_units_* data sets by adding a variable for counts of multifamily rental units to this part of the Num_units_all.sas code, as well as replace the existing sf, condo, and coop counts with MAR-based counts.
The rest of the Num_units_all.sas program can then summarize the rental unit counts along with the existing ones.
The address-to-parcel file (Mar.Address_ssl_xref) should be used to connect the Parcel_base and Address_points_view data sets. Note that the relationship between addresses and parcels is "many to many," so some work is need to figure out the best way to add the unit count variable (active_res_occupancy_count) to the parcel data and avoid duplicating unit counts. A procedure like this may be the way to go.
The best way to do 1. may be, where an address is matched to multiple parcels, to pick the parcel that is active (i.e., in Parcel_base, in_last_ownerpt=1). If more than one active parcel matches, then perhaps pick the most recent one (i.e., has highest value of ownerpt_extractdat_first). But, it's possible that we may need to match on some of the older parcels to get accurate historical unit counts. So, we need to experiment and check the results.
@lhendey @rpitingolo, It would be good if this issue could be done as part of the large unit study, but it would also be useful for the ODCA study.