AndreaBozzo/ceres-open-data-index huggingface dataset:
1.14 High Risk Inspections (detail FY16/17)

The National Fire Protection Association (NFPA) and Commission on Fire Accreditation International (CFAI) standards provide criteria for for defining a High Risk Occupancy that can be tailored to the needs of the community. High risk occupancies have a: * higher than average probability of a fire or other emergency occurring due to the type and/or quantity of materials stored, used, or handled on site related to the processes performed in business operations; * higher than average risk for injury or death to occupants due to age, physical or mental abilities of the occupants, the number of occupants (occupants load), or size and complexity of the structure. Examples may include elder care facilities, buildings with flammable liquids, and high rises where many inpiduals can become trapped. Both CFAI and NFPA recommend that High Risk Occupancies be inspected annually. The total number of high risk occupancies in the city may change from month-to-month as fire inspections and evaluations of occupancy risk are assessed utilizing the Community Risk Assessment Guideline to verify risk classification of occupancies. For example, the number of high risk occupancies ranged from 559 in 2015 based on a risk assessment guideline developed in 1997, to 808 in mid-2018 utilizing the updated risk assessment guideline developed in 2016. The updated Risk Assessment Guideline’s definition of occupancy risk and frequency of inspections were based on NFPA 1730 (Standard on organization and deployment of fire prevention inspection and code enforcement, plan review, investigation, and public education programs), and standards set forth by the Commission on Fire Accreditation International. This page provides data for the High Risk Facilities Fire Inspections performance measure. High Risk Inspections Completed for Fiscal Year 16/17. Data used to schedule annual Fire inspections based on high risk occupancies. High risk occupancies have a higher than average probability of a fire or other emergency occurring due to type and/or quantity of materials stored, used, or handled on site due to processes performed in business operations and a higher than average risk for injury or death to occupants due to age, physical or mental abilities of the occupants, the number of occupants (occupants load), or size and complexity of the structure. The performance measure dashboard is available at [1.14 High Risk Inspections] Additional Information Source: Firehouse Software Contact: Jim Schmit Contact E-Mail: jim_schmit@tempe.gov Data Source Type: Tabular Preparation Method: Queried from Firehouse Server in Excel Publish Frequency: Monthly Publish Method: Manual [Data Dictionary]
Select Demographics - ACS 2012-2016, Census 2010 - Tempe Block Groups

This feature layer of Tempe's Census block groups are joined with the Census Bureau's data from the 2018 Planning Database (PDB), which was established to prepare for the upcoming 2020 Census. The 2018 PDB contains select operational, demographic, and socio-economic statistics from the 2010 Census and the 2012-2016 5-year ACS. For more information, see the United States Census Bureau 2018 Planning Database: [https://www.census.gov/topics/research/guidance/planning-databases.html].
Select Demographics - ACS 2012-2016, Census 2010 - Tempe Tracts

This feature layer of Tempe's Census tracts are joined with the Census Bureau's data from the 2018 Planning Database (PDB), which was established to prepare for the upcoming 2020 Census. The 2018 PDB contains select operational, demographic, and socio-economic statistics from the 2010 Census and the 2012-2016 5-year ACS. For more information, see the United States Census Bureau 2018 Planning Database: [https://www.census.gov/topics/research/guidance/planning-databases.html]
Internet Access - ACS 2013-2017 - Tempe Tracts

Tempe Census Census Tracts and internet access by household. Data source: U.S. Census Bureau, 2013-2017 American Community Survey 5-Year Estimates, table BD28011 (Internet Subscription in Household). Also includes "low response scores" from the the Census Bureau's data from the 2018 Planning Database (PDB), which was established to prepare for the upcoming 2020 Census. For more information on the low response score, see the United States Census Bureau 2018 Planning Database: [https://www.census.gov/topics/research/guidance/planning-databases.html] Layer generally supports 2020 Census story map [Ensuring a Complete Count in the 2020 Census].
1.01 ALS Response Time (2012)

The Tempe Fire Medical Rescue Department (TFMR) is an “all hazards” department that responds to all types of calls for service. Advanced Life Support (ALS) is an advanced set of life supporting procedures that go further than Basic Life Support (BLS) to assist the ill or injured with breathing, blood circulation, and other vital functions in emergencies. The response time for providing Advanced Life Support for a life-threatening event is related to patient outcomes (chance of full recovery). This data is based on calls received by the Phoenix 911 system and given an Advanced Life Support (ALS) response code, indicating the nature of the call. * Alarm Processing Time (also known as Dispatch Time to Notification Time) is calculated from the time Phoenix 911 answers the call to the time Phoenix 911 notifies a Fire Department Unit. * Turnout Time (also known as Acknowledgment Time to Roll Time) is calculated from the time a Fire Department Unit is notified of the call to the time the unit rolls out of the station or begins proceeding to the incident. * Travel Time (also known as Roll Time to Arrival Time) is calculated from the time a Fire department Unit starts proceeding to an incident to the time it arrives at the incident. The performance measure dashboard is available at [1.01 Fire Response Time]. Additional Information Source: Tempe Fire Medical Rescue Department/Phoenix Fire Department Dispatch Contact: Jim Schmit Contact E-Mail: Data Source Type: Tabular Preparation Method: Publish Frequency: Monthly Publish Method: Manual [Data Dictionary]
1.01 ALS Response Time (2013)

The Tempe Fire Medical Rescue Department (TFMR) is an “all hazards” department that responds to all types of calls for service. Advanced Life Support (ALS) is an advanced set of life supporting procedures that go further than Basic Life Support (BLS) to assist the ill or injured with breathing, blood circulation, and other vital functions in emergencies. The response time for providing Advanced Life Support for a life-threatening event is related to patient outcomes (chance of full recovery). This data is based on calls received by the Phoenix 911 system and given an Advanced Life Support (ALS) response code, indicating the nature of the call. * Alarm Processing Time (also known as Dispatch Time to Notification Time) is calculated from the time Phoenix 911 answers the call to the time Phoenix 911 notifies a Fire Department Unit. * Turnout Time (also known as Acknowledgment Time to Roll Time) is calculated from the time a Fire Department Unit is notified of the call to the time the unit rolls out of the station or begins proceeding to the incident. * Travel Time (also known as Roll Time to Arrival Time) is calculated from the time a Fire department Unit starts proceeding to an incident to the time it arrives at the incident. The performance measure dashboard is available at [1.01 Fire Response Time]. Additional Information Source: Tempe Fire Medical Rescue Department/Phoenix Fire Department Dispatch Contact: Jim Schmit Contact E-Mail: Data Source Type: Tabular Preparation Method: Publish Frequency: Monthly Publish Method: Manual [Data Dictionary]
1.01 ALS Response Time (2014)

The Tempe Fire Medical Rescue Department (TFMR) is an “all hazards” department that responds to all types of calls for service. Advanced Life Support (ALS) is an advanced set of life supporting procedures that go further than Basic Life Support (BLS) to assist the ill or injured with breathing, blood circulation, and other vital functions in emergencies. The response time for providing Advanced Life Support for a life-threatening event is related to patient outcomes (chance of full recovery). This data is based on calls received by the Phoenix 911 system and given an Advanced Life Support (ALS) response code, indicating the nature of the call. * Alarm Processing Time (also known as Dispatch Time to Notification Time) is calculated from the time Phoenix 911 answers the call to the time Phoenix 911 notifies a Fire Department Unit. * Turnout Time (also known as Acknowledgment Time to Roll Time) is calculated from the time a Fire Department Unit is notified of the call to the time the unit rolls out of the station or begins proceeding to the incident. * Travel Time (also known as Roll Time to Arrival Time) is calculated from the time a Fire department Unit starts proceeding to an incident to the time it arrives at the incident. The performance measure dashboard is available at [1.01 Fire Response Time]. Additional Information Source: Tempe Fire Medical Rescue Department/Phoenix Fire Department Dispatch Contact: Jim Schmit Contact E-Mail: Data Source Type: Tabular Preparation Method: Publish Frequency: Monthly Publish Method: Manual [Data Dictionary]
1.01 ALS Response Time (2015)

The Tempe Fire Medical Rescue Department (TFMR) is an “all hazards” department that responds to all types of calls for service. Advanced Life Support (ALS) is an advanced set of life supporting procedures that go further than Basic Life Support (BLS) to assist the ill or injured with breathing, blood circulation, and other vital functions in emergencies. The response time for providing Advanced Life Support for a life-threatening event is related to patient outcomes (chance of full recovery). This data is based on calls received by the Phoenix 911 system and given an Advanced Life Support (ALS) response code, indicating the nature of the call. * Alarm Processing Time (also known as Dispatch Time to Notification Time) is calculated from the time Phoenix 911 answers the call to the time Phoenix 911 notifies a Fire Department Unit. * Turnout Time (also known as Acknowledgment Time to Roll Time) is calculated from the time a Fire Department Unit is notified of the call to the time the unit rolls out of the station or begins proceeding to the incident. * Travel Time (also known as Roll Time to Arrival Time) is calculated from the time a Fire department Unit starts proceeding to an incident to the time it arrives at the incident. The performance measure dashboard is available at [1.01 Fire Response Time]. Additional Information Source: Tempe Fire Medical Rescue Department/Phoenix Fire Department Dispatch Contact: Jim Schmit Contact E-Mail: Data Source Type: Tabular Preparation Method: Publish Frequency: Monthly Publish Method: Manual [Data Dictionary]
1.01 ALS Response Time (2016)

The Tempe Fire Medical Rescue Department (TFMR) is an “all hazards” department that responds to all types of calls for service. Advanced Life Support (ALS) is an advanced set of life supporting procedures that go further than Basic Life Support (BLS) to assist the ill or injured with breathing, blood circulation, and other vital functions in emergencies. The response time for providing Advanced Life Support for a life-threatening event is related to patient outcomes (chance of full recovery). This data is based on calls received by the Phoenix 911 system and given an Advanced Life Support (ALS) response code, indicating the nature of the call. * Alarm Processing Time (also known as Dispatch Time to Notification Time) is calculated from the time Phoenix 911 answers the call to the time Phoenix 911 notifies a Fire Department Unit. * Turnout Time (also known as Acknowledgment Time to Roll Time) is calculated from the time a Fire Department Unit is notified of the call to the time the unit rolls out of the station or begins proceeding to the incident. * Travel Time (also known as Roll Time to Arrival Time) is calculated from the time a Fire department Unit starts proceeding to an incident to the time it arrives at the incident. The performance measure dashboard is available at [1.01 Fire Response Time]. Additional Information Source: Tempe Fire Medical Rescue Department/Phoenix Fire Department Dispatch Contact: Jim Schmit Contact E-Mail: Data Source Type: Tabular Preparation Method: Publish Frequency: Monthly Publish Method: Manual [Data Dictionary]
1.01 ALS Response Time (2017)

The Tempe Fire Medical Rescue Department (TFMR) is an “all hazards” department that responds to all types of calls for service. Advanced Life Support (ALS) is an advanced set of life supporting procedures that go further than Basic Life Support (BLS) to assist the ill or injured with breathing, blood circulation, and other vital functions in emergencies. The response time for providing Advanced Life Support for a life-threatening event is related to patient outcomes (chance of full recovery). This data is based on calls received by the Phoenix 911 system and given an Advanced Life Support (ALS) response code, indicating the nature of the call. * Alarm Processing Time (also known as Dispatch Time to Notification Time) is calculated from the time Phoenix 911 answers the call to the time Phoenix 911 notifies a Fire Department Unit. * Turnout Time (also known as Acknowledgment Time to Roll Time) is calculated from the time a Fire Department Unit is notified of the call to the time the unit rolls out of the station or begins proceeding to the incident. * Travel Time (also known as Roll Time to Arrival Time) is calculated from the time a Fire department Unit starts proceeding to an incident to the time it arrives at the incident. The performance measure dashboard is available at [1.01 Fire Response Time]. Additional Information Source: Tempe Fire Medical Rescue Department/Phoenix Fire Department Dispatch Contact: Jim Schmit Contact E-Mail: Data Source Type: Tabular Preparation Method: Publish Frequency: Monthly Publish Method: Manual [Data Dictionary ]
Residential Density (General Plan)

This polygonal layer represents projected residential density in the year 2040. This layer was submitted as part of the City of Tempe's General Plan. Contact: Will Duke, Robbie Aaron Contact E-Mail: [will_duke@tempe.gov,] [robbie_aaron@tempe.gov] Contact Phone: 480-350-8096 Link to department home page: [http://www.tempe.gov/planning] Data Source: Spatial Database Data Source Type: Geospatial Preparation Method: Created based off documentation in current and previous General Plans Publish Frequency: As Necessary Publish Method: Automatic [Link to Data Dictionary]
Post World War II Areas

The contents of this feature layer provide a visual aid for homes constructed during the period between 1945 to 1960. Data supporting the visual aids list which neighborhood these post World War II homes resides in, the style of the homes, along with its condition and integrity. The Historic Preservation Office works with the community to preserve these homes by enhancing archaeological, prehistoric, and historic resources throughout the City of Tempe. This work includes a wide range of partnerships with local homeowners, neighborhoods, developers/architects, boards/commissions, state and national agencies, as well as volunteer and non-profit preservation groups Contact: Will Duke Contact E-Mail: will_duke@tempe.gov Contact Phone: N/A Link: N/A Data Source: SQL Server/ArcGIS Server Data Source Type: Geospatial Preparation Method: N/A Publish Frequency: As information changes Publish Method: Automatic [Data Dictionary]
1.08 Crash Data Report (detail)

Please note that 2025 data are incomplete and will be updated as additional records become available. Data are complete through 12/31/2024. Fatal and serious injury crashes are not “accidents” and are preventable. The City of Tempe is committed to reducing the number of fatal and serious injury crashes to zero. This data page provides details about the performance measure related to High Severity Traffic Crashes, as well as access to the data sets and any supplemental data. The Engineering and Transportation Department uses this data to improve safety in Tempe. This data includes vehicle/vehicle, vehicle/bicycle, and vehicle/pedestrian crashes in Tempe. The data also includes the type of crash and location. This layer is used in the related Vision Zero story map, web maps, and operations dashboard. Time Zones Please note that data is stored in Arizona time, which is UTC-07:00 (7 hours behind UTC) and does not adjust for daylight saving (as Arizona does not partake in daylight saving). The data is intended to be viewed in Arizona time. Data downloaded as a CSV may appear in UTC time and, in some rare circumstances and locations, may display online in UTC or local time zones. As a reference to check data, the record with incident number 2579417 should appear as Jan. 10, 2012, 9:04 AM. Please note that 2025 data are incomplete and will be updated as additional records become available. Data are complete through 12/31/2024. This page provides data for the High Severity Traffic Crashes performance measure. The performance measure page is available at [1.08 High Severity Traffic Crashes] Additional Information Source: Arizona Department of Transportation (ADOT) Contact (author): Shelly Seyler Contact (author) E-Mail: Shelly_Seyler@tempe.gov Contact (maintainer): Julian Dresang Contact (maintainer) E-Mail: Julian_Dresang@tempe.gov Data Source Type: CSV files and Excel spreadsheets can be downloaded from the ADOT website Preparation Method: Data is sorted to remove license plate numbers and other sensitive information Publish Frequency: semi-annually Publish Method: Manual [Data Dictionary]
1.08 High Severity Traffic Crashes (summary)

Fatal and serious injury crashes are not “accidents” and are preventable. The City of Tempe is committed to reducing the number of fatal and serious injury crashes to zero. This data page provides details about the performance measure related to High Severity Traffic Crashes as well as access to the data sets and any supplemental data. Click on the Showcases tab for visual representations of this data. The Engineering and Transportation Department uses this data to improve safety in Tempe. This page provides data for the High Severity Traffic Crashes performance measure. City of Tempe crash data summarized to show fatal and serious injury crashes by year. The performance measure dashboard is available at [1.08 High Severity Traffic Crashes] Additional Information Source: Arizona Department of Transportation (ADOT) Contact: Julian Dresang Contact E-Mail: Julian_Dresang@tempe.gov Data Source Type: CSV files and Excel spreadsheets can be downloaded from ADOT website Preparation Method: Data is sorted to remove license plate numbers and other sensitive information Publish Frequency: Monthly Publish Method: Manual [Data Dictionary]
Police Transparency - Calls for Service - All Data (Dataset)

The Calls for Service dataset includes police service requests for which patrol officers, traffic officers, bike officers and, on occasion, detectives will be dispatched to public safety response. It also includes self-initiated calls for service where an officer witnesses a violation or suspicious activity for which they would respond. This item represents a consolidated item of all records. Why the Datasets are Organized into Separate Layers In January of 2022, the Tempe Police Department completed a major transition in how crimes data is reported, moving from the FBI Uniform Crime Report program to the enhanced National-Incident Based Reporting System, or NIBRS. NIBRS is now the required reporting method for the FBI. The Uniform Crime Report (UCR) Program's traditional Summary Reporting System (SRS) was limited in comparison to NIBRS, which offers more detailed data collection that provides a deeper understanding of crime and its circumstances. NIBRS captures a wider range of details on crime incidents and can reflect separate offenses occurring during the same event, including information on victims, known offenders, relationships between victims and offenders, arrestees, and property involved in the crimes. With greater specificity in reporting offenses, NIBRS provides for more accurate and detailed crime-related information, and helps give context to specific crime issues while affording greater analytic capability of crime. Below is the link to Tempe-specific NIBRS reports. Use the drop-down filters to select Tempe PD, the year, and the type of report. Because of these differences, trends and numbers between the two systems should not be directly compared. That’s why we treat 2022 and later (NIBRS) separately from 2021 and earlier (UCR). To make the older data easier to browse, we grouped the data from 2021 and earlier into year ranges instead of showing it all at once. This helps with performance and loading speed due to the large count of records. For detailed guidance on interpreting calls for service data, as well as data scope and limitations, please refer to the [User Guide]. [Data Dictionary] Additional Information Contact Email: [PD-DataRequest@tempe.gov] Contact Phone: N/A Link: N/A Data Source: Versaterm Informix RMS Data Source Type: Informix and/or SQL Server Preparation Method: Automated process Publish Frequency: Daily Publish Method: Automatic
3.34 Community Health and Well-Being (summary)

This dataset comes from the Community Survey questions relating to the Community Health & Well-Being performance measure: "With “10” representing the best possible life for you and “0” representing the worst, how would you say you personally feel you stand at this time?" and "With “10” representing the best possible life for you and “0” representing the worst, how do you think you will stand about five years from now?" – the results of both scores are then used to assess a Cantril Scale which is a way of assessing general life satisfaction. As per the Cantril Self-Anchoring Striving Scale, the three categories of identification are as follows: * Thriving – Respondents rate their current life as a 7 or higher AND their future life as an 8 or higher. * Suffering – Respondents rate their current life negatively (0 to 4) AND their future life negatively (0 to 4). * Struggling – Respondents who do not meet the criteria for Thriving or Suffering. The survey is mailed to a random sample of households in the City of Tempe and has a 95% confidence level. Note on Methodology Update: In 2025, the Cantril classification method was revised to align with Gallup’s official Life Evaluation Index methodology. This change affects only a small number of respondents whose answers did not fit cleanly into the previous custom definition of “Struggling,” which classified respondents who rated their current life moderately (5 or 6) or their future life moderately or negatively (0 to 7). Under the updated approach, respondents who previously fell outside that definition are now appropriately included in the Struggling category. The overall distribution of Thriving, Struggling, and Suffering changed only minimally, and the updated methodology has been applied consistently to all prior years. This page provides data for the Community Health and Well-Being performance measure. The performance measure dashboard is available at [3.34 Community Health and Well-Being]. [Data Dictionary] Additional Information Source: Community Attitude Survey (Vendor: ETC Institute) Contact: Amber Asburry Contact email: amber_asburry@tempe.gov Preparation Method: Survey results from two questions are calculated to create a Cantril Scale value that falls into the categories of Thriving, Struggling, and Suffering. Publish Frequency: Annually Publish Method: Manual