Loading...
HomeMy WebLinkAboutApplication APPLICANT 9/21/2021City of Springfield Development & Public Works 225 Fifth Street Springfield, OR 97477 Development Issues Meeting (DIM) SPRINGFIELD M Required Project Information (Applicant: complete this section) Prospective Applicant Name: Village Park Apartments, LLC Phone- 541-344-0028 Company: Bunting Management Group Fax: Address: 2677 Willakenzie Road #3 Eugene OR 97401 Prospective Shane McCloskey Applicant's REP.: Phone: 541-338-8544 Company: Dustrud Architecture, p.c. Fax• Address: 1699Pearl Street I Eugene OR97401 / Property Owner: Village Park Apartments, LLC Phone: 541-3440028 Company: Bunting Management Group Fax' Address: 2677 Willakenzie Road #3 Eugene OR 97401 ASSESSOR'S MAP NO: 17023311 I N- 'J3 � TAX LOT NOS : 4400 and 4404 Property Address: 5236 Main Street I Springfield OR 97478 Size of Property: 0.52 AcresitSquare Feet Description of If you are filling in this form by hand, please attach your proposal description to this application. Pro oral• parking lot rehab with new One -Way traffic, Exit apron & prefab maintenance shop and office, Type V const. Existin Use: tax lot 4400 is currently a vacant lot # of Lots Parcels: N/A Av . Lot Parcel Size: N/A Sf Densi 29 du acre Prospective <ny Applicant:�—Date: September 20, 2021 Signature Shane McCloskey Dustrud Architecture Print Required Project Information (City Intake Staff., complete this section) Case No.: %I I _2 - L?o0"2-St- PRS Date: 2E-ff� 74 1 Z9 I Reviewed by: Application Fee: 16 10D Technical Fee: 0 Posta a Fee: 0 TOTAL FEES: &q& -01b PR03ECT NUMBER: Revised 5/21/13 KL 1 of 3 Development Issues Meeting Process The purpose of a Development Issues Meeting is to give an applicant the opportunity to discuss his/her development proposal with the development review staff of the City. The discussion can be general or specific, depending on the details provided with the application. A Development Issues Meeting provides information to an applicant related to the current development conditions and standards of the City. The Development Issues Meeting is not a land use decision and does not confer any development rights, establish any conditions, or bind the applicant or the City to any course of action. The meeting conveys the status of known development opportunities and constraints. The status may change over time as development conditions or standards change. 1. Applicant Submits a Development Issues Meeting Application • The application must conform to the Development Issues Meeting Submittal Requirements Checklist on page 3 of this application packet. • Development issues meetings are conducted every Thursday. • We strive to conduct the development issues meetings within three to four weeks of receiving the application. • The applicant's proposal is circulated to the relevant staff in preparation for the meeting. 2. Applicant and the City Conduct the Development Issues Meeting • The applicant and any design team should attend the development issues meeting. • The meeting is scheduled for one hour. • Staff attending the meeting will be prepared to discuss the issues raised in the submittal by the applicant. Other issues raised during the meeting may also be discussed. • The meeting is informal and the City will issue no staff report. Revised 5/21/13 KL 2 of 3 Development Issues Meeting Submittal Requirements Checklist ❑ Application Fee - refer to the Development Code Fee Schedule for the appropriate fee calculation formula. A copy of the fee schedule is available at the Development & Public Works Department. The applicable application, technology, and postage fees are collected at the time of complete application submittal. ❑ Development Issues Meeting Application Form ❑ Five (5) questions - list specific questions the applicant would like staff to answer during the meeting. So that each question may be fully evaluated, the list is limited to five questions. ❑ Four (4) Copies of the Proposed Plan - suggested information valuable for staff to review the proposal is listed below. It is not necessary to include all of these items on the site or plot plan. However, applicants are encouraged to address as many as possible given that the level of information that will be derived from the meeting is commensurate with the level of detail provided in the application. Applicants are also encouraged to include additional information on the plan as listed in the Springfield Development Code (SDC) 5.12-120, Land Divisions - Partitions & Subdivisions - Tentative Plan Submittal Requirements or 5.17-120, Site Plan Review Submittal Requirements. ❑ Drawn in ink on quality paper no smaller than 11" x 17" ❑ Scale appropriate to the area involved and sufficient to show detail of the plan and related data, such as 1" = 30', 1" = 50' or 1" = 100' ❑ North arrow ❑ Date of preparation ❑ Street address and assessor's map and tax lot number ❑ Dimensions (in feet) and size (either square feet or acres) of the development area ❑ Location and size of existing and proposed utilities, including connection points ❑ On-site drainage collection system and flow patterns, the size and location of drain lines and catch basins, dry wells, and natural drainageways to be retained ❑ Area and dimensions of all property to be conveyed, dedicated, or reserved for common open spaces DIMS Related to Land Divisions ❑ Approximate location, number and dimensions of proposed lots ❑ How streets in the proposal area connect with existing streets DIMS Related to Site Plan Review ❑ Proposed and existing buildings: location, dimensions, size (gross floor area), setbacks from property lines, distance between buildings, and height ❑ Area and percentage of the site proposed for buildings, structures, driveways, sidewalks, patios and other impervious surfaces ❑ Parking and circulation plan Revised 5/21/13 KL 3 of AN DUMUD architecture 1699 Pearl Street I Eugene OR 974011541.338-85441 dustrudarchitecture.com September 20, 2021 Development Issues Meeting for 5236 Main Street ( Springfield, Oregon Proposed Scope of Work at Village Park Apartments IVPAI: - Replacement of (e) parking lot with minor additions & upgrades for Fire & Stormwater. - Development of adjacent parcel for added parking, outdoor amenities & exit apron onto Main St. The (e) Parking lot of the VPA is in need of replacement due to its 1964 installation. The (e) stormwater piping, of the same vintage, and should be replaced while the parking lot is pulled up. Staff had previously directed the catch basins to be upgraded to 2 stage units with approved filtration as well. This has been scheduled for mid-November. At some point afterwards, the adjacent parcel will be developed as additional residential parking with outdoor picnic and gardening amenities, a stormwater treatment facility tied to the rehabbed piping & a new Exit driveway onto Main Street. The (e) lot and proposed lot would be connected and used as one U shaped circulation path. The proposed Exit would beget the (e) access point to be the dedicated Entry. The VPA and th[ future parking lot are two separate tax lots, thus the 2 aprons should be allowable, yet ODOT may have more direction to provide for development. At a previous DIM, Staff advised that the Sites be tied together with a deed covenant eliminating the option to sell the parcels individually, and the Owner agreed it would preserve the intent of the development. The (e) parking lot does not conform to the current Fire Code as the depth is greater than 150' from Main with no option to turnaround. Once both lots have been revived and developed the Owner would like to eliminate some spots from the center parking isle to accommodate a Fire truck hammerhead turnaround navigable from either the Entrance or Exit. As no parking stalls can impede the clear turning radius and the lot currently allows parking in this area, a small planting island is proposed for the semi -circular areas to clearly delineate the fire isle. Alternately the area could be delineated with striping but current parking patterns could persists despite the lines in the AC. Staff input on best practices to preserve the hammerhead clearances is welcomed. The dedicated Ingress & Egress will make the lot and Main Street safer for residence and drivers. Tenants within the facility will have directional flow of traffic, significantly reducing the opportunity for collisions. Currently traffic shares the same apron which is situated <10' from a 2 story building to the East adjacent to the West bound lane of Main St.. Exiting the parking lot eastbound while a car enters from that eastbound lane requires one party to wait. With a'-40' buffer between one way traffic onto and off of Main Street traffic can proceed without major pause nor conflict. Previous development proposals for the empty lot located a wood framed Maintenance Shop in the SW corner where parking spot 36-38 now appear. The Owner wanted to preserve the 'open lawn' feel of the gardening and playground amenities by placing a prefabricated 'Tuff Shed' (24'x30') toward the North PL to the West behind the (e) apartments. They intend to have a WC, lavatory and utility sink within the shed, tying into the (e) apartment sanitary system. DIM QUESTIONS for 5236 Main Street to City Staff: 9/20/21 1. How does Staff view the final parking lot configuration as it relates to the added planting isle in the (e) lot, developed to clearly set the fire isle aside from parking? Would this trigger other development requirements in the (e) lot beyond the intended rehabbed stormwater piping and 2 stage catchment basins? Is a permit required for replacement piping that maintains the drain locations, routes, and destination? 2. Does the City or ODOT take issue with proposed one-way traffic where the (e) apron is ENTER & the proposed Western apron is EXIT? The Entry will have 50' queuing lane before the barrier arm security gate, traffic control arm which will be active after 6PM until 7AM. The Exit drive will have the same barrier arm security gate near the ROW to clearly delineate the Entry from the EXIT. 3. Stormwater: Is the removal of the AC between the northern most units an acceptable offset to add a drive isle to the face of the shop? 4. Stormwater: Is it acceptable to collect the 'proposed' lot runoff in a swale tied to the (e) stormwater system, which will be re-habbed at the time of AC maintenance in November? 5. Wastewater & Supply: is it acceptable to connect the maintenance shed plumbing to the existing apartments supply and wastewater? 6. Fire: Does the Site Plan meet the requirements for fire equipment/access? How does the development need to address fire access and circulation once the two lots are combined in a U -pattern? 7. What does City Staff require for the placement of a prefabricated "Tuff Shed" Maintenance shop (24"x30') behind the (e) apartments 5' from the N PL? Dustrud Architecture, p.c. Page 2 of 2