ADPARCEL displays parcel-based addresses, including multiple addresses per parcel when parcels have more than one address. Addresses are derived from address codes, 0,7,8, and 9 in ADR_PIMA, then overlaid with parcels to gather parcel-related attributes.Click here to visit Pima County's Open Data site.PurposeThis layer was developed locate addresses in Pima County, Arizona.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is not in any known applications.Known Errors Address points from ADR_PIMA do not represent precise locations of buildings and are intended only to represent a general location within a particular parcel.ContactPima CountyUpdate FrequencyAs Needed

Zipped raster dataset of 2018 Land-Use-Land-Cover (named pima_landcover_noroads.zip)Download this zipped dataset here by clicking the download button at top right.https://gis.pima.gov/data/contents/metadet.cfm?name=lulc18

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 suspendisse.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 ErrorsParcels are derived from the Pima County Parcel Fabric. A relatively small number of parcels have more than one polygon per parcel, which are displayed as multi-part polygons with a total area for all polygon parts. Subdivision common areas are typical example of where you will find multi-part polygons. Roadway areas that are not assigned a tax code by the Assessor are "True Void" areas, having no polygon or attributes. These include a major portion of county street areas. However, private street areas will have assigned tax codes, attributes, and polygonal shape. The ADDRESS_OL field contains the situs address. ADDRESS_OL only includes situs addresses that have a one-parcel to one-situs address relationship as indicated by an ADR_STATUS field value of "ONE". ADRRESS_OL values that are null or blank mean that the parcel has either no situs address or multiple situs addresses as indicated by ADR_STATUS field values of "NONE" or "MULTIPLE" respectively. The MAIL1 through MAIL5 fields contain the owner name and mailing address. The Full Cash Initial Amount Value, and the Limited Net Assessed (Taxable) Value are displayed for analysis and are not reflective of the Market Value.Contactgisdata@pima.govUpdate FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

https://gis.pima.gov/data/contents/metadet.cfm?name=pcgprsbm***Note: overlapping data is present, and attention needs to be paid to dates on the instruments. Any questions should be addressed to transsyseim@pima.gov.***

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

https://gis.pima.gov/data/contents/metadet.cfm?name=fp_ss***Download shapefile of this dataset here. (Normal download using button on Geospatial Data Portal item details page won't be successful.)***

The Hydrologic Soils Group Map was derived from the soil survey shape files obtained from Soils Datamart (https://sdmdataaccess.nrcs.usda.gov/) which were joined with an appropriate attribute table (derived from the component file ‘comp.txt’ and the mapping unit attribute file) which was distributed with the digital release of the soil surveys. See more information.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 hydrologic soils groups in Pima County, Arizona.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is not in any known applications.Known Errors No known errorsContactPima County - GISdata@pima.govUpdate FrequencyAs Needed

https://gis.pima.gov/data/contents/metadet.cfm?name=pcgpraqm***Note: overlapping data is present, and attention needs to be paid to dates on the instruments. Any questions should be addressed to transsyseim@pima.gov.***

The Digital Geologic Map of the Tucson Mountains Caldera, Arizona is composed of GIS data layers, two ancillary GIS tables, a Windows Help File with ancillary map text, figures and tables, GIS data layer and table FGDC metadata and ArcView 3.X legend (.AVL) files. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). All GIS and ancillary tables were produced as per the NPS GIS-Geology Coverage/Shapefile Data Model (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as coverage and table export (.E00) files, and as a shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 12N. That data is within the area of interest of Saguaro National Park.

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.

ADFACIL displays facilities-based addresses as derived from codes 1 through 6 in adr_pima, then overlaid with parcels to populate parcel-related attributes.Click here to visit Pima County's Open Data site.PurposeThis layer was developed to locate facility addresses in Pima County, Arizona.Dataset ClassificationLevel 0 - OpenKnown UsesThis layer is not in any known applications.Known Errors Facility addresses do not include all utility addresses as tracking started in 1998. Facility address points do not represent precise locations of facilities and are intended only to represent a general location within a particular parcel.ContactPima County - GISdata@pima.govUpdate FrequencyAs Needed

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.

This is the 2017 version of the AVCA administrative boundary. It generally follows the previous (2000) boundary with the following modifications. Priority of drawing went first to the Pima County Parcel map, then to the NHD watershed boundary, and finally to Santa Cruz Parcels. Essentially, the original was cleaned up by following existing 3rd party shapes from the USG, Pima County, and Santa Cruz county. For frequent requests, please direct inquiries to the service endpoint located below or to a shapefile located here: https://avca.maps.arcgis.com/home/item.html?id=65d1c58205064196841da533169cb287

This is the City of Tucson's public platform for exploring and downloading open data, discovering and building apps, and engaging to solve important local issues. You can analyze and combine Open Datasets using maps, as well as develop new web and mobile applications. Let's make our great community even better, together!

Boundaries of subdivisions in Pima County.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 FrequencyLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

This website features Story Maps designed and written by various departments across the City. See what stories we're most excited about telling.

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

Status: NOT MAINTAINEDContact: GIS_IT, City of Tucson Information Technology GIS Services, 520-791-4747, GIS_IT@tucsonaz.govIntended Use: For map display and provides finer level of detail than Pima County GIS library data layer WASHES.Supplemental Information: DATA QUALITY IS QUESTIONABLE because it has not been regularly maintained. Per Frank Sousa (Winter 2009), he would prefer to call this layer "drainage network" because it includes streets flow which may not be considered a watercourse. Started in 1999 it covered the municipal planning area, done in pieces startings with the core of the City. Was densified to make sure there was a line where there was 100 cfs flow or more for regulatory purposes. Streets flow mapping is incomplete. 7/10/2010 - loaded shapefile into EDITSDE geodatabase from Stormwater shapes folder. circa 1999 - Shapefile create by Frank Sousa in City of Tucson Stormwater from aerial photos, topography and ground knowledge. Additional edits done by Frank Sousa.

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.

The Tucson Police Calls for Service - 2021 - Open Data item contains calls for service events that were responded to in 2021 by Tucson Police Department personnel. Information in this file is based on initial closure of calls, and data for calls becoming incidents may vary from the incident file due to further information, follow-up, and/or investigation. To protect the privacy of victims, all address locations have been rounded to the nearest hundred-block, and reflect the location where the Officer responded to the event. The date and time provided reflect when the event was reported, not necessarily when the event occurred.PurposeThis data is provided for informational purposes only. This data is not to be relied upon for official purposes.Dataset ClassificationLevel 0 - OpenKnown UsesLorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.Known ErrorsThere is a small margin of error when processing the data for mapping purposes; therefore, some incidents may either be omitted from, or inaccurately mapped.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.