AndreaBozzo/ceres-open-data-index huggingface dataset:
Feeding Mesa - Pounds of Food Distributed

Information about the number of meals and lbs of food distributed by the Mesa CARES Feeding Mesa program and is an aggregation of United Food Bank and Waste Not agency distributions. More information about the Feeding Mesa Program is available at https://www.mesaaz.gov/government/mesa-cares/feeding-mesa Aggregated dataset to be used for performance measures sourced by https://citydata.mesaaz.gov/Mesa-CARES/Feeding-Mesa-United-Food-Bank-Distribution/p4v3-2bab and https://citydata.mesaaz.gov/Mesa-CARES/Feeding-Mesa-Waste-Not/ihds-rh5e
Feeding Mesa - Emergency Food Bags

This dataset quantifies the number of Emergency Food Bags (EFB) packaged at the Mesa Convention Center in Partnership with United Food Bank as part of the Mesa Cares Feeding Mesa Program. Prepared EFB’s are delivered to United Food Bank for redistribution to their recipient agencies. More information about Feeding Mesa program is available at https://www.mesaaz.gov/government/mesa-cares/feeding-mesa
Feeding Mesa - City of Mesa Food Drive

**This dataset is no longer updating** This dataset details the locations of, and pounds received at fourteen canned food drives throughout the City of Mesa as part of the Mesa Cares Feeding Mesa Program. Food drives were conducted by City of Mesa Staff and volunteers. Food received was distributed to United Food Bank and/or Midwest Food Bank for distribution to their constituent agencies. More information about Feeding Mesa program is available at https://www.mesaaz.gov/government/mesa-cares/feeding-mesa
Falcon Field Airport Operations

The number of arrivals and departures from the airport at Falcon Field Airport by type: local and itinerant. Local operations are aircraft that remain in the local traffic pattern, execute simulated instrument approaches or low passes at the airport, and the operations to or from the airport and a designated practice area within a 20−mile radius of the tower. Itinerant operations are aircraft, either IFR (Instrument Flight Rules), SVFR, or VFR (Visual Flight Rules), that lands at an airport, arriving from outside the airport area, or departs an airport and leaves the airport area. This data is sourced from information published by the Federal Aviation Administration (FFA) Operational Network Airport Code = FFZ. Reports IFR itinerant and VFR itinerant operations (arrivals and departures), and local operations at the airport as reported by Air Traffic Control Towers (ATCTs). It does not include overflights.
Energy Resources - Outage Frequency

This dataset allows for the monthly computation of the System Average Interruption Frequency Index (SAIFI) for the City of Mesa’s electric utility. The System Average Interruption Frequency Index is commonly used as a reliability indicator by electric power utilities. It measures the average outage frequency per customer and is calculated by taking the sum of the total customers interrupted divided by the total number of active customers. Data reporting may have a 14 day lag.
Energy Resources - Locates

This dataset contains the necessary information to compute the average cost of a utility locate in the Mesa and/or Magma Service Areas (see Service Area maps). A utility locate involves identification of all underground utilities prior to excavation in a specified area. A utility locate is initiated, usually by a homeowner or excavator, by calling 811 or contacting Arizona’s 811 center’s website and providing the address, county and nearest cross street of where they’re planning to dig, as well as the type of project they’re completing and the exact area on the property they’re planning to dig. 811 then contacts the city’s utilities so they can mark the presence of any underground utilities in the proposed project area. Utility locates can contribute to increased safety to people and property and can eliminate unexpected costs due to accidental damage of buried utilities. A locate can be initiated by either a homeowner or an excavator. Data being reported may have a 14 day lag.
Energy Resources - Aggregated PM Data

Department aggregated list of performance measures and metric tracker. Data reporting may have a 14-day lag. Includes the following performance measures: Accuracy of Switching Orders; 12kV Substation Capacity Available for Use; Response Times to Call Outs; Reliability – Number of Outages; Reliability – Outage Duration (SAIDI); Reliability – Outage Frequency (SAIFI); and Accuracy of Meters.
Employment and Labor Force - Monthly

Monthly statistics regarding the labor force, employment and unemployment in Mesa and nearby municipalities. Unemployment rate sourced at [BLS.gov Data Viewer]. Employment Data - Bureau of Labor Statistics - [http://www.bls.gov/data/] Local Area Unemployment Statistics (LAUS) - [https://www.bls.gov/lau/] (See for next data release dates). To see how these terms are defined and what they include, please visit the Terms Glossary from the United State Department of Labor’s Bureau of Labor Statistics (BLS), which can be found at the following web address: http://www.bls.gov/bls/glossary.htm
Employment and Labor Force - Annual

Historical information on the Employment Dataset shows several current and historical annual statistics regarding population, the labor force, employment and unemployment in the City of Mesa. Monthly labor force, employment and unemployment information is at https://citydata.mesaaz.gov/External-Data/Employment-and-Labor-Force-Monthly/3vbg-xf63. Sources: Population Data - United States Census Bureau -https://www.census.gov/topics/population/data.html Employment Data - Bureau of Labor Statistics - http://www.bls.gov/data/ Local Area Unemployment Statistics (LAUS) - https://www.bls.gov/lau/ To see how these terms are defined and what they include, please visit the Terms Glossary from the United State Department of Labor’s Bureau of Labor Statistics (BLS), which can be found at the following web address: http://www.bls.gov/bls/glossary.htm
Electric Energy & Natural Gas Supply Costs

This is the cumulative sum of expenditures for each accounting string (EECAF & PNGCAF) by fiscal year and accounting period. The accumulation starts in the first accounting period for each fiscal year and ends on the last accounting period for the fiscal year. Data sources are publicly available via Open Expenditures at https://openexpenditures.mesaaz.gov/#!/year/All%20Years/explore/0/activity_name/EECAF+Elec+Energ+Cost+Adj+Factor+(EECAF)/0/department_name and https://openexpenditures.mesaaz.gov/#!/year/All%20Years/explore/0/activity_name/PNGCAF+Purch+Natur+Gas+Cost+Adjust+Factor/0/department_name Data reporting may have a 14 day lag.
Electric Consumption

Monthly electric consumption data in kWh and customer counts within the City of Mesa's electric service territory broken down by Rate Classification (i.e. Residential, Commercial, Other Public Authority, Interdepartmental). Consumption totals are for the month in which they are billed to the customer (“Billing Month”). Due to the constant reading of utility meters throughout the month, much of the consumption occurs in the month prior to the Billing Month. Data reporting may have a 14 day lag.
Downtown Tax Revenue by Post Month

NOTE: Effective March 1, 2019, the Mesa tax rate increased from 1.75% to 2.0%. Period revenues are delayed by up to 120 days. For example, May revenues are generally posted by mid July. This dataset contains sales tax revenue for taxpayers within downtown Mesa by posting month. Posting month is the accounting period the City booked the revenues and is used for financial reporting and budgeting purposes. To see a map of downtown Mesa boundaries see the "Source Link" in the 'About this Dataset' section below. Because of taxpayer confidentiality guidelines, a category or business class with fewer than 10 taxpayers is combined with a similar taxpayer category. If after combining there are still less than 10 taxpayers then the category is excluded and associated revenues are posted as "Other". Transient Lodging Tax (TLT) revenues are NOT included in this dataset because there are too few taxpayers in the downtown area to report. For sales tax revenues reflecting consumer activity periods (period when the taxes where collected by businesses), see "Downtown Tax Revenue by Report Month" at https://data.mesaaz.gov/Financials/Downtown-Tax-Revenue-by-Report-Month/258t-7i6w. Sales tax revenue includes Transaction Privilege Tax (TPT) and Transient Lodging Tax (TLT). Effective January 2017, the Arizona Department of Revenue administers sales and use tax collection for all state, county and municipal taxing jurisdictions. Visit https://www.mesaaz.gov/business/tax-audit for more information about sales tax in the City of Mesa.
Downtown Tax Revenue by Consumer Activity Period (Excludes Utility and Construction)

This dataset shows sales tax revenues generated within the downtown Mesa area. See the [Downtown Mesa map] for the boundary used in this dataset. Sales tax revenues collected by City of Mesa Utilities and construction contractors are excluded from this dataset because these revenues are reported by the location of the Utility or contractor’s office, not the customer or job site. These revenues are included in the dataset [Citywide Tax Revenue]. Effective March 1, 2019, the City of Mesa sales tax rate increased from 1.75% to 2.0%. For comparisons using the prior 1.75% tax rate, see [Comparable Rate Downtown Revenue]. Notes: Includes revenues from Transaction Privilege Tax (TPT) and Transient Lodging Tax (TLT) taxpayers in Downtown Mesa. Revenues are grouped by reporting year and month, reflecting when the sales activity occurred, not when payment was received by City of Mesa. Categories with fewer than 10 taxpayers are grouped as “Other.” Data may be delayed up to 120 days (e.g., May activity is typically posted by mid-July). Revenue amounts may change over time as corrections or late payments are reported.
Dataset Currency Report

Information about the the timeliness of datasets published on the portal as measured by age of most recent data in each dataset compared with Max Expected Data Age. This dataset is populated via FME workflow that checks Socrata dataset currency by having the workflow keep a history of the dataset currency in Data Services data warehouse. A second FME workflow sends that currency data to this Socrata dataset. To remove a dataset from this check, enter 0 as the Max Expected Data Age metadata field for the relevant dataset. Not included in the check are datasets that have: a) RETIRED or DUPLICATE in the dataset name b) 0 for Max Expected Data Age metadata field c) no Max Expected Data Age value / does not have Date & Time formatted columns d) no Date/Time formatted columns in the dataset. e) draft dataset (not published)
Crime Reporting Statistics

***In January 2020, as part of implementing a new citywide police incident reporting system the City began moving away from reporting crime to the FBI Unified Crime Reporting (UCR) Program and instead to the new National Incident-Based Reporting System (NIBRS) format. For this reason, 2020 UCR data may have inconsistencies and/or inaccuracies. A filtered view of UCR data is available for 2011-2019 at https://citydata.mesaaz.gov/Police/Crime-Reporting-Statistics-Uniform-Crime-Reporting/bfen-qa5d As of January 1, 2021, the National Incident-Based Reporting System (NIBRS) became the national crime data collection program. NIBRS was implemented to improve the overall quality of crime data collected by law enforcement, by capturing details on each single crime incident, as well as on separate offenses within the same incident. The historic Summary Reporting System (SRS) data collection, which collects more limited information than the more robust NIBRS, was phased out to make Uniform Crime Reporting (UCR) a NIBRS-only data collection. Coming soon, look for a new dataset based on NIBRS, which will provide more complete and comprehensive data for law enforcement, researchers, and the public. The Uniform Crime Reporting Program collects statistics on the number of offenses known to City of Mesa Police Department. Address and Location data are not exact location of incidents and have been rounded to nearest hundred block. Lat/Long are approximations only based on rounded hundred block. Part 1 offenses are reported monthly and are chosen by the Federal Bureau of Investigation (FBI) because they are serious crimes, they occur with regularity in all areas of the country, and they are likely to be reported to police. Part I offenses are defined as: Criminal homicide, Forcible Rape, Robbery, Aggravated Assault, Burglary (breaking or entering), Larceny-theft (except motor vehicle theft), Motor vehicle theft and Arson.
DoIT - Desktop Incidents Resolved

DoIT - Desktop Incidents Resolved Requests into the DoIT Sparc system are either incident tickets (access requests, app changes, helpdesk) or service requests. Service requests are performed by the Desktop division of DoIT and include hardware adds/changes/moves. Service requests are assigned a priority level between 1-5 based on type of request. Each level has a service level agreement – how quick the DoIT Desktop team will complete tickets of that priority level. This metric calculates what percentage of our service request tickets are completed within the service level agreements established by DoIT.
Cost Burdened Households

Information about number of households by annual income level and housing costs as a percentage of total income. Housing costs include mortgage/rent and utilities. Data sourced by US Census American Community Survey (ACS) 5-Year Estimates. See ACS Table B25106 "Tenure by Housing Costs as a Percentage of Household Income in the Past 12 Months"; Universe: Occupied housing units. This dataset's API field names match the US Census Variable / API names (see also metadata spreadsheet in attachments section).
Communications - Availability of TOPAZ Network

The TOPAZ Regional Wireless Cooperative (TRWC) is a multi-jurisdictional radio network whose members are the City of Apache Junction, the Fort McDowell Yavapai Nation, the Town of Gilbert, the City of Mesa, the Town of Queen Creek, the Rio Verde and the Superstition Fire & Medical districts. The TOPAZ voice radio network has a standalone system that monitors the radio system and records events that occur with the network. These events include the interruptions or failures that are counted for purposes of availability of the TOPAZ voice radio network. These event records include the time the interruption or failure began, the time the interruption or failure ended, and the time service returned to normal. This provides the duration of the event and is thus recorded in a log for inclusion in reports and metrics. Impairment means available, but not full capacity. In the TOPAZ network, impairments are usually not visible due to overlap in the radio site coverage or redundancy.
Commercial Vacancy - Multi-Family

The Commercial Vacancy Multi-Family (MF) dataset shows a variety of current and historical data points regarding the commercial real estate availability, vacancy, and absorption across the entire City of Mesa for all MF properties. This dataset was collected from a third-party source, CoStar, which is a commercial real estate database. CoStar is widely accepted as the trusted, industry standard for commercial real estate data, and while the City of Mesa believes this information to be accurate, we do not claim to have verified every and all information provided. If you require further explanation of some of the real estate terms used in the dataset, please visit the CoStar Terms Glossary below, which explains each term in greater detail. CoStar Terms Glossary: https://www.costar.com/about/support/costar-glossary
Commercial Vacancy - All Properties

The Commercial Vacancy All Properties dataset shows a variety of current and historical data points regarding the commercial real estate availability, vacancy, and absorption across the entire City of Mesa for all commercial properties. This dataset was collected from a third-party source, CoStar, which is a commercial real estate database. CoStar is widely accepted as the trusted, industry standard for commercial real estate data, and while the City of Mesa believes this information to be accurate, we do not claim to have verified every and all information provided. If you require further explanation of some of the real estate terms used in the dataset, please visit the CoStar Terms Glossary below, which explains each term in greater detail. CoStar Terms Glossary: https://www.costar.com/about/support/costar-glossary
Combined Assets Visited - City Data Portals

Information about accesses (visits) of city data assets. Combines analytics from both employee (citydata.mesaaz.gov) and public data (data.mesaaz.gov) portals. The following usage types are included in the Access Type column: grid view – tabular view of the dataset / filtered view primer page view – dataset / filtered view’s homepage, includes metadata and table preview of the data download – download of the dataset / filtered view to CSV, JSON, etc. api read access – programmatic access of dataset/filtered vew, etc. story page view – accessing a story page asset visualization page view – accessing a chart or map asset measure page view – accessing a performance measure asset Usage data are segmented into the following user types: site member: users who have logged in and have been granted a role on the domain community user: users who have logged in but do not have a role on the domain anonymous: users who have not logged in to the domain Data are updated by a system process at least once a day. Please see Site Analytics: Asset Access for more detail.
Code Compliance Investigation Response

This dataset is a subset of information about code compliance cases and includes turn-around-time from time case is opened to when initial inspection is completed. It is used by the Performance Measure "Response Time to Code Complaints" https://citydata.mesaaz.gov/d/8jwz-3v2t. Some fields are calculated or derived. Full "Code Compliance" dataset = https://citydata.mesaaz.gov/dataset/Code-Enforcement/hgf6-yenu
Code Compliance Case Workflow And Inspections

This dataset includes all statuses for status changes associated with Code Compliance cases. Code cases move through various workflow tasks and status prior to closing the case. For this reason, a distinct code case may be represented by multiple rows or records for each change in workflow and workflow status. To learn more about code compliance in the City of Mesa, visit the [Code Compliance Office]. For distinct code cases showing only the most recent status, see [Code Compliance Cases]. See also the following related datasets: [Code Enforcement Case Turn Around Time], [Code Cases by Officer], and [Code Compliance Investigation Response].
Code Compliance

Information about city code compliance cases. This dataset includes only the most recent workflow status, and each record/row represents a unique code compliance case. To learn more about code compliance in the City of Mesa, visit the [Code Compliance Office]. To see all workflow status changes associated with a case, see [Code Compliance Case Workflow and Inspections]. See also the following related datasets: [Code Enforcement Case Turn Around Time], [Code Cases by Officer], and [Code Compliance Investigation Response].
Class A Signal Preventive Maintenance

This is a record of every Class A performed at signalized intersections maintained by the City of Mesa. Class A traffic signal maintenance is defined as the preventive and responsive activities to preserve traffic signal infrastructure and control devices necessary for the safe and efficient utilization of arterial, collector, and local roadways. This includes doing an AC/DC voltage check, cleaning the cabinet, checking the controller and monitor programming and operation, checking pedestrian and vehicle detection operation, checking for signal indication outages, checking equipment inventory, checking communications to the traffic management center, and checking wiring
Citywide Tax Revenue by Report Month

NOTE: Effective March 1, 2019, the Mesa tax rate increased from 1.75% to 2.0%.Period revenues are delayed by up to 120 days. For example, May revenues are generally posted by mid July. This dataset contains sales tax revenue for taxpayers within the City of Mesa by reporting month. Reporting month refers to the time period when the consumer activity took place and is a representation of economic activity in the city. For example, a sale registered in the month of March, appears in the reporting month March, regardless of when the payment was actually received/posted by the City. Revenues by reporting month change as audits, collections and other taxpayer payments/refunds are processed or other corrections to previous periods are received. These updates to revenues are reported to the month for which the taxable activity occurred. For these reasons, generally speaking, reporting month revenues become a more accurate reflection of consumer activity over time. For sales tax revenues reflecting posting month (accounting period when the tax revenues were posted), see "Citywide Tax Revenue by Post Month" at https://data.mesaaz.gov/Financials/Citywide-Tax-Revenue-by-Post-Month/e9zg-r4w9. Sales tax revenue includes Transaction Privilege Tax (TPT) and Transient Lodging Tax (TLT). Effective January 2017, the Arizona Department of Revenue administers sales and use tax collection for all state, county and municipal taxing jurisdictions. Visit https://www.mesaaz.gov/business/tax-audit for more information about sales tax in the City of Mesa.
Citywide Tax Revenue by Post Month

NOTE: Effective March 1, 2019, the Mesa tax rate increased from 1.75% to 2.0%. Period revenues are delayed by up to 120 days. For example, May revenues are generally posted by mid July. This dataset contains sales tax revenue for taxpayers within the City of Mesa by posting month. Revenues from license and renewal fees are NOT included in this dataset. Posting month is the accounting period the City booked the revenues and is used for financial reporting and budgeting. For sales tax revenues reflecting consumer activity periods (period when the taxes where collected by businesses), see "Citywide Tax Revenue by Report Month" at https://data.mesaaz.gov/Financials/Citywide-Tax-Revenue-by-Report-Month/8y5v-kwui. Sales tax revenue includes Transaction Privilege Tax (TPT) and Transient Lodging Tax (TLT). Effective January 2017, the Arizona Department of Revenue administers sales and use tax collection for all state, county and municipal taxing jurisdictions. Visit https://www.mesaaz.gov/business/tax-audit for more information about sales tax in the City of Mesa.
City Revenues (RETIRED)

**This dataset is no longer actively updated and is replaced by [https://citydata.mesaaz.gov/Office-of-Management-and-Budget/City-Revenues/ntuh-v7ru/about_data].** Listing of all City revenues per department. This data includes transactions received by check and cash. Includes record date, customer, amount and the accounting string that describes which fund and organizational department benefited from the transaction. The data contained on this website is for informational purposes only and represents revenue transactions of the City of Mesa. The data includes transactions received by check and cash. The data as represented is unaudited and may contain omissions. For audited financial statements please reference the Comprehensive Annual Financial Report (CAFR). Certain Mesa customer names have been redacted for confidentiality and safety issues; therefore not all customer names are represented. Certain Activity assignments may change mid-year. This year-to-date information is updated monthly and represents the most current activity assignment regardless of the assignment at the time of the transaction.