# Telemetry Data Mining at Scale

THE CHRISTMAS HEIST! · challenge 14 · hard

> Detective Quacker's jaw drops. "The low-income district? But the thefts were from the wealthy district! Something's not right here..." Tech Specialist Bailey boots up his holographic data parser with excitement. "Detective! I've been analyzing those thousands of package tracking events Agent Smith found. Each one stores detailed sensor data in the event_metadata JSON column. Inside that structure, there are nested fields: temperature readings, scan quality metrics, handling notes, and more! We need to parse this JSON at scale and find which volunteer loaded the most packages with temperature anomalies (above 10°C). Who was deliberately keeping these packages warm? Give me their name!"

## Task

Find who loaded the most packages with temperature above 10°C and return their name. You will be working with `dbquacks_xmas.package_tracking_events` (MotherDuck) and `volunteer_ducks` (local) tables.

## Tables

### `volunteer_ducks` (50 rows)

| column | type |
| --- | --- |
| duck_id | INTEGER |
| name | VARCHAR |
| specialty | VARCHAR |
| shift_start | TIME |
| shift_end | TIME |
| experience_level | INTEGER |
| background_check_date | DATE |
| home_district | VARCHAR |

### `dbquacks_xmas.package_tracking_events`

A table in a MotherDuck share; its columns are not listed here.

## Data

The tables live in a DuckDB database: https://dbquacks.com/data/databases/christmas_local.duckdb

To query it outside the browser, attach it read-only:

```sql
ATTACH 'https://dbquacks.com/data/databases/christmas_local.duckdb' AS db (READ_ONLY);
USE db;
```

This level also queries MotherDuck shares, which need a MotherDuck token. On the page, the editor asks for one.

Play it in the browser: https://dbquacks.com/challenges/christmas/14

## Answer

The expected answer is not published. Submit on the page to have it checked.