This dataset, released by DoD, contains geographic information for major installations, ranges, and training areas in the United States and its territories. This release integrates site information about DoD installations, training ranges, and land assets in a format which can be immediately put to work in commercial geospatial information systems. Homeland Security/Homeland Defense, law enforcement, and readiness planners will benefit from immediate access to DoD site location data during emergencies. Land use planning and renewable energy planning will also benefit from use of this data. Users are advised that the point and boundary location datasets are intended for planning purposes only, and do not represent the legal or surveyed land parcel boundaries.

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 layer is sourced from maps.bts.dot.gov.

The Military Bases dataset was last updated on October 23, 2024 and are defined by Fiscal Year 2023 data, from the Office of the Assistant Secretary of Defense for Energy, Installations, and Environment and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). The dataset depicts the authoritative locations of the most commonly known Department of Defense (DoD) sites, installations, ranges, and training areas world-wide. 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 Assistant Secretary of Defense for Energy, Installations, and Environment. Only sites reported in the BSR or released in a map supplementing the Foreign Investment Risk Review Modernization Act of 2018 (FIRRMA) Real Estate Regulation (31 CFR Part 802) were considered for inclusion. This list does not necessarily represent a comprehensive collection of all Department of Defense facilities. 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. While every attempt has been made to provide the best available data quality, this data set is intended for use at mapping scales between 1:50,000 and 1:3,000,000. For this reason, boundaries in this data set may not perfectly align with DoD site boundaries depicted in other federal data sources. Maps produced at a scale of 1:50,000 or smaller which otherwise comply with National Map Accuracy Standards, will remain compliant when this data is incorporated. Boundary data is most suitable for larger scale maps; point locations are better suited for mapping scales between 1:250,000 and 1:3,000,000. If a site is part of a Joint Base (effective/designated on 1 October, 2010) as established under the 2005 Base Realignment and Closure process, it is attributed with the name of the Joint Base. All sites comprising a Joint Base are also attributed to the responsible DoD Component, which is not necessarily the pre-2005 Component responsible for the site.

Historical chart and dataset showing U.S. military size by year from 1985 to 2020.

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. The Census Bureau includes landmarks such as military installations in the MTDB for locating special features and to help enumerators during field operations. In 2012, the Census Bureau obtained the inventory and boundaries of most military installations from the U.S. Department of Defense (DOD) for Air Force, Army, Marine, and Navy installations and from the U.S. Department of Homeland Security (DHS) for Coast Guard installations. The military installation boundaries in this release represent the updates the Census Bureau made in 2012 in collaboration with DoD.

The United States Military Installations database contains the boundaries and location information for important military installations in the United States and Puerto Rico. The database includes records for 405 military installations.

Purpose

To provide graphic representation, location and attribute data for analysis, modeling and simulation, and studies. CLOSURE, REALIGN, and BRAC columns are from the office of Economic Adjustment and OSD websites at http://www.oea.gov , https://www.denix.osd.mil .

US Military

## Overview

US Military is a dataset for object detection tasks - it contains Objects annotations for 1,440 images.

## Getting Started

You can download this dataset for use within your own projects, or fork it into a workspace on Roboflow to create your own model.

  ## License

  This dataset is available under the [CC BY 4.0 license](https://creativecommons.org/licenses/CC BY 4.0).

The dataset depicts the authoritative locations of the most commonly known Department of Defense (DoD) sites, installations, ranges, and training areas world-wide. 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 Assistant Secretary of Defense for Energy, Installations, and Environment. Only sites reported in the BSR or released in a map supplementing the Foreign Investment Risk Review Modernization Act of 2018 (FIRRMA) Real Estate Regulation (31 CFR Part 802) were considered for inclusion. This list does not necessarily represent a comprehensive collection of all Department of Defense facilities. 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.While every attempt has been made to provide the best available data quality, this data set is intended for use at mapping scales between 1:50,000 and 1:3,000,000. For this reason, boundaries in this data set may not perfectly align with DoD site boundaries depicted in other federal data sources. Maps produced at a scale of 1:50,000 or smaller which otherwise comply with National Map Accuracy Standards, will remain compliant when this data is incorporated. Boundary data is most suitable for larger scale maps; point locations are better suited for mapping scales between 1:250,000 and 1:3,000,000.If a site is part of a Joint Base (effective/designated on 1 October, 2010) as established under the 2005 Base Realignment and Closure process, it is attributed with the name of the Joint Base. All sites comprising a Joint Base are also attributed to the responsible DoD Component, which is not necessarily the pre-2005 Component responsible for the site.

This dataset is designed for object detection of military aircraft. The dataset encompasses 74 different military aircraft types, with some types merged as one class along with their variants.

A-10, A-400M, AG-600, AH-64, AV-8B, An-124, An-22, An-225, An-72, B-1, B-2, B-21, B-52, Be-200, C-130, C-17, C-2, C-390, C-5, CH-47, CL-415, E-2, E-7, EF-2000, F-117, F-14, F-15, F-16, F-22, F-35, F-4, F/A-18, H-6, J-10, J-20, JAS-39, JF-17, JH-7, KC-135, KF-21, KJ-600, Ka-27, Ka-52, MQ-9, Mi-24, Mi-26, Mi-28, Mig-29, Mig-31, Mirage2000, P-3, RQ-4, Rafale, SR-71, Su-24, Su-25, Su-34, Su-57, TB-001, TB-2, Tornado, Tu-160, Tu-22M, Tu-95, U-2, UH-60, US-2, V-22, Vulcan, WZ-7, XB-70, Y-20, YF-23, Z-19.

This Dataset is in YOLO8 Format consist of Images and labels in jpg and txt files respectively.

Description This dataset contains both tabular and geospatial data of eight great powers' overseas military bases, including China, the United States, the United Kingdoms, Russia, Japan, India, the United Arab Emirates, and France up until November 2020. An interactive view of this dataset: Link Source All data were collected from multiple public sources and specified in each data point in the Excel file and Shapefile. For metadata, such as data description and available methods for geospatial data processing, please read the readme.pdf. Terms of use This dataset features in a collection of geospatial data "Geo-mapping databases for the Belt and Road Initiative". To cite this work, available citation styles can be found here: https://doi.org/10.6084/m9.figshare.c.6076193

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.

Version 2 (18 March 2025) includes a further 356 service itineraries. In addition, 41 entries from the previous version were updated or expanded. Currently the database covers a total of 1,858 Jewish soldiers, 421 wives and 83 children.

ORIGINAL VERSION 1 (18 September 2024)

With more than 1,500 individual entries, this is the inaugural instalment of my research database collated in the framework of the Project Forgotten Soldiers: Jewish Military Experience in the Habsburg Monarchy. This is an open access database, and everyone is welcome to use it according to their own scholarly and personal interests. In 1,189 cases we have official documented records confirming the soldiers were Jewish. In another 313 entries I was able to identify likely Jewish soldiers based on circumstantial evidence cross-referencing names and places of birth, with the presence of confirmed Jewish soldiers drafted into the same units as part of the same recruitment drive. This dataset further includes evidence for 156 spouses and 47 children. While military records do mentions these, their number suggests that the Habsburg army preferred to enlist unmarried men.

The database is structured in a similar way to an official individual entry in the Habsburg military records. These were arranged in tables, with soldiers listed by seniority. Name, place and land of birth are followed by age and religion. This latter rubric allows identifying the bulk of the Jewish soldiers. Also included in the record is marital status, profession (if any), number, names and ages of children (if any), followed by a short summary text of the soldier’s service itinerary. While not always consistent in detail, these texts mention enlistment dates, transfers between units, promotions, desertions, periods as prisoner of war and military awards (if any). I have taken the material from the personal records and added several additional parameters:

The soldiers are entered into the database according to their date of enlistment. This is followed by a colour-coded table showing their years of service. To see the meaning of the different colours employed, scroll to the legend at the end of the dataset.

Following the years of service, we see the date when the soldier left service (final year in service for incomplete service records). When known, the reason the soldier left the army is given (discharge/ death/ desertion etc).

Then come the three most important columns within the table: service record, primary sources and units. At first glance, these columns have only a few letters and numbers, but bring your mouse courser onto the relevant field marked with red triangles. An additional window will then open:

a. Service Record: Shows the entire service record of the soldier arranged by date. I use original German as it appears in the archival records. If you see spelling differences with modern German – they are there for a reason.

b. Primary Sources: Provides the information on all the archival records consulted to reconstruct the service itinerary. The number in the field denotes the number of the archival cartons consulted.

c. Units: Number of units in which a soldier serves. Bringing the cursor on to the field will open their list. Most Jewish soldiers served in the line infantry (IR) and the Military Transport Corps (MFWK or MFK). However, there were also Jewish sharpshooters, cavalrymen, gunners and even a few members of the nascent Austrian Navy.

The next two columns provide entries of the soldier’s conduct and medical condition, which in Habsburg military jargon was referred to rather callously as Defekten. I note the original medical diagnoses verbatim. When possible to identify, I note the modern medical term.

General database-wide parameters are then noted in the next part of the table. Among others, it provides information on enlistment type (conscript/ volunteer?), main branches of service (such as Infantry/ Cavalry/ Artillery), and roles within the military (such as non-commissioned officers/ drummers/ medics).

Concluding this part of the table are columns covering desertions, periods as prisoner of war and awards of the army cannon cross (for veterans of 1813-14) and other military awards.

The last column provides the original German outtake rubric as to how the soldier left service. In special cases, additional service notes are provides on the right.

How to use this dataset

This depends on what you are looking for. Firstly, download the dataset on to your computer via the link provided below. It is a simple Excel file which is easy to work with. If you wish to find out whether one of your ancestors served in the Habsburg army, use a simple keyword search. Please note that in our period there was no single accepted orthography meaning that some letters were used interchangeably (for instance B/P; D/T). There were also various patronymic suffices used in different parts of the monarchy (-witz in German/ -wicz in Polish/ -vits in Hungarian). Habsburg military clerks were mostly German speakers who often recorded the name phonetically. For instance, Jankel/ Jankl/ Jacob/ Jacobus all denote the same name. A Jewish teenager who identified himself as Moische when first reporting to duty, may have stayed so in the military records for decades, even if he was already a non-commissioned officer whose subordinates referred to as Herr Corporal.

If you study the history of concrete Jewish communities, use the keyword search and the filter option to find entries in the database where this locality is mentioned. Some places like Prague and Lublin could be identified effortlessly. In other cases (and see the above point on German-speaking clerks), place names were recorded phonetically. The military authority usually stuck to official Polish names in Galicia, and Hungarian in the Lands of the Crown of St. Stephan. In reality, a Jewish recruit from Transcarpathian Ruthenia could have his place of birth recorded in Hungarian, Romanian or Rusin. When I could not identify the place in question, I marked it with italics. Do you think you identified something I could not? Excellent! Then please write me, and I will correct the entry in the next instalment of this database.

I should stress that, currently, the database is not statistically representative. I have worked chronologically, meaning that there are disproportionally more entries for Jewish soldiers from the Turkish War, the first two Coalition Wars, and the Wars of 1805 and 1809. If you look at some of my other databases (for instance, that of the 1st Line Infantry Regiment 'Kaiser'), you will find least as many Jews who served in the wars of 1813-15. I will cover these in due course. This said, using the filter option of the Excel sheet, you can already make some individual queries. For instance, did Jewish grenadiers meet the minimal height requirement to be eligible for transfer into the elite infantry? (Hint: they did not!) If you are interested in the historical study of nutritional standards, compare the height of the soldiers with their year and place of birth. In my other project, I made calculations of the average height of Habsburg soldiers and I can already reveal that Jewish conscripts were, on average, several centimetres smaller than their non-Jewish comrades drafted in the same annual intake. Whatever stereotypes said, most Jews in the Habsburg Monarchy around 1800 were very poor and the sad fact of malnutrition as a child is reflected in their height as adults.

I should stress that this is a cumulative database. ZENODO has an excellent feature allowing updated versions to supersede earlier files while retaining the same DOI (Digital Object Identifier) and metadata. As my research progresses, I plan to upload new versions of this database bi-annually. This includes not only adding new entries, but also expanding and correcting existing ones. It might well be that the service record of a soldier covered up to 1806 will be brought to a later date, possibly even to his discharge from the army. If you have not found whom you are looking for, or if you want to work with larger samples for your research, visit this page again in a few months’ time. And if you do use this database for scholarly research (by all means, please do), do not forget to cite it as you would cite any other item in your bibliography! If you are a museum professional and you want to employ material from your database to illustrate your exhibitions, you are welcome, but please cite this resource for others to learn. Links to this database will also be appreciated.

Military Facilities. The dataset contains locations and attributes of Military Facilities, created as part of the DC Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO) and participating D.C. government agencies. Information researched by the DC Office of the Chief Technology Officer identified Military Facilities and DC GIS staff geo-processed the data.

The world has become much more peaceful, and yet, even after adjusting for inflation, global military spending is now three times greater than at the height of the Cold War. These developments have motivated a renewed interest from both policy makers and scholars about the drivers of military spending and the implications that follow. Existing findings on the relationship between threat and arming and arms races and war hinge on the completeness and accuracy of existing military spending data. Moreover, data on military spending is used to measure important concepts from international relations such as the distribution of power, balancing, the severity of states’ military burdens, and arms races. Everything we know about which states are most powerful, whether nations are balancing, and whether military burdens and arms races are growing more or less severe rests on the accuracy of existing military spending estimates.

The TIGER/Line Files are shapefiles and related database files (.dbf) that 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 File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Census Bureau includes landmarks such as military installations in the MTDB for locating special features and to help enumerators during field operations. In 2008, the Census Bureau obtained the inventory and boundaries of most military installations from the U.S. Department of Defense (DOD) for Air Force, Army, Marine, and Navy installations and from the U.S. Department of Homeland Security (DHS) for Coast Guard installations. In a few cases, the files supplied to the Census Bureau contained older, unverified information than that obtained from the DOD for Census 2000; in those cases the military installations in MTDB were reviewed, but not updated to match the files obtained in 2008.

YOLO Military

## Overview

YOLO Military is a dataset for object detection tasks - it contains YOLO Military annotations for 2,929 images.

## Getting Started

You can download this dataset for use within your own projects, or fork it into a workspace on Roboflow to create your own model.

  ## License

  This dataset is available under the [MIT license](https://creativecommons.org/licenses/MIT).

This dataset is about books. It has 1 row and is filtered where the book is A revolution in military adaptation : the US Army in the Iraq War. It features 7 columns including author, publication date, language, and book publisher.

Data was collected from the game "warno" with an emphasis on tanks. Images are in 4k, the goal is to make an object classifier that can spot tanks when they are very far away (32pixels height or width). This dataset will eventually be mixed in with real images. Hopfully the warno/synthetic images will make the final model more robust from an areal perspective.

This layer depicts boundaries of military/armed forces facilities (Army, Navy, Air Force, Marines & Coast Guard) managed by the federal government within the 17 jurisdictions of the Hampton Roads Planning District Commission (HRPDC) in southeast Virginia. This data set contains the major military facilities found in Hampton Roads but may not include every federally owned parcel in the region.

Homeland Infrastructure Foundation-Level Data (HIFLD) geospatial data sets containing information on US Army Corps of Engineers (USACE) Military Districts.