This dataset maps out the boundaries for municipal jurisdictions in Pima County, Arizona. Jurisdictions include:City of TucsonTown of MaranaTown of Oro ValleyTown of SahuaritaCity of South TucsonPima CountyClick here to visit Pima County's Open Data site.PurposeThis layer was developed locate the municipal boundaries of jurisdictions in Pima County, Arizona.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is not in any known applications.Get Started with this Data• What is the largest incorporated jurisdiction by area?• Which incorporated jurisdiction has the longest boundary?• Which jurisdiction do I live in?Known Errors NoneContactPima CountyUpdate FrequencyAs Needed

Displays Speed Limit Ordinances for the City of Tucson. Created by copying features from stnetall.PurposeLine Layer that shows the speed limits of streets in Tucson.Dataset ClassificationLevel 0 - OpenKnown UsesUsed in Various Web MapsKnown ErrorsUrban streets from 12000 scale & rural streets from 100000 scale; 1/3 streets rectified to parcel base. 10/2013: While this layer is maintained as a Shapefile, the coverage format is still required for certain nightly processing. Data ContactDepartment of Transportation and MobilityUpdate FrequencyUpdated as needed

The ESZ is used to verify location in creating calls for service and to determine the proper responses for unit recommendations. Layer was created from the Fire Station Boundary polygon shapefile provided by Ann Moser. Edits were done to edge match with streets and other jurisdictional boundaries. Additional edits for splitting boundaries along N/S Broadway and Alpha Trucks.PurposeLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Dataset ClassificationLevel 0 - OpenKnown UsesFor CADKnown ErrorsLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Data ContactLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Update FrequencyOccasionally using ArcMap.Last known update: January 2012

COMPLETED 2010. The data was converted from the most recent (2010) versions of the adopted plans, which can be found at https://cms3.tucsonaz.gov/planning/plans/ Supplemental Information: In March 2010, Pima Association of Governments (PAG), in cooperation with the City of Tucson (City), initiated the Planned Land Use Data Conversion Project. This 9-month effort involved evaluating mapped land use designations and selected spatially explicit policies for nearly 50 of the City's adopted neighborhood, area, and subregional plans and converting the information into a Geographic Information System (GIS) format. Further documentation for this file can be obtained from the City of Tucson Planning and Development Services Department or Pima Association of Governments Technical Services. A brief summary report was provided, as requested, to the City of Tucson which highlights some of the key issues found during the conversion process (e.g., lack of mapping and terminology consistency among plans). The feature class "Plan_boundaries" represents the boundaries of the adopted plans. The feature class "Plan_mapped_land_use" represents the land use designations as they are mapped in the adopted plans. Some information was gathered that is implicit based on the land use designation or zones (see field descriptions below). Since this information is not explicitly stated in the plans, it should only be viewed by City staff for general planning purposes. The feature class "Plan_selected_policies" represents the spatially explicit policies that were fairly straightforward to map. Since these policies are not represented in adopted maps, this feature class should only be viewed by City staff for general planning purposes only. 2010 - created by Jamison Brown, working as an independent contractor for Pima Association of Governments, created this file in 2010 by digitizing boundaries as depicted (i.e. for the mapped land use) or described in the plans (i.e. for the narrative policies). In most cases, this involved tracing based on parcel (paregion) or street center line (stnetall) feature classes. Snapping was used to provide line coincidence. For some map conversions, freehand sketches were drawn to mimick the freehand sketches in the adopted plan. Field descriptions Field descriptions for the "Plan_boundaries" feature class: Plan_Name: Plan name Plan_Type: Plan type (e.g., Neighborhood Plan) Plan_Num: Plan number ADOPT_DATE: Date of Plan adoption IMPORTANT: A disclaimer about the data as it is unofficial. URL: Uniform Resource Locator Field descriptions for the "Plan_mapped_land_use" feature class: Plan_Name: Plan name Plan_Type: Plan type (e.g., Neighborhood Plan) Plan_Num: Plan number LU_DES: Land use designation (e.g., Low density residential) LISTED_ALLOWABLE_ZONES: Allowable zones as listed in the Plan LISTED_RAC_MIN: Minimum residences per acre (if applicable), as listed in the Plan LISTED_RAC_TARGET: Target residences per acre (if applicable), as listed in the Plan LISTED_RAC_MAX: Maximum residences per acre (if applicable), as listed in the Plan LISTED_FAR_MIN: Minimum Floor Area Ratio (if applicable), as listed in the Plan LISTED_FAR_TARGET: Target Floor Area Ratio (if applicable), as listed in the Plan LISTED_FAR_MAX: Maximum Floor Area Ratio (if applicable), as listed in the Plan BUILDING_HEIGHT_MAX Building height maximum (ft.) if determined by Plan policy IMPORTANT: A disclaimer about the data as it is unofficial. URL: Uniform Resource Locator IMPLIED_ALLOWABLE_ZONES: Implied (not listed in the Plan) allowable zones IMPLIED_RAC_MIN: Implied (not listed in the Plan) minimum residences per acre (if applicable) IMPLIED_RAC_TARGET: Implied (not listed in the Plan) target residences per acre (if applicable) IMPLIED_RAC_MAX: Implied (not listed in the Plan) maximum residences per acre (if applicable) IMPLIED_FAR_MIN: Implied (not listed in the Plan) minimum Floor Area Ratio (if applicable) IMPLIED_FAR_TARGET: Implied (not listed in the Plan) target Floor Area Ratio (if applicable) IMPLIED_FAR_MAX: Implied (not listed in the Plan) maximum Floor Area Ratio (if applicable) IMPLIED_LU_CATEGORY: Implied (not listed in the Plan) general land use category. General categories used include residential, office, commercial, industrial, and other.PurposeLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is intended to be used in the City of Tucson's Open Data portal and not for regular use in ArcGIS Online, ArcGIS Enterprise or other web applications.Known ErrorsLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Data ContactJohn BeallCity of Tucson Development Services520-791-5550John.Beall@tucsonaz.govUpdate FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

This dataset shows zip codes located in Pima County. The layer is maintained by Pima County, originally sourced from the US Postal Service zip code areas. Click here to visit Pima County's Open Data site.PurposeTo delineate zip codes within Pima CountyDataset ClassificationLevel 0 – OpenKnown UsesNoneKnown ErrorsMetropolitan boundaries are delineated well. Rural boundaries are extrapolated in some areas. Refer to US Postal Service for latest ZIP Code routes and for exact individual addresses. Zip codes defined by the US Postal Service as "unique", "military", and "post office box" are not included in this layer as they have no defined areas.ContactGISData@pima.govUpdate FrequencyAs Needed

The dataset includes approximate flood-hazard boundary areas prepared by both detailed and approximate methods. Study limits were defined using the highlighted drainage-problem areas shown on the city's zoning base maps as a guide. Floodplain studies completed and sealed in 2007 and 2008. The highlighted drainage problem areas shown on the city's zoning base maps did not distinguish between FEMA flood plains and problem areas approximated either from drainage complaints or from information included in subdivision/development drainage studies.PurposeLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is intended to be used in the City of Tucson's Open Data portal and not for regular use in ArcGIS Online, ArcGIS Enterprise or other web applications.Known ErrorsLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Data ContactLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Update FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

COMPLETED 2010. The data was converted from the most recent (2010) versions of the adopted plans, which can be found at https://cms3.tucsonaz.gov/planning/plans/Supplemental Information: In March 2010, Pima Association of Governments (PAG), in cooperation with the City of Tucson (City), initiated the Planned Land Use Data Conversion Project. This 9-month effort involved evaluating mapped land use designations and selected spatially explicit policies for nearly 50 of the City's adopted neighborhood, area, and subregional plans and converting the information into a Geographic Information System (GIS) format. Further documentation for this file can be obtained from the City of Tucson Planning and Development Services Department or Pima Association of Governments Technical Services. A brief summary report was provided, as requested, to the City of Tucson which highlights some of the key issues found during the conversion process (e.g., lack of mapping and terminology consistency among plans). The feature class "Plan_boundaries" represents the boundaries of the adopted plans. The feature class "Plan_mapped_land_use" represents the land use designations as they are mapped in the adopted plans. Some information was gathered that is implicit based on the land use designation or zones (see field descriptions below). Since this information is not explicitly stated in the plans, it should only be viewed by City staff for general planning purposes. The feature class "Plan_selected_policies" represents the spatially explicit policies that were fairly straightforward to map. Since these policies are not represented in adopted maps, this feature class should only be viewed by City staff for general planning purposes only.2010 - created by Jamison Brown, working as an independent contractor for Pima Association of Governments, created this file in 2010 by digitizing boundaries as depicted (i.e. for the mapped land use) or described in the plans (i.e. for the narrative policies). In most cases, this involved tracing based on parcel (paregion) or street center line (stnetall) feature classes. Snapping was used to provide line coincidence. For some map conversions, freehand sketches were drawn to mimick the freehand sketches in the adopted plan. Field descriptionsField descriptions for the "Plan_boundaries" feature class: Plan_Name: Plan name Plan_Type: Plan type (e.g., Neighborhood Plan) Plan_Num: Plan number ADOPT_DATE: Date of Plan adoption IMPORTANT: A disclaimer about the data as it is unofficial. URL: Uniform Resource Locator Field descriptions for the "Plan_mapped_land_use" feature class: Plan_Name: Plan name Plan_Type: Plan type (e.g., Neighborhood Plan) Plan_Num: Plan number LU_DES: Land use designation (e.g., Low density residential) LISTED_ALLOWABLE_ZONES: Allowable zones as listed in the Plan LISTED_RAC_MIN: Minimum residences per acre (if applicable), as listed in the Plan LISTED_RAC_TARGET: Target residences per acre (if applicable), as listed in the Plan LISTED_RAC_MAX: Maximum residences per acre (if applicable), as listed in the Plan LISTED_FAR_MIN: Minimum Floor Area Ratio (if applicable), as listed in the Plan LISTED_FAR_TARGET: Target Floor Area Ratio (if applicable), as listed in the Plan LISTED_FAR_MAX: Maximum Floor Area Ratio (if applicable), as listed in the Plan BUILDING_HEIGHT_MAX Building height maximum (ft.) if determined by Plan policy IMPORTANT: A disclaimer about the data as it is unofficial. URL: Uniform Resource Locator IMPLIED_ALLOWABLE_ZONES: Implied (not listed in the Plan) allowable zones IMPLIED_RAC_MIN: Implied (not listed in the Plan) minimum residences per acre (if applicable) IMPLIED_RAC_TARGET: Implied (not listed in the Plan) target residences per acre (if applicable) IMPLIED_RAC_MAX: Implied (not listed in the Plan) maximum residences per acre (if applicable) IMPLIED_FAR_MIN: Implied (not listed in the Plan) minimum Floor Area Ratio (if applicable) IMPLIED_FAR_TARGET: Implied (not listed in the Plan) target Floor Area Ratio (if applicable) IMPLIED_FAR_MAX: Implied (not listed in the Plan) maximum Floor Area Ratio (if applicable) IMPLIED_LU_CATEGORY: Implied (not listed in the Plan) general land use category. General categories used include residential, office, commercial, industrial, and other.PurposeLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Dataset ClassificationLevel 0 - OpenKnown UsesLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Known ErrorsLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Data ContactJohn BeallCity of Tucson Development Services520-791-5550John.Beall@tucsonaz.govUpdate FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

ward_cot displays the six city council districts in the City of Tucson. Ward area legal boundaries are based on Pima County voting precinct legal boundaries. Last updated September 19, 2023.PurposeShows the six wards of the City of Tucson and the respective councilmembers elected them.Dataset ClassificationLevel 0 - OpenKnown Uses--Known Errors--Data ContactCity of Tucson Information Technology Department, GIS Services, GIS_IT@tucsonaz.govUpdate FrequencyUpdated as new annexation or redistricting occurs.

Status: UPDATED occasionally using ArcMap Contact: Michael Liberti, Tucson Water, 520-837-2226, Michael.Liberti@tucsonaz.gov Intended Use: Primary data record of service area boundaries. Not intended for map display unless approved by data owner. Known errors/qualifications This is a rough approximation of the obligated areas served by Tucson Water and some errors may exist especially in those areas outside the City of Tucson limits. Does not include the non-potable service area boundaries. The non-potable water system includes all water types that have not been treated to potable standards: reclaimed water lines, raw CAP mains from the canal, secondary effluent piped from the County treatment plant to the Roger Road reclaimed plan, TARP water in the mains between the recovery wells and the treatment plant and the CAVSARP recovery wellfields. Boundaries may overlap other water company service area boundaries because their definition of the boundaries may vary.***SERVED = The parcel has a TW water meter and is consuming water.***OBLIGATED = Either 1) a vacant parcel inside the City of Tucson that does not have a TW meter, or 2) a vacant/abandoned parcel that has a meter, but is not consuming water. ***COMMITTED = a parcel outside the City of Tucson that 1) is in an area of intergovernmental contractual agreement (e.g. Dove Mountain/Continental Ranch...) 2) is a master planned development for which TW previously granted a service agreement (will have a corresponding GREENLINE feature) 3) is under 20 acres and is located adjacent to a delivery pipe and is served on three sides 4) a Tucson Unified School District parcel ***NOT OBLIGATED = Call Tucson Water Development Services for clarification. ALSO NOTE THAT PIPELINE RIGHT-OF-WAYS OUTSIDE TUCSON ARE ALSO COMMITTED (NO PARCEL) So, a parcel can be committed by contract, by prior approval or by location Individuals that live outside Tucson who are not currently served by TW fall under #3. Unless directed otherwise by Tucson Water, by default any parcel outside the City of Tucson that does not have a Tucson Water meter will NOT be served unless they annex. Replaces ObligatedServiceArea feature class formerly maintained in VMDB. The name ObligatedServiceArea is still used, but now is just a filtered view of ServiceArea. September 2010 - loaded ServiceArea shapefile into EDITSDE geodatabase to be maintained as feature class instead of shapefile. Renamed to ServiceArea. ObligatedServiceArea becomes a view of the ServiceArea feature class. sdetable -o create_view -T OBLIGATEDSERVICEAREA -t SERVICEAREA -w "SA_TYPE in ('SERVED','OBLIGATED','COMMITTED')" -c "OBJECTID,SHAPE,SA_TYPE,SA_SUBTYPE,REC_DATE,INSTALLYEAR" -i sde:sqlserver:pw-sql2005 -D editsdeAugust 2010 - ObligatedServiceArea criteria is redefined based on decisions by Mayor and Council. New shapefile called ServiceArea becomes the data of record.10/10/2008 Bryn Enright Copy of most recent Obligated Service Area provided to John Regan from Pima County to post in the GIS Library and MapGuide site.10/10/2008 Bryn Enright Renamed the feature class from admin.ObligatedServiceArea to admin.ObligatedServiceAreaHistory. The most current area will be made available in a new database view called admin.ObligatedServiceArea.10/10/2008 Bryn Enright "Appended the most recent obligated service area created by Michael Liberti which was created by:1. Dissolving the current service area (req_SA_current.shp) with committed areas outside the city (dove mtn, larry's marana, diamond bell, corona de tucson...)2. Erased the city polygon (LIMJURIS) from the dissolve.3. Added the entire city polygon back in (i.e. obligated area) but then erased all of the ""water providers"" with CCNs ('56' water right)." In = req_SA_obligated.shp Out = ADMIN.ObligatedServiceAreaJune 2008 Bryn Enright Shapefile imported into Geodatabase (EMAPDB) In = Req_ServiceArea_v1.shp Out = ObligatedServiceAreaJune 2008 Michael Liberti Layer dissolved to show only 1 polygon for obligated area. In = ServiceArea_v1.shp Out = Req_ServiceArea_v1.shpJune 2008 Michael Liberti Layer updated with new services and existing remote services that were not previously included.February 2008 Michael Liberti Layer updated with new services for the 2008 Update to the Water Plan 2000-2050November 2004 Michael Liberti "Modified PCLIS WATERCOS as collection of PARCELS intersecting SERVICES by M Liberti. Layer created for use in the Water Plan 2000-2050" In=PCLIS WATERCOS Out=ServiceArea_v1.shp Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Lorem ipsum dolor sit amet consectetur adipiscing elit. Massa enim nec dui nunc. Quis commodo odio aenean sed adipiscing diam donec adipiscing. Nulla pellentesque dignissim enim sit amet venenatis urna. Sit amet volutpat consequat mauris nunc congue nisi vitae. Fames ac turpis egestas maecenas pharetra convallis posuere morbi leo. Morbi tristique senectus et netus et malesuada fames ac turpis. Eget lorem dolor sed viverra ipsum nunc. Id ornare arcu odio ut sem. Morbi leo urna molestie at elementum eu. In metus vulputate eu scelerisque. Lobortis mattis aliquam faucibus purus in massa tempor nec feugiat. Ut sem viverra aliquet eget sit amet tellus cras adipiscing. Lobortis mattis aliquam faucibus purus in massa tempor. Donec massa sapien faucibus et molestie ac feugiat. Et odio pellentesque diam volutpat commodo sed egestas egestas. Pharetra magna ac placerat vestibulum lectus. Fermentum leo vel orci porta non pulvinar neque laoreet suspendissePurposeLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Dataset ClassificationLevel 0 - OpenKnown UsesLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Known ErrorsLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Data ContactLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Update FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Displays the smallest unit in the Public Land Survey System; Township/Ranges are subdivided into 36 Sections; each Section is approximately one square mile. These polygons are maintained in the Parcel Fabric. This layer has been adjusted to Section corner data from the GIS parcel Section Auto CAD drawings. It also includes the half Township South of 12S14E Sections 31-34, designated as 12F14E (field TR). TOWNSHIP and RANGE field values are four characters where the last two characters indicate the direction where 01 is North, 02 is East, 03 is South and 04 is West.https://gis.pima.gov/data/contents/metadet.cfm?name=trsPurposeLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Dataset ClassificationLevel 0 – OpenKnown UsesLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Known ErrorsThe Canoa Land Grant area is not part of the Public Land Survey System. The trs layer includes sections in the Canoa Land Grant area as if it had been included in the survey.2021 - This layer contains a Stated Area field in square miles. This is a GIS calculated estimate and should not be used in place of official stated areas from the original documents.Contactgisdata@pima.govUpdate FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

A copy of located in editsde for backup purposes. The dataset includes approximate flood-hazard boundary areas prepared by both detailed and approximate methods. Study limits were defined using the highlighted drainage-problem areas shown on the city's zoning base maps as a guide. Floodplain studies completed and sealed in 2007 and 2008 . Shape files created April 2011. Shape files exported from Autodesk Map 3D 2006 and projected using ArcMap 10. Maintenance and frequency to be determined by City of Tucson, Planning and Development ServicesReplace feature class "dsdFHZStudy2007CrossSections" See feature class "cotFloodHazardsPurposeLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is intended to be used in the Open Data portal and not for regular use in ArcGIS Online and ArcGIS Enterprise.Known ErrorsLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Data ContactLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Update FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

The dataset includes approximate flood-hazard boundary areas prepared by both detailed and approximate methods. Study limits were defined using the highlighted drainage-problem areas shown on the city's zoning base maps as a guide. Floodplain studies completed and sealed in 2007 and 2008 . Shape files created April 2011. Shape files exported from Autodesk Map 3D 2006 and projected using ArcMap 10.PurposeThis layer is intended to be used in the Open Data portal and not for regular use in ArcGIS Online and ArcGIS Enterprise.Dataset ClassificationLevel 0 - OpenKnown UsesLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Known ErrorsLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Data ContactLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Update FrequencyMaintenance and frequency to be determined by City of Tucson, Planning and Development Services.

fp_lomxb displays area boundaries in which the floodplain data has been revised by Letter Of Map Revision (LOMR).This layer is maintained by Pima County. Click here to visit Pima County's Open Data site. Click here to visit Pima County's GIS Library metadata. PurposeThis layer was developed to show Floodplain Areas of Revision in Pima County, Arizona.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is not in any known applications.Known Errors Many of the revision area boundaries were digitized from paper copies or screen digitized using the FIRM panel as a reference.12/2013: While this layer is maintained as a Shapefile, the coverage format is still required for certain nightly processing. See Steve Whitney. - FEMA floodplain data extraction processContactPima County - GISdata@pima.govUpdate FrequencyAs Needed

Created by Johanna Kraus September 2012. Historic and Neighborhood Preservation areas just copied from ZONE_COT layer. UOD-1 from area_zonePurposeThis layer is intended to be used in the Open Data portal and not for regular use in ArcGIS Online and ArcGIS Enterprise.Dataset ClassificationLevel 0 - OpenKnown UsesLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Known ErrorsLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Data ContactJohanna.Kraus@tucsonaz.govUpdate FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

This map was created to provide a link to significant projects that are in an "active" status, meaning that the work is visible to the community, in the case of permits, or that community members had an opportunity to provide input through various means, in the case of special approvals.“BY RIGHT” PERMITSWhat are “By Right” Permits?By Right permits, which are also referred to as ministerial permits or simply permits, are granted if the proposed project complies with established standards set forth in the City of Tucson’s Unified Development Code (UDC) and the accompanying Technical Standards. These permits, since they are not discretionary, are not subject to public review, are reviewed by PDSD staff for compliance with the code and standards, and are issued administratively by PDSD staff. For what period of time are permits shown on the Activity Map?Permits are shown on the Development Activity Map from the time PDSD issues a permit to the applicant until the work authorized by the permit is considered complete. In general, this period corresponds to the time in which physical activity, such as grading, paving, landscaping, and construction, and the related inspections, occur. Each permit on the Map has an associated project status between work authorization and completion. Definitions of each of these "active" statuses can be found here.What kinds of permits are not shown on the Activity Map?PDSD issues around 10,000 permits a year, many for small activities that are have little to no visibility or impact outside the property in question. Because there are so many permits for projects such as solar installations, water heater replacements, installation of fences or walls, and installations of pools and spas, these permits are excluded from the Map. For more information on all activities associated with a specific property, go to Property Research Online.A list of all the permits shown on the Development Activity Map can be found here.SPECIAL APPROVALSWhat are special approvals?Special approvals, which are also referred to as “discretionary decisions,” are granted at the discretion of an authorized decision maker -- such as the PDSD Director; an appointed Board, Committee, or Commission; the Zoning Examiner; Board of Adjustment; and/or the Mayor and Council -- and include public notification. A special approval may be needed for a variety of reasons, such as if the proposed project is not consistent with underlying zoning for the property, is deviating from regulations found in the City Unified Development Code, or does not comply with the requirements of a designated special district, such as an Historic Preservation Zone. For what period of time are special approvals shown on the Development Activity Map?Projects requiring special approvals and public notification are shown on the Development Activity Mapfrom the time PDSD receives the project application and remain throughout the public review process. Each special approval on the Map has an associated project status between application and approval (projects are removed from the Map once the final approvals for the project are obtained). Definitions of each of these "active" statuses can be found here.What kinds of special approvals are not shown on the Activity Map?Some special approvals are approved administratively by the PDSD Director and do not require review by an advisory body or public notification. These approvals consist almost exclusively of minor replacement of equipment on existing cell towers, for which public notification is not required. For more information on all activities associated with a specific property, go to Property Research Online.A list of all special approvals shown on the Development Activity Map can be found here.

Plan submitted by: WBeard on 10/21/2021 USER DESCRIPTION: The areas of Arizona City/Eloy and South Casa Grande have a greater community of interest being in the same district as Marana (CD 6 on map) than with Yuma. The population balance is created by adjusting the amount of the City of Tucson within CD 7 on this map. USER PLAN OBJECTIVE: The area east of Tohono reservation in Pinal County (ELoy/S Casa Grande/AZ City) have more in common with Marana than with Yuma. Population balanced in City of Tucson. Maintains more communities of interest and doesn't affect VRA requirements.

Plan submitted by: WBeard on 11/7/2021 USER DESCRIPTION: Applies the comments from Mayor Romero of Tucson regarding placing Tucson within the SW Arizona District #7. Balances this by including areas of SE Pima County and Santa Cruz to maintain communities of interest and balance population. Maintains competitiveness and VRA compliance. USER PLAN OBJECTIVE: Corrects approved CD map to comply with the requests of Mayor Romero regarding the City of Tucson be included with D7. Uses River Rd and Pantano Creek as northern and eastern boundaries of D7. Balances population by adding communities of interest in SE Pima County (Green Valley/Corona de Tucson/Sahurita) and northern/eastern Santa Cruz County. Places David Monthan AFB inside D6 to comply with request of the military. Maintains communities of interest and VRA compliance. Also maintains competitiveness.

This web map contains the new Hybrid Reference Layer vector tile layer, which is designed to be used to overlay imagery. The vector tile layer is similar in content and style to the popular Imagery with Labels map, which is delivered as a map service with raster tiles, with additional labels for transportation features.The 'Imagery with Labels' basemap contains the World Imagery map service and the World Boundaries and Places map service, so when you use that basemap you get boundaries and places, but you don't get highways and streets at small scales or street labels at large scale.If you prefer a map that uses raster tiles for both boundary and transportation features, you can use the Imagery with Labels and Transportation map.

Plan submitted by: arizconway@msn.com on 10/5/2021 USER DESCRIPTION: N/A USER PLAN OBJECTIVE: This Map is intended meet all the requirements of Proposition 106 with special emphasis on Communities of Interest and County lines, City and Town limits and Native American Community boundaries. No Native American Communities are split. The Northern Arizona urban area including Flagstaff and Prescott are in a single District. Phoenix is included in six Phoenix only Districts, Mesa in two Mesa only Districts, Tucson in two Tucson only Districts, and Glendale in one Glendale only District. Yuma is in a one District. Marana and the Catalina Foothills are separated from Tucson. Sun City and Sun City West are in the same District.

Plan submitted by: WBeard on 11/1/2021 USER DESCRIPTION: The areas including Eloy/South Casa Grande/Arizona City have more in common with the remaining parts of Pinal County than with Yuma or SW Arizona. The areas of Corona de Tucson/Green Valley and Rita Ranch have historically been associated with a SE Arizona district and should remain so. These communities of interest have more in common with SE AZ than they do with SW AZ. USER PLAN OBJECTIVE: The areas including Eloy/South Casa Grande/Arizona City have more in common with the remaining parts of Pinal County than with Yuma or SW Arizona. The areas of Corona de Tucson/Green Valley and Rita Ranch have historically been associated with a SE Arizona district and should remain so. These communities of interest have more in common with SE AZ than they do with SW AZ. Have included more areas within the City of Tucson, including the University of AZ with D7 to balance the map. This maintains competitiveness and enhances communities of interest.