Loading...
HomeMy WebLinkAboutResolution 554 - Habitat for Humanity Prelim. PUD;~. a ? ~;. PLANNING COMMISSION RESOI.U`I'ION NC). SS4 A RESOLUTION GRANTING PRELIMINARY I'UD DEVLLOPMEN"I' I'I.,AN AI'PROVAI.~ OP PHASE I IiOR I-IAI~ITA`I' FOR I-IUMANIT'Y (Applicant (s} :1-Iabitat for I Iumanity 1 Rogue Valley (372W03DB, `T'ax Lot 800 ) Recitals 1. Applicant(s) has/have submitted an application for preliminazy PUD plan approval to create six single family homes on this phase of the development. A second phase has been proposed on an adj acent parcel and will be submitted to the City at a future date. Tl~e subj ect propezty for Phase 1 is located at 431 North Second Street within the TOD-MMR, Medium Mix residential zonizag district, within the City of Central Point, Oregon. 2. On October I, 2002, the Central Point PIanning Commission conducted aduly-noticed public hearing on the application, at which tune it reviewed the City staff reports and heard testimony and comments on the application. Now, therefore; BE IT RESOLVED BY THE PLANNING COMMISSION OF THE CITY OF CENTRAL POINT, OREGON, AS FOLLOWS: Section 1. Approval Critezia. The requirements for approval of land partitions and tentative plans aze set forth in CPMC Title 16 and 17, relating to informational requirements, zoning, lot dimension, access, and similar requirements. Section 2. Findingand Col~clusions. The Planning Commission fznds and detezmines as follows: A. Tentative Plan Requirements; The application and tentative plan are in the correct foz-zn and contain all of the information required by CPMC 16.10. B. Area and Width of Lot. `T'his subdivision in a TOD-MMR, Medium Mix Residential zoning district would create 6 single family lots: All lots meet the n~iniznum az•ea and width requirements for lots inthe TOD-MMR zone as set Earth in CPMC 17.20, and P.U.D. set forth in CPMC 16.10 and such parcels meet the general requirements for lots contained in CPMC 16.24.050. PIanning Commission Resol€afion No. 554 {10012002 ) C. Preliminar~UD P1a€1. `The pz-elimi€lary dcvciopment pla€~ contains those items nccesstz€y to proceed with the deveIapment proposal. Section 3. Conditional Approval. The application forte€~tative plan for [and subdivision herein is hereby approved, subject to the conditions set faz•th on l3xhibits "A", and "I3",attached hereto by zefezcnce ineozporated herein, imposed under authority of CPMC Chapter l 6.36 including a €~ecluirement that interior parking apzon widths be reduced with the undez-standing that suc11 area will be converted i€zto additional landscape area. "l'lae Commission has also required design changes to the homes fronting Second Street so that there will be adequate off street parking area. This is intended to reduce a pate€ltial conflict between homeowners and pedestrians using tl~e adjoining sidewalk. passed bythe Planning Commission and signed by €~~e in authentication ofits passage this day of ~.~ ~+~.~ ~ , 2002. planning Camrnission Chai€• Approved by me this ~ ~ ~' day of C;'c..-k-~~~~-~ 2002. Planning Commission Chair Planning Commission Resolution No. _554 (10012DD2 ) 2°'~ a-~' Sion i5 Exhibi# "A" , ~ Ca~~ merit RECOMMENDED PLANNING DEPARTMENT CONDITIONS OF APPROVAL 1. A final development plan, containing in final form the information required in the preliminary plan shall be submitted to the City within six months of approval or by October 1, 2043. A six month extension maybe granted by the City upon the applicant's request and for good cause. 2. The project must comply with all applicable local, state, and federal regulations including, but not limited to, the Oregon Uniform Fire Code and Structural Specialty Code. 3. The applicant shall submit final parking, landscaping, lighting and sign plans to the City for approval as part of the final development plan. A suitable landscape and irrigation plan shall show the types of tree's, shrubs, and ground cover that will be planted and the irrigation for the common space. 4. The applicant shall subzn.it a copy of the Covenants, Codes and Restrictions (CG&R's) or any comparable agreement governing the use, maintenance and continued protection of the PUD as part of the final development plan. 5. The applicant shall reduce the width of paved areas in front of the units to increase landscape area. Off street parking requirements stipulate that two spaces must be provided for each unit (l covered and l uncovered) but the Commission felt that the paved area was excessive since each unit had area provided for three cars. 6. The Planning Commission would like to have units 5 and 6 built with higher quality composition roof material as both units face Second Street. 1-i:1Planning142038.~~pc1 Habitat for7-Irrmarri~~ PIt%D Staf/~~~eport ~a/o~/~oo.~ CITY OI~ CEN~I`RAI, P01N'I` PUBLIC WORKS DIsP.~ KT MELT STAIR P Rl ;PORT Date: October 1St, 2002 Applicant) Owner: Habitat for Humanity P.O. Box 6$8 Medford, Oregon 97501 Agent: Hoffbuhr & Associates 3155 Alameda Street Suite 201 Medford, OR 97504 Location: 431 North Second Street Central Point, Oregon Legal: 372W03DC Tax Lot 800 Zoning: TOD DISTRICT - MMR Report By: Public Works Department PURPOSE Exhibit "B" Provide informations to the Planning Commission and Applicant (hereinafter referred to as "Developer"} regarding City Public Works Department (PWD} standards, requirements, and conditions to be included in the design and development of the proposed commercial facility. Gather information frown the Developer/Engineer regarding the proposed development. SPECIAL REQUIREMENTS 1. Exrstin In rastructrcre: The Developer shall demonstrate that all connections to existing infrastructure (i.e. streets, water, sanitary sewer, storm drain systems, natural drainage systems, etc.,} will not interfere with or provide for the degradation of the existing effective level of service or operation of the infrastz-uctuz•e facilities, and that the existing infrastructure facilities have either adequate capacities to accommodate the flows and/or demands imposed on tl~e existing infrastructure as the result of the connection of the proposed development's infrastructure, or will be improved by and at the expezase of the Developer to accommodate the additional flows and/or demands; while maintaining or improving the existing level of service of the affected facility, as approved by (as applicable} the regulatory agency, utility owner, andlor property owner involved. Y Fla6ital for Hrrmafait}~ P~--~%D ,Staff I~cpo~r 11/6/2002 2. Tra~fc .Impact: The proposed Development is a lotiv traffic_impact development that will be located to the West of North Second Street. Two entrances are currently projected from North Second Street to the proposed development. 7"he first is a twenty-foot wide driveway throat, which accesses the twenty-foot ingress & egress easement. The second entrance is a curb cut directly entering a carport located on the South portion of the development. These entrances will be required to meet Public Works Department Standards, which calls far a zninimuzn throat width of twelve-feet and a maximum of thirty-feet 3. Easements: The Developer shall provide suitable and acceptable 15-foot-wide minimum easements for any City public works infrastructure located outside the public rights-al=way. These easements sl~zaIl be dedicated for sole use by the City, and shall not overlap {crossings are acceptable, as long as required infrastructure separation is maintained} other utility or infrastructure easements. All construction plans and as-built drawings shall accurately portray (both horizontally and vertically) utility line and appurtenance locations and the locations of any existing and new easements on the proposed development. A!1 final plats shall accurately portray the horizontal location of all easements and rights-of--way dedicated as part of the development of this project. All right-off way and easement dedication shall be completed prior to final construction plan approval. 5. Site Layout/Traffic Plan: The developer shall prepaz•e and submit for City pWD approval a suitable site traffic plan for the proposed development. The traffze plan shall illustrate that all driveways and connections to streets shall accommodate the turning and access movements of all expected truck, bus, emergency vehicle (i.e, fire truck) and all other applicable vehicles. 6. Clear Vision Areas/Triarzgles. All driveway approaches of the proposed Development connecting to public roads shall maintain a minimum 55-foot sight vision triangle as measured from the edge of the right-of way to the center of the driveway. This requirement may be adjusted by the public Works Department, depending on f pal orientation and lane layout of the adjoining roads, in accordance with AAS1-1T0 clear sight-vision requirements. Adequate clear vision area/triangles shall also be maintained at all internal driveway intersections. Landscaping/Street Trees: The developer will be required to submit a suitable landscaping/street tree plan for review and approval by the City of Central Point Parks Department. $. Erasion Control Plan: A suitable erosion control plan must be prepared and submitted to the Oregon Department of Environmental Quality {DEQ} and City pWD for tl~e construction of any improvements associated with this development. The City PWD will not approve the construction plans associated with this development until the City PWD receives a copy of the written approval of the erosion control plan by the DEQ. 2 HdGitat for Flrana~ti_l}' PI~'!D Sta~Aef>ort »/r/~aoz 9. Storm Dr~rinrc~e System: The storm drain system shall be designed to accolnlnodate the storm water run-off from and run-an onto the proposed developme~lt (either surface run-an or culvert or creek/ditch conveyance); any future development on adjacent properties; conveyed storm drainage or surface water flow, and any flows froln areas deemed by the City that will need to connect into the proposed developlnent's SD System. Currently, the City of Central Paint Public Works Department is recommending the 15-foot stoma drain easez~~ents, which exist along the South & West property boundaries be reduced to an adequate width for private maintenance. Furthermore, it is the suggestion of the Public Works Department that all on-site storm drain be deemed private, and the newly created easements exist solely of the purpose of private maintenance of a storm conveyance system extending South. from the North West pzoperty corner to the South West Property corner turning East. The private storm system should continue East for the entire length of the property providing an area drain for each proposed unit. 11. Water Distributiosi S stem: The water distribution system far the proposed Development shall be of "reinforced loop" design; a minimum of two connections will need to be made to the City's distribution system. Presently, a practical connection paint is unavailable. Based on existing line types and location it is the recommendation of the Public Works Department that every effort be made to provide for a future "reinfarcizig loop connection". 12. Above round Utilities: If applicable, coordinate efforts with Pacific Power, Qwest, and Charter Communications, to convert any overhead electrical power, telephone, or cable facilities within the proposed development to underground facilities, prior to the acceptance by the City PWD of the public improvements associated with the praposed development. All agreements and costs associated with the conversion of these facilities from overhead to underground facilities shall be by and between the utility owl~ers and the Developer. GENERAL 1. Public Inznrovements: All construction of public improvements shall conform to the City's PWD Standards, the conditions approved and stipulated by the Planning Commission, anal other special specifications, details, standards, and/ox upgrades as may be approved by the City Administrator or his designee prior to the approval of the construction plans far the proposed development. During construction, changes proposed by the Developer shall be submitted in writing by the Developer's engineer to the City PWD for approval prior to implementation. 2. Permits ~cnd A~~rovals: Developer shall provide copies of any permits, variances, approvals, and conditions as may be required by other agencies, including, but not limited to, the Oregon Department of Fish and Wildlife (DFW), Oregon Department of )/nvironrrzental Quality (DEQ}, Oregon Division of State Lands {DSL), U.S. Army Cozps of Engineers {ALOE), affected irrigation districts, and Jackson County Roads and Parks Services {JC Roads}, Fire District No. 3, and Bear Creek Valley Sanitary Authority (BCVSA), as applicable. The Developer shall submit written approvals of the f nal construction plans from Fire District No. 3 (fire hydrant placement, waterline sizing, and emergency velaicIe access), Bear Creek Valley Sanitary Authority {BCVSA, for sazaitary sewers), and JC Roads, (E. Pine Street improvements and driveway/access road I-Ia6ital foi-Ilsrniaur~~ PItlD Sta~`~eborl 19/6/2002 connections} prior to final construction plan review and approval by City 1'WD. 3. .~s-Bunts: Prior to approval and acceptance of the project, the Developer's engineer or surveyor shall provide the Public Works Department with "as-built" drawings. if feasible, the Developer's engineer or surveyor should provide the drawings in both a "haz-d copy' form (produced on Mylar~'} and in a "digital" format compatible with AutoCAD~, or othez• form as approved by the City PWD. As-built drawings are to be provided to the City which provide "red-line" changes to final approved construction plans which identify the locations and or elevations (as appropriate) of actual installed items, including, but not limited to, invert, inlet, and rim or lip elevations; spot elevations identified on drawings; water lines, valves, and fire hydrants; water and sewer lateral; modifications to street section; manhole and curb inlet; street light locations; other below grade utility lints; etc. Provide a "red-line" hard copy (on Mylar°), or an approved alternative farzxzat, of construction drawings, and if feasible, an acceptable AutoCAD~' compatible drawing electronic file to the City at completion of construction and prior to acceptance of public infrastructure facilities completed as part of the proposed development, or as otherwise approved by the City Administrator or his designee. 4. Elevations: AlI elevations used on the construction plans, on temporary benchmarks, and on the permanent benchmark shall be tied into an established City approved benchmark and be so noted on the plans. At least one permanent benchmark shall be provided for the proposed development, the location of the bencl~zrzark shall be as jointly determined by the City PWD and the Developer's surveyor. S. Existirz~ .Infrastrrccture: As applicable, field verify all existing infrastructure elevations and locations (i.e. pipe inverts, curb elevations, street elevations, etc.), to which the proposed development will connect into existing improvements, prior to final construction plan design and submittal for final approval. The accurate locations of any existing underground and above ground public infrastructure, and the location of the associated easements with these facilities, shall be accurately portrayed {both horizontally and vertically} on the construction plans. 6. Fill Placentetat: All fll placed in the development shall be engineered f 11 that is suitably placed and compacted in accordance with City PWD and Building Department standards, except for the upper 1.5-feet of fill placed outside of public rights-of-way and that does not underlie building, structures, or traveled vehicular access ways or parking areas. 7. Road/Drivefva /ParkitraAreas: The Developer shall evaluate the strength of the native soils and determine the access road, parking, and driveway section designs to handle the expected loads (including fire equipment} to be traveled on these private driveways, access roads, and parking areas. Need to provide designed road section for review. The road/street/driveway sections within the public rights-of way shall be constructed per the design of the City PWD. ` Utr'lity,Platzs: 'I'he utility plans shall be drawn to scale with accurate horizontal and vertical 4 T-IaGitat jor I Iarvila~ritj~ PII%D Sta~j~F~cpart 11/G/2002 depiction of utility lines and appurtenances (transformers, valves, etc.). Utility infrastructure location must be accurately included on the as-built drawings, or as a separate set of draw€ngs attached to the as-built drawings. R. Area Li~htinQ Plan: Need to provide azad iznplezrzent an adequate area lighting plan for parking and public access areas, including the driveway entrances. 10. Easements: Easements for City infrastructure {i.e. sanitary sewer, water, and storm drain cif appIicable]) should be a minimum of I S-feet wide, and should not split lot lines. Easements for public storm drainage, sanitary sewer, and water lines shall be dedicated to the City and not just a P.U.E. Centerline of buried infrastructure shall be aligned a minimum of flue (5) feet from the edge of the easement. if two or more City owned utilities are located within an easement, then a minimum of 20-foot width should be required. Easement dedications in fznal deeds or CC&Rs need a statement, which should clearly indicate that easements must be maintained with suitable, drivable vehicular access to City public infrastructure facilities, as determined by the City PWD. 11. Street LiQlxts: Construction drawings for this tentative plan shall include a Street Lighting Plan in accordance with the requirements of the City PWD or as otherwise approved by the City Administrator or his designee {with maximum 200 foot spacing). The construction drawings shall include clear vision areas designed to meet tl~ze City's PWD Standards. 12. Storm ~raina e S` stem: Developer's engineer shall develop a facility plan for the storm drain collection, retention, and conveyance system {SD System} which provides for storm water run- off from and run-on onto the proposed development {either surface run-on or culvert or creek/ditch conveyance}, any existing or future development on adjacent properties, conveyed storm drainage, or surface water flow, and any areas deemed by the City that will need to connect-into the proposed deveIopment's SD System. As applicable, the Developer's engineer shall determine how the SD system will work during 10- year and 100-year flood events associated with Bear Creek. Identify the HGL in Bear Creek during 10- and 100-year storm event, and what affect it will have on the proposed outlets and storm drain system and building elevations. System should be designed to adequately drain a 10- year storm event without surcharging or shall provide adequate storage to prevent surcharging; and be designed to prevent backflow of water from Bear Creek up into SD system during storm events. The design of the storm drain collection and conveyance system (SD System} should provide for storm water run-off from and run-on onto the proposed development (either surface run-on or culvert or creek ditch conveyance); the Developer shall demonstrate that the storm watez• flows from the completion of the proposed development (and at any tune prior to completion of development} do not exceed predevelopznent flows into Bear Creek; or that allowances or provisions have been made (and approval of the applicable properties owners and regulatory agencies has been obtained), which accommodate any additional flow which exceed Habita6 far Hra»tatrity P[i'staffl3.epar~ 99/6/2002 predeveIopznent flows. The Developer azad the City PWD shall agree on the applicable run-off coefficients, curve numbers, etc., to be used in the engineering calculations. Developer's engineer shall provide a site drainage plan designed, at a minimum., to accommodate a 10-year storm event. The SD system must be designed to adequately drain the 10-year storm event without surcharging or must be provided with adequate storage to prevent surcharging; az~d be designed to not impact existing public storm drainage facilities. Catch basins and area drains shall be designed for on-site sediment and petroleum hydrocarbon retention. The private storm drain system shall be designed to directly connect to the public storm drain system, and shall not be designed to discharge to the street surfaces. Public storm drainpipe materials shall be PVC, HDPE, or reinforced concrete, with watertight joints. Provide concrete or sand-cement slurry encasement where required in areas of minimum cover. Roof drains and under drains shall not be directly connected to public storm drain lines and shall drain to the on-site private storm drain system. As applicable, any discharge points of the storm water facilities shall be designed to provide an aesthetically pleasing, useful, and low maintenance facility, that are designed fio mitigate erosion, damage, or loss during a 100-year storm event; and that mitigate the "attractive nuisance" hazards associated with these types of facilities. Prior to City PWD construction plan review, the Developer shall provide the City PWD with a complete set of hydrologic and hydraulic calculations and profile plots for sizing the ~D system, which shall incorporate the use of the City PWD'srainfall/intensity curve, and Gity approved run-off coefficients, curve numbers, pipe roughness coefficients, etc., that are used in the engineering calculations. sheet flaw surface drainage from the property onto the public rights-af way or onto neighboring properties is unacceptable, Plans which propose to include the discharge to Bear Creels and any construction or modification within the floodway of Bear Creels or in the road ditches, shall be in compliance with DSL, ALOE, ODFW, DEQ, J'C Roads, and/or City PWD (as applicable) guidelines and requirements and any applicable conditions and or approvals, of these regulatory agencies. 13. Fire Hydra~zts: Provide locations of existing and any new required fire hydrants. Fire Hydrants need to be connected to 8-inch-diameter and larger lines, with the supply lines being "looped" as feasible. if applicable, steamer ports at hydrants located near the building shall face the buildings. Fire hydrants shall be suitably protected from potential vehicle damage and ezlcraachment. 14. I-Voter System_Cross Connection Control: Developer shall comply with Oregon ffealth Division (OHD} and City requirements for cross connection control. if a pressurized irrigation system 6 Ilaliitat for Ilun~aju~! PIS%D Sta_Q'I~e]~orl 91/6/2002 and/or domestic water wells exist az~ the property, the Developer will be required to izzstall the required baclcflow prevention assemblies directly bellied the City's water meters. 15. Water System: Construction drawings shall include the size, type, and location of all water mains, hydrants, valves, service coz~rzection, meter, service laterals, and other appurtenance details in accordance with City PWD Standards and as required by the City PWD. 16. Roa /Area Drains: All structures shall have roof drains, area drains, and/or crawl spaces with positive drainage away froze the building. 17. Grading Plans: Grading plans shall have original/existing grades and final grades plotted on the plan. Typically, existing grade contour lines are dashed and screened back, and final grade contour lines are overlaid on top of the existing grades and are in a heavier line width and solid. Contour lines should be labeled with elevations. 1 S. Sanitar Sewer: All sanitary sewer collection and conveyance system {SS System} design, construction and testing shall confarzxz to the standards and guidelines ofthe Oregon DEQ; 1990 APWA Standards, Oregon Chapter, Bear Creek Valley Sanitary Authority (BCVSA}, and the City PWD Standards, where applicable. The construction plans and the as-built drawings shall identify lateral stationing for construction of sewer laterals. 19. Water Ri,~Irts: Zf applicable, Developer shall provide a Statement of Water Rights (on a City approved form}, for any affected properties. For properties determined to have water rights, the developer will coordinate with the State Water master the re-allocation of any waters attached to lands no longer irrigable as a result of the proposed development. 7