Content

Lists the military spending, GDP, and population estimate for the US each year from 1960 to 2020.

Acknowledgements

Banner image source: https://unsplash.com/photos/BQgAYwERXhs

https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F954461%2F41f0017368e1043a2c643aea10cbb3e4%2FgoogleDataStudio.jpg?generation=1561570478866938&alt=media" alt="">

Context

This dataset will be used to help users get familiar with Google Data Studio. It's also a great way to mix history with data visualization skills.

Later I will develop a lesson that will help new users get up to speed with Google Data Studio. This dataset is small, but it will be a good dataset to start with. The same concepts learned with this project will be used with larger datasets.

Content

This data comes from wikipedia.

Acknowledgements

wikipedia

https://en.wikipedia.org/wiki/United_States_military_casualties_of_war

Inspiration

Project based learning. Get it going! Teach kids using data.

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.

https://i.imgur.com/Vrs6apv.png" alt="">

Context

There is a well-documented phenomenon of increased suicide rates among United States military veterans. One recent analysis, published in 2016, found the suicide rate amongst veterans to be around 20 per day. The widespread nature of the problem has resulted in efforts by and pressure on the United States military services to combat and address mental health issues in and after service in the country's armed forces.

In 2013 News21 published a sequence of reports on the phenomenon, aggregating and using data provided by individual states to typify the nationwide pattern. This dataset is the underlying data used in that report, as collected by the News21 team.

Content

The data consists of six files, one for each year between 2005 and 2011. Each year's worth of data includes the general population of each US state, a count of suicides, a count of state veterans, and a count of veteran suicides.

Acknowledgements

This data was originally published by News21. It has been converted from an XLS to a CSV format for publication on Kaggle. The original data, visualizations, and stories can be found at the source.

Inspiration

What is the geospatial pattern of veterans in the United States? How much more vulnerable is the average veteran to suicide than the average citizen? Is the problem increasing or decreasing over time?

Munitions 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

analyze 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

Jails and Prisons (Correctional Institutions). The Jails and Prisons sub-layer is part of the Emergency Law Enforcement Sector and the Critical Infrastructure Category. A Jail or Prison consists of any facility or location where individuals are regularly and lawfully detained against their will. This includes Federal and State prisons, local jails, and juvenile detention facilities, as well as law enforcement temporary holding facilities. Work camps, including camps operated seasonally, are included if they otherwise meet the definition. A Federal Prison is a facility operated by the Federal Bureau of Prisons for the incarceration of individuals. A State Prison is a facility operated by a state, commonwealth, or territory of the US for the incarceration of individuals for a term usually longer than 1 year. A Juvenile Detention Facility is a facility for the incarceration of those who have not yet reached the age of majority (usually 18 years). A Local Jail is a locally administered facility that holds inmates beyond arraignment (usually 72 hours) and is staffed by municipal or county employees. A temporary holding facility, sometimes referred to as a "police lock up" or "drunk tank", is a facility used to detain people prior to arraignment. Locations that are administrative offices only are excluded from the dataset. This definition of Jails is consistent with that used by the Department of Justice (DOJ) in their "National Jail Census", with the exception of "temporary holding facilities", which the DOJ excludes. Locations which function primarily as law enforcement offices are included in this dataset if they have holding cells. If the facility is enclosed with a fence, wall, or structure with a gate around the buildings only, the locations were depicted as "on entity" at the center of the facility. If the facility's buildings are not enclosed, the locations were depicted as "on entity" on the main building or "block face" on the correct street segment. Personal homes, administrative offices, and temporary locations are intended to be excluded from this dataset; however, some personal homes of constables are included due to the fact that many constables work out of their homes. TGS has made a concerted effort to include all correctional institutions. This dataset includes non license restricted data from the following federal agencies: Bureau of Indian Affairs; Bureau of Reclamation; U.S. Park Police; Federal Bureau of Prisons; Bureau of Alcohol, Tobacco, Firearms and Explosives; U.S. Marshals Service; U.S. Fish and Wildlife Service; National Park Service; U.S. Immigration and Customs Enforcement; and U.S. Customs and Border Protection. This dataset is comprised completely of license free data. The Law Enforcement dataset and the Correctional Institutions dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes. With the merge of the Law Enforcement and the Correctional Institutions datasets, NAICS Codes & Descriptions were assigned based on the facility's main function which was determined by the entity's name, facility type, web research, and state supplied data. In instances where the entity's primary function is both law enforcement and corrections, the NAICS Codes and Descriptions are assigned based on the dataset in which the record is located (i.e., a facility that serves as both a Sheriff's Office and as a jail is designated as [NAICSDESCR]="SHERIFFS' OFFICES (EXCEPT COURT FUNCTIONS ONLY)" in the Law Enforcement layer and as [NAICSDESCR]="JAILS (EXCEPT PRIVATE OPERATION OF)" in the Correctional Institutions layer). 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 fields that TGS populated. Double spaces were replaced by single spaces in these same fields. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. 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 the values in this field, the oldest record dates from 12/07/2004 and the newest record dates from 10/22/2009

Jails and Prisons (Correctional Institutions). The Jails and Prisons sub-layer is part of the Emergency Law Enforcement Sector and the Critical Infrastructure Category. A Jail or Prison consists of any facility or location where individuals are regularly and lawfully detained against their will. This includes Federal and State prisons, local jails, and juvenile detention facilities, as well as law enforcement temporary holding facilities. Work camps, including camps operated seasonally, are included if they otherwise meet the definition. A Federal Prison is a facility operated by the Federal Bureau of Prisons for the incarceration of individuals. A State Prison is a facility operated by a state, commonwealth, or territory of the US for the incarceration of individuals for a term usually longer than 1 year. A Juvenile Detention Facility is a facility for the incarceration of those who have not yet reached the age of majority (usually 18 years). A Local Jail is a locally administered facility that holds inmates beyond arraignment (usually 72 hours) and is staffed by municipal or county employees. A temporary holding facility, sometimes referred to as a "police lock up" or "drunk tank", is a facility used to detain people prior to arraignment. Locations that are administrative offices only are excluded from the dataset. This definition of Jails is consistent with that used by the Department of Justice (DOJ) in their "National Jail Census", with the exception of "temporary holding facilities", which the DOJ excludes. Locations which function primarily as law enforcement offices are included in this dataset if they have holding cells. If the facility is enclosed with a fence, wall, or structure with a gate around the buildings only, the locations were depicted as "on entity" at the center of the facility. If the facility's buildings are not enclosed, the locations were depicted as "on entity" on the main building or "block face" on the correct street segment. Personal homes, administrative offices, and temporary locations are intended to be excluded from this dataset. TGS has made a concerted effort to include all correctional institutions. This dataset includes non license restricted data from the following federal agencies: Bureau of Indian Affairs; Bureau of Reclamation; U.S. Park Police; Federal Bureau of Prisons; Bureau of Alcohol, Tobacco, Firearms and Explosives; U.S. Marshals Service; U.S. Fish and Wildlife Service; National Park Service; U.S. Immigration and Customs Enforcement; and U.S. Customs and Border Protection. This dataset is comprised completely of license free data. The Law Enforcement dataset and the Correctional Institutions dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes. With the merge of the Law Enforcement and the Correctional Institutions datasets, NAICS Codes & Descriptions were assigned based on the facility's main function which was determined by the entity's name, facility type, web research, and state supplied data. In instances where the entity's primary function is both law enforcement and corrections, the NAICS Codes and Descriptions are assigned based on the dataset in which the record is located (i.e., a facility that serves as both a Sheriff's Office and as a jail is designated as [NAICSDESCR]="SHERIFFS' OFFICES (EXCEPT COURT FUNCTIONS ONLY)" in the Law Enforcement layer and as [NAICSDESCR]="JAILS (EXCEPT PRIVATE OPERATION OF)" in the Correctional Institutions layer). 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 fields that TGS populated. Double spaces were replaced by single spaces in these same fields. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. 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 the values in this field, the oldest record dates from 12/27/2004 and the newest record dates from 09/08/2009

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.

Data Dictionary

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

Acknowledgement

Original Data

CORGIS Dataset Project

Foto von Samuel Branch auf Unsplash

Context Pakistan Drone Attacks (2004-2016)

The United States has targeted militants in the Federally Administered Tribal Areas [FATA] and the province of Khyber Pakhtunkhwa [KPK] in Pakistan via its Predator and Reaper drone strikes since year 2004. Pakistan Body Count (www.PakistanBodyCount.org) is the oldest and most accurate running tally of drone strikes in Pakistan. The given database (PakistanDroneAttacks.CSV) has been populated by using majority of the data from Pakistan Body Count, and building up on it by canvassing open source newspapers, media reports, think tank analyses, and personal contacts in media and law enforcement agencies. We provide a count of the people killed and injured in drone strikes, including the ones who died later in hospitals or homes due to injuries caused or aggravated by drone strikes, making it the most authentic source for drone related data in this region.

We will keep releasing the updates every quarter at this page.

Content Geography: Pakistan

Time period: 2004-2016

Unit of analysis: Attack

Dataset: The dataset contains detailed information of 397 drone attacks in Pakistan that killed an estimated 3,558 and injured 1,333 people including 2,539 civilians.

Variables: The dataset contains Serial No, Incident Day & Date, Approximate Time of the attack, Specific Location, City, Province, Number of people killed who claimed to be from Al-Qaeeda, Number of people killed who claimed to be from Taliban, minimum and maximum count of foreigners killed, minimum and maximum count of civilians killed, minimum and maximum count of civilians injured, special mention (more details) and comments about the attack, longitude and latitude of the location. Sources: Unclassified media articles, hospital reports, think tank analysis and reports, and government official press releases.

Acknowledgements & References Pakistan Body Count has been leveraged extensively in scholarly publications, reports, media articles and books. The website and the dataset has been collected and curated by the founder Zeeshan-ul-hassan Usmani. Users are allowed to use, copy, distribute and cite the dataset as follows: “Zeeshan-ul-hassan Usmani, Pakistan Body Count, Drone Attacks Dataset, Kaggle Dataset Repository, Jan 25, 2017.”

Past Research Zeeshan-ul-hassan Usmani and Hira Bashir, “The Impact of Drone Strikes in Pakistan”, Cost of War Project, Brown University, December 16, 2014

Inspiration Some ideas worth exploring:

• How many people got killed and injured per year in last 12 years?

• How many attacks involved killing of actual terrorists from Al-Qaeeda and Taliban?

• How many attacks involved women and children?

• Visualize drone attacks on timeline

• Find out any correlation with number of drone attacks with specific date and time, for example, do we have more drone attacks in September?

• Find out any correlation with drone attacks and major global events (US funding to Pakistan and/or Afghanistan, Friendly talks with terrorist outfits by local or foreign government?)

• The number of drone attacks in Bush Vs Obama tenure?

• The number of drone attacks versus the global increase/decrease in terrorism?

• Correlation between number of drone strikes and suicide bombings in Pakistan

Questions? For detailed visit www.PakistanBodyCount.org

Or contact Pakistan Body Count staff at info@pakistanbodycount.org

The Impact of COVID-19 on Veterans in America

County-Level Data on Veteran Cases and Proportion of Population

About this dataset

Welcome 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!

How to use the dataset

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

Research Ideas

• Find the correlation between the number of veterans in a county and the number of confirmed cases of COVID-19.
• Find the counties with the highest percentage of veterans and the lowest number of confirmed cases of COVID-19.
• Predict how many veterans in a county will contract COVID-19 based on the percentage of veterans in the population

Columns

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 ...

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 file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

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.

Acknowlegement

Original Data

Foto von israel palacio auf Unsplash

Context

One way to track the priorities of the U.S. Air Force is through their budget and what programs they increase or decrease funding towards.

Content

The FY 2018 and FY 2019 Estimates come from the Air Force’s documents for Fiscal Year (FY) 2018. The FY 2019 President’s Budget Request comes from the FY 2019 budget documents released in February 2018 and are the Administration’s, and the Air Force’s, request for funding for FY 2019. To see how the Administration’s priorities have changed, reference the change in funding from the FY 2019 Estimates and the FY 2019 President’s Budget Request.

Acknowledgements

The data is from the (https://aerospace.csis.org/data/u-s-air-force-budget-requests/).

This data layer is an element of the Oregon GIS Framework. 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 file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census and beyond, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

From the project website: "url"> https://sites.tufts.edu/css/mip-research/mip-dataset/

The Military Intervention Project (MIP) within the Center for Strategic Studies (CSS) seeks to solve the puzzle of US foreign military interventions. It is building a new, comprehensive dataset of all US military interventions from 1776 until 2017 to measure the costs, benefits, and unintended consequences of US military involvements abroad. In other words, this dataset will provide strong empirical evidence regarding the trade-offs of US military interventions – a current hot topic in Congress, the media, and in public opinion. MIP will measure the costs and benefits to US national interests, economic growth, international reputation as well as human rights, democratic, and economic outcomes within the target state, and much more.

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 file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census and beyond, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

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.

This Public Schools feature dataset is composed of all Public elementary and secondary education facilities in the United States as defined by the Common Core of Data (CCD, https://nces.ed.gov/ccd/ ), National Center for Education Statistics (NCES, https://nces.ed.gov ), US Department of Education for the 2017-2018 school year. This includes all Kindergarten through 12th grade schools as tracked by the Common Core of Data. Included in this dataset are military schools in US territories and referenced in the city field with an APO or FPO address. DOD schools represented in the NCES data that are outside of the United States or US territories have been omitted. This feature class contains all MEDS/MEDS+ as approved by NGA. Complete field and attribute information is available in the ”Entities and Attributes” metadata section. Geographical coverage is depicted in the thumbnail above and detailed in the Place Keyword section of the metadata. This release includes the addition of 3065 new records, modifications to the spatial location and/or attribution of 99,287 records, and removal of 2996 records not present in the NCES CCD data.

Explore the historical conflicts involving the United States from the 18th century to the present day with this comprehensive dataset. Derived from publicly available sources like Wikipedia, this dataset offers a detailed glimpse into the wars, conflicts, and military engagements the US has been involved in over the years.

The dataset comprises the following columns:

Conflict: Name of the conflict Century: Century in which the conflict occurred Year: Specific year of the conflict Location: Geographical location of the conflict Allies: Parties allied with the United States Opponent(s): Opposing forces faced by the United States Result for the United States and its Allies: Outcome of the conflict for the US and its allies Presidents of the United States: Presidents in office during the conflict The dataset presents a unique opportunity for historical analysis, military studies, and political research. Analysts can delve into patterns of alliances, examine the impact of conflicts on presidential legacies, and trace the evolution of US military engagements over time. Researchers interested in diplomacy, military strategy, and international relations will find this dataset invaluable for their studies.

Note: This dataset is provided for non-commercial use. Credits to Wikipedia for the primary data source.