Concept map: Temporal gaps and irregular timestamps
Prerequisites (two levels) and direct dependents of Temporal gaps and irregular timestamps. Show everything
- 3prerequisites shown
- 1direct dependents
- 2lessons use it
Insights 14
- Expect SUM over an empty or all-NULL group to return NULL, and handle it at the edge
- Densify dates before a ROWS-based rolling window, because "7 rows" is not "7 days" when days are missing
- Store instants in UTC and assign the business date with the local zone of where it happened
- Expect 23-hour and 25-hour days in hourly data around daylight-saving changes
- Check row volume per entity and period to find gaps that schema tests cannot see
- Use a coverage table and an anti-join to count what did not happen
- In SQLite, treat dates as text with a fixed format and never mix representations in one column
- Truncate timestamps in an explicit time zone, because date_trunc on a timestamptz uses the session zone
Projects 13
- Late deliveries and review scores in a marketplace: how much damage, and on which lanes?
- Where does a steel plant's electricity cost exposure concentrate? Load and power-factor profile
- Readmissions by admitting specialty: case-mix-adjusted comparison without chasing noise
- From session data to an experiment backlog: which conversion drivers deserve a test?
- Yield-failure screening from 590 sensor signals: feature selection without fooling yourself
- Client segments for a wholesale distributor: stable, actionable, and more than the channel label
List view151 concepts
Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 11
Day 12
Day 13
Day 14
Day 15
Day 16
Day 17
Day 18
Day 19
Day 21
Day 22
Day 23
Day 24
Day 25
Day 26
Day 27
Day 28
Day 29
Day 31
Day 32
Day 33
Day 34
Day 35
Day 36
Day 37
Day 38
Day 39
Day 40
Day 41
Day 42
Day 43
Day 44
Day 45
Day 46
Day 47
Day 48
Day 49
Day 51
Day 52
Day 53
Day 54
Day 55
Day 58
Day 59
Day 60