My WebLink
|
Help
|
About
|
Sign Out
Home
COM 0200.002 2006-2008
ClerkCouncil
>
Council Records
>
Communications
>
2006-2008
>
COM 0200.002 2006-2008
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/13/2008 1:12:41 AM
Creation date
5/8/2008 5:27:12 PM
Metadata
Fields
Template:
Communications
Communications - Type
COM
Communications - Council Term
2006-2008
Communication
0200
Point
002
Author
Christopher J. Yuen, Planning Director
Communications - Referred To
COUNCIL
Document Relationships
BIL 156 Draft 01 2004-2006
(Related)
Path:
\Council Records\Bills\2004-2006
COM 0200.000 2006-2008
(Related)
Path:
\Council Records\Communications\2006-2008
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
5
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
<br /> Honorable Pete Hoffmann <br /> Chair and Presiding Officer <br /> and Members of the County Council <br /> COUNTY COUNCIL <br /> Page 2 <br /> March 8, 2007 <br /> typically do a subdivision to create the individual lots for sale, bearing the cost of roads, <br /> water, and other infrastructure, then sell the individual lots. Then the lot owners will <br /> apply for plan approval for their buildings. Because plan approval is tied to a particular <br /> use, it is easier to estimate job generation at that time, but the various owners will come <br /> in one by one, and obviously, it wouldn't be fair or practical for the County to waive <br /> affordable housing in a particular industrial subdivision for the first 99 employees, then <br /> start to assess affordable housing on every business that came in afterwards. <br /> The option is to have the original developer of the industrial subdivision take care of the <br /> affordable housing at the time of subdivision. Apart from the difficulty of estimating the <br /> number of employees, the developer cannot do this by creating affordable housing onsite, <br /> because residential uses are not allowed in ML, MG, or MCX zones. It can also be a very <br /> high requirement for a developer who is just building infrastructure and not the final <br /> buildings on the site, as discussed below. <br /> So if the council wants to do something like this, the ordinance must have: (1) an initial <br /> assessment at the time of rezoning whether the project, as a whole, will generate more <br /> than 100 jobs, to determine if there will be a future affordable housing requirement; and <br /> (2) a fair way of assessing the affordable housing requirement when the businesses <br /> actually start to occupy the project. <br /> The attached proposed amendments to Chap. 11 would do the following: <br /> First, at the time of any new zoning to ML, MG, or MCX, the future potential job <br /> generation would be estimated at ten employees per acre. This is basically consistent <br /> with an economic study done for TSA in their recent LUC application and rezoning for <br /> Increment 4 of the Kaloko industrial park. This means that a rezoning of ten or more <br /> acres of ML, MG, or MCX would trigger a future affordable housing requirement when <br /> the project is developed. <br /> Second, the actual affordable housing requirement, within any such project, would be <br /> determined at the time of plan approval. To avoid having to deal with businesses on a <br /> case-by-case basis, the number of employees would be assessed based on ten employees <br /> per acre, or one employee per 1000 square feet of gross floor area, whichever is greater. <br /> (A one-acre light industrial lot developed with awarehouse-type building will typically <br /> have 10,000-20,000 square feet in gross floor area, after allowance for setbacks and <br /> parking.) The Zoning Code requires one parking space for 400 square feet of gross floor <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.