Dev Patel
Data NOV 2023 → FEB 2024

Student Data Researcher

Five inconsistent disaster-response datasets turned into something a model could actually learn from.

Classification
Data
Client
Texas A&M University
Window
NOV 2023 → FEB 2024
Duration
3 MO
Location
College Station, TX
The brief

The brief

A disaster-management research group had data from five sources that disagreed with each other about almost everything: units, column names, date formats, what counted as a missing value.

I built the Python workflows that reconciled them, then the models on top. The interesting work was upstream — by the time the data was clean, the modelling was comparatively ordinary.

Scope of work

Scope of work

  • Architected and deployed Python workflows that automated cleansing and integration across 5+ multi-source datasets.
  • Improved predictive analysis for disaster-management strategy by 25% using ML models over Pandas, SciPy and SQL.
  • Refined reporting with complex SQL — CTEs and views — surfacing results through Power BI and Tableau for decision-makers.
Measured

Measured

5+source datasets
25%better prediction
2BI surfaces
Plan

Plan

Plan

5 items · scale 1:1
5+ SOURCEScsv · sql · api1CLEANSINGPython · Pandas2FEATURE STOREnormalised SQL3MODELSSciPy4REPORTINGPower BI · Tableau5
Note · Ingest, reconcile, model, report — the reconciliation stage is where the accuracy came from.
What I'd redraw

What I'd redraw

I validated the cleaned data by eye and by spot-check. With hindsight I'd have written the expectations down as tests — row counts, value ranges, join cardinality — so that a bad upstream refresh failed loudly instead of quietly shifting the model.

Materials

Materials

PythonPandasSciPySQLETLPower BITableau