Laserfiche WebLink
<br />The fees collected by the City to develop the proposed building include building permit fees and <br />systems development charges (SDCs). The City publishes a fee-estimating guide, which was <br />provided to the developer at the November 6, 2007 pre-development meeting. There are no <br />exemptions to building permit fees. The only available SDC waiver applies to affordable <br />housing. <br /> <br /> <br />2.Can/should we impose a temporary moratorium on this building until after the Infill <br />Compatibility Standards (ICS) Task Team completes its work? <br />The council can impose a moratorium, but only after following the state statutory process and <br />only if the council finds that the statutory criteria are met. ORS 197.520(1) requires a city to <br />provide the State with notice of a proposed moratorium at least 45 days before the final public <br />hearing. ORS 197.520(3) specifies the circumstances under which a city can impose a <br />moratorium, including the types of findings that must be made to justify the moratorium. Unless <br />the moratorium is adopted prior to the submittal of an application, the moratorium will not affect <br />or apply to the application. ORS 227.178(3) provides that a city must base its decision on an <br />application on the standards and criteria in effect at the time that an application is submitted, <br />even if the standards and criteria change after the application is submitted. <br /> <br /> <br />Because of the 45-day required notice, which provides a large window for an application to be <br />submitted, a moratorium does not appear to be an effective way of dealing with this issue. <br />However, the ICS process is an appropriate place for these types of issues to be explored and <br />addressed. The ICS Task Team is in the process of establishing committees to work on specific <br />issues; compatibility between high density and low density development, parking concerns and <br />mass and scale have been put on the table numerous times and will be addressed by one of the <br />committees, with the goal of producing recommended solutions by the end of the year. <br /> <br /> <br />3.Can the Minor Code Amendments Process be accelerated to help deal with this circumstance? <br />The Minor Code Amendments Process (MiCAP) is moving forward. Twenty proposals for <br />amendments are going through the Planning Commission recommendation process, slated for <br />public meetings in late March or early April. A Planning Commission hearing on the <br />recommended code amendments will follow later this spring, followed by a City Council <br />hearing. The MiCAP list of potential amendments currently includes a building height <br />measurement item, and a parking requirements item that could potentially affect the proposed <br />th <br />19 and Alder development, depending on what the Planning Commission recommends and the <br />council eventually adopts. However, it is unlikely the outcome of the building height item, as it <br />is currently being discussed, will significantly affect what can be built on this development site. <br />Allowable height is currently 120 feet, and the proposed building is roughly 90 feet in height. <br /> <br />The parking requirement item, as it is currently being discussed, could result in a requirement for <br />increased parking on this site. Currently, one off-street parking space is required per unit (with <br />an allowance of a 25% reduction by right). If the minimum number of parking spaces required is <br />revised for lots affected by a Residential Parking Permit Program, or based on the number of <br />bedrooms instead of units, the required number of parking spaces for the site could increase. The <br />applicable requirements will be those in effect at the time a building permit application is <br />submitted. It is unlikely the MiCAP process can be completed prior to the submittal of building <br />permit plans, due to the public notice and hearing requirements involved with amending the land <br />use code. <br />F:\CMO\2008 Council Agendas\M080310\S080310B.doc <br /> <br />