This layer shows the age statistics in Tucson by neighborhood, aggregated from block level data, between 2010-2019. For questions, contact GIS_IT@tucsonaz.gov. The data shown is from Esri's 2019 Updated Demographic estimates.Esri's U.S. Updated Demographic (2019/2024) Data - Population, age, income, sex, race, home value, and marital status are among the variables included in the database. Each year, Esri's Data Development team employs its proven methodologies to update more than 2,000 demographic variables for a variety of U.S. geographies.Additional Esri Resources:Esri DemographicsU.S. 2019/2024 Esri Updated DemographicsEssential demographic vocabularyPermitted use of this data is covered in the DATA section of the Esri Master Agreement (E204CW) and these supplemental terms.

The Tucson Police Calls for Service - 2016 - Open Data contains calls for service events that were responded to in 2016 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.

The Tucson Police Arrests - 2017 - Open Data item contains data for all arrests made in 2017 by Tucson Police Department sworn personnel and includes all associated charges and arrestee demographic information. To protect the privacy of victims, all address locations have been rounded to the nearest hundred-block, and reflect the location where the arrest occurred. 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 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.

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.

Plan submitted by: redistrictadmin on 12/8/2021 USER DESCRIPTION: In this version based off CD Test Map Version 8.0, CD Test Map Version 8.1 looks to replicate the boundaries of District 22 and District 23 of the Yuma Gold map to District 7 and District 9. CD Test Map Version 8.1 offers a boundary change in Tucson.

USER PLAN OBJECTIVE: N/A

Plan submitted by: redistrictadmin on 10/26/2021 USER DESCRIPTION: In this version based off LD Test Map Version 8.0, LD Test Map Version 9.1 looks to move Flowing Wells into District 20. All of Red Rock and Vail are moved into District 17, while Tucson Estates, Oracle, Sane Manuel, and Mammoth move into District 16. The Davis-Monthan Air Base is moved into District 21, and Quail Creek Country Club, Amado, Tubac, and the eastern half of Santa Cruz County are moved into District 19. Finally, all of Coolidge is united in District 16, and District 7 moves further west into Apache Junction. USER PLAN OBJECTIVE: N/A

Plan submitted by: redistrictadmin on 12/8/2021 USER DESCRIPTION: In this version based off CD Test Map Version 8.0, CD Test Map Version 8.3 looks to replicate the boundaries of District 22 and 23 of the Yuma Gold map to District 7 and District 9. CD Test Map Version 8.3 also offers an alternative boundary change in Tucson and balancing method from CD Test Map Version 8.1.

USER PLAN OBJECTIVE: N/A

The Tucson Police Arrests - 2018 - Open Data item contains data for all arrests made in 2018 by Tucson Police Department sworn personnel and includes all associated charges and arrestee demographic information. To protect the privacy of victims, all address locations have been rounded to the nearest hundred-block, and reflect the location where the arrest occurred.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 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.

Plan submitted by: redistrictadmin on 10/15/2021 USER DESCRIPTION: In this version based off CD Test Map Version 3.4, CD Test Map Version 3.5 looks to match the eastern border of District 7 to that of District 7’s in CD Test Map Version 3.0 in order to achieve population balancing. The eastern border of District 6 is pushed east to take Tucson south of the Rillito River. District 6 is also pushed north into Pinal County, west of I-79. Additions to District 6 include Red Rock, Eloy, Arizona City, Picacho, Maricopa, and some of Casa Grande. For more information on the methodology used to create these boundaries, please visit: https://redistricting-irc-az.hub.arcgis.com/pages/draft-maps USER PLAN OBJECTIVE: N/A

Plan submitted by: redistrictadmin on 10/15/2021 USER DESCRIPTION: In this version, we overcome the issues of LD Test Map Version 3.0. Flagstaff is split between District 6 and District 7. Changes also focus on Phoenix and Tucson. For more information on the methodology used to create these boundaries, please visit: https://redistricting-irc-az.hub.arcgis.com/pages/draft-maps USER PLAN OBJECTIVE: N/A

The Tucson Police Calls for Service - Last 45 Days - Open Data item contains calls for service events that were responded to in the last 45 days by Tucson Police Department or University of Arizona 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.

The Tucson Police Incidents - 2021 - Open Data item contains incidents that were reported in 2021 to the Tucson Police Department, were responded to and for which a report was generated. Totals in this file may vary from official totals following investigation of the incident. 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 incident - not necessarily where the incident occurred. The date and time provided reflect when the incident was reported, not necessarily when it happened. 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.

The Tucson Police Incidents - 2012 - Open Data item contains incidents that were reported in 2012 to the Tucson Police Department, were responded to and for which a report was generated. Totals in this file may vary from official totals following investigation of the incident. 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 incident - not necessarily where the incident occurred. The date and time provided reflect when the incident was reported, not necessarily when it happened. 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. On July 31, 2012 TPD transitioned to a completely new computer-aided dispatch and records management system, therefore some fields in this dataset will not be populated prior to this date.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 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.

The Tucson Police Incidents - 2020 - Open Data item contains incidents that were reported in 2020 to the Tucson Police Department, were responded to and for which a report was generated. Totals in this file may vary from official totals following investigation of the incident. 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 incident - not necessarily where the incident occurred. The date and time provided reflect when the incident was reported, not necessarily when it happened. PurposeThis data is provided for informational purposes only. This data is not to be relied upon for official purposes.Dataset ClassificationLevel 0 - OpenKnown UsesKnown 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 ContactUpdate Frequency

Status: UPDATED occasionally using ArcMap Contact: Allen Scully for dissolved version: allen.scully@tucsonaz.govJesse Reyes for original, non-dissolved data. City of Tucson Development Services, 520-837-6963, Jesse.Reyes@tucsonaz.gov Intended Use: For map display. Supplemental Information: An overlay zone typically imposes a set of requirements in addition to those laid out by the underlying zoning regulations in the Land Use Code (LUC). The exact boundaries of the IID overlay are identified on the official zoning maps kept on file in the offices of the Planning and Development Services Department and the City Clerks. Changes triggered by Mayor and Council amendments to Land Use Code. Links:http://www.tucsoncommercial.com/images/Tucson_Zoning_Summary.pdfhttp://cms3.tucsonaz.gov/sites/default/files/imported/maps/city/infillincentivedistmaterial.pdf 6/6/2011 - BAE - deleted IIS_CODE field, not used and was getting out of sync with the NAME fieldDecember 2010 - J. Reyes added subdistrict polygon 10/05/2010 - split into two subdistricts per ordinance 10841 03/23/2010 - Name change. Formerly known as infill_incentive 09/15/2009 - Modified per direction from mayor and council09/09/2009 - Modified as per ordinance 10710 10/24/2006 - Defined by resolution 204487

The Tucson Police Incidents - 2018 - Open Data item contains incidents that were reported in 2018 to the Tucson Police Department, were responded to and for which a report was generated. Totals in this file may vary from official totals following investigation of the incident. 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 incident - not necessarily where the incident occurred. The date and time provided reflect when the incident was reported, not necessarily when it happened. 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.

Plan submitted by: redistrictadmin on 10/12/2021 USER DESCRIPTION: As the first version based off the newly adopted CD Pre-Draft Map 1.1, CD Test Map Version 2.0 looks to offer a view of splitting Tucson diagonally into differing districts as well as moves the northern tribes from District 9 to District 2. USER PLAN OBJECTIVE: N/A

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.

Status: UPDATED occasionally using ArcMap Contact: Allen Scully for dissolved version: allen.scully@tucsonaz.govJesse Reyes for original, non-dissolved data. City of Tucson Development Services, 520-837-6963, Jesse.Reyes@tucsonaz.gov Intended Use: For map display. Supplemental Information: An overlay zone typically imposes a set of requirements in addition to those laid out by the underlying zoning regulations in the Land Use Code (LUC). The exact boundaries of the IID overlay are identified on the official zoning maps kept on file in the offices of the Planning and Development Services Department and the City Clerks. Changes triggered by Mayor and Council amendments to Land Use Code. Links:http://www.tucsoncommercial.com/images/Tucson_Zoning_Summary.pdfhttp://cms3.tucsonaz.gov/sites/default/files/imported/maps/city/infillincentivedistmaterial.pdf 6/6/2011 - BAE - deleted IIS_CODE field, not used and was getting out of sync with the NAME fieldDecember 2010 - J. Reyes added subdistrict polygon 10/05/2010 - split into two subdistricts per ordinance 10841 03/23/2010 - Name change. Formerly known as infill_incentive 09/15/2009 - Modified per direction from mayor and council09/09/2009 - Modified as per ordinance 10710 10/24/2006 - Defined by resolution 204487