Slot: Equation Validity Range (equation_validity_range)
Validity-range conditions for the equation, serialised as a JSON string. For Heat Index: {"min_temperature_F": 80, "min_relative_humidity_pct": 40} — Rothfusz is undefined below 80 °F / 40 % RH.
Tier: conditionally_core
Why this slot matters
The Rothfusz Heat Index is undefined below ~80 °F / 40 % RH; applied outside its range an equation produces plausible-looking nonsense. Without the recorded range, no downstream consumer can flag values computed where the formula does not hold.
In plain terms
Every formula only works within a fence of weather conditions it was designed for. This field writes the fence down, so anyone can check whether a value was computed inside or outside it.
URI: envar:slot/equation_validity_range
Applicable Classes
| Name |
Description |
Modifies Slot |
| DerivedHeatMetric |
Methodology slots specific to derived heat metrics (WBGT, Heat Index, UTCI, a... |
yes |
Properties
Type and Range
Cardinality and Requirements
Examples
| Value |
| {"min_wind_speed_m_s": 0.13} |
See Also
Annotations
| property |
value |
| tier |
conditionally_core |
| justification |
The Rothfusz Heat Index is undefined below ~80 °F / 40 % RH; applied outside its range an equation produces plausible-looking nonsense. Without the recorded range, no downstream consumer can flag values computed where the formula does not hold. |
| explanation |
Every formula only works within a fence of weather conditions it was designed for. This field writes the fence down, so anyone can check whether a value was computed inside or outside it. |
Schema Source
Mappings
| Mapping Type |
Mapped Value |
| self |
envar:equation_validity_range |
| native |
envar:equation_validity_range |
LinkML Source
name: equation_validity_range
annotations:
tier:
tag: tier
value: conditionally_core
justification:
tag: justification
value: The Rothfusz Heat Index is undefined below ~80 °F / 40 % RH; applied outside
its range an equation produces plausible-looking nonsense. Without the recorded
range, no downstream consumer can flag values computed where the formula does
not hold.
explanation:
tag: explanation
value: Every formula only works within a fence of weather conditions it was designed
for. This field writes the fence down, so anyone can check whether a value was
computed inside or outside it.
description: 'Validity-range conditions for the equation, serialised as a JSON string.
For Heat Index: `{"min_temperature_F": 80, "min_relative_humidity_pct": 40}` — Rothfusz
is undefined below 80 °F / 40 % RH.'
title: Equation Validity Range
examples:
- value: '{"min_wind_speed_m_s": 0.13}'
description: Liljegren 2008 clamps wind speed below 0.13 m/s
from_schema: https://w3id.org/linkml/microschemas/envar
see_also:
- https://www.weather.gov/safety/heat-index
rank: 1000
domain_of:
- DerivedHeatMetric
range: string