Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This item has been archived. It is no longer being updated.For current COVID-19 cases data updates, please see the COVID-19 Cases Per 100,000 by Zip Code dashboard, which shows the COVID-19 case rate per 100,000 population by week for each zip code and is supported by the weekly release of data from the Maricopa County Department of Public Health (MCDPH) https://data.tempe.gov/datasets/covid-19-case-indicators/explore.--------As of 3/2/2022 the Arizona Department of Health Services has shifted to a weekly update schedule. We've adjusted our process to update every Wednesday afternoon.This table provides a weekly log of confirmed COVID-19 cases by Zip Code. Data are provided by the Arizona Department of Health Services (ADHS). Data Source: Arizona Department of Health Services (AZDHS) daily COVID-19 report by zip code (https://adhsgis.maps.arcgis.com/apps/opsdashboard/index.html#/84b7f701060641ca8bd9ea0717790906). Daily Change is calculated by taking the current day’s case value for a given Postal Code and subtracting the prior day’s value. This resulting value is the Daily Change. Based on reporting from ADHS Daily Change may be a positive or negative number or 0 if no change has been reported. Moving Average is calculated by summing the current day’s case count with the prior 6 days’ cases for a given Postal Code and dividing by 7.Arizona Department of Health Services (AZDHS) data are scheduled for daily updates at 9:00 AM (COVID-19 cases) and 12:00 PM (COVID-19 vaccinations), but the times when the AZDHS releases that days COVID-19 cases and vaccinations may vary. City of Tempe data are updated each afternoon at 3:00 PM to allow for possible AZDHS delays. When there are AZDHS delays in updating the daily data, dashboard data updates may be delayed by 24 hours. The charts and daily values list can be used to confirm the date of the most recent counts on the COVID-19 cases and vaccinations dashboards. If data are not released by the time of the scheduled daily dashboard refresh, that day's values may appear on the dashboard as an addition to the next day's value.Additional InformationSource: Arizona Department of Health Services (AZDHS) daily COVID-19 report by zip code (https://adhsgis.maps.arcgis.com/apps/opsdashboard/index.html#/84b7f701060641ca8bd9ea0717790906)Contact (author): n/aContact E-Mail (author): n/aContact (maintainer): City of Tempe Open Data TeamContact E-Mail (maintainer): data@tempe.govData Source Type: TablePreparation Method: Data are exposed via ArcGIS Server and its REST API.Publish Frequency: DailyPublish Method: Data are downloaded each afternoon once ADHS updates its public API. Data are transformed and appended to a table in Tempe’s Enterprise GIS.Data Dictionary
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Project Tycho datasets contain case counts for reported disease conditions for countries around the world. The Project Tycho data curation team extracts these case counts from various reputable sources, typically from national or international health authorities, such as the US Centers for Disease Control or the World Health Organization. These original data sources include both open- and restricted-access sources. For restricted-access sources, the Project Tycho team has obtained permission for redistribution from data contributors. All datasets contain case count data that are identical to counts published in the original source and no counts have been modified in any way by the Project Tycho team, except for aggregation of individual case count data into daily counts when that was the best data available for a disease and location. The Project Tycho team has pre-processed datasets by adding new variables, such as standard disease and location identifiers, that improve data interpretability. We also formatted the data into a standard data format. All geographic locations at the country and admin1 level have been represented at the same geographic level as in the data source, provided an ISO code or codes could be identified, unless the data source specifies that the location is listed at an inaccurate geographical level. For more information about decisions made by the curation team, recommended data processing steps, and the data sources used, please see the README that is included in the dataset download ZIP file.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Context
The dataset tabulates the Maricopa population by race and ethnicity. The dataset can be utilized to understand the racial distribution of Maricopa.
The dataset will have the following datasets when applicable
Please note that in case when either of Hispanic or Non-Hispanic population doesnt exist, the respective dataset will not be available (as there will not be a population subset applicable for the same)
Good to know
Margin of Error
Data in the dataset are based on the estimates and are subject to sampling variability and thus a margin of error. Neilsberg Research recommends using caution when presening these estimates in your research.
Custom data
If you do need custom data for any of your research project, report or presentation, you can contact our research staff at research@neilsberg.com for a feasibility of a custom tabulation on a fee-for-service basis.
Neilsberg Research Team curates, analyze and publishes demographics and economic data from a variety of public and proprietary sources, each of which often includes multiple surveys and programs. The large majority of Neilsberg Research aggregated datasets and insights is made available for free download at https://www.neilsberg.com/research/.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Context
The dataset tabulates the Phoenix population by race and ethnicity. The dataset can be utilized to understand the racial distribution of Phoenix.
The dataset will have the following datasets when applicable
Please note that in case when either of Hispanic or Non-Hispanic population doesnt exist, the respective dataset will not be available (as there will not be a population subset applicable for the same)
Good to know
Margin of Error
Data in the dataset are based on the estimates and are subject to sampling variability and thus a margin of error. Neilsberg Research recommends using caution when presening these estimates in your research.
Custom data
If you do need custom data for any of your research project, report or presentation, you can contact our research staff at research@neilsberg.com for a feasibility of a custom tabulation on a fee-for-service basis.
Neilsberg Research Team curates, analyze and publishes demographics and economic data from a variety of public and proprietary sources, each of which often includes multiple surveys and programs. The large majority of Neilsberg Research aggregated datasets and insights is made available for free download at https://www.neilsberg.com/research/.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Context
The dataset tabulates the Surprise population by race and ethnicity. The dataset can be utilized to understand the racial distribution of Surprise.
The dataset will have the following datasets when applicable
Please note that in case when either of Hispanic or Non-Hispanic population doesnt exist, the respective dataset will not be available (as there will not be a population subset applicable for the same)
Good to know
Margin of Error
Data in the dataset are based on the estimates and are subject to sampling variability and thus a margin of error. Neilsberg Research recommends using caution when presening these estimates in your research.
Custom data
If you do need custom data for any of your research project, report or presentation, you can contact our research staff at research@neilsberg.com for a feasibility of a custom tabulation on a fee-for-service basis.
Neilsberg Research Team curates, analyze and publishes demographics and economic data from a variety of public and proprietary sources, each of which often includes multiple surveys and programs. The large majority of Neilsberg Research aggregated datasets and insights is made available for free download at https://www.neilsberg.com/research/.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Analysis of ‘COVID-19 HPSC Detailed Statistics Profile’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from http://data.europa.eu/88u/dataset/9ea959dd-3b80-4e9b-8f06-f3e73f3e0e21 on 12 January 2022.
--- Dataset description provided by original source is as follows ---
Please see FAQ for latest information on COVID-19 Data Hub Data Flows. https://covid-19.geohive.ie/pages/helpfaqs
Notice:
A technical issue impacted processing of COVID-19 cases on CIDR on 2/11/2021. Given the impact on CIDR notifications, the daily case numbers reported between 3rd and 8th November, were based on SARS-CoV-2 results uploaded to the COVID Care Tracker. These data were provisional. The number of cases reported as ‘Latest Daily Cases’ (ConfirmedCovidCases in open data) and ‘Total Confirmed Cases’ (CovidCasesConfirmed in open data) on the COVID-19 Data Hub for those dates reflect reported cases from the COVID Care Tracker. Reporting of daily cases and cumulative total cases based on notifications on CIDR recommenced from 9th November onwards.
Data contained in all other Profile data fields (e.g. county, age, hospitalised, healthcare workers) are based on CIDR notifications. Data contained in the HPSC ‘COVID-19 14-day epidemiology reports’ is also based on CIDR notifications and further details is available here https://www.hpsc.ie/a-z/respiratory/coronavirus/novelcoronavirus/surveillance/covid-1914-dayepidemiologyreports/.
Note: This service is only updated Monday-Friday. Records in the service created on a Saturday and a Sunday will be the same as updated on the Friday. This may have an impact on users who are consuming the services when calculating averages over time. All records in the service for the weekend will be provided in the normal open data update each Monday evening. There will be no gaps in the time series. As CIDR data is subject to ongoing review, validation and update, there may be revisions to previously published data. It is advised to always download the latest version of the open data for use.
Notice:
The Health Service Executive’s (HSE) IT systems suffered a major cyber-attack on Friday 14 May 2021. As a consequence, updates of the data in some fields of this layer were paused. Updates of the following fields were not paused: 'ConfirmedCovidCases' and 'TotalConfirmedCovidCases'. From 17 June 2021 onwards, all notified COVID-19 related deaths are reported on a weekly, rather than a daily, basis in this table in the field 'TotalCovidDeaths'. Updates to other fields in this service were paused between 15 May and 1 September 2021. This pause in updates affected data dated from 12 May to 31 August 2021. On 2 September updates to all the paused fields except ‘CloseContact’, ‘CommunityTransmission’, ‘HealthcareWorkersCovidCases’, 'TravelAbroad', and ‘UnderInvestigation’ resumed. These resumed updates include the data from the date range of the paused updates (12 May to 31 August 2021). On 27 October 2021 updates to the 'HealthcareWorkersCovidCases' field resumed, including the data from the date range of its paused updates (12 May to 26 October 2021).
Data for the period impacted by the cyber-attack (14 May-31 August 2021) should continue to be interpreted with caution. CIDR, as the national surveillance system is the definitive source for validated data on COVID-19 cases in Ireland which meet Irish and European case definitions.
Full details on the recommencement of reporting from CIDR can be found on the HPSC website
*** Notice ***
Please be advised that on 29th April 2021, the 'Aged65up' and 'HospitalisedAged65up' fields were removed from this table.
The three fields 'Aged65to74', 'Aged75to84', and 'Aged85up' replace the 'Aged65up' field.
<pThe TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national filewith no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independentdata set, or they can be combined to cover the entire nation. Linear Water Features includes single-line drainage water features and artificial path features that run through double-line drainage features such as rivers and streams, and serve as a linear representation of these features. The artificial path features may correspond to those in the USGS National Hydrographic Dataset (NHD). However, in many cases the features do not match NHD equivalent feature and will not carry the NHD metadata codes. These features have a MAF/TIGER Feature Classification Code (MTFCC) beginning with an "H" to indicate the super class of Hydrographic Features.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Context
The dataset tabulates the Scottsdale population by race and ethnicity. The dataset can be utilized to understand the racial distribution of Scottsdale.
The dataset will have the following datasets when applicable
Please note that in case when either of Hispanic or Non-Hispanic population doesnt exist, the respective dataset will not be available (as there will not be a population subset applicable for the same)
Good to know
Margin of Error
Data in the dataset are based on the estimates and are subject to sampling variability and thus a margin of error. Neilsberg Research recommends using caution when presening these estimates in your research.
Custom data
If you do need custom data for any of your research project, report or presentation, you can contact our research staff at research@neilsberg.com for a feasibility of a custom tabulation on a fee-for-service basis.
Neilsberg Research Team curates, analyze and publishes demographics and economic data from a variety of public and proprietary sources, each of which often includes multiple surveys and programs. The large majority of Neilsberg Research aggregated datasets and insights is made available for free download at https://www.neilsberg.com/research/.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Context
The dataset tabulates the Eagar population by race and ethnicity. The dataset can be utilized to understand the racial distribution of Eagar.
The dataset will have the following datasets when applicable
Please note that in case when either of Hispanic or Non-Hispanic population doesnt exist, the respective dataset will not be available (as there will not be a population subset applicable for the same)
Good to know
Margin of Error
Data in the dataset are based on the estimates and are subject to sampling variability and thus a margin of error. Neilsberg Research recommends using caution when presening these estimates in your research.
Custom data
If you do need custom data for any of your research project, report or presentation, you can contact our research staff at research@neilsberg.com for a feasibility of a custom tabulation on a fee-for-service basis.
Neilsberg Research Team curates, analyze and publishes demographics and economic data from a variety of public and proprietary sources, each of which often includes multiple surveys and programs. The large majority of Neilsberg Research aggregated datasets and insights is made available for free download at https://www.neilsberg.com/research/.
The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national filewith no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independentdata set, or they can be combined to cover the entire nation. Linear Water Features includes single-line drainage water features and artificial path features that run through double-line drainage features such as rivers and streams, and serve as a linear representation of these features. The artificial path features may correspond to those in the USGS National Hydrographic Dataset (NHD). However, in many cases the features do not match NHD equivalent feature and will not carry the NHD metadata codes. These features have a MAF/TIGER Feature Classification Code (MTFCC) beginning with an "H" to indicate the super class of Hydrographic Features.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Context
The dataset tabulates the Navajo County population by race and ethnicity. The dataset can be utilized to understand the racial distribution of Navajo County.
The dataset will have the following datasets when applicable
Please note that in case when either of Hispanic or Non-Hispanic population doesnt exist, the respective dataset will not be available (as there will not be a population subset applicable for the same)
Good to know
Margin of Error
Data in the dataset are based on the estimates and are subject to sampling variability and thus a margin of error. Neilsberg Research recommends using caution when presening these estimates in your research.
Custom data
If you do need custom data for any of your research project, report or presentation, you can contact our research staff at research@neilsberg.com for a feasibility of a custom tabulation on a fee-for-service basis.
Neilsberg Research Team curates, analyze and publishes demographics and economic data from a variety of public and proprietary sources, each of which often includes multiple surveys and programs. The large majority of Neilsberg Research aggregated datasets and insights is made available for free download at https://www.neilsberg.com/research/.
This data release contains numerous comma-separated text files with data summarizing observations in the within and adjacent to the Woodbury Fire, which burned from 8 June to 15 July 2019. In particular, this monitoring data was focused on debris flows in burned and unburned areas. Rainfall data (Wdby_Rainfall.zip) are contained in csv files called Wdby_Rainfall for 3 rain gages named: B2, B6, and Reavis. This is time-series data where the total rainfall is recorded at each timestamp. The location of each rain gage is listed as a latitude/longitude in each file. Data from absolute (i.e. not vented) pressure transducers (Wdby_Pressure.zip), which can be used to constrain the time of passage of a flood or debris flow, are available in csv files called Wdby_Pressure for four drainages (B1, B6, Reavis 1, and Reavis 2). This is time-series data where the measured pressure in kilopascals is recorded at each timestamp. The location of each pressure transducer is listed as a latitude/longitude in each file. Infiltration data are located in the csv file called WoodburyInfiltration.csv. The location of the measurement is listed as a latitude/longitude. Three measurement values are reported at each location: Saturated Hydraulic Conductivity (Ks) [mm/hr], Sorptivity (S) [mm/h^(1/2)], and pressure head (hf) [m]. The date of each measurement and soil burn severity class are also reported at each location, as well as a table explaining the burn-severity numerical class conversion. Particle size analyses using laser diffraction (WoodburyLaserDiffractionSummary.zip) are located in the files called WoodburyLaserDiffractionSummary for the fine fraction (< 2 mm) of hillslope and debris flow Deposits. The diameter of each particle size class is listed in the first column. All subsequent columns begin with the sample name. The value in each row is the percentage of the grain sizes in the size class. Location data for each of these samples is listed in the accompanying data table titled: WoodburyParticleSizeSummary.csv. The particle size data are summarized in the csv files (WoodburyParticleSizeSummary.zip) called WoodburyParticleSizeSummary by debris flow deposits and hillslope samples. These files group the raw data into more useable information. The sample name (Lab ID) is used to identify the Laser Diffraction data. The data columns (Lat) and (Lon) show the latitude and longitude of the sample locations. The total fraction of all the grain sizes, determined by sieving, are listed in three classes (Fraction < 16 mm, Fraction < 4 mm, Fraction < 2 mm). The fine fractions (< 2 mm) are also summarized in the columns (%Sand, %Silt, %Clay), as determined by laser diffraction. The data are identfied as in the burn area using entries of Yes, whereas unburned areas are shown as No, indicating no burn. The median particle size (D50) is listed if the sample collected in the field was representative of the deposit. In some cases, large cobbles and boulders had to be removed from the sample because were much too large to be included in sample bags that were brought back to the lab for analysis. The last column label (Description) contains notes about each sample. Pebble count data (WoodburyPebbleCountsSummary.zip) are available in csv files called WoodburyPebbleCountsSummary for six drainages (U10 Fan, U10 Channel, U22 Channel, B1 Channel, B7 Fan, and U42 Fan). Here U represents unburned, and B represents burned. The data name indicates whether the data come from a deposit located in a channel or a fan. In each file the particle is numbered (Num) and the B-axis measurement of the particle is reported in centimeters. The location of each pebble count is listed as a latitude/longitude in each file. Channel width measurements for 23 channels are saved in unique shapefiles within the file called Channel_Width_Transects.zip. These width measurements were made using Digital Globe imagery from 19 October 2019. The study basins used for the entire study can be found in the shapefile: Woodbury_StudyBasins.shp. The attribute table along with many morphometric and fire related statistics for each basin is also available in the file Woodbury_StudyBasins_Table.csv. A description of each column name in the table is available in the file Woodbury_StudyBasins_Table_descriptions.csv. Debris flow volumes were available in eleven drainage basins. The volume data is contained in the file Wdby_FlowVolume.csv in a column named (Volume). The volume units are cubic meters. The other column is the Basin ID, which can be found in the shapefile: Woodbury_StudyBasins.shp.
The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national filewith no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independentdata set, or they can be combined to cover the entire nation. Linear Water Features includes single-line drainage water features and artificial path features that run through double-line drainage features such as rivers and streams, and serve as a linear representation of these features. The artificial path features may correspond to those in the USGS National Hydrographic Dataset (NHD). However, in many cases the features do not match NHD equivalent feature and will not carry the NHD metadata codes. These features have a MAF/TIGER Feature Classification Code (MTFCC) beginning with an "H" to indicate the super class of Hydrographic Features.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Updated: As of 7/3/2021 the Arizona Department of Health Services is no longer updated its vaccination data. This item has been deprecated as a result.This table provides a daily log of confirmed COVID-19 vaccinations by Zip Code for the state of Arizona. Data are provided by the Arizona Department of Health Services (ADHS). Data Source: Arizona Department of Health Services (AZDHS) daily COVID-19 vaccinations report by zip code (https://experience.arcgis.com/experience/bcf70a0f5cac4262a411166dbcac9053). Daily Change is calculated by taking the current day’s vaccination value for a given Postal Code and subtracting the prior day’s value. This resulting value is the Daily Change. Based on reporting from ADHS Daily Change may be a positive or negative number or 0 if no change has been reported. Arizona Department of Health Services (AZDHS) data are scheduled for daily updates at 9:00 AM (COVID-19 cases) and 12:00 PM (COVID-19 vaccinations), but the times when the AZDHS releases that days COVID-19 cases and vaccinations may vary. City of Tempe data are updated each afternoon at 3:00 PM to allow for possible AZDHS delays. When there are AZDHS delays in updating the daily data, dashboard data updates may be delayed by 24 hours. The charts and daily values list can be used to confirm the date of the most recent counts on the COVID-19 cases and vaccinations dashboards. If data are not released by the time of the scheduled daily dashboard refresh, that day's values may appear on the dashboard as an addition to the next day's value.---------------------------------------------------Please also see the following items for up-to-date COVID-19 vaccination data:COVID-19 Vaccination Rates by Zip Code (Maricopa County)https://data.tempe.gov/datasets/covid-19-vaccination-rates-by-zip-code-maricopa-county/exploreCOVID-19 Vaccination Rates by City (Maricopa County)https://data.tempe.gov/datasets/covid-19-vaccination-rates-by-city-maricopa-county/explore ---------------------------------------------------Additional InformationSource: Arizona Department of Health Services (AZDHS) daily COVID-19 vaccinations report by zip code (https://experience.arcgis.com/experience/bcf70a0f5cac4262a411166dbcac9053)Contact (author): n/aContact E-Mail (author): n/aContact (maintainer): City of Tempe Open Data TeamContact E-Mail (maintainer): data@tempe.govData Source Type: TablePreparation Method: Data are exposed via ArcGIS Server and its REST API.Publish Frequency: DailyPublish Method: Data are downloaded each afternoon once ADHS updates its public API. Data are transformed and appended to a table in Tempe’s Enterprise GIS.Data Dictionary
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national filewith no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independentdata set, or they can be combined to cover the entire nation. Linear Water Features includes single-line drainage water features and artificial path features that run through double-line drainage features such as rivers and streams, and serve as a linear representation of these features. The artificial path features may correspond to those in the USGS National Hydrographic Dataset (NHD). However, in many cases the features do not match NHD equivalent feature and will not carry the NHD metadata codes. These features have a MAF/TIGER Feature Classification Code (MTFCC) beginning with an "H" to indicate the super class of Hydrographic Features.
https://www.icpsr.umich.edu/web/ICPSR/studies/20358/termshttps://www.icpsr.umich.edu/web/ICPSR/studies/20358/terms
The project goal was to collect data on approximately 100 Unified Family Court (UFC) cases at each of the three selected jurisdictions -- Maricopa County, Arizona, Deschutes County, Oregon, and Jackson County, Oregon -- that have developed systems to address the special needs of families with multiple court cases. The purpose of the study was to examine research questions related to: (1) dependency case processing and outcomes, (2) delinquency case processing and outcomes, (3) domestic relations/probate case processing and outcomes, and (4) criminal case processing and outcomes. The data used in this study were generated from a review of the court records of 602 families including 406 families served by the UFC as well as comparison groups of 196 non-UFC multi-case families. During the study's planning phase, an instrument was drafted for use in extracting this information. Data collectors were recruited from former UFC staff and current and former non-UFC court staff. All data collectors were trained by the principal investigator in the use of the data collection form. The vast majority of all data extraction required a manual review of paper files. Variables in this dataset are organized into the following categories: background variables, items from dependency/abuse and neglect filings, delinquency filings, domestic relations/probate filings, civil domestic violence/protection order filings, criminal domestic violence filings, criminal child abuse filings, other criminal filings, and variables from a summary across cases.
The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national filewith no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independentdata set, or they can be combined to cover the entire nation. Linear Water Features includes single-line drainage water features and artificial path features that run through double-line drainage features such as rivers and streams, and serve as a linear representation of these features. The artificial path features may correspond to those in the USGS National Hydrographic Dataset (NHD). However, in many cases the features do not match NHD equivalent feature and will not carry the NHD metadata codes. These features have a MAF/TIGER Feature Classification Code (MTFCC) beginning with an "H" to indicate the super class of Hydrographic Features.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Context
The dataset tabulates the Clarkdale population by race and ethnicity. The dataset can be utilized to understand the racial distribution of Clarkdale.
The dataset will have the following datasets when applicable
Please note that in case when either of Hispanic or Non-Hispanic population doesnt exist, the respective dataset will not be available (as there will not be a population subset applicable for the same)
Good to know
Margin of Error
Data in the dataset are based on the estimates and are subject to sampling variability and thus a margin of error. Neilsberg Research recommends using caution when presening these estimates in your research.
Custom data
If you do need custom data for any of your research project, report or presentation, you can contact our research staff at research@neilsberg.com for a feasibility of a custom tabulation on a fee-for-service basis.
Neilsberg Research Team curates, analyze and publishes demographics and economic data from a variety of public and proprietary sources, each of which often includes multiple surveys and programs. The large majority of Neilsberg Research aggregated datasets and insights is made available for free download at https://www.neilsberg.com/research/.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Context
The dataset tabulates the Pinal County population by race and ethnicity. The dataset can be utilized to understand the racial distribution of Pinal County.
The dataset will have the following datasets when applicable
Please note that in case when either of Hispanic or Non-Hispanic population doesnt exist, the respective dataset will not be available (as there will not be a population subset applicable for the same)
Good to know
Margin of Error
Data in the dataset are based on the estimates and are subject to sampling variability and thus a margin of error. Neilsberg Research recommends using caution when presening these estimates in your research.
Custom data
If you do need custom data for any of your research project, report or presentation, you can contact our research staff at research@neilsberg.com for a feasibility of a custom tabulation on a fee-for-service basis.
Neilsberg Research Team curates, analyze and publishes demographics and economic data from a variety of public and proprietary sources, each of which often includes multiple surveys and programs. The large majority of Neilsberg Research aggregated datasets and insights is made available for free download at https://www.neilsberg.com/research/.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Context
The dataset tabulates the Jerome population by race and ethnicity. The dataset can be utilized to understand the racial distribution of Jerome.
The dataset will have the following datasets when applicable
Please note that in case when either of Hispanic or Non-Hispanic population doesnt exist, the respective dataset will not be available (as there will not be a population subset applicable for the same)
Good to know
Margin of Error
Data in the dataset are based on the estimates and are subject to sampling variability and thus a margin of error. Neilsberg Research recommends using caution when presening these estimates in your research.
Custom data
If you do need custom data for any of your research project, report or presentation, you can contact our research staff at research@neilsberg.com for a feasibility of a custom tabulation on a fee-for-service basis.
Neilsberg Research Team curates, analyze and publishes demographics and economic data from a variety of public and proprietary sources, each of which often includes multiple surveys and programs. The large majority of Neilsberg Research aggregated datasets and insights is made available for free download at https://www.neilsberg.com/research/.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This item has been archived. It is no longer being updated.For current COVID-19 cases data updates, please see the COVID-19 Cases Per 100,000 by Zip Code dashboard, which shows the COVID-19 case rate per 100,000 population by week for each zip code and is supported by the weekly release of data from the Maricopa County Department of Public Health (MCDPH) https://data.tempe.gov/datasets/covid-19-case-indicators/explore.--------As of 3/2/2022 the Arizona Department of Health Services has shifted to a weekly update schedule. We've adjusted our process to update every Wednesday afternoon.This table provides a weekly log of confirmed COVID-19 cases by Zip Code. Data are provided by the Arizona Department of Health Services (ADHS). Data Source: Arizona Department of Health Services (AZDHS) daily COVID-19 report by zip code (https://adhsgis.maps.arcgis.com/apps/opsdashboard/index.html#/84b7f701060641ca8bd9ea0717790906). Daily Change is calculated by taking the current day’s case value for a given Postal Code and subtracting the prior day’s value. This resulting value is the Daily Change. Based on reporting from ADHS Daily Change may be a positive or negative number or 0 if no change has been reported. Moving Average is calculated by summing the current day’s case count with the prior 6 days’ cases for a given Postal Code and dividing by 7.Arizona Department of Health Services (AZDHS) data are scheduled for daily updates at 9:00 AM (COVID-19 cases) and 12:00 PM (COVID-19 vaccinations), but the times when the AZDHS releases that days COVID-19 cases and vaccinations may vary. City of Tempe data are updated each afternoon at 3:00 PM to allow for possible AZDHS delays. When there are AZDHS delays in updating the daily data, dashboard data updates may be delayed by 24 hours. The charts and daily values list can be used to confirm the date of the most recent counts on the COVID-19 cases and vaccinations dashboards. If data are not released by the time of the scheduled daily dashboard refresh, that day's values may appear on the dashboard as an addition to the next day's value.Additional InformationSource: Arizona Department of Health Services (AZDHS) daily COVID-19 report by zip code (https://adhsgis.maps.arcgis.com/apps/opsdashboard/index.html#/84b7f701060641ca8bd9ea0717790906)Contact (author): n/aContact E-Mail (author): n/aContact (maintainer): City of Tempe Open Data TeamContact E-Mail (maintainer): data@tempe.govData Source Type: TablePreparation Method: Data are exposed via ArcGIS Server and its REST API.Publish Frequency: DailyPublish Method: Data are downloaded each afternoon once ADHS updates its public API. Data are transformed and appended to a table in Tempe’s Enterprise GIS.Data Dictionary