Powered By Socrata
Refine Results

The population count of Tucson, AZ was 527,586 in 2016.

Population

Population Change

Above charts are based on data from the U.S. Census American Community Survey | ODN Dataset | API - Notes:

1. ODN datasets and APIs are subject to change and may differ in format from the original source data in order to provide a user-friendly experience on this site.

2. To build your own apps using this data, see the ODN Dataset and API links.

3. If you use this derived data in an app, we ask that you provide a link somewhere in your applications to the Open Data Network with a citation that states: "Data for this application was provided by the Open Data Network" where "Open Data Network" links to http://opendatanetwork.com. Where an application has a region specific module, we ask that you add an additional line that states: "Data about REGIONX was provided by the Open Data Network." where REGIONX is an HREF with a name for a geographical region like "Seattle, WA" and the link points to this page URL, e.g. http://opendatanetwork.com/region/1600000US5363000/Seattle_WA

Demographics and Population Datasets Involving Tucson, AZ

  • API

    Tucson, AZ- TPD Arrests (2014)

    data.policefoundation.org | Last Updated 2015-10-19T13:44:49.000Z

    "The TPD Arrest - 2014 file contains data for all arrests made in 2014 by TPD 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. There is a small margin of error when processing the data for mapping purposes; therefore, some arrest incidents may either be omitted from, or inaccurately mapped."

  • API

    Tucson, AZ- TPD Arrests (2013)

    data.policefoundation.org | Last Updated 2015-10-19T13:34:00.000Z

    "The TPD Arrest - 2013 file contains data for all arrests made in 2013 by TPD 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. There is a small margin of error when processing the data for mapping purposes; therefore, some arrest incidents may either be omitted from, or inaccurately mapped."

  • API

    Tucson, AZ- TPD Arrests (2010)

    data.policefoundation.org | Last Updated 2015-10-19T13:09:59.000Z

    "The TPD Arrest - 2010 file contains data for all arrests made in 2010 by TPD 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. There is a small margin of error when processing the data for mapping purposes; therefore, some arrest incidents may either be omitted from, or inaccurately mapped."

  • API

    Tucson, AZ- TPD Arrests (2011)

    data.policefoundation.org | Last Updated 2015-10-19T13:14:58.000Z

    "The TPD Arrest - 2011 file contains data for all arrests made in 2011 by TPD 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. There is a small margin of error when processing the data for mapping purposes; therefore, some arrest incidents may either be omitted from, or inaccurately mapped."

  • API

    Tucson, AZ- TPD Arrests (2012)

    data.policefoundation.org | Last Updated 2015-10-19T13:24:43.000Z

    "The TPD Arrest - 2012 file contains data for all arrests made in 2012 by TPD 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. There is a small margin of error when processing the data for mapping purposes; therefore, some arrest incidents may either be omitted from, or inaccurately mapped."

  • API

    Tucson, AZ- TPD Arrests (2009)

    data.policefoundation.org | Last Updated 2015-10-19T12:59:27.000Z

    The TPD Arrest - 2009 file contains data for all arrests made in 2009 by TPD 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. There is a small margin of error when processing the data for mapping purposes; therefore, some arrest incidents may either be omitted from, or inaccurately mapped.

  • API

    Tucson, AZ- TPD Incidents (2011)

    data.policefoundation.org | Last Updated 2015-10-15T19:32:42.000Z

    "The TPD Arrest - 2011 file contains data for all arrests made in 2011 by TPD 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. There is a small margin of error when processing the data for mapping purposes; therefore, some arrest incidents may either be omitted from, or inaccurately mapped."

  • API

    Tucson, AZ- TPD Incidents (2009)

    data.policefoundation.org | Last Updated 2015-10-15T19:48:16.000Z

    "The TPD Incidents – 2009 file contains incidents that were reported in 2009 to the Tucson Police Department, were responded to and for which a report was generated. This data is provided for informational purposes only. Totals in this file may vary from official totals following investigation of the incident. This data is not to be relied upon for official purposes. 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 actually occurred. The date and time provided reflect when the incident was reported, not necessarily when it happened. There 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."

  • API

    Tucson, AZ- TPD Incidents (2010)

    data.policefoundation.org | Last Updated 2015-10-19T12:36:31.000Z

    "The TPD Incidents – 2010 file contains incidents that were reported in 2010 to the Tucson Police Department, were responded to and for which a report was generated. This data is provided for informational purposes only. Totals in this file may vary from official totals following investigation of the incident. This data is not to be relied upon for official purposes. 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 actually occurred. The date and time provided reflect when the incident was reported, not necessarily when it happened. There 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."

  • API

    Tucson, AZ- TPD Incidents (2013)

    data.policefoundation.org | Last Updated 2015-10-15T19:30:47.000Z

    "The TPD Incidents – 2013 file contains incidents that were reported in 2013 to the Tucson Police Department, were responded to and for which a report was generated. This data is provided for informational purposes only. Totals in this file may vary from official totals following investigation of the incident. This data is not to be relied upon for official purposes. 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 actually occurred. The date and time provided reflect when the incident was reported, not necessarily when it happened. There 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."