My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Item 28 - Public Hearing - ZOA No. 20204-01 South Coast Technology Center
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2024
>
08/06/2024
>
Item 28 - Public Hearing - ZOA No. 20204-01 South Coast Technology Center
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/6/2024 9:17:46 AM
Creation date
8/6/2024 8:50:42 AM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Planning & Building
Item #
28
Date
8/6/2024
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
591
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
not required to be separated from structures on separate parcels, and except <br />for walkway covers connecting pedestrian access and atrium connections <br />between buildings. <br />4. Site Coverage. All building setbacks as described in Section 6.2 above <br />(Setbacks) above. Building setbacks shall be maintained for site coverage &te <br />preGise plan provided thathe sethanks described abode are maintainer+ <br />ccrccvc�cn�cacnucc ccnrrccr <br />5. Parking. Parking within the Lake (enter Specific Development Plan SD-58 will <br />be design to take adVan+age of the urban Setting and halanne of A Sec provided <br />to attract companies contemplated by the Permitted Uses described in Section <br />3 above (Uses Permitted). This is represented by the miv of Similar land A Aoeo <br />I1GGated within Giese proximity to transportation fa y the properties <br />governed by the SD-58 zoning. It is the intent of the app! rt to provide <br />parking facilities in the form of surface parking, parking structures above and, <br />possibly, below grade or any combination thereof. The parking structures' <br />design shall be compatible with the surrounding land uses. <br />The sitesite GurreRtly has C�ur-fano narking spaGes Rd 861 spaGes On nag <br />str�, yes. Future on -site buildings may be served by a mix of surface and <br />structure parking (annr a ely 1,684 narking cnaGes in narking StrUGtures <br />Rd 289 supfaEe c Future spaces will be provided on a phase -by -phase <br />basis consistent with projected demand coinciding with the construction of the <br />proposed buildings. At build et pPejeGted tetal narking is an�tininated to her <br />3,342 spares in a r+omhination of s ArfaGe anal ctrA Anti Are narking <br />a. Location of Parking. Required off-street parking shall be provided. When <br />parking is provided on a site of different ownership a recorded document <br />shall be approved and filed with the City of Santa Ana Planning Division <br />and signed by the owners of the parking site stipulating to the <br />reservation of use of the site for said parking. <br />b. Joint Use of Parking. Two or more office or commercial uses may jointly <br />develop and utilize required parking facilities if approved by the Planning <br />Division. Parking requirements for each individual use may be reduced <br />through City of Santa Ana (i.e. no compact stalls) as of the date of <br />adoption with regard to surfacing, marking, grading, lighting, walls <br />circulation, parking dimensions, and layout. Landscaping requirements <br />will be in accordance with this Specific Development Plan. <br />c. Off -Street Parking Plan/Site Plan. A parking plan will be submitted for all <br />projects requiring more than ten parking spaces, unless off street <br />parking facilities are already provided. <br />The required number of off street spaces may be reduced <br />commensurate with the specific type of use and demonstrated hourly <br />parking demand upon approval by the Zoning Administrator. For off - <br />Ordinance No. NS-XXXX <br />Page 10 of 22 <br />
The URL can be used to link to this page
Your browser does not support the video tag.