Microfiche records prior to 2006 have not been completely digitized and may not be available yet on PRO. If you can not find what you are looking for please submit a records request.
Permit Review Detail
Review Status: Requires Resubmit
Review Details: DEVELOPMENT PACKAGE REVIEW v.2
Permit Number - DP22-0210
Review Name: DEVELOPMENT PACKAGE REVIEW v.2
Review Status: Requires Resubmit
| Review Date | Reviewer's Name | Type of Review | Description | Status | Comments |
|---|---|---|---|---|---|
| 12/09/2022 | CDRC Post Review | PENDING ASSIGNMENT | |||
| 12/09/2022 | Site Engineering | REQUIRES RESUBMIT | 1. The following comment was not addressed: Clearly show the required 1-foot setback of the canopies from the edge of the PAAL. 2. Address all zoning comments regarding development package content requirements Scott Haseman scott.haseman@tucsonaz.gov |
||
| 11/23/2022 | Site Zoning | REQUIRES RESUBMIT | CDRC TRANSMITTAL TO: Development Services Department Plans Coordination Office FROM: Paul Camarena PDSD Zoning Review Section PROJECT: 4040 N ORACLE RD Development Package (1st Review) DP22-0210 TRANSMITTAL DATE: November 23, 2022 COMMENTS: Please resubmit revised drawings and any redlined plans along with a detailed response letter, which states how all Zoning Review Section comments were addressed. 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 August 03, 2023 . SECTION 2-06.0.0: DEVELOPMENT PACKAGE (TENTATIVE PLATS AND SITE PLANS) Comment: Remove the aerial image from the site plan. 2-06.3.0 FORMAT REQUIREMENTS 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. 1. COMMENT: 2-06.3.2 - This comment is applicable 2-06.3.4 - A title block shall be provided in the lower right quadrant of each sheet. 2. COMMENT: 2-06.3.4 - This comment is applicable 2-06.3.7 - A small, project-location map shall be provided in the upper right corner of the cover sheet. 3. COMMENT: 2-06.3.7 - This comment is applicable 2-06.3.9 - The plan drawing shall be oriented with north toward the top of the sheet. If it is not practical to orient north to the top of the sheet, the plan drawing shall be oriented with north to the left side of the sheet. 4. COMMENT: 2-06.3.9 - This comment is applicable 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. 5. COMMENT: 2-06.3.10 - This comment is applicable 2-06.3.12 - An index of sheets in the development package shall be provided on the first sheet. 6. COMMENT: 2-06.3.12 - This comment is applicable 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. 7. COMMENT: 2-06.4.1 - This comment is applicable 2-06.4.2 - The title block shall include the following information and be provided on each sheet: 2-06.4.2.A - The proposed name of the project or subdivision, or if there is no name, the proposed tenant's name; 8. COMMENT: 2-06.4.2.A - This comment is applicable 2-06.4.2.B - A brief legal description and a statement as to whether the project is a re-subdivision are to be provided. On re-subdivisions, provide the recording information of the existing subdivision plat; 9. COMMENT: 2-06.4.2.B - This comment is applicable 2-06.4.2.D - The page number and the total number of pages in the package (i.e., sheet xx of xx). 10. COMMENT: 2-06.4.2.D - This comment is applicable 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. 11. COMMENT: 2-06.4.3 - Provide the development package case number, DP22-0210, adjacent to the title block on each sheet. 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. 12. COMMENT: 2-06.4.4 - This comment is applicable 2-06.4.4.A - Show the subject property approximately centered within the one square mile area; 13. COMMENT: 2-06.4.4.A - This comment is applicable 2-06.4.4.B - Identify major streets and regional watercourses within the square mile area and all streets that abut the subject property; and, 14. COMMENT: 2-06.4.4.B - This comment is applicable 2-06.4.4.C - Section, township, and range; section corners; north arrow; and the scale will be labeled. 15. COMMENT: 2-06.4.4.C - This comment is applicable 2-06.4.5 - When the development package documents consists of more than one sheet, a sheet index (a legible drawing of the site showing the area represented on each sheet) is to be placed on the cover sheet or the second sheet. 16. COMMENT: 2-06.4.5 - This comment is applicable 2-06.4.7 - General Notes The following general notes are required. Additional notes specific to each plan are required where applicable. Zoning and Land Use Notes 2-06.4.7.A.1 - List as a general note: "Existing zoning is ____." 17. COMMENT: 2-06.4.7.A.1 - This comment is applicable 2-06.4.7.A.2 - List the gross area of the site/subdivision by square footage and acreage. 18. COMMENT: 2-06.4.7.A.2 - This comment is applicable 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. 19. COMMENT: 2-06.4.7.A.4 - This comment is applicable 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. COMMENT: 2-06.4.7.A.6 - As oracle and roger rd is designated as an Arterial on the COT MS&R map, provide a general note on the cover sheet stating “THIS PROJECT IS DESIGNED TO MEET THE OVERLAY ZONE(S) CRITERIA, UDC ARTICLE 5.4 MAJOR STREETS AND ROUTES SETBACK ZONE (MS&R)” 2-06.4.7.A.8 - For development package documents provide: 2-06.4.7.A.8.c - Percentage of building, lot area, or vehicular use area expansion. If the building(s) or lot area have been previously expanded, those calculations shall be included; and, 20. COMMENT: 2-06.4.7.A.8.c - This comment is applicable 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.A - Provide site boundary/subdivision perimeter information, including bearing in degrees, minutes, and seconds, with basis for bearing noted, together with distances in feet, to hundredths of a foot, or other functional reference system. 21. COMMENT: 2-06.4.8.A - This comment is applicable 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 provided. 22. COMMENT: 2-06.4.8.B - This comment is applicable 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. 23. COMMENT: 2-06.4.8.C - This comment is applicable 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.A - Draw in all proposed lot lines with approximate distances and measurements. 24. COMMENT: 2-06.4.9.A - This comment is applicable 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. 25. COMMENT: 2-06.4.9.F - This comment is applicable 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. 26. COMMENT: 2-06.4.9.H.2 - This comment is applicable 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. 27. COMMENT: 2-06.4.9.H.4 - This comment is applicable 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. 28. COMMENT: 2-06.4.9.H.5 - This comment is applicable - 2-06.4.9.Q - Provide the square footage and the height of each commercial, industrial, or business structure and the specific use proposed within the footprint of the building(s). 29. COMMENT: 2-06.4.9.Q - This comment is applicable 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. 30. COMMENT: 2-06.4.9.R - This comment is applicable 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. 31. COMMENT: 2-06.4.9.S - This comment is applicable ***For additional information on the any standard presented in this memo, please refer to the City of Tucson “Unified Development Code” – Administrative Manual Section 2-06 or Technical Standards noted in the comments. https://www.tucsonaz.gov/pdsd/all-codes-plans-determinations To resubmit your plans for additional review, please visit: https://docs.tucsonaz.gov/Forms/tucsonpermitapp If you have any questions about this transmittal, Contact Paul Camarena at (520)837-4986 or by email Paul.Camarena@tucsonaz.gov RESUBMITTAL OF THE FOLLOWING IS REQUIRED: Revised development package |