Skip to content

Slot: Native Value Column (native_value_column)

Name of a second column carrying the same values in the source's native units (VariableIdentity.native_units_ucum), when the companion file ships both, e.g. Amadeus's value_kelvin next to value_celsius. value_column stays the binding for the values in units_ucum; this binds the native-unit twin.

Tier: optional

Why this slot matters

When a producer ships both unit representations, binding only one leaves an unexplained column in the data file and hides the cheapest available cross-check (recomputing one column from the other via unit_conversion_formula).

In plain terms

Some data files helpfully include the same measurement twice, in two units — like a column in Kelvin next to one in Celsius. This names that second column so it is accounted for rather than mysterious.

URI: envar:slot/native_value_column

Applicable Classes

Name Description Modifies Slot
DataLayout How the companion data file (CSV / parquet) is laid out and how this record's... no

Properties

Type and Range

Property Value
Range String
Domain Of DataLayout

Cardinality and Requirements

Property Value

Examples

Value
value_kelvin

Comments

  • Added after the reverse gap survey (docs/reverse-gap-survey.md, 2026-07): the Amadeus pipeline's native CSV carries value_kelvin and value_celsius twin columns, and DataLayout could bind exactly one of them — the native-unit copy had no home and its very existence went unrecorded. Rider on the native-unit conversion record in envar_variable (native_units_ucum, unit_conversion_formula).

Identifier and Mapping Information

Annotations

property value
tier optional
justification When a producer ships both unit representations, binding only one leaves an unexplained column in the data file and hides the cheapest available cross-check (recomputing one column from the other via unit_conversion_formula).
explanation Some data files helpfully include the same measurement twice, in two units — like a column in Kelvin next to one in Celsius. This names that second column so it is accounted for rather than mysterious.

Schema Source

Mappings

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

LinkML Source

name: native_value_column
annotations:
  tier:
    tag: tier
    value: optional
  justification:
    tag: justification
    value: When a producer ships both unit representations, binding only one leaves
      an unexplained column in the data file and hides the cheapest available cross-check
      (recomputing one column from the other via `unit_conversion_formula`).
  explanation:
    tag: explanation
    value: Some data files helpfully include the same measurement twice, in two units
      — like a column in Kelvin next to one in Celsius. This names that second column
      so it is accounted for rather than mysterious.
description: Name of a second column carrying the same values in the source's *native*
  units (`VariableIdentity.native_units_ucum`), when the companion file ships both,
  e.g. Amadeus's `value_kelvin` next to `value_celsius`. `value_column` stays the
  binding for the values in `units_ucum`; this binds the native-unit twin.
title: Native Value Column
comments:
- 'Added after the reverse gap survey (docs/reverse-gap-survey.md, 2026-07): the Amadeus
  pipeline''s native CSV carries `value_kelvin` and `value_celsius` twin columns,
  and `DataLayout` could bind exactly one of them — the native-unit copy had no home
  and its very existence went unrecorded. Rider on the native-unit conversion record
  in envar_variable (`native_units_ucum`, `unit_conversion_formula`).'
examples:
- value: value_kelvin
  description: Amadeus gridMET output ships Kelvin and Celsius side by side
from_schema: https://w3id.org/linkml/microschemas/envar
rank: 1000
domain_of:
- DataLayout
range: string