TheDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/HelenDiMo/archaios-data-Intelligence/llms.txt
Use this file to discover all available pages before exploring further.
adi_dataset_master table is the primary analytical table in the Power BI semantic model, powering the “Día D” dashboard page. It contains the full enriched mission record for June 6, 1944 (D-Day) operations, with 49 fields total: 46 columns derived directly from THOR source data, plus three A.D.I.-derived columns (he_tons, frag_tons, weapon_type) added by the Jupyter notebook cleaning pipeline. Data types and field names below are taken directly from the adi_dataset_master.tmdl schema definition and the CSV header row. The other two ADI master tables (adi_master_1943_1944 and adi_master_1_5_junio) share the first 46 columns but do not include the A.D.I. enrichment fields.
Mission Identification
These fields uniquely identify each THOR mission record and establish its basic operational context.Unique mission identifier from the DoD THOR database. Serves as the primary key for cross-table relationships — it joins
adi_dataset_master and adi_master_1_5_junio to adi_master_1943_1944 via bidirectional one-to-many relationships in the Power BI semantic model. Format: integer (no decimal), summarizeBy: none.Date of the bombing mission. Stored as a
dateTime column cast to date at load time (Short Date format). This column drives Power BI’s time intelligence features via the local date table relationship (joinOnDateBehavior: datePartOnly). The date hierarchy — labeled “Jerarquía de fechas” in the Spanish-locale UI — enables year/quarter/month/day drill-downs.Operational type of the mission as recorded in the THOR source (e.g., tactical strike, strategic bombing, escort). Populated inconsistently in the source data — many records have this field empty.
summarizeBy: none.Radio callsign assigned to the mission. Used to trace individual sortie groups within a coordinated operation. Sparse in the THOR records — not all missions were assigned a formal callsign in the surviving documentation.
summarizeBy: none.Origin Fields
These fields describe the attacking force — the nation, air branch, unit, aircraft, and departure location.The strategic theater in which the mission was conducted. For D-Day records in
adi_dataset_master, this is exclusively ETO (European Theater of Operations). The pre-D-Day dataset (adi_master_1943_1944) also contains MTO (Mediterranean Theater of Operations) records. summarizeBy: none.The nation of the attacking force. Common values:
USA, GREAT BRITAIN. Maps to the allied air forces operating from UK bases in the lead-up to and execution of D-Day. summarizeBy: none.The specific air force command that flew the mission (e.g.,
8 AF for the Eighth Air Force, 9 AF for the Ninth Air Force, 15 AF for the Fifteenth Air Force). Key for filtering missions by strategic vs. tactical bomber commands. summarizeBy: none.The specific bomb group, wing, or squadron identifier (e.g.,
27 FBG/86 FBG). Provides the most granular unit-level attribution in the THOR records. Frequently null or empty — THOR coverage of unit-level detail is inconsistent. summarizeBy: none.THOR code for the aircraft type used (e.g.,
B17 = Boeing B-17 Flying Fortress, B24 = Consolidated B-24 Liberator, B26 = Martin B-26 Marauder, P51 = North American P-51 Mustang, A36 = Douglas A-36 Apache). Cross-reference with 3_thor_wwii_aircraft_gloss.csv to decode to full model names. summarizeBy: none.Name of the airfield from which the mission departed (e.g.,
PONTE OLIVO AIRFIELD). Used in geospatial analysis to map the origin network of Allied bombing operations. summarizeBy: none.Geographic region or country of the takeoff base (e.g.,
SICILY, ENGLAND). Provides a higher-level geographic grouping above Takeoff Base. summarizeBy: none.Latitude coordinate of the takeoff base, stored as text in the Power BI model. Decimal degree format (e.g.,
37.131022). Note: stored as string in the semantic model despite being a numeric coordinate — handle type conversion if using in map visuals or DAX calculations.Longitude coordinate of the takeoff base, stored as text. Decimal degree format (e.g.,
14.321464). Same type caveat applies as Takeoff Latitude.Target Fields
These fields define the geographic, operational, and industrial classification of each bombing target — the most analytically significant fields for archaeological prospection.THOR’s internal identifier for the target location. Integer format. Used for
summarizeBy: count (i.e., counting distinct targets) rather than summing. Cross-references THOR’s target registry for additional metadata.Country containing the target (e.g.,
FRANCE, GERMANY, ITALY). For Normandy analysis, the vast majority of records are FRANCE. summarizeBy: none.City, town, or location name of the target as recorded in THOR (e.g.,
AMIENS, ST. LÔ, BREST, LA HAYE, UNKNOWN). This is the primary geographic field for the Power BI map and bar chart visuals. summarizeBy: none.Approximately 18% of records have
Target City = "UNKNOWN" or "UNIDENTIFIED" in the THOR source data. These records are retained in the ADI master datasets but reduce the precision of city-level archaeological targeting.High-level category of the bombed target (e.g.,
TACTICAL TARGET, AIRDROME, CITY AREA, GUN EMPLACEMENTS, BRIDGES). The primary classification field for understanding the strategic purpose of each mission. summarizeBy: none.Industrial or infrastructure sub-type within the target category (e.g.,
AIR FIELDS AND AIRDROMES, GUN EMPLACEMENTS, TACTICAL TARGETS: (UNIDENTIFIED OR NOT LISTED BELOW)). More granular than Target Type but also more frequently null. summarizeBy: none.Strategic priority ranking assigned to the target in the THOR records (e.g.,
1 = highest priority). Integer format. summarizeBy: sum in Power BI — treat sum aggregation with care; average or first-value is more analytically meaningful for priority analysis.Latitude coordinate of the target. Stored as
int64 in the Power BI model but annotated with PBI_FormatHint: isDecimal = true, meaning the underlying values are decimal degrees (e.g., 49.9 for Amiens). The summarizeBy: sum setting is inherited from the THOR schema — use with caution; only geographic averaging makes analytical sense.Longitude coordinate of the target. Same type and annotation as
Target Latitude. Combined with Target Latitude, these fields power the Power BI map visual that forms the core of the archaeological prospection interface.Aircraft and Sortie Fields
These fields capture the size and outcome of each mission’s sortie — how many aircraft flew, how many engaged, and what happened to them.The bombing altitude in hundreds of feet (e.g.,
180 = 18,000 ft, 110 = 11,000 ft). Relevant for interpreting bomb dispersion patterns and the likely crater/impact radius at the target. summarizeBy: sum.Total number of aircraft that departed on the mission. The top-line sortie count, before any aborts or losses.
summarizeBy: sum.Number of aircraft that actually reached and engaged the target (i.e., minus early returns and mechanical aborts).
summarizeBy: sum.Number of aircraft that released ordnance over the target. Generally equal to or less than
Attacking Aircraft. The most direct measure of ordnance delivery capacity. summarizeBy: sum.Count of aircraft that returned safely to base, stored as text. Null values are common where this data was not recorded.
summarizeBy: none.Count of aircraft that failed to complete the mission (mechanical failure, early return), stored as text.
summarizeBy: none.Count of aircraft that sustained damage during the mission, stored as text. Relevant for calibrating the intensity of enemy air defense at the target location.
summarizeBy: none.Count of aircraft that did not return (shot down, ditched, or missing in action), stored as text. Combined with target coordinates, this field helps identify areas of intense ground fire or fighter opposition — locations where aircraft wreckage may also be present.
summarizeBy: none.Ordnance Fields
These fields record what was dropped — the quantities, types, and weights of each ordnance category. Together they determine theweapon_type classification and the he_tons/frag_tons enrichment values.
Count of high-explosive bombs dropped, stored as text. The raw unit count before conversion to tonnage.
summarizeBy: none.THOR specification string for the HE bomb type (e.g.,
"500 LB GP (GP-M43/M64)"). Decode against 5_thor_wwii_weapon_gloss.csv for full ordnance descriptions. Key input for UXO risk assessment. summarizeBy: none.Total weight of HE ordnance dropped, in pounds, stored as text.
summarizeBy: none.Total weight of HE ordnance dropped, in tons. Integer representation of the tonnage.
summarizeBy: sum — this is a key aggregation field used in ordnance density calculations across the dashboard.Count of incendiary bombs dropped, stored as text.
summarizeBy: none.THOR specification string for the incendiary device type.
summarizeBy: none.Total weight of incendiary ordnance in pounds, stored as text.
summarizeBy: none.Total weight of incendiary ordnance in tons, stored as text in
adi_dataset_master (in contrast to adi_master_1943_1944 where this field is int64). summarizeBy: none.Count of fragmentation bombs dropped, stored as text.
summarizeBy: none.THOR specification string for the fragmentation bomb type.
summarizeBy: none.Total weight of fragmentation ordnance in pounds, stored as text.
summarizeBy: none.Total weight of fragmentation ordnance in tons.
summarizeBy: sum. Used alongside High Explosives Weight (Tons) to calculate the ordnance mix ratio for each mission.Sum of all ordnance dropped in pounds, stored as text.
summarizeBy: none.Sum of all ordnance dropped in tons. The primary tonnage aggregation field across all three ordnance categories (HE + incendiary + fragmentation).
summarizeBy: sum — the principal metric for bomb density mapping in the Power BI map visual.A.D.I. Enrichment Fields
These fields were added by A.D.I.’s Jupyter notebook pipeline and do not exist in the raw THOR source files. They are present only inadi_dataset_master, not in adi_master_1943_1944 or adi_master_1_5_junio.
A.D.I.-derived HE tonnage, normalized from the raw THOR weight fields. Provided as a clean integer aggregate to simplify DAX measures in Power BI.
summarizeBy: sum.A.D.I.-derived fragmentation ordnance tonnage, normalized from the raw THOR weight fields. Used alongside
he_tons to power the weapon_type classification logic. summarizeBy: sum.A.D.I.’s Spanish-language classification of each mission’s ordnance mix, derived by comparing
he_tons and frag_tons values. This field drives the ordnance category filter slicer in the “Día D” dashboard page. summarizeBy: none.Known classification values:| Value | Meaning |
|---|---|
Ataque Combinado (HE + Fragmentación) | Mission used both HE and fragmentation bombs |
Solo Explosivos | Mission used high-explosive bombs only |
Solo Fragmentación | Mission used fragmentation bombs only |
Supporting Mission Fields
These fields provide additional operational context and post-mission assessment data.The time at which the aircraft were over the target, stored as text. Recorded in THOR’s original format (e.g.,
"0630"). Useful for correlating with dawn/daylight bombing windows and AAA (anti-aircraft artillery) effectiveness studies. summarizeBy: none.Post-mission evaluation of damage inflicted, as recorded by THOR (e.g., photo reconnaissance results or crew reports). Coverage is sparse — many missions have null BDA entries. Where present, this field is the closest THOR comes to a ground-truth validation of bombardment effectiveness.
summarizeBy: none.Reference identifier linking back to the THOR source record. Used for provenance tracing —
summarizeBy: count in Power BI (i.e., used to count records rather than sum). Maps to the original THOR archive entry.The Power BI semantic model for this project uses Spanish locale (
es-ES, as defined in model.tmdl). All date hierarchy labels visible in the Power BI Desktop UI — year, quarter, month, day — appear in Spanish (e.g., “Año”, “Trimestre”, “Mes”, “Día”), and the date variation is labeled “Variación”. The underlying CSV column names, however, remain in English as documented in this schema reference.