11.07.2015 Views

Saticoy & Wells Community Plan & Development ... - City Of Ventura

Saticoy & Wells Community Plan & Development ... - City Of Ventura

Saticoy & Wells Community Plan & Development ... - City Of Ventura

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Saticoy</strong> & <strong>Wells</strong> <strong>Community</strong> <strong>Plan</strong> and Code EIRSection 4.12 Population and HousingTable 4.12-4Forecast Project Area and <strong>City</strong>wide Jobs/Housing RatiosProject Area<strong>City</strong>wide(existing + ProjectArea development)Projected Jobs 639 a 66,688Projected Housing Units 1,833 44,240Projected Jobs/Housing Ratio 0.35:1 1.51:1aThe Project Area job estimate was derived using a factor of 2.36 employees/1,000 square feetof retail area and an estimate of 270,625 square feet of Project Area retail development (seeSection 2.0, Project Description). The employees/1,000 square feet estimate is from theNatelson Company, Inc., Employment Density Study Summary Report, prepared for SouthernCalifornia Association of Governments, October 31, 2001.Mitigation Measures. Mitigation is not required.Significance After Mitigation. Impacts would be less than significant withoutmitigation.c. Cumulative Impacts. As indicated in Impact PH-1, housing and population growthfacilitated by the Project would be consistent with the forecasts contained in the 2005 General<strong>Plan</strong>. Similarly, other planned and pending development in the <strong>City</strong> is consistent with what isenvisioned in the 2005 General <strong>Plan</strong>. As such, cumulative citywide population and housinggrowth would be consistent with the SCAG growth forecasts through 2025. Therefore,cumulative impacts relating to population and housing would not be significant.4.12-4<strong>City</strong> of <strong>Ventura</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!