Microfiche records prior to 2006 have not been completely digitized and may not be available yet on PRO. If you cannot find what you are looking for please submit a records request.

Permit Review Detail

Permit Number: DP14-0216
Parcel: 11515044A

Address:
1801 N ORACLE RD

Review Status: Completed

Review Details: SITE and/or GRADING

Permit Number - DP14-0216
Review Name: SITE and/or GRADING
Review Status: Completed
Review Date Reviewer's Name Type of Review Description Status Comments
11/25/2014 RBROWN1 ADA REVIEW Passed
11/28/2014 MARTIN BROWN FIRE REVIEW Approved
12/16/2014 RONALD BROWN H/C SITE REVIEW Reqs Change SHEET AC2/3 of 13
1. At the ramp leading to the Oracle street right of way:
a. Provide a landing at the top of the ramp, in front of the gate, as required by the 2009 ICC A117 Sections 405.7 and 404.2.3.2(b).
b. At note 30 delete all references to ADA and the 6" riser limitation. As per the 2009 ICC A117.1, Section 405.6, the ramp may rise 30" maximum.
c. Provide a large scale detail of the ramp showing all accessible requirements such as dimensioning, landings, slope, grade differences, handrails and width.
2. Provide a large scale detail of both smaller ramps showing all accessible requirements suc as dimensioning, landings, slope, grade differences, handrails and width.
3. Reference large scale detail of the accessible parking to detail shown on sheet C3/6 of 13.
4. At note 14 delete the ADA and COT STDS references.
5. At note 25 delete the ADA reference.
6. At note 22 change to read "as per the 2012 IBC, Chapter 11 and the 2009 ICC A117.1.
7. Provide for reduced vertical clearance as per the 2009 ICCA 117.1, Section 307.4.
8. Add a note: "All accessible route slopes shall comply with the 2009 ICC A117.1, Section 403.3; 5% maximum running slope and 2% maximum cross slopes."
9. There is no 6" step at this landing.
SHEET C3/6 OF 13
10. Provide a number or lettering identification system for all details and partial site plans.
11. At the accessible parking space detail:
a. Provide for a maximum grade slope of 2% in all directions.
b. Reference the accessible parking sign to detail C/C3.
c. Indicate a flush condition for the concrete walk
abuttment to the asphaltic paving.
12. Replace all ADA references with the 2012 IBC, Chapter 11 and the 2009 ICC A117.1.
END OF REVIEW
12/22/2014 ANDREW CONNOR LANDSCAPE REVIEW Reqs Change ADMINISTRATIVE MANUAL SECTION 2-10.0.0: LANDSCAPE PLAN REQUIREMENTS

A detailed landscape plan is required. In accordance with Section 2-11.0.0, Landscape Plan Requirements.

Identification and Descriptive Data

All improvements and site information, such as adjacent rights-of-way and property lines, shown on the landscape plan will be identical in size and location to those shown on the base plan (site plan or tentative plat). Should amendments be required to the base plan through the review process, the same amendments will be made to the landscape plan which will then be resubmitted along with the base plan.

The landscape plan will contain the following identification in the lower right corner of each sheet:

Rezoning case;

Subdivision case;

Board of Adjustment case;

Design Development Option case;

Development Review Board (DRB) case; and/or,
Any other relevant case number for reviews or modifications that affect the site.



ARTICLE 7: DEVELOPMENT STANDARDS
LANDSCAPING AND SCREENING

Minimum Width
Street landscape borders must be a minimum of ten feet wide as measured from the street property line. On streets designated as Major Streets and Routes (MS&R), the street landscape border must be measured from the future MS&R right-of-way line as determined by Section 5.4.4, Establishment of MS&R Right-of-Way Lines and Gateway Routes.

Street landscape borders must be located entirely on site, except that, if approved by the City Engineer or designee, up to five feet of the required ten foot width may be placed within the adjacent right-of-way area or within the Major Streets and Routes (MS&R) right-of-way area on MS&R streets.


Fifty percent or more of the area of the street landscape border must be covered with shrubs or vegetative ground cover. The required ground coverage must be achieved within two years from the date of planting.

Continuous screens along street frontages for vehicle use area must be as determined by Table 7.6.4-I. Provide appropriate screening.

Vegetation used to meet the screening standards is not included in the ground cover calculation as provided in Section 5-01.5.3, Calculation of Plant Growth Coverage.

Note: The maximum permitted height of a screen and vegetation is 30 inches within a sight visibility triangle (see Section 10-01.5.0, Sight Visibility, of the Technical Standards Manual). Trees may be planted within these areas in accordance with Section 5-01.0.0, Landscaping and Screening Standards.


Note: Except as otherwise provided by this section, the area between the right-of-way line and sidewalk and the area between the sidewalk and the curb, if not covered with vegetation, must be covered with an appropriate inorganic ground cover, such as decomposed granite.


Ensure that all Zoning and Engineering comments and concerns are addressed.

Additional comments may apply
12/22/2014 ANDREW CONNOR NPPO REVIEW Approved
12/22/2014 MICHAEL ST. PAUL ZONING REVIEW Reqs Change CDRC TRANSMITTAL

TO: Development Services Department
Plans Coordination Office

FROM: Michael St Paul
Planning Technician

PROJECT: DP14-0216
1801 North Oracle Road
Commercial Storage and Multi-Family Residential

TRANSMITTAL DATE: December 22, 2014

DUE DATE: December 24, 2014

COMMENTS: Please resubmit revised drawings along a response letter, which states how all Zoning Review Section comments regarding the Unified Development Code, The Administrative and Technical Manuals were addressed.

This plan has been reviewed for compliance with the Development Package Standards listed in section 2-06 of the City of Tucson Administrative Manual. Also compliance with applicable development criteria for the proposed use as listed in the City of Tucson Uniform Development Code (UDC).

The review comments include the actual standard first with the applicable Administrative Manual section number and the following paragraph is the actual comment related to the specific item that must be addressed. If you need to review the sections listed below click on the link or copy it in the address bar of your internet program. http://www.amlegal.com/nxt/gateway.dll/Arizona/tucson_az_udc/administrativemanual?f=templates$fn=default.htm$3.0$vid=amlegal:tucson_udc_az

This link will take you directly to the section used for the standards review. The UDC requirements are in the Unified Development Code and can be viewed at the same web link as above

1. Section 3.3.3.G.5.c UDC, An applicant has one year from the date of application to obtain approval of a site plan that complies with zoning and other development requirements in effect at the time of application, unless an ordinance adopted by Mayor and Council during this period states otherwise. A site plan application that has been in review for a period of one year and has not yet been approved is considered denied. To continue the review of a site plan for the property, a new site plan must be submitted that complies with regulations in effect at the time of re-submittal. The new submittal initiates a new one-year review period. One year Expiration date is .

2. SECTION 2-06.0.0: DEVELOPMENT PACKAGE (TENTATIVE PLATS AND SITE PLANS)
Section

2-06.1.0 GENERAL

2-06.2.0 APPLICATION SUBMITTAL REQUIREMENTS

2-06.3.0 FORMAT REQUIREMENTS

2-06.4.0 CONTENT REQUIREMENTS

2-06.1.0 GENERAL

2-06.1.1 PURPOSE
This standard has been prepared for the purpose of informing applicants of the submittal and review requirements for development package documents to assure proper and adequate information is presented in a consistent manner, thereby providing the basis for an efficient and timely review. The development package documents are prepared in support of applications for building permits and related reviews.

The information that is requested establishes the basis upon which the project will be approved and could affect what is required of the property in the future, should there be a proposal for expansion or for a different use of the property.

This standard does not waive any applicable city regulations or codes.

2-06.1.2 APPICABILITY
This standard shall be used for all site plans and tentative plats submitted to PDSD for review.

2-06.2.1 APPLICATION SUBMITTAL REQUIREMENTS
Development Package applications are available from PDSD. Completed applications and accompanying materials shall be submitted to PDSD. Incomplete or inaccurate applications will not be accepted, nor will any application in which the pre-application conference or neighborhood meeting requirements have not been met. The types of documents and the specific number of copies required of each of the documents are on the PDSD website or may be obtained from PDSD. Resubmittals of development packages require a comment response letter that details how all previous comments have been addressed. Provide the same number of copies of the comment response letter as plans provided.
The following documents and information shall be submitted upon application:

2-06.2.1 Application Form
A completed application signed by the property owner or authorized designee;

2-06.2.2 Development Package
A development package must be prepared to the format and content requirements described herein;

2-06.2.3 Related Reviews
In addition to the plan process, a project may require review for other types of plans and documents. The applications for those processes are submitted to the appropriate department for review and approval. These related reviews can be applied for so that review can occur concurrently with the development package application. However, it must be understood that, should the related application be approved subject to conditions or denied, this may affect the;

2-06.2.4 Concurrent Reviews
The development package is designed to allow for concurrent review of any site related reviews. Concurrent review means that all plans and documents needed for the review are submitted as one package. Examples of site related reviews include but are not limited to: site plans, landscape plans, NPPO plans, water harvesting plans, grading plans, SWPPP plans, floodplain use permits, and overlay reviews. Separate applications are often required for the different site related reviews even if the plans are submitted concurrently; and,

2-06.2.5 Fees
Fees in accordance with Section 4-01.0.0, Development Review Fee Schedule.

2-06.3.0 FORMAT REQUIREMENTS

2-06.3.1 - Each sheet shall measure 24 inches by 36 inches and include a minimum one inch margin on left side and one-half inch margin on all other sides to facilitate efficient record keeping. A larger sheet format may be used with the approval of the Planning and Development Services Department (PDSD).

2-06.3.2 - All mapped data shall be drawn at an engineering scale having no more than 50 feet to the inch. This scale is the minimum accepted to assure the plan will be legible during review and when digitized and/or reduced for record-keeping purposes. The same scale shall be used for all sheets within the set. Smaller scales (60:1 or greater) may be used for some or all of the sheets with the prior approval of PDSD when it is determined legibility and the ability to be digitized and/or reduced for archiving will not be affected.
2-06.3.3 - All lettering and text (upper or lower case), and numbering, shall be a minimum of three-thirty-seconds inches in height to assure the plan will be legible during review and when digitized and/or reduced for archiving.

2-06.3.4 - A title block shall be provided in the lower right quadrant of each sheet.

2-06.3.6 - Provide a blank three-inch by five-inch block in the lower right corner of the plan adjacent to the title block on the first sheet of the development package for use by Pima County Addressing.

1) COMMENT: Provide the block for addressing.

2-06.3.7 - A small, project-location map shall be provided in the upper right corner of the cover sheet.

2) COMMENT: See comments for project location map.

2-06.3.8 - The north arrow, contour interval, and scale as applicable to each sheet should be placed together in the upper right corner of each sheet.

2-06.3.10 - A legend that shows and describes all symbols used on the drawing is to be provided, preferably on the first sheet.

3) COMMENT: Provide a legend as described above (2-06.3.10) on the first sheet.

2-06.4.0 CONTENT REQUIREMENTS

2-06.4.1 - The name, mailing and email addresses, and phone number of the primary property owner of the site, the developer of the project, registrant(s), and other person(s), firm(s), or organization(s) that prepared the development package documents shall be provided on the right half of the cover sheet. The applicable registration or license number shall be provided if prepared by or with the assistance of a registered professional, such as a surveyor, architect, landscape architect, or engineer. All sealing shall be consistent with Arizona Board of Technical Registration guidelines.

4) COMMENT: Provide the address and email address for all of the above on the cover sheet.

2-06.4.2 - The title block shall include the following information and be provided on each sheet:

2-06.4.2.B - A brief legal description and a statement as to whether the project is a resubdivision are to be provided. On resubdivisions, provide the recording information of the existing subdivision plat;

5) COMMENT: Provide a grief legal description in the title block.


2-06.4.3 - The administrative street address and relevant case numbers (development package document, subdivision, rezoning, board of adjustment, DDO, MDR, DSMR, overlay, etc.) shall be provided adjacent to the title block on each sheet.

6) COMMENT: The project number (DP14-0216) and the address shall be adjacent to the title block.

2-06.4.4 - The project-location map to be located on the first sheet of the development package in the upper right corner, shall cover approximately one square mile, be drawn at a minimum scale of three inch equals one mile, and provide the following information.

7) COMMENT: Provide the project location map, as described above (2-06.4.4) in the upper-right corner of the cover sheet.

2-06.4.4.C - Section, township, and range; section corners; north arrow; and the scale will be labeled.

8) COMMENT: Provide the section corners and scale on, and with, the location map.

2-06.4.7 - General Notes
The following general notes are required. Additional notes specific to each plan are required where applicable.

2-06.4.7.A - Zoning and Land Use Notes

2-06.4.7.A.1 - List as a general note: "Existing zoning is ____."

9) COMMENT: Provide the note as quoted above on the cover sheet with C-2 as the zone.

2-06.4.7.A.2 - List the gross area of the site by square footage and acreage.

2-06.4.7.A.4 - Identify the existing and proposed use of the property as classified per the UDC. List all UDC sections applicable to the proposed uses.

10) COMMENT: The existing use is vacant. The proposed uses are commercial storage and multifamily residential (UDC Section 4.7.21, Table 4.8-4). The commercial storage has Use Specific Standard 4.9.10.A. Provide this information on the cover sheet. There is nothing on the plans to demonstrate compliance with an event center for special events. Remove this reference for the plans.

2-06.4.7.A.6 - If a plan or plat is prepared in conjunction with other applications or overlays or the parcel being developed is subject to conditions of an application processed previously, additional information must be added to the plan. Such applications and overlays include, but are not limited to: annexations; rezonings; special exceptions; Board of Adjustment variances; Design Development Options; Technical Standard Modification Request; overlays (Airport Environs Zone, Environmental Resource Zone, Gateway Corridor Zone, Hillside Development Zone, Historic Preservation Zone, Major Streets and Routes, Rio Nuevo District, Scenic Corridor Zone, WASH); Modification of Development Regulations through the Downtown Area Infill Incentive District or Rio Nuevo District; Downtown Heritage Incentive Zone; or, Design Review Board. Provide the following information on the plan.

11) COMMENT: Provide the Technical Standards Modification Request (DS14-32) information on the plan.

2-06.4.7.A.8 - For development package documents provide:

2-06.4.7.A.8.a - Floor area for each building;

12) COMMENT: Provide the floor area for each building.

2-06.4.7.A.8.d - When the proposed site is part of a larger site, the calculations encompass the entire site, whether existing or proposed. If the project is being phased, calculations must show that, at each phase, requirements are being met.

13) COMMENT: In this instance there are two principle uses on the site. Provide the calculations for each use, coverage, vehicle use and parking, and bicycle parking, on the site plan.

2-06.4.8 - Existing Site Conditions
The following information shall be provided on the plan/plat drawing to indicate the existing conditions on site and within 50 feet of the site. On sites bounded by a street with a width of 50 feet or greater, the existing conditions across the street will be provided.

2-06.4.8.B - All easements shall be drawn on the plan. The recordation information, location, width, and purpose of all easements on site will be stated. Blanket easements should be listed in the notes, together with recordation data and their proposed status. Should an easement not be in use and be proposed for vacation or have been abandoned, so indicate. However, should the easement be in conflict with any proposed building location, vacation of the easement shall occur prior to approval of plan unless written permission from easement holder(s) is/are provided.

14) COMMENT: Provide all the above easement information on the site plan. See the survey plan.

2-06.4.8.C - The following information regarding existing private or public right-of-way adjacent to or within the site shall be provided: the name, right-of-way width, recordation data, type and dimensioned width of paving, curbs, curb cuts, and sidewalks.

15) COMMENT: The future right-of-way is incorrect on sheet 2 of 13 (AC1) on the site plan. The future right-of-way is somewhat incorrect on the paving plan. The section line is also identified as the center line of Oracle Road on the paving and grading plan sheet 4 of 13 (C1). This is incorrect. See the street paving plans provided.

2-06.4.8.D - The following information regarding existing utilities shall be provided: the location and size of water wells, water pumping plants, water reservoirs, water lines, fire hydrants, sanitary and storm sewers, including the pipe diameter and the invert and rim elevations of all manholes and cleanouts; the Pima County Wastewater Management Department (PCWMD) reference number; locations of gas lines, electric and telephone lines, poles, and communications cables, on-ground junction boxes, and street lights. If water mains and sewers are not located on or adjacent to the tract, indicate the direction, distance to, and sizes of those nearest the property.
Identifying the locations of all utilities and service equipment immediately adjacent to the project is especially important in situations where pedestrian and vehicular access and circulation or landscaping can be in conflict. By knowing the location of the existing utilities, design of the project can take those elements into consideration and can help avoid expensive and time-consuming relocation of utilities, major redesign, or requests to vary regulations after commencement of construction.

16) COMMENT: Provide all the relevant utility information, as described above, on the site plan.

2-06.4.9 - Information on Proposed Development
The following information on the proposed project shall be shown on the drawing or added as notes.

2-06.4.9.F - All existing zoning classifications on and adjacent to the project (including across any adjacent right-of-way) shall be indicated on the drawing with zoning boundaries clearly defined. If the property is being rezoned, use those boundaries and classifications. The basis for this requirement is that some zoning requirements on a project are based on the zoning classification of adjacent property. Also, in some instances, each zone has to be taken into consideration on property that is split by two or more zoning classifications, as each may have different requirements.

17) COMMENT: Provide the zoning of the adjacent properties on the site plan.

2-06.4.9.H - Proposed Traffic Circulation

2-06.4.9.H.2 - Show future and existing sight visibility triangles. On a designated MS&R street, the sight visibility triangles are based on the MS&R cross-section.

18) COMMENT: Revise the sight-visibility triangles (SVTs) on the MS&R to match the correct F/ROW information on Oracle Road. Provide the SVTs for Lester driveway.

2-06.4.9.H.4 - Indicate if existing streets are public or private; provide street names, widths, curbs, sidewalks, and utility locations, all fully dimensioned.

2-06.4.9.H.5 - If utilizing parking area access lanes (PAALs), they shall be designed in accordance with Section 7.4.6, Motor Vehicle Use Area Design Criteria, of the UDC.

19) COMMENT: Dimension the PAAL and the driveways on the site plan. See comments concerning the gates from the engineering section and the Transportation Department.

2-06.4.9.H.5.a - Show all motor vehicle off-street parking spaces provided, fully dimensioned. As a note, provide calculations on the number of spaces required (include the ratio used) and the number provided, including the number of spaces required and provided for the physically disabled. The drawing should indicate parking space locations for the physically disabled. A typical parking space detail shall be provided for both standard parking spaces and those for the physically disabled. For information on parking requirements for the physically disabled, refer to adopted building and accessibility codes of the City of Tucson. Design criteria for parking spaces and access are located in Section 7.4.6, Motor Vehicle Use Area Design Criteria, of the UDC.

20) COMMENT: Provide the parking calculations for both the commercial storage and the multifamily residential uses. Use UDC Table 7.4.4-1 for the parking calculations for each use. Use the 2012 International Building Code; TABLE 1106.1 for the accessible parking requirements and calculations. Revise the parking calculations on the site plan.

2-06.4.9.H.5.c - Show all loading zones, vehicle maneuverability fully dimensioned, and access route. Provide as a note the number of loading spaces required, the number provided, whether the loading space is a Type A or B as provided in UDC Section 7.5.4.

21) COMMENT: Show the "vehicle maneuverability fully dimensioned, and access route" on the site plan. There appears to be no real access for the Type A loading space.

2-06.4.9.H.5.d - Show bicycle parking facilities fully dimensioned. For specifics, refer to Section 7.4.9, Bicycle Parking Design Criteria, of the UDC. Provide, as a note, calculations for short and long term bicycle spaces required and provided.

22) COMMENT: There are two uses for the bicycle parking as well. There are two (2) long-term and two (2) short-term bicycle parking spaces for the multifamily residential use (UDC Table 7.4.8-1). There are two (2) long-term and zero (0) short-term bicycle parking spaces required for the commercial storage use (UDC Table 7.4.8-1). Also see the bicycle parking design criteria (UDC Section 7.4.9 et al).

2-06.4.9.L - All proposed easements (utility, sewer, drainage, access, etc.) are to be dimensioned and labeled as to their purposes and whether they will be public or private. The easements may have to be recorded and the recordation information added to the development package prior to approval.

23) COMMENT: Provide all proposed easements, as described above (2-06.4.9.L), on the site plan.

2-06.4.9.O - All applicable building setback lines, such as erosion hazard, floodplain detention/retention basins, and zoning, including sight visibility triangles, will be shown.

24) COMMENT: Provide the SVTs for Lester Street and correct the ones for the MS&R along Oracle Road.

2-06.4.9.R - Show on-site pedestrian circulation and refuge utilizing location and the design criteria in Section 7-01.0.0, Pedestrian Access, of the Technical Standards Manual.

25) COMMENT: "Within all development, a continuous pedestrian circulation path is required" (TSM 7-01.3.3). "The areas within the development which must be connected include, but are not limited to, all buildings, all bicycle and vehicle parking areas, all recreation areas, all dumpster areas and all other common use areas" (TSM 7-01.3.3.B). Provide full pedestrian circulation on the site.

2-06.4.9.S - Show existing or proposed pedestrian circulation along abutting rights-of-way. Such sidewalks must comply with accessibility requirements for the physically disabled and the design criteria in Section 10-01.0.0, Street Technical Standards, of the Technical Standards Manual.

26) COMMENT: There are some inconsistencies between the plan for the ROW and the sidewalk areas along the ROWs.

2-06.4.9.T - Show refuse collection areas, including locations of dumpsters, screening location and materials, and vehicle maneuverability, fully dimensioned, and access route. If dumpster service is not proposed, indicate type of service. For specific information on refuse collection, refer to Section 8-01.0.0, Solid Waste and Recycle Disposal, Collection, and Storage, of the Technical Standards Manual. Refuse collection on all projects shall be designed based on that section, even if collection is to be contracted to a private firm.

27) COMMENT: See comments by the engineering section.

2-06.4.9.W - Indicate the locations and types of proposed signs (wall, free-standing, pedestal) to assure there are no conflicts with other requirements and that minimal locational requirements can be met. Indicate if there are any existing billboards on site. Compliance to the Sign Code, Chapter 3 of the Tucson Code, is required.

28) COMMENT: All signage must have separate permits. The main sign on the plan is in the future right-of-way.

2-06.4.9.X - Show compliance with landscaping and screening requirements by locations, material descriptions, and dimensions. Specific plant or hardscape material shall be detailed on a landscape plan. A detailed landscape plan is required. In accordance with Section 2-11.0.0, Landscape Plan Requirements.

29) COMMENT: See comments by the landscaping section.

If you have any questions about this transmittal, please call Michael St. Paul, (520) 837-4959.

RESUBMITTAL OF THE FOLLOWING IS REQUIRED: Revised development package site plan and any requested documents.

This site is located in the C-2 zone (UDC Section 4.7.21). There are two proposed uses. Both the multifamily residential and the commercial storage uses are allowed in this zone (UDC Table 8.4-4). The commercial storage has a Use Specific Standard (UDC Table 8.4-4). "Outdoor storage, when permitted, shall not be located in the street perimeter yard" (UDC Section 4.9.10.A.2). Add this note as quoted to the use section of the plans. See both comments by Transportation Department and engineering section for the proposed gate in the entrance along Oracle Road.

Remove all of the Land Use Code (LUC) references.

I have provided copies of the street paving plans with the return set of plans.
12/24/2014 ROBERT SHERRY PLUMBING-COMMERCIAL REVIEW Reqs Change The rim elevation of the next upstream sanitary manhole (2362.53') is higher than the first floor elevations (2360.37 - 2361.37'). Provide a note on the plans requiring the installation of a backwater valve when future plumbing activities take place. Floors discharging from more than 12" above the rim elevation of the next upstream sanitary manhole shall not discharge through the backwater valve. Reference: Section 715.1, IPC 2012, as amended by the City of Tucson.
12/24/2014 ELIZABETH LEIBOLD ENGINEERING REVIEW Reqs Change TO: Al Cornelio Jr, R.A., Kevin Hall, P.E.
DATE: December 24, 2014
SUBJECT: Engineering Review Development Package (SP/GP/SWPP) 1st submittal Engineering Review
LOCATION: 1801 N Oracle Rd T14S R13E Sec2, Ward 3
PROJECT: Warehouse/Residence
FLOODPLAIN: FEMA zone X-unshaded, 2276L
WATERSHED: Bronx Wash Watershed (TSMS DC) non-designated Basin Management Plan area
REVIEWER: Elizabeth Leibold, P.E.
PROJECT: DP14-0216, T14CM08052

SUMMARY: Engineering has reviewed Development Package for site plan and grading review including Drainage Report review. Engineering does not recommend approval of the Development Package at this time until the following comments are addressed.

MASTER COVER SHEETS/ GENERAL NOTES:
1) Admin Man Sec.2-06.4.7.6.a, B.2.b: List additional applications and overlays, by case number (including TSMR case DS14-32), in lower right corner of each sheet. As a general note provide the type of application processed or overlays applicable, a statement that the project meets the criteria/conditions of the additional application or overlay, the case number, date of approval, what was approved, and the conditions of approval, if any.

BASE LAYER SHEET COMMENTS:
2) Admin Man Sec.2-06.3: Add DP14-0216 case number to Development Package sheets.

SITE PLAN SHEET COMMENTS:
3) Admin Man Sec.2-06.4.4.B&C: Clarify project-location map on sheet G1.
a) The project-location map shall be located on the first sheet of the development package in the upper right corner;
b) Add scale (three inch equals one mile);
c) Scale appears to be 4"=1 mile but scale is labeled at 3"=1 mile. Required scale needs to be labeled as 3"=1 mile.
d) Identify major streets within the square mile area and all streets that abut the subject property;
e) Label section, township, and range, and section corners.
4) Admin Man Sec.2-06.4.8: Assure all existing utilities are shown and clearly labeled. Show and label new location for the existing light pole on planview.
5) Tucson Code 25-39: Address the following radii comments:
a) Existing radius of the Lester Oracle corner shall be revised on architectural sheets to accurately depict actual existing radius.
b) Development Package planview sheets shall be updated to match approved TSMR.
6) Tech Man. Sec.10-01.5.3: Revise Planview Keynote 13 to not include "basin".
7) UDC Sec.6.4.2.A.1: A development site with frontage on a street designated on the MS&R Plan shall be designed with sufficient width and depth so that motor vehicles can enter or leave the lot without backing out onto the MS&R street. There is a proposed gate at the MS&R side of project and Lester side. Backing up into the street for those vehicles not being able to open a locked gate causes potential for safety hazard and is not allowed on MS&R routes. Vehicular circulation restriction by the proposed gate at Oracle may need a variance, and may not be supported due to safety constraints. A revised design is needed for the project's layout if a gated is proposed.

DRAINAGE REPORT COMMENTS:
8) Tech Man Sec.4-04.2.3: Address the following drainage related comments:
a) Tech Man Sec.4-01.Exh.3.1: The proposed volume of waterharvesting shall be located within the site, not in the right-of-way. Clarify limits of waterharvesting area on site by revising exhibit Proposed Conditions Watershed Map and planviews in the Development Package sheets.
b) Tech Man Sec.4-03.3.5.1.3.a: Hydrologic type D-soils are indicated at site. Retention is not suitable for this site due to subsurface conditions listed in the Geotechnical Evaluation. Waterharvesting shall be carefully design, with positive gradients to assure drain down time of no more than 12 hours. Revise grading planview sheet to show positive gradients and any necessary bleed pipes or scuppers.
c) Update Report with date of 2nd submittal, label as 2nd submittal and add Development Package number to cover.

GRADING, PAVING, DETAIL SHEET COMMENTS:
9) Admin Man Sec.2-06.4.9.M.1, Tech Man Secs.2-01.4.1.C, 8-01.5.2.G: Address the following grading comments:
a) Clarify on cross sections and planviews how positive gradients and scuppers/outlets are provided for each waterharvesting area.
b) Label and depict on grading sheet planview a local Basis of Elevation.

UTILITIES / EASEMENTS COMMENTS:
10) Admin Man Sec.2-06.4.8.B, 2-06.4.9.L: All easements shall be drawn on the plan. The recordation information, location, width, and purpose of all easements on site will be stated. Blanket easements should be listed in the notes, together with recordation data and their proposed status. Should an easement not be in use and be proposed for vacation or have been abandoned, so indicate. However, should the easement be in conflict with any proposed building location, vacation of the easement shall occur prior to approval of plan unless written permission from easement holder(s) is provided. Assure complete information is provided for easements on the site. All proposed easements (utility, sewer, drainage, access, etc.) are to be dimensioned and labeled as to their purposes and whether they will be public or private. Any easements should be recorded and the recordation information added to the development package prior to approval.

STORMWATER POLLUTION PREVENTION PLAN COMMENTS:
11) No comment.

SOILS/GEOTECHNICAL REPORT COMMENTS:
12) Tech Man Sec.4-03.III.3.5.1.3.a: Provide one copy of the same soils report in next submittal.

Please provide a revised Development Package plan sheets, revised Drainage Report, SWPPP, Soils Report, and comprehensive response letter that address the comments provided above. If you have questions, call me at 837-4934.

Elizabeth Leibold, P.E., CPM, CFM
Civil Engineer
Engineering Division
Planning & Development Services Department

Final Status

Task End Date Reviewer's Name Type of Review Description
04/09/2015 AROMERO4 APPROVAL SHELF Completed
04/09/2015 AROMERO4 OUT TO CUSTOMER Completed
04/09/2015 CPIERCE1 REJECT SHELF Completed