Slot: Variable Name (variable_name)

Short machine-readable name for the variable, usually the name the upstream tool uses for it (e.g. tmax, tmmx, air.2m). Identity only — not necessarily the column header in the companion data file; that binding lives in DataLayout.value_column (see envar_layout).

Tier: core

Why this slot matters

This is the handle under which the upstream product knows the variable (Daymet tmax vs gridMET tmmx). Without it the record cannot be traced back to the source product's variable, and a rerun cannot request the same quantity from the tool.

In plain terms

Data tools give each measurement a short nickname, like tmax for maximum temperature. This is that nickname, written down exactly as the tool spells it, so you can go back to the source and find the same measurement again.

URI: envar:slot/variable_name

Applicable Classes

Name	Description	Modifies Slot
VariableIdentity	The identity and semantics of an environmental exposure variable — what physi...	yes

Properties

Type and Range

Property	Value
Range	String
Domain Of	VariableIdentity

Cardinality and Requirements

Property	Value

Examples

Value
tmax

Identifier and Mapping Information

Annotations

property	value
tier	core
justification	This is the handle under which the upstream product knows the variable (Daymet tmax vs gridMET tmmx). Without it the record cannot be traced back to the source product's variable, and a rerun cannot request the same quantity from the tool.
explanation	Data tools give each measurement a short nickname, like tmax for maximum temperature. This is that nickname, written down exactly as the tool spells it, so you can go back to the source and find the same measurement again.
covered_by	None

Schema Source

• from schema: https://w3id.org/linkml/microschemas/envar

Mappings

Mapping Type	Mapped Value
self	envar:variable_name
native	envar:variable_name

LinkML Source

name: variable_name
annotations:
  tier:
    tag: tier
    value: core
  justification:
    tag: justification
    value: This is the handle under which the upstream product knows the variable
      (Daymet `tmax` vs gridMET `tmmx`). Without it the record cannot be traced back
      to the source product's variable, and a rerun cannot request the same quantity
      from the tool.
  explanation:
    tag: explanation
    value: Data tools give each measurement a short nickname, like `tmax` for maximum
      temperature. This is that nickname, written down exactly as the tool spells
      it, so you can go back to the source and find the same measurement again.
  covered_by:
    tag: covered_by
    annotations:
      omop_gaia:
        tag: omop_gaia
        annotations:
          extent:
            tag: extent
            value: full
          status:
            tag: status
            value: verified
          where:
            tag: where
            value: gaia_db/variable_source.variable_name; DeGAUSS/Amadeus emit the
              short name only as a bare column header (tmax / tmmx)
          evidence:
            tag: evidence
            value: EnVar/examples/heat/COMPARISON.md §F (Variable short name — ✅ for
              GAIA)
          note:
            tag: note
            value: GAIA carries the variable short name first-class in variable_source.variable_name;
              the combined stack surfaces it as a named slot.
      degauss:
        tag: degauss
        annotations:
          extent:
            tag: extent
            value: partial
          status:
            tag: status
            value: asserted
          where:
            tag: where
            value: cohort_addresses_geocoded_daymet CSV column header `tmax`
          note:
            tag: note
            value: 'DeGAUSS carries the short name only as the value column header,
              not as a first-class named slot. Conservative: partial.'
      amadeus:
        tag: amadeus
        annotations:
          extent:
            tag: extent
            value: partial
          status:
            tag: status
            value: asserted
          where:
            tag: where
            value: gridmet_tmmx.csv column header `tmmx`; thredds_dataset.xml long_name/standard_name
              = tmmx
          note:
            tag: note
            value: 'Amadeus carries the short name as a column header and in the THREDDS
              long_name, not as a portable variable-name slot. Conservative: partial.'
      cher:
        tag: cher
        annotations:
          extent:
            tag: extent
            value: partial
          status:
            tag: status
            value: asserted
          where:
            tag: where
            value: table_column_dictionary.column_name (literal column name)
          note:
            tag: note
            value: 'C-HER records each resource''s literal column_name, which serves
              as the variable''s machine-readable handle; not a portable sidecar short-name.
              Conservative: partial.'
      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: A tool-specific short name is an instance-layer handle; the CODATA/I-ADOPT
              conceptual layer names the property canonically, not the upstream tool's
              nickname.
description: Short machine-readable name for the variable, usually the name the upstream
  tool uses for it (e.g. `tmax`, `tmmx`, `air.2m`). Identity only — not necessarily
  the column header in the companion data file; that binding lives in `DataLayout.value_column`
  (see envar_layout).
title: Variable Name
examples:
- value: tmax
  description: Daymet daily maximum air temperature variable
from_schema: https://w3id.org/linkml/microschemas/envar
rank: 1000
domain_of:
- VariableIdentity
range: string