Facebook
TwitterWelcome to the Kaggle dataset on The Impact of COVID-19 on Veterans in the United States! This dataset contains data on confirmed cases of COVID-19 in counties across the United States, as well as information on the percentage of each county's population that are veterans. With this dataset, you can investigate how the pandemic has impacted veterans specifically, and compare veteran case rates to the general population. How do veteran cases differ across age groups? Are there any geographical patterns? What can we learn about risk factors for COVID-19 among veterans? Download the dataset and explore for yourself today!
This dataset includes information on the number of confirmed cases of COVID-19 by county, as well as the percentage of the population in each county that are veterans. This data can be used to examine the relationship between veteran cases and the proportion of population who are veterans.
To do this, simply look at the 'CASES' and 'VET_CASES' columns for each county. The 'CASES' column represents the total number of confirmed cases of COVID-19 in that county, while the 'VET_CASES' column represents the number of confirmed cases among veterans. To compare these two values, simply divide 'VET_CASES' by 'CASES'. This will give you a ratio of veteran cases to total cases for each county.
You can then use this ratio to compare counties and see which ones have a higher proportion of veteran cases. This data can be used to help understand where more outreach may be needed to support veterans during this pandemic
File: CountyVACOVID.csv | Column name | Description | |:---------------------------|:-----------------------------------------------------------------------------------------------------------------------| | FIPS | Federal Information Processing Standards code that uniquely identifies counties within the USA. (String) | | COUNTY | County name. (String) | | STATE | State name. (String) | | POP | County population. (Integer) | | VETS | Number of veterans in the county. (Integer) | | VET_PERCENT | Percentage of the population that are veterans. (Float) | | CASES | Number of confirmed cases of COVID-19 in the county. (Integer) | | YESTER_CASES | Number of confirmed cases of COVID-19 in the county from the previous day. (Integer) | | VET_CASES | Number of confirmed cases of COVID-19 in veterans in the county. (Integer) | | VET_YESTER | Number of confirmed cases of COVID-19 in veterans in the county from the previous day. (Integer) | | LOWER_Hospitalizations | Lower bound of the 95% confidence interval for the number of hospitalizations due to COVID-19 in the county. (Integer) | | UPPER_Hospitalizations | Upper bound of the 95% confidence interval for the number of hospitalizations due to COVID-19 in the county. (Integer) | | DATE | Date of data. (Date) |
File: VAChart.csv | Column name | Description | |:------------------------|:----------------------------------------------------------------------------------| | DATE | Date of data. (Date) | | US Cases | The number of confirmed cases of COVID-19 in the United States. (Integer) | | **New US ...
Facebook
Twitterhttps://www.usa.gov/government-works/https://www.usa.gov/government-works/
The Military Bases dataset is as of May 21, 2019, and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics's (BTS's) National Transportation Atlas Database (NTAD). The dataset depicts the authoritative boundaries of the most commonly known Department of Defense (DoD) sites, installations, ranges, and training areas in the United States and Territories. These sites encompass land which is federally owned or otherwise managed. This dataset was created from source data provided by the four Military Service Component headquarters and was compiled by the Defense Installation Spatial Data Infrastructure (DISDI) Program within the Office of the Deputy Under Secretary of Defense for Installations and Environment, Business Enterprise Integration Directorate. Sites were selected from the 2010 Base Structure Report (BSR), a summary of the DoD Real Property Inventory. This list does not necessarily represent a comprehensive collection of all Department of Defense facilities, and only those in the fifty United States and US Territories were considered for inclusion. For inventory purposes, installations are comprised of sites, where a site is defined as a specific geographic location of federally owned or managed land and is assigned to military installation. DoD installations are commonly referred to as a base, camp, post, station, yard, center, homeport facility for any ship, or other activity under the jurisdiction, custody, control of the DoD.
Foto von israel palacio auf Unsplash
Facebook
TwitterAttribution-ShareAlike 4.0 (CC BY-SA 4.0)https://creativecommons.org/licenses/by-sa/4.0/
License information was derived automatically
SELECTED SOCIAL CHARACTERISTICS IN THE UNITED STATES VETERAN STATUS - DP02 Universe - Civilian population 18 Year and over Survey-Program - American Community Survey 5-year estimates Years - 2020, 2021, 2022 Veteran status is used to identify people with active duty military service and service in the military Reserves and the National Guard. Veterans are men and women who have served (even for a short time), but are not currently serving, on active duty in the U.S. Army, Navy, Air Force, Marine Corps, or the Coast Guard, or who served in the U.S. Merchant Marine during World War II. People who served in the National Guard or Reserves are classified as veterans only if they were ever called or ordered to active duty, not counting the 4-6 months for initial training or yearly summer camps.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This dataset is about countries in Central America. It has 8 rows. It features 3 columns: military expenditure, and population.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This dataset is about countries per year in Northern America. It has 2 rows and is filtered where the date is 2021. It features 4 columns: country, military expenditure, and rural population.
Facebook
Twitteranalyze the current population survey (cps) annual social and economic supplement (asec) with r the annual march cps-asec has been supplying the statistics for the census bureau's report on income, poverty, and health insurance coverage since 1948. wow. the us census bureau and the bureau of labor statistics ( bls) tag-team on this one. until the american community survey (acs) hit the scene in the early aughts (2000s), the current population survey had the largest sample size of all the annual general demographic data sets outside of the decennial census - about two hundred thousand respondents. this provides enough sample to conduct state- and a few large metro area-level analyses. your sample size will vanish if you start investigating subgroups b y state - consider pooling multiple years. county-level is a no-no. despite the american community survey's larger size, the cps-asec contains many more variables related to employment, sources of income, and insurance - and can be trended back to harry truman's presidency. aside from questions specifically asked about an annual experience (like income), many of the questions in this march data set should be t reated as point-in-time statistics. cps-asec generalizes to the united states non-institutional, non-active duty military population. the national bureau of economic research (nber) provides sas, spss, and stata importation scripts to create a rectangular file (rectangular data means only person-level records; household- and family-level information gets attached to each person). to import these files into r, the parse.SAScii function uses nber's sas code to determine how to import the fixed-width file, then RSQLite to put everything into a schnazzy database. you can try reading through the nber march 2012 sas importation code yourself, but it's a bit of a proc freak show. this new github repository contains three scripts: 2005-2012 asec - download all microdata.R down load the fixed-width file containing household, family, and person records import by separating this file into three tables, then merge 'em together at the person-level download the fixed-width file containing the person-level replicate weights merge the rectangular person-level file with the replicate weights, then store it in a sql database create a new variable - one - in the data table 2012 asec - analysis examples.R connect to the sql database created by the 'download all microdata' progr am create the complex sample survey object, using the replicate weights perform a boatload of analysis examples replicate census estimates - 2011.R connect to the sql database created by the 'download all microdata' program create the complex sample survey object, using the replicate weights match the sas output shown in the png file below 2011 asec replicate weight sas output.png statistic and standard error generated from the replicate-weighted example sas script contained in this census-provided person replicate weights usage instructions document. click here to view these three scripts for more detail about the current population survey - annual social and economic supplement (cps-asec), visit: the census bureau's current population survey page the bureau of labor statistics' current population survey page the current population survey's wikipedia article notes: interviews are conducted in march about experiences during the previous year. the file labeled 2012 includes information (income, work experience, health insurance) pertaining to 2011. when you use the current populat ion survey to talk about america, subract a year from the data file name. as of the 2010 file (the interview focusing on america during 2009), the cps-asec contains exciting new medical out-of-pocket spending variables most useful for supplemental (medical spending-adjusted) poverty research. confidential to sas, spss, stata, sudaan users: why are you still rubbing two sticks together after we've invented the butane lighter? time to transition to r. :D
Facebook
Twitterhttp://www.gnu.org/licenses/old-licenses/gpl-2.0.en.htmlhttp://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html
This dataset has records for the awarding of the United States Medal of Honor. The Medal of Honor is the United States of America’s highest military honor, awarded for personal acts of valor above and beyond the call of duty. The medal is awarded by the President of the United States in the name of the U.S. Congress to U.S. military personnel only. There are three versions of the medal, one for the Army, one for the Navy, and one for the Air Force.[5] Personnel of the Marine Corps and Coast Guard receive the Navy version. The dataset was collected from the official military site, and includes records about how the medal was awarded and characteristics of the recipient. Unfortunately, because of the nature of century-old record keeping, many of the records are incomplete. While a very interesting dataset, it does have some missing data.
| Key | List of... | Comment | Example Value |
|---|---|---|---|
| death | Boolean | $MISSING_FIELD | True |
| name | String | $MISSING_FIELD | "Sagelhurst, John C." |
| awarded.General Order number | Integer | $MISSING_FIELD | -1 |
| awarded.accredited to | String | $MISSING_FIELD | "" |
| awarded.citation | String | $MISSING_FIELD | "Under a heavy fire from the enemy carried off the field a commissioned officer who was severely wounded and also led a charge on the enemy's rifle pits." |
| awarded.issued | String | $MISSING_FIELD | "01/03/1906" |
| birth.location name | String | $MISSING_FIELD | "Buffalo, N.Y." |
| metadata.link | String | $MISSING_FIELD | "http://www.cmohs.org/recipient-detail/1176/sagelhurst-john-c.php" |
| military record.company | String | $MISSING_FIELD | "Company B" |
| military record.division | String | $MISSING_FIELD | "1st New Jersey Cavalry" |
| military record.entered service at | String | $MISSING_FIELD | "Buffalo, N.Y." |
| military record.organization | String | $MISSING_FIELD | "U.S. Army" |
| military record.rank | String | $MISSING_FIELD | "Sergeant" |
| awarded.date.day | Integer | $MISSING_FIELD | 6 |
| awarded.date.full | String | $MISSING_FIELD | "1865-2-6" |
| awarded.date.month | Integer | $MISSING_FIELD | 2 |
| awarded.date.year | Integer | $MISSING_FIELD | 1865 |
| awarded.location.latitude | Integer | $MISSING_FIELD | 38 |
| awarded.location.longitude | Integer | $MISSING_FIELD | -77 |
| awarded.location.name | String | $MISSING_FIELD | "Hatchers Run Court, Stafford, VA 22554, USA" |
| birth.date.day | Integer | $MISSING_FIELD | -1 |
| birth.date.month | Integer | $MISSING_FIELD | -1 |
| birth.date.year | Integer | $MISSING_FIELD | -1 |
Foto von Samuel Branch auf Unsplash
Facebook
TwitterThe Military Bases dataset is as of May 21, 2019, and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics's (BTS's) National Transportation Atlas Database (NTAD). The dataset depicts the authoritative boundaries of the most commonly known Department of Defense (DoD) sites, installations, ranges, and training areas in the United States and Territories. These sites encompass land which is federally owned or otherwise managed. This dataset was created from source data provided by the four Military Service Component headquarters and was compiled by the Defense Installation Spatial Data Infrastructure (DISDI) Program within the Office of the Deputy Under Secretary of Defense for Installations and Environment, Business Enterprise Integration Directorate. Sites were selected from the 2010 Base Structure Report (BSR), a summary of the DoD Real Property Inventory. This list does not necessarily represent a comprehensive collection of all Department of Defense facilities, and only those in the fifty United States and US Territories were considered for inclusion. For inventory purposes, installations are comprised of sites, where a site is defined as a specific geographic location of federally owned or managed land and is assigned to military installation. DoD installations are commonly referred to as a base, camp, post, station, yard, center, homeport facility for any ship, or other activity under the jurisdiction, custody, control of the DoD.
Facebook
TwitterMunitions and explosives of concern (MEC) have been deposited on the seabed of the United States outer continental shelf since World War I. The bulk of these munitions have originated from the U.S. Armed Forces while conducting military training exercises, war-time placement, and disposal and dumping activities. Since 1972 ocean disposal of munitions and other pollutants has been banned by the Marine Protection, Research, and Sanctuaries Act. Federal and state efforts to mitigate, map, monitor, and sometimes remove these munitions are ongoing. The location of these munitions is generally unknown, and their existence remains a hazard to people and the natural resources within this geography. The term MEC defines a collection of munitions including; a) unexploded ordnance, b) discarded military munitions, and c) munitions constituents that are present in high enough concentrations to pose an explosive hazard. Additional information on the location of MECs can be found in the data and references listed below: Formerly Used Defense Sites Danger Zones and Restricted Areas U.S. Disposal of Chemical Weapons in the Ocean: Background and Issues for Congress, CRS Report for Congress, January 3, 2007 Defense Environmental Programs Annual Report to Congress for Fiscal Year 2009. Chapter 10. Sea Disposal of Military Munitions
Facebook
Twitterhttps://www.icpsr.umich.edu/web/ICPSR/studies/29646/termshttps://www.icpsr.umich.edu/web/ICPSR/studies/29646/terms
This data collection is comprised of responses from the March and April installments of the 2008 Current Population Survey (CPS). Both the March and April surveys used two sets of questions, the basic CPS and a separate supplement for each month.The CPS, administered monthly, is a labor force survey providing current estimates of the economic status and activities of the population of the United States. Specifically, the CPS provides estimates of total employment (both farm and nonfarm), nonfarm self-employed persons, domestics, and unpaid helpers in nonfarm family enterprises, wage and salaried employees, and estimates of total unemployment.In addition to the basic CPS questions, respondents were asked questions from the March supplement, known as the Annual Social and Economic (ASEC) supplement. The ASEC provides supplemental data on work experience, income, noncash benefits, and migration. Comprehensive work experience information was given on the employment status, occupation, and industry of persons 15 years old and older. Additional data for persons 15 years old and older are available concerning weeks worked and hours per week worked, reason not working full time, total income and income components, and place of residence on March 1, 2007. The March supplement also contains data covering nine noncash income sources: food stamps, school lunch program, employer-provided group health insurance plan, employer-provided pension plan, personal health insurance, Medicaid, Medicare, CHAMPUS or military health care, and energy assistance. Questions covering training and assistance received under welfare reform programs, such as job readiness training, child care services, or job skill training were also asked in the March supplement.The April supplement, sponsored by the Department of Health and Human Services, queried respondents on the economic situation of persons and families for the previous year. Moreover, all household members 15 years of age and older that are a biological parent of children in the household that have an absent parent were asked detailed questions about child support and alimony. Information regarding child support was collected to determine the size and distribution of the population with children affected by divorce or separation, or other relationship status change. Moreover, the data were collected to better understand the characteristics of persons requiring child support, and to help develop and maintain programs designed to assist in obtaining child support. These data highlight alimony and child support arrangements made at the time of separation or divorce, amount of payments actually received, and value and type of any property settlement.The April supplement data were matched to March supplement data for households that were in the sample in both March and April 2008. In March 2008, there were 4,522 household members eligible, of which 1,431 required imputation of child support data. When matching the March 2008 and April 2008 data sets, there were 170 eligible people on the March file that did not match to people on the April file. Child support data for these 170 people were imputed. The remaining 1,261 imputed cases were due to nonresponse to the child support questions. Demographic variables include age, sex, race, Hispanic origin, marital status, veteran status, educational attainment, occupation, and income. Data on employment and income refer to the preceding year, although other demographic data refer to the time at which the survey was administered.
Facebook
TwitterAnnual Population Estimates for the United States; States; Metropolitan Statistical Areas, Micropolitan Statistical Areas, and Related Statistical Areas; Counties; and Subcounty Places; and for Puerto Rico and Its Municipios: April 1, 2010 to July 1, 2016 // Source: U.S. Census Bureau, Population Division // The contents of this file are released on a rolling basis from December through May. // Note: The estimates are based on the 2010 Census and reflect changes to the April 1, 2010 population due to the Count Question Resolution program and geographic program revisions. // The Office of Management and Budget's statistical area delineations for metropolitan, micropolitan, and combined statistical areas, as well as metropolitan divisions, are those issued by that agency in July 2015. // The 2010 Census did not ascertain the military status of the household population. Therefore, variables for the 2010 Census civilian, civilian noninstitutionalized, and resident population plus Armed Forces overseas populations cannot be derived and are not available on this file. // For detailed information about the methods used to create the population estimates, see https://www.census.gov/programs-surveys/popest/technical-documentation/methodology.html. // Each year, the Census Bureau's Population Estimates Program (PEP) utilizes current data on births, deaths, and migration to calculate population change since the most recent decennial census, and produces a time series of estimates of population. The annual time series of estimates begins with the most recent decennial census data and extends to the vintage year. The vintage year (e.g., Vintage 2016) refers to the final year of the time series. The reference date for all estimates is July 1, unless otherwise specified. With each new issue of estimates, the Census Bureau revises estimates for years back to the last census. As each vintage of estimates includes all years since the most recent decennial census, the latest vintage of data available supersedes all previously produced estimates for those dates. The Population Estimates Program provides additional information including historical and intercensal estimates, evaluation estimates, demographic analysis, and research papers on its website: https://www.census.gov/programs-surveys/popest.html.
Facebook
TwitterAnnual Population Estimates for the United States; States; Metropolitan Statistical Areas, Micropolitan Statistical Areas, and Related Statistical Areas; Counties; and Subcounty Places; and for Puerto Rico and Its Municipios: April 1, 2010 to July 1, 2018 // Source: U.S. Census Bureau, Population Division // The contents of this file are released on a rolling basis from December through May. // Note: The estimates are based on the 2010 Census and reflect changes to the April 1, 2010 population due to the Count Question Resolution program and geographic program revisions. // The Office of Management and Budget's statistical area delineations for metropolitan, micropolitan, and combined statistical areas, as well as metropolitan divisions, are those issued by that agency in July 2015. // The 2010 Census did not ascertain the military status of the household population. Therefore, variables for the 2010 Census civilian, civilian noninstitutionalized, and resident population plus Armed Forces overseas populations cannot be derived and are not available on this file. // For detailed information about the methods used to create the population estimates, see https://www.census.gov/programs-surveys/popest/technical-documentation/methodology.html. // Each year, the Census Bureau's Population Estimates Program (PEP) utilizes current data on births, deaths, and migration to calculate population change since the most recent decennial census, and produces a time series of estimates of population. The annual time series of estimates begins with the most recent decennial census data and extends to the vintage year. The vintage year (e.g., Vintage 2017) refers to the final year of the time series. The reference date for all estimates is July 1, unless otherwise specified. With each new issue of estimates, the Census Bureau revises estimates for years back to the last census. As each vintage of estimates includes all years since the most recent decennial census, the latest vintage of data available supersedes all previously produced estimates for those dates. The Population Estimates Program provides additional information including historical and intercensal estimates, evaluation estimates, demographic analysis, and research papers on its website: https://www.census.gov/programs-surveys/popest.html.
Facebook
TwitterVBA EDUCATION BENEFITS PROGRAM to provide educational assistance to persons entering the Armed Forces after December 31, 1976, and before July 1, 1985; to assist persons in obtaining an education they might otherwise not be able to afford; and to promote and assist the all volunteer military program of the United States by attracting qualified persons to serve in the Armed Forces. The participant must have entered on active duty on or after January 1, 1977, and before July 1, 1985, and either served on active duty for more than 180 continuous days receiving an other than dishonorable discharge, or have been discharged after January, 1, 1977 because of a service-connected disability. Also eligible are participants who serve for more than 180 days and who continue on active duty and have completed their first period of obligated service (or 6 years of active duty, whichever comes first). Participants must also have satisfactorily contributed to the program. (Satisfactory contribution consists of monthly deduction of $25 to $100 from military pay, up to a maximum of $2,700, for deposit in a special training fund.) Participants may make lump-sum contributions. No individuals on active duty in the Armed Forces may initially begin contributing to this program after March 31, 1987.
Facebook
TwitterOpen Data Commons Attribution License (ODC-By) v1.0https://www.opendatacommons.org/licenses/by/1.0/
License information was derived automatically
The Department of Defense Health Agency’s (DHA) Vision Center of Excellence (VCE) analyzed data from the MHS MART database on behalf of the VEHSS project. MHS MART is a data management and reporting system used to support decision-making, health care analysis, and operational reporting. MART integrates various sources within MHS to provide a centralized repository for health care data, facilitating access to information that aids in managing health care services, resources, and performance across MHS.
Data are based on claims and encounter records in the MHS Management Analysis and Reporting Tool (MART) database. The population includes all active-duty and retired military members and their dependents in the MHS. The sample size is approximately 9.08 million persons.
These data are also available in the VEHSS Data Explorer, an interactive data visualization tool reporting prevalence information from more than 10 data sources: https://www.cdc.gov/vision-health-data/index.html
Facebook
TwitterState and Local Public Health Departments in the United States Governmental public health departments are responsible for creating and maintaining conditions that keep people healthy. A local health department may be locally governed, part of a region or district, be an office or an administrative unit of the state health department, or a hybrid of these. Furthermore, each community has a unique "public health system" comprising individuals and public and private entities that are engaged in activities that affect the public's health. (Excerpted from the Operational Definition of a functional local health department, National Association of County and City Health Officials, November 2005) Please reference http://www.naccho.org/topics/infrastructure/accreditation/upload/OperationalDefinitionBrochure-2.pdf for more information. Facilities involved in direct patient care are intended to be excluded from this dataset; however, some of the entities represented in this dataset serve as both administrative and clinical locations. This dataset only includes the headquarters of Public Health Departments, not their satellite offices. Some health departments encompass multiple counties; therefore, not every county will be represented by an individual record. Also, some areas will appear to have over representation depending on the structure of the health departments in that particular region. Town health officers are included in Vermont and boards of health are included in Massachusetts. Both of these types of entities are elected or appointed to a term of office during which they make and enforce policies and regulations related to the protection of public health. Visiting nurses are represented in this dataset if they are contracted through the local government to fulfill the duties and responsibilities of the local health organization. Since many town health officers in Vermont work out of their personal homes, TechniGraphics represented these entities at the town hall. This is denoted in the [DIRECTIONS] field. Effort was made by TechniGraphics to verify whether or not each health department tracks statistics on communicable diseases. Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries. "#" and "*" characters were automatically removed from standard HSIP fields populated by TechniGraphics. Double spaces were replaced by single spaces in these same fields. At the request of NGA, text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. At the request of NGA, all diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] field. Based on this field, the oldest record dates from 11/18/2009 and the newest record dates from 01/08/2010.
Facebook
TwitterCC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
AbstractObjective: To generate a national multiple sclerosis (MS) prevalence estimate for the United States by applying a validated algorithm to multiple administrative health claims (AHC) datasets. Methods: A validated algorithm was applied to private, military, and public AHC datasets to identify adult cases of MS between 2008 and 2010. In each dataset, we determined the 3-year cumulative prevalence overall and stratified by age, sex, and census region. We applied insurance-specific and stratum-specific estimates to the 2010 US Census data and pooled the findings to calculate the 2010 prevalence of MS in the United States cumulated over 3 years. We also estimated the 2010 prevalence cumulated over 10 years using 2 models and extrapolated our estimate to 2017. Results: The estimated 2010 prevalence of MS in the US adult population cumulated over 10 years was 309.2 per 100,000 (95% confidence interval [CI] 308.1–310.1), representing 727,344 cases. During the same time period, the MS prevalence was 450.1 per 100,000 (95% CI 448.1–451.6) for women and 159.7 (95% CI 158.7–160.6) for men (female:male ratio 2.8). The estimated 2010 prevalence of MS was highest in the 55- to 64-year age group. A US north-south decreasing prevalence gradient was identified. The estimated MS prevalence is also presented for 2017. Conclusion: The estimated US national MS prevalence for 2010 is the highest reported to date and provides evidence that the north-south gradient persists. Our rigorous algorithm-based approach to estimating prevalence is efficient and has the potential to be used for other chronic neurologic conditions. Usage notesPrev of MS in the US-E-Appendix-Feb-19-2018
Facebook
TwitterIM3 Projected US Data Center Locations This dataset contains model projections of new data center facilities in the contiguous United States (CONUS) through 2035 using the CERF – Data Centers model. Data center locations are modeled across four data center electricity demand growth scenarios (low, moderate, high, higher) and five market gravity scenarios (0%, 25%, 50%, 75%, 100%). Projected locations are intended to be regional representations of feasible siting locations in the future to assess potential grid and water stress impacts. The data center load growth scenarios correspond with the rates outlined in EPRI (2024) and include 3.71%, 5%, 10%, and 15% annual growth of electricity demand for data centers from 2023 values in 37 states across the CONUS. Market gravity scenarios correspond to the relative importance of proximity to data center markets or high population areas compared to locational cost in the siting algorithm. 0% market gravity means that siting decisions were entirely determined by the locational cost in each feasible location. 100% market gravity means that only market proximity was considered when siting. Other scenarios have weight placed on both components where total weight always equals 100%. Locational cost is dependent on facility cooling type and corresponding electricity cost, taxes, and other factors. Facility cooling type is spatially determined where high water stress and/or areas with high summer wet bulb temperatures are assumed to operate with mechanical cooling for a higher fraction of the year rather than evaporative cooling. Feasible data center siting areas are based on geospatial suitability raster data developed with open-source information. The following areas are excluded from siting: Areas within 300 m of a federal airport runway Waterbodies Areas with slope >16% Areas susceptible to sinkholes High coastal or inland flood risk areas Local, state, and federal parks, leisure areas, and cemeteries Areas >2 km away from electric substations Areas >5 km away from a municipal water supplier service area Areas >2 km away from high-speed fiber provider service territory Protected Areas Database of the United States (PAD-US) areas Railroads, major roadways, and minor roadways Military areas and training grounds NLCD developed lands Areas >0.8 km (0.5 miles) from NLCD developed lands Because we use open-source information, proprietary information that can influence siting decisions such as individual tax agreements with cities, detailed fiber line connectivity, electric grid power capacity agreements, and others, are not currently accounted for in the modeling process. Using specific building locations and footprints in the dataset for local planning purposes is not advised. Technical Information Geospatial data is provided in geojson format using the Albers Equal Area Conic (ESRI:102003) coordinate reference system. The datasets contain the following parameters: id - unique identification number within given scenario file growth_scenario – data center demand growth scenario market_gravity_weight – market gravity weight scenario (%) region – name of region (i.e., US State) total_cost_million_usd – locational siting cost ($million) campus_size_square_ft – total land acquired for data center facility (square ft) data_center_it_power_mw – IT power of data center facility (MW) mechanical_cooling_frac – fraction of year when data center uses mechanical cooling system water_cooling_frac– fraction of year when data center uses evaporative cooling system cooling_energy_demand_mwh – total annual facility energy demand for cooling (MWh) cooling_water_demand_mgy – total annual facility water demand for cooling (MG) cooling_water_consumption_mgy – total annual facility water consumed (MG) normalized_locational_cost – normalized total locational cost score for location normalized_gravity_score – normalized market gravity score for location weighted_siting_score – total weighted siting score of locational cost and gravity score geometry – polygon geometry of facility Acknowledgment IM3 is a multi-institutional effort led by Pacific Northwest National Laboratory and supported by the U.S. Department of Energy's Office of Science as part of research in MultiSector Dynamics, Earth and Environmental Systems Modeling Program. License This data is made available under a CCBY4.0 License Disclaimer This material was prepared as an account of work sponsored by an agency of the United States Government. Neither the United States Government nor the United States Department of Energy, nor the Contractor, nor any or their employees, nor any jurisdiction or organization that has cooperated in the development of these materials, makes any warranty, express or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness or any information, apparatus, product, software, or process disclosed, or represents that its use would not infringe privately owned rights. Reference herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise does not necessarily constitute or imply its endorsement, recommendation, or favoring by the United States Government or any agency thereof, or Battelle Memorial Institute. The views and opinions of authors expressed herein do not necessarily state or reflect those of the United States Government or any agency thereof. PACIFIC NORTHWEST NATIONAL LABORATORYoperated byBATTELLEfor theUNITED STATES DEPARTMENT OF ENERGYunder Contract DE-AC05-76RL01830
Facebook
TwitterU.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
FVAP data from 2008 post election survey of military voting assistance officers (VAO). VAOs help and guide military members and their dependents through the absentee voting process.
Facebook
TwitterConnecticut State Archives Archival Record Group (RG) #069:050, Noble (William H. and Henrietta) Pension Applications General William H. Noble and his daughter Henrietta M. Noble, Pension Agents in Bridgeport, assisted veterans and their descendants to secure pensions from the United States Government. The collection includes correspondence and official papers that document their work with veterans of the Civil War and Spanish American War. The files are arranged alphabetically by veteran’s name. The database contains the following information: veteran’s name, rank, pension file application number, date enlisted, date discharged, and military unit. People may request a copy of a file by contacting the staff of the History & Genealogy Unit by telephone (860) 757-6580 or email. When requesting a copy of a record, please include at least the name of the individual, date, and residence. Abbreviations of Connecticut Military Branch of Service: · CLB – Connecticut Light Battery · CVA – Connecticut Volunteer Artillery · CVC – Connecticut Volunteer Cavalry · CVHA – Connecticut Volunteer Heavy Artillery · CVI – Connecticut Volunteer Infantry · CVLB – Connecticut Volunteer Light Battery
Facebook
TwitterCounty Buddy is a dataset detailing the presence, count, and institutions of special populations (incarcerated individuals, college students, military personnel, and Native Americans) at the U.S. county and census tract levels. It offers geographic and demographic context to help explain variation in socio-economic indicators like life expectancy, income, and education.
Facebook
TwitterWelcome to the Kaggle dataset on The Impact of COVID-19 on Veterans in the United States! This dataset contains data on confirmed cases of COVID-19 in counties across the United States, as well as information on the percentage of each county's population that are veterans. With this dataset, you can investigate how the pandemic has impacted veterans specifically, and compare veteran case rates to the general population. How do veteran cases differ across age groups? Are there any geographical patterns? What can we learn about risk factors for COVID-19 among veterans? Download the dataset and explore for yourself today!
This dataset includes information on the number of confirmed cases of COVID-19 by county, as well as the percentage of the population in each county that are veterans. This data can be used to examine the relationship between veteran cases and the proportion of population who are veterans.
To do this, simply look at the 'CASES' and 'VET_CASES' columns for each county. The 'CASES' column represents the total number of confirmed cases of COVID-19 in that county, while the 'VET_CASES' column represents the number of confirmed cases among veterans. To compare these two values, simply divide 'VET_CASES' by 'CASES'. This will give you a ratio of veteran cases to total cases for each county.
You can then use this ratio to compare counties and see which ones have a higher proportion of veteran cases. This data can be used to help understand where more outreach may be needed to support veterans during this pandemic
File: CountyVACOVID.csv | Column name | Description | |:---------------------------|:-----------------------------------------------------------------------------------------------------------------------| | FIPS | Federal Information Processing Standards code that uniquely identifies counties within the USA. (String) | | COUNTY | County name. (String) | | STATE | State name. (String) | | POP | County population. (Integer) | | VETS | Number of veterans in the county. (Integer) | | VET_PERCENT | Percentage of the population that are veterans. (Float) | | CASES | Number of confirmed cases of COVID-19 in the county. (Integer) | | YESTER_CASES | Number of confirmed cases of COVID-19 in the county from the previous day. (Integer) | | VET_CASES | Number of confirmed cases of COVID-19 in veterans in the county. (Integer) | | VET_YESTER | Number of confirmed cases of COVID-19 in veterans in the county from the previous day. (Integer) | | LOWER_Hospitalizations | Lower bound of the 95% confidence interval for the number of hospitalizations due to COVID-19 in the county. (Integer) | | UPPER_Hospitalizations | Upper bound of the 95% confidence interval for the number of hospitalizations due to COVID-19 in the county. (Integer) | | DATE | Date of data. (Date) |
File: VAChart.csv | Column name | Description | |:------------------------|:----------------------------------------------------------------------------------| | DATE | Date of data. (Date) | | US Cases | The number of confirmed cases of COVID-19 in the United States. (Integer) | | **New US ...