Validated case study · Data Science

Humach Mobility: Trip Demand

Engineer temporal/weather features and reason about demand patterns without leaking future trip counts.

Download mini_mobility.csvUse Python, SQL, Excel or your preferred workflow unless a task specifies otherwise.
Project mode
Project dataset

Inspect the CSV before you answer the tasks

Scroll horizontally or vertically to examine the exact miniature data used by the validator.

Download CSV
record_idhourtemperature_crainweekdaytrips
10150149
21180246
32210343
43240440
54270537
65120635
76150033
87180132
98210232
109241325
1110270434
1211120537
1312150640
1413180043
1514210146
1615240249
1716270352
1817120455
1918150556
2019181649
2120210057
2221240156
2322270255
2423120352
250150449
261180546
272210643
283240040
294270137
305121227
316150333
327180432
338210532
349240633
3510270034
3611120137
3712150240
3813180343
3914210446
4015241541
4116270652
4217120055
4318150156
4419180257
4520210357
4621240456
4722270555
4823120652
48 rows6 columnsmini_mobility.csv
Project workspace

Analyse → validate → submit.

Numeric and decision tasks are auto-checked. Written reasoning is checked for completeness and key ideas, then included in your local submission report.

0/5 validated
01

How many hourly records are provided?

02

How many records have rain=1?

03

What is mean trip demand?

04

Which feature is legal for forecasting the next hour if known in advance?

05

Propose one cyclical time feature for hour-of-day.

Submit your project locally

HumachLearn stores no server-side data. Submission creates a portable JSON report containing your answers, validation state and timestamp.