Status: 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 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.

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.

File originated from: lfil_ex for landfill sites in eastern Pima County by Pima County, but is being updated by the City of Tucson - Environmental Services. For historic information on this file, refer to the Pima County GIS Technical Services. Additional attribute fields were added to this shapefile for the City of Tucson - Environmental Services projects. City landfill boundaries are approximate and updated as new information becomes available. Original file adopted from Pima County LFIL_EX gis file. See Pima County metadata for original filePurposeTo be used on the City of Tucson - Environmental Services Potential Environmental Concerns Webmap.Dataset ClassificationLevel 0 – OpenKnown UsesNoneKnown ErrorsBoundaries are for general, approximate location of landfill boundaries and are not exact. The City of Tucson has not verified boundaries which had no City of Tucson involvement.ContactTucson Department of Environmental and General ServicesUpdate FrequencyAs Needed

This dataset displays Tucson Police Department's activity for calendar year 2025. The data provided in this table can be accessed in dashboard form at https://policeanalysis.tucsonaz.gov. Older Police Activity data can be accessed as separate data sets by year back to 2018.PurposeTo provide publicly available data collected by Tucson Police Department.Dataset ClassificationLevel 0 – OpenKnown UsesNoneKnown ErrorsNo known errorsContactTucson Police DepartmentUpdate FrequencyUpdated monthly

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

Status: Updated occasionallyContact: Johanna Kraus, 837.4941Lineage: created from AutoCAD static maps, cleaned up in 2007/2008 by Johanna Kraus - zones verified against static map and research done where necessary.Attributes: ZONE_COT - displayed on map, includes overlay designator of H (historic), N (neighborhood preservation) or U (urban overlay). ORIG_ZONE - hard zoning without overlayUsage: This layer is intended to be used in the Open Data portal and not for regular use in ArcGIS Online and ArcGIS Enterprise.Link to Open Data item: https://gisdata.tucsonaz.gov/datasets/zoning-tucson-open-data

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.

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.

This dataset displays Tucson Police traffic enforcement from December 31st, 2016 to the present. The data provided in this table can be accessed in dashboard form at https://policeanalysis.tucsonaz.gov. PurposeTo provide publicly available police traffic enforcement data.Dataset ClassificationLevel 0 – OpenKnown Uses https://policeanalysis.tucsonaz.gov. Known ErrorsNo known errorsContactTucson Police DepartmentUpdate FrequencyMonthly

A preliminary data version of fp_zonex. FP_ZONEX shows areas of shallow 100-year floodplain (ZONE X - SHADED) with identified subclassifications for areas within unincorporated Pima County. Areas in this layer should have identical exterior boundaries to the area of ZONE X - SHADED polygons in the fp_dfirm layer. Will be official June 16, 2011. Spatial Domain: Pima County Maintenance Organization: PC ITD GIS Maintenance Frequency: Varies Maintenance Format: Shape Primary Source Organization: RFCD Primary Source Contact: Terry Hendricks Primary Source Date: 20110301 Primary Source Format: Shape Secondary Source Organization: FEMA Secondary Source Format: Shape GIS Contact: Steve WhitneyPurposeLorem 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.

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.

This dataset displays Tucson Police Department's activity for calendar year 2024. The data provided in this table can be accessed in dashboard form at https://policeanalysis.tucsonaz.gov. Older Police Activity data can be accessed as separate data sets by year back to 2018.PurposeTo provide publicly available data collected by Tucson Police Department.Dataset ClassificationLevel 0 – OpenKnown UsesNoneKnown ErrorsNo known errorsContactTucson Police DepartmentUpdate FrequencyUpdated monthly

A paper copy of the Geologic Map of the Catalina Core Complex and San Pedro Trough (Dickinson, 1992) was scanned and digitized by U.S. Geological Survey staff and contractors at the Southwest Field Office (Tucson, AZ) in 2000-2001 for input into an ArcInfo geographic information system (GIS). The resulting geologic map database (in ArcInfo format) can be queried in many ways to produce a variety of geologic maps. Digital base map data files. (topography, roadways, towns, and hydrography) are not included: they may be obtained from a variety of commercial and government sources. Geologic map graphics and plot files that are provided in the Open-File Report are representations of the digital database and are not designed to be cartographic products.

This dataset displays Tucson Police Department's activity for calendar year 2019. The data provided in this table can be accessed in dashboard form at https://policeanalysis.tucsonaz.gov. PurposeTo provide publicly available data collected by Tucson Police Department.Dataset ClassificationLevel 0 – OpenKnown UsesNoneKnown ErrorsNo known errorsContactTucson Police DepartmentUpdate FrequencyNot updated.

Sidewalks ramps in the City of Tucson. 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 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 dataset displays Tucson Police Arrests from 2018 to the present. The data provided in this table can be accessed in dashboard form at https://policeanalysis.tucsonaz.gov. PurposeTo provide publicly available police arrests data.Dataset ClassificationLevel 0 – OpenKnown Uses https://policeanalysis.tucsonaz.gov. Known ErrorsNo known errorsContactTucson Police DepartmentUpdate FrequencyMonthly

This dataset displays Tucson Police Department's activity for calendar year 2021. The data provided in this table can be accessed in dashboard form at https://policeanalysis.tucsonaz.gov. PurposeTo provide publicly available data collected by Tucson Police Department.Dataset ClassificationLevel 0 – OpenKnown UsesNoneKnown ErrorsNo known errorsContactTucson Police DepartmentUpdate FrequencyNot updated.

This dataset displays Tucson Police Department's activity for calendar year 2018. The data provided in this table can be accessed in dashboard form at https://policeanalysis.tucsonaz.gov. PurposeTo provide publicly available data collected by Tucson Police Department.Dataset ClassificationLevel 0 – OpenKnown UsesNoneKnown ErrorsNo known errorsContactTucson Police DepartmentUpdate FrequencyNot updated.

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.

This dataset displays Tucson Police Department's activity for calendar year 2022. The data provided in this table can be accessed in dashboard form at https://policeanalysis.tucsonaz.gov. PurposeTo provide publicly available data collected by Tucson Police Department.Dataset ClassificationLevel 0 – OpenKnown UsesNoneKnown ErrorsNo known errorsContactTucson Police DepartmentUpdate FrequencyNot updated.