Slot: Metric Temporal Aggregation Rule (metric_temporal_aggregation_rule)
For heat-wave flags, how multi-day exposures are stamped on individual days (e.g. first_day_of_event / each_day_of_event / last_day_of_event).
Tier: recommended
Why this slot matters
Stamping a five-day event only on its first day versus on every day changes which person-days count as exposed, directly altering effect estimates in daily time-series and case-crossover designs.
In plain terms
A heat wave spans several days but health records are kept day by day; this says which calendar days actually get the "heat wave" label — just the first day, every day, or the last.
URI: envar:slot/metric_temporal_aggregation_rule
Applicable Classes
| Name |
Description |
Modifies Slot |
| DerivedHeatMetric |
Methodology slots specific to derived heat metrics (WBGT, Heat Index, UTCI, a... |
no |
Properties
Type and Range
Cardinality and Requirements
Examples
Annotations
| property |
value |
| tier |
recommended |
| justification |
Stamping a five-day event only on its first day versus on every day changes which person-days count as exposed, directly altering effect estimates in daily time-series and case-crossover designs. |
| explanation |
A heat wave spans several days but health records are kept day by day; this says which calendar days actually get the "heat wave" label — just the first day, every day, or the last. |
| covered_by |
None |
Schema Source
Mappings
| Mapping Type |
Mapped Value |
| self |
envar:metric_temporal_aggregation_rule |
| native |
envar:metric_temporal_aggregation_rule |
LinkML Source
name: metric_temporal_aggregation_rule
annotations:
tier:
tag: tier
value: recommended
justification:
tag: justification
value: Stamping a five-day event only on its first day versus on every day changes
which person-days count as exposed, directly altering effect estimates in daily
time-series and case-crossover designs.
explanation:
tag: explanation
value: A heat wave spans several days but health records are kept day by day;
this says which calendar days actually get the "heat wave" label — just the
first day, every day, or the last.
covered_by:
tag: covered_by
annotations:
omop_gaia:
tag: omop_gaia
annotations:
extent:
tag: extent
value: absent
status:
tag: status
value: asserted
where:
tag: where
value: no column
note:
tag: note
value: Tmax scenario is per-day values, not a heat-wave flag; no multi-day
event-stamping rule.
degauss:
tag: degauss
annotations:
extent:
tag: extent
value: absent
status:
tag: status
value: asserted
where:
tag: where
value: no column
note:
tag: note
value: No multi-day heat-event flag, so no event-stamping rule.
amadeus:
tag: amadeus
annotations:
extent:
tag: extent
value: absent
status:
tag: status
value: asserted
where:
tag: where
value: no column
note:
tag: note
value: No multi-day heat-event flag, so no event-stamping rule.
cher:
tag: cher
annotations:
extent:
tag: extent
value: absent
status:
tag: status
value: asserted
where:
tag: where
value: no column
note:
tag: note
value: C-HER stamps no multi-day heat events onto days.
codata:
tag: codata
annotations:
extent:
tag: extent
value: out_of_layer
status:
tag: status
value: asserted
where:
tag: where
value: no column
note:
tag: note
value: Multi-day event stamping is instance-layer; out of scope for CODATA.
description: For heat-wave flags, how multi-day exposures are stamped on individual
days (e.g. `first_day_of_event` / `each_day_of_event` / `last_day_of_event`).
title: Metric Temporal Aggregation Rule
examples:
- value: each_day_of_event
from_schema: https://w3id.org/linkml/microschemas/envar
rank: 1000
domain_of:
- DerivedHeatMetric
range: string